WCAG AA vs AAA: What's the Difference and Which Level Do You Actually Need?
WCAG 2.1 has three conformance levels: A, AA, and AAA. Level AA is the one referenced by laws, lawsuits, and contracts. But AAA adds another 28 success criteria — and understanding what they are (and aren't) is essential for anyone building accessible websites in 2026.
Legal Bottom Line
WCAG 2.1 Level AA is the legal standard. No major accessibility law requires AAA. Start with AA — selectively pursue AAA where it serves your users.
🔍 Check Your WCAG AA Compliance Free📋 Table of Contents
1. The Three WCAG Levels Explained
WCAG — the Web Content Accessibility Guidelines published by the W3C — organizes its success criteria into three conformance levels:
Level A
Minimum25 success criteria
The baseline. Level A addresses the most severe accessibility barriers — things that completely prevent access for users with disabilities. Failing Level A means parts of your site are entirely unusable for certain users.
Example criteria:
- •Images without alt text
- •Video with no text alternative
- •Non-keyboard-accessible controls
- •Content that flashes and could cause seizures
Level AA
Legal Standard13 additional criteria (38 total with Level A)
The practical standard. Level AA is what laws, regulations, and legal settlements reference. It removes significant barriers while remaining achievable for most websites without redesign.
Example criteria:
- •Captions for live video
- •Color contrast ratio of 4.5:1
- •Text resizable to 200% without loss of content
- •Multiple ways to navigate (search, sitemap, etc.)
- •Focus visible on all interactive elements
Level AAA
Enhanced28 additional criteria (66 total)
The enhanced standard. The W3C explicitly notes that AAA conformance is NOT recommended as a general policy for entire sites because it's not achievable for all content types. It's best applied selectively.
Example criteria:
- •Sign language for pre-recorded video
- •Color contrast ratio of 7:1
- •No timing requirements for any task
- •Sign language interpretation available
- •Pronunciation information for unusual words
Each level is cumulative: Level AA conformance means you satisfy all Level A and all Level AA criteria. Level AAA conformance means you satisfy all 66 criteria. However, WCAG explicitly permits partial AAA conformance — meaning you can implement specific AAA criteria without claiming full AAA conformance.
2. What WCAG Level AA Requires
Level AA adds 13 success criteria on top of the 25 Level A requirements. These are the criteria that separate "minimum" from "legally required" accessibility:
| Criterion | Requirement | Common Failure |
|---|---|---|
| 1.2.4 Captions (Live) | Live audio content in synchronized media has captions | Live webinars or streams without real-time captions |
| 1.2.5 Audio Description (Pre-recorded) | Audio description of pre-recorded video content | Video where visuals convey meaning not in the audio track |
| 1.3.4 Orientation | Content not restricted to one display orientation | Mobile forms that only work in portrait mode |
| 1.3.5 Identify Input Purpose | Form fields use autocomplete attributes | Login and payment forms missing autocomplete attributes |
| 1.4.3 Contrast (Minimum) | Text has at least 4.5:1 contrast ratio (3:1 for large text) | Gray text on white backgrounds; light text on colored buttons |
| 1.4.4 Resize Text | Text resizable to 200% without loss of content | Fixed-px font sizes that break layout at 200% zoom |
| 1.4.5 Images of Text | Avoid images of text except in logos | Screenshots of code or text used as content images |
| 1.4.10 Reflow | Content reflows at 320px wide without scrolling | Horizontal scrolling required on mobile viewports |
| 1.4.11 Non-text Contrast | UI components have 3:1 contrast ratio | Low-contrast button borders and form field outlines |
| 1.4.12 Text Spacing | No loss of content when text spacing is adjusted | Content overflow when line-height or letter-spacing modified |
| 1.4.13 Content on Hover or Focus | Hover/focus content is dismissible, hoverable, persistent | Tooltips that disappear before user can read them |
| 2.4.5 Multiple Ways | More than one way to locate pages (search, sitemap) | Single-navigation sites with no search or sitemap |
| 2.4.6 Headings and Labels | Headings and labels are descriptive | Generic headings like 'Section 1' or unlabeled form fields |
| 2.4.7 Focus Visible | Keyboard focus indicator is visible | Removed focus rings via CSS outline:none with no replacement |
| 3.1.2 Language of Parts | Language changes within content are marked | Inline foreign language phrases without lang attribute |
| 3.2.3 Consistent Navigation | Navigation repeated across pages is consistent | Navigation order changing between pages |
| 3.2.4 Consistent Identification | Components with same function identified consistently | Icon buttons labeled differently on different pages |
| 3.3.3 Error Suggestion | Error messages include suggestions for correction | Validation errors that say 'invalid' without guidance |
| 3.3.4 Error Prevention (Legal, Financial) | Submissions are reversible, checked, or confirmable | Irreversible financial transactions without confirmation |
📊 The Most Commonly Failed AA Criteria
WebAIM's Million report consistently finds that color contrast (1.4.3) and missing form labels cause the majority of WCAG AA failures on the web. These two criteria alone account for over 60% of all WCAG errors detected in automated testing.
🔍 Test Your Site's AA Conformance Free3. What WCAG Level AAA Adds
AAA adds 28 more success criteria. Some are practical extensions of AA requirements; others are specific to niche contexts. Here are the most significant:
Perceivable (More Media Accessibility)
Sign Language (Pre-recorded)
Sign language interpretation for all pre-recorded audio content. Requires a human sign language interpreter in the video.
Extended Audio Description (Pre-recorded)
Pausing video to provide additional audio descriptions when the natural pauses in audio are insufficient.
Media Alternative (Pre-recorded)
Full text alternative provided for all pre-recorded synchronized media.
Audio-only (Live)
Alternative for all live audio-only content.
Contrast (Enhanced)
Text contrast of 7:1 instead of AA's 4.5:1. Large text requires 4.5:1 instead of 3:1.
Low or No Background Audio
Speech audio doesn't have background sounds, or sounds are 20dB below speech.
Visual Presentation
Users can select foreground/background colors, line width max 80 characters, text not justified, 1.5x line spacing.
Images of Text (No Exception)
Images of text only used for decoration or where presentation is essential.
Operable (No Time Pressure, No Interruptions)
Keyboard (No Exception)
All functionality available via keyboard with no exceptions (AA's 2.1.1 has exceptions for path-dependent input).
No Timing
No time limits on tasks, except for real-time events or essential timing.
Interruptions
Interruptions can be postponed or suppressed by the user, except for emergencies.
Re-authenticating
When session expires, user can re-authenticate and continue without loss of data.
Timeouts
Users warned of timeouts that could cause data loss (WCAG 2.2 addition).
Three Flashes
No content flashes more than 3 times per second at all. AA allows content below thresholds.
Animation from Interactions
Motion animation triggered by interaction can be disabled (WCAG 2.2 addition).
Location
User's location within a set of web pages is indicated (breadcrumbs, site map highlighting).
Link Purpose (Link Only)
Link purpose determinable from link text alone (AA's 2.4.4 allows context).
Section Headings
Section headings used to organize content.
Target Size
Interactive targets are at least 44x44 CSS pixels.
Concurrent Input Mechanisms
Web content doesn't restrict use of input modalities.
Understandable (Clarity and Pronunciation)
Unusual Words
Mechanism to identify definitions of unusual words and jargon.
Abbreviations
Mechanism to identify expanded forms of abbreviations.
Reading Level
Content readable at lower secondary education level, or simplified version available.
Pronunciation
Mechanism to identify specific pronunciation of words where meaning is ambiguous without it.
Change on Request
Context changes only initiated by user request.
Help
Context-sensitive help is available.
Error Prevention (All)
Submission of any input can be checked, confirmed, or reversed.
4. Which Level Is Required by Law
The short answer: Level AA. Here's how this plays out across major legal frameworks:
ADA (US — Private Sector)
The ADA does not formally adopt WCAG. Courts and DOJ use WCAG 2.1 AA as the benchmark in enforcement and litigation. No AAA requirement.
Section 508 (US — Federal Government)
Section 508 explicitly references WCAG 2.0 Level AA for web content. The Revised 508 Standards (2017) are harmonized with WCAG 2.0 AA.
ADA Title II (State & Local Gov)
The DOJ's 2024 rule for Title II explicitly requires WCAG 2.1 Level AA for state and local government websites and mobile apps.
EN 301 549 (EU — EAA / Web Accessibility Directive)
The EU Web Accessibility Directive and European Accessibility Act reference EN 301 549, which maps to WCAG 2.1 Level AA.
AODA (Canada — Ontario)
WCAG 2.0 Level AA required for Ontario public sector (2014) and private sector with 50+ employees (2021).
WCAG AAA
No major accessibility law or regulation requires full WCAG AAA conformance. Selective AAA criteria may appear in some government contracts.
⚠️ The "Technical Conformance" vs "Legal Defense" Distinction
Passing automated WCAG AA checks is not the same as being "ADA compliant." Automated tools detect approximately 30–40% of WCAG failures. True conformance requires both automated testing and manual testing with assistive technology. Courts look at actual user experience, not just tool scores.
That said, documented WCAG AA conformance efforts — regular audits, accessibility statements, ongoing monitoring — significantly reduce lawsuit risk even if your site isn't perfect.
5. When You Should Target AAA
The W3C's own guidance is clear: "It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content."
But AAA isn't irrelevant. There are specific scenarios where targeting AAA (or specific AAA criteria) makes sense:
Deaf and Hard-of-Hearing Focused Services
SC 1.2.6 (Sign Language) — consider providing sign language interpretation if your primary audience includes Deaf users.
Online Testing or Timed Applications
SC 2.2.3 (No Timing) — removing time limits is AAA, but critical for users with cognitive disabilities completing assessments.
Government Services with High Disability User Base
SC 1.4.6 (Enhanced Contrast 7:1) — elderly and low-vision users benefit substantially from enhanced contrast in critical service portals.
Medical or Legal Information Sites
SC 3.1.3 (Unusual Words) + SC 3.1.5 (Reading Level) — jargon glossaries and simplified summaries are valuable in high-stakes content.
Disability-Focused Organizations
Full AAA conformance as a mission statement — accessibility agencies, disability advocacy organizations, and assistive technology vendors benefit from demonstrating full AAA conformance.
E-Commerce or Marketing Sites
Most AAA criteria (sign language video, no timing, reading level) are either not applicable or would require significant content restructuring with minimal user benefit.
6. Practical AAA: The Criteria Worth Implementing for Most Sites
Even if you don't pursue full AAA conformance, some AAA criteria are low-effort and high-impact for general audiences. These are worth implementing on most sites:
2.4.8 — Location (Breadcrumbs)
Adding breadcrumb navigation is straightforward on most platforms and significantly helps users who navigate deep content hierarchies. It also improves SEO.
2.4.10 — Section Headings
Using descriptive headings to organize content is good writing practice, good SEO, and good accessibility. There's almost no reason not to do this.
3.3.5 — Context-Sensitive Help
Adding inline help text next to complex form fields is low-effort and dramatically improves form completion rates for all users, including those with cognitive disabilities.
3.1.3 — Unusual Words (Glossary)
For technical or legal content, adding a glossary or inline definitions helps all users and is particularly valuable for non-native speakers and users with cognitive disabilities.
1.4.6 — Enhanced Contrast (7:1)
If your user base includes elderly users or people with low vision, bumping body text to 7:1 contrast is a meaningful improvement. More restrictive than AA's 4.5:1 but achievable with dark gray (#222) instead of black.
2.5.5 — Target Size (44×44px)
Making all interactive targets at least 44px improves usability for users with motor disabilities and generally makes sites more pleasant to use on touch devices. WCAG 2.2 added a modified version (SC 2.5.8) at AA level.
7. How to Test for AA and AAA Conformance
Testing for WCAG AA conformance requires both automated tools and manual testing:
Automated Testing (Detects ~30–40% of Issues)
- axe DevTools (Deque) — the most widely used WCAG testing engine; detects AA issues with minimal false positives
- WAVE (WebAIM) — visual overlay tool; excellent for identifying contrast and structural issues
- Lighthouse (Google Chrome DevTools) — built-in accessibility audit based on axe-core
- Siteimprove, Pope Tech, Monsido — enterprise platforms for scanning entire sites at scale
Manual Testing (Required for Full AA Conformance)
- Keyboard-only navigation — test every interactive element with Tab, Enter, Escape, and arrow keys
- Screen reader testing — NVDA + Firefox (Windows), VoiceOver + Safari (macOS/iOS), TalkBack (Android)
- 200% zoom test — verify reflow and no horizontal scrolling at 200% zoom
- Color blindness simulation — Chrome DevTools Rendering panel has built-in simulation modes
- Focus visibility check — tab through every interactive element and verify the focus indicator is visible
🔍 Start with a Free Automated AA Scan
Run RatedWithAI's free scanner to identify WCAG AA violations on your site. Get a prioritized report of the issues most likely to create legal exposure.
Sponsored
Also audit your site's full technical health
SEMrush Site Audit checks 130+ issues — missing alt text, broken links, slow pages. Free crawl up to 100 pages, no credit card required.
8. Frequently Asked Questions
Is WCAG AA or AAA legally required?
WCAG 2.1 Level AA is the legal standard referenced by the ADA, Section 508, the EU Web Accessibility Directive, and AODA (Canada). WCAG AAA is not required by any major accessibility law. The W3C itself doesn't recommend AAA as a general policy for entire websites.
What does WCAG AAA add that AA doesn't cover?
WCAG AAA adds 28 criteria including: sign language video interpretation, enhanced contrast ratio (7:1 vs 4.5:1), no timing requirements on any tasks, sign language for live audio, reading level requirements, pronunciation guidance, and extended audio descriptions. Many are specific to particular content types.
Can I be sued for not meeting WCAG AAA?
Almost certainly not for failing AAA alone. ADA lawsuits in the US benchmark against WCAG 2.1 AA. If your site meets AA, AAA non-conformance is not a legal liability. The exception would be specific government contracts or accessibility standards that explicitly require certain AAA criteria.
Should I implement any AAA criteria even if not required?
Yes, selectively. Breadcrumb navigation (2.4.8), section headings (2.4.10), context-sensitive help text (3.3.5), and enhanced contrast (1.4.6) are low-effort AAA criteria with broad user benefit. They improve UX for everyone, not just users with disabilities.
Does WCAG 2.2 change anything about AA vs AAA?
WCAG 2.2 (published October 2023) added new criteria and moved some previously AAA criteria into AA. Most notably, Focus Not Obscured (2.4.11) and Dragging Movements (2.5.7) are now AA requirements. This means WCAG 2.2 AA is slightly more demanding than WCAG 2.1 AA.
Is Your Site Meeting WCAG 2.1 Level AA?
Run a free scan to find WCAG AA violations before they become a lawsuit. Get a detailed report with specific fixes and priority rankings.