WCAG AA vs AAA 2026 | Which Conformance Level Should You Target?
Last updated: 2026-04-27
WCAG 2.2 defines three conformance levels: A, AA, and AAA. Level A is the bare minimum that most laws treat as below the legal floor, Level AA is the de facto standard for legal compliance worldwide, and Level AAA is an aspirational level intended for content where the highest possible accessibility is genuinely required, such as government emergency information or services aimed primarily at people with cognitive disabilities. The W3C explicitly states that AAA conformance is not required for general-purpose websites, and trying to meet every AAA criterion across an entire site is usually impractical or impossible. Yet AAA criteria contain useful guidance that many teams selectively adopt to improve readability, contrast, and timing for users with low vision, cognitive disabilities, or who use assistive technology in challenging environments. This comparison covers what AA and AAA actually require, where the differences hurt the most when you try to upgrade from one to the other, the legal context that almost always lands on AA, and a realistic strategy for borrowing from AAA without overcommitting your team. None of this is legal advice; consult a qualified attorney for your jurisdiction.
At a Glance
| Feature | WCAG 2.2 Level AA | WCAG 2.2 Level AAA |
|---|---|---|
| Color contrast (normal text) | 4.5:1 minimum (1.4.3) | 7:1 minimum (1.4.6) |
| Color contrast (large text) | 3:1 minimum | 4.5:1 minimum |
| Audio description for prerecorded video | Required (1.2.5) | Extended audio description required where pauses are needed (1.2.7) |
| Sign language for prerecorded video | Not required | Required (1.2.6) |
| Live captions | Required for live audio (1.2.4) | Required for all live media (covered by AA plus 1.2.9) |
| Reading level | Not required | Required where text exceeds lower secondary education level (3.1.5) |
| Pronunciation guidance | Not required | Required where meaning is ambiguous without it (3.1.6) |
| Timing | Adjustable timing required (2.2.1) | No timing limits except as essential to activity (2.2.3); interruptions can be postponed (2.2.4) |
| Help available on every page | Required only where help is provided (3.2.6) | Required across consistent flows in addition to AA |
| Legal adoption as primary standard | EAA, ADA case law, AODA, EN 301 549, Section 508 | Voluntarily adopted by some governments for emergency content; not the working standard for any major law |
WCAG 2.2 Level AA
Pros
- Adopted by virtually every modern accessibility law and government policy as the working standard, including the European Accessibility Act, the 2024 DOJ Title II rule, AODA, EN 301 549, and Section 508
- Achievable for most consumer websites and SaaS products without redesigning the visual brand or rewriting content from scratch
- Covers the highest-impact criteria for keyboard users, screen reader users, and people with low vision, including 4.5:1 text contrast, visible focus, descriptive link text, and consistent navigation
- Audit results, compliance documents, and accessibility statements written for AA are easily understood by procurement teams, regulators, and plaintiffs' lawyers
Cons
- Color contrast ratio of 4.5:1 for normal text is still hard to read for some users with low vision who would benefit from the higher AAA threshold
- Does not require sign language interpretation for prerecorded video, real-time captioning for live audio, or restrictions on flashing content beyond the basic three-flash rule
- Allows complex language as long as content is technically perceivable and operable, which still excludes some users with cognitive disabilities
- Reading level and timing requirements are minimal compared to AAA, leaving content that is hard to skim, hard to read, or that times out unexpectedly
WCAG 2.2 Level AAA
Pros
- Higher contrast ratio of 7:1 for normal text dramatically improves readability for users with low vision and improves performance in bright environments such as outdoors on a phone screen
- Stronger requirements around timing, motion, and interruptions reduce barriers for users with cognitive disabilities, attention disorders, and motor impairments
- Sign language and extended audio description criteria meaningfully improve access for Deaf users and people with cognitive disabilities consuming video content
- Reading level guidance (3.1.5 Reading Level) prompts teams to write at a lower secondary education level, which improves comprehension for native speakers, non-native speakers, and people with cognitive disabilities alike
Cons
- Some criteria are explicitly noted by the W3C as not applicable to all content types - for example, sign language interpretation is not feasible for every video on every site
- AAA color contrast often requires redesigning brand palettes, which is a hard organizational ask when the brand is owned by marketing rather than engineering
- Reading level criterion (3.1.5) is not currently enforceable in any major jurisdiction and is impractical for technical or domain-specific content that genuinely requires advanced vocabulary
- No major law requires full AAA conformance; pursuing it in isolation can divert resources from broader AA fixes that benefit more users overall
Our Verdict
For almost every organization, the right target is full WCAG 2.2 Level AA across the entire site or application, with selected AAA criteria adopted where they make a meaningful difference. The most common AAA enhancements worth borrowing are 7:1 contrast on key reading surfaces, plain-language summaries on policy pages, captions and transcripts on every video rather than only live audio, and avoiding session timeouts where possible. Trying to claim full AAA across a site usually creates more risk than it removes, because a single non-conformant page invalidates the AAA claim and gives plaintiffs a paper trail to argue the organization promised more than it delivered. Be specific in your accessibility statement: state that the site targets WCAG 2.2 Level AA, list the AAA criteria you have committed to where applicable, and describe the parts of the site (such as embedded third-party widgets or legacy PDFs) where conformance is not yet met. None of this is legal advice; talk to an accessibility-experienced attorney before publishing any compliance claim.
Further Reading
Other Comparisons
Get our free accessibility toolkit
We're building a simple accessibility checker for non-developers. Join the waitlist for early access and a free EAA compliance checklist.
No spam. Unsubscribe anytime.