WCAG 2.2 Level AAA Compliance Checklist: Going Beyond Minimum Standards

Most accessibility laws reference WCAG Level AA. That means 4.5:1 contrast ratios, keyboard navigation, alt text on images, and form labels. It is the floor. Level AAA is the ceiling — and the gap between them is significant. AAA requires 7:1 contrast for normal text, sign language interpretation for prerecorded video, no time limits whatsoever, reading level adjustments, and pronunciation guides for ambiguous words. No major regulation mandates full AAA conformance across an entire site, and the W3C itself acknowledges that AAA is not achievable for all content types. But that does not make it irrelevant. Individual AAA criteria can be adopted selectively to dramatically improve the experience for users with cognitive, visual, and auditory disabilities who find AA compliance insufficient.

AAA vs AA: What Actually Changes

The difference between AA and AAA is not just stricter numbers. AAA introduces entirely new requirements that AA does not address at all. Here is the complete comparison across the four WCAG principles:

Several AAA criteria address user populations that AA effectively ignores: people with cognitive disabilities, users who rely on sign language rather than written text, and people with combined disabilities who need multiple accommodations simultaneously.

The Complete WCAG 2.2 AAA Checklist

Below is every WCAG 2.2 success criterion at Level AAA, organized by principle. Each criterion includes its number, a plain-language explanation, and an implementation difficulty rating.

Perceivable (Principle 1)

1.2.6 Sign Language (Prerecorded) — Provide sign language interpretation for all prerecorded audio content in synchronized media. Implementation: high difficulty. Requires professional sign language interpreters and video production for each piece of media content.

1.2.7 Extended Audio Description (Prerecorded) — Where pauses in foreground audio are insufficient for audio description, provide extended audio description that pauses the video to insert descriptions. Implementation: high difficulty. Requires re-editing video content.

1.2.8 Media Alternative (Prerecorded) — Provide a full text alternative for all prerecorded synchronized media and video-only content. Implementation: moderate. Essentially a detailed transcript that describes both audio and visual elements.

1.2.9 Audio-only (Live) — Provide a text alternative for live audio-only content. Implementation: moderate to high. Real-time captioning services like CART or automated speech-to-text with human correction.

1.4.6 Contrast (Enhanced) — Text has a contrast ratio of at least 7:1 for normal text and 4.5:1 for large text. Implementation: low to moderate. Often requires only CSS color value changes. Our color contrast checker tests against both AA and AAA thresholds.

1.4.7 Low or No Background Audio — For prerecorded audio with speech, background sounds are at least 20 dB lower than the foreground speech, or there is a mechanism to turn off background audio. Implementation: moderate. Applies to podcasts, videos, and audio guides.

1.4.8 Visual Presentation — Users can select foreground and background colors, line spacing of at least 1.5, paragraph spacing of at least 1.5x line spacing, text not justified, and line width under 80 characters. Implementation: moderate. Requires a text customization panel or adherence to all defaults.

1.4.9 Images of Text (No Exception) — Images of text are only used for pure decoration or where a particular visual presentation is essential (like a logo). Implementation: low. AA already restricts images of text; AAA removes the customizable exception.

Operable (Principle 2)

2.1.3 Keyboard (No Exception) — All functionality is operable through a keyboard interface with no exceptions. AA allows exceptions for path-dependent input; AAA does not. Implementation: moderate to high for applications with drawing, mapping, or gesture-based features.

2.2.3 No Timing — Timing is not an essential part of the event or activity presented, except for real-time events and non-interactive synchronized media. Implementation: low for most websites (remove session timeouts, quiz timers). High for timed assessments or auction sites.

2.2.4 Interruptions — Interruptions can be postponed or suppressed by the user, except for emergency interruptions. Implementation: moderate. Affects pop-ups, notifications, auto-updating content, chat widgets, and newsletter modals.

2.2.5 Re-authenticating — When an authenticated session expires, the user can continue the activity without data loss after re-authenticating. Implementation: moderate. Requires server-side session state preservation — save form data before timeout.

2.2.6 Timeouts — Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours. Implementation: low. A notification before session timeout satisfies this.

2.3.2 Three Flashes — Pages do not contain anything that flashes more than three times in any one second period. AA limits this to content below certain size thresholds; AAA removes the size exception entirely. Implementation: low for most sites. Affects video content and animations.

2.3.3 Animation from Interactions — Motion animation triggered by interaction can be disabled, unless the animation is essential. Implementation: low. Respect prefers-reduced-motion media query in CSS. This is a WCAG 2.1 addition that many developers already implement.

2.4.8 Location — Provide information about the user's location within a set of pages (breadcrumbs). Implementation: low. Standard breadcrumb navigation satisfies this criterion.

2.4.9 Link Purpose (Link Only) — The purpose of each link can be determined from the link text alone. No "click here" or "read more" links without additional context. AA allows the surrounding sentence to provide context; AAA requires the link text itself to be self-sufficient. Implementation: moderate. Requires reviewing every link on your site.

2.4.10 Section Headings — Section headings are used to organize content. Implementation: low. Proper heading hierarchy (H1 > H2 > H3) that most accessibility-aware sites already have.

Understandable (Principle 3)

3.1.3 Unusual Words — A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. Implementation: moderate. Glossary links, tooltip definitions, or a dedicated glossary page.

3.1.4 Abbreviations — A mechanism for identifying the expanded form or meaning of abbreviations is available. Implementation: low. Use the HTML <abbr> element with title attribute, or spell out abbreviations on first use.

3.1.5 Reading Level — Content is written at a lower secondary education reading level (roughly grade 7-9), or a simplified version is available. Implementation: high for technical content. Requires either simplifying primary content or maintaining a parallel simplified version.

3.1.6 Pronunciation — A mechanism is available for identifying the pronunciation of words where meaning is ambiguous without pronunciation. Implementation: moderate. Relevant for words like "read" (present vs past tense) or proper nouns. Ruby annotations or pronunciation guides.

3.2.5 Change on Request — Changes of context are initiated only by user request, or a mechanism to turn off such changes is available. Implementation: moderate. Affects auto-redirects, auto-submitting forms, and content that changes without user action.

3.3.5 Help — Context-sensitive help is available. Implementation: moderate. Inline help text, tooltips, or links to help documentation for form fields and interactive elements.

3.3.6 Error Prevention (All) — For all pages that require user data submission: submissions are reversible, data is checked for errors and the user is given an opportunity to correct them, or a mechanism is available for reviewing and confirming before final submission. AA limits this to legal/financial transactions; AAA extends it to all submissions. Implementation: moderate. Add confirmation steps or undo functionality to all forms.

Robust (Principle 4)

WCAG 2.2 Level AAA does not introduce additional Robust criteria beyond what Level AA already requires. The Robust principle at AA already covers parsing (4.1.1, now deprecated in 2.2), name/role/value for UI components (4.1.2), and status messages (4.1.3). If your site meets AA Robust criteria, it meets AAA Robust criteria.

That said, AAA-level commitment to Robust means going beyond minimum conformance:

• Test with multiple assistive technologies, not just one screen reader
• Validate ARIA usage with tools like the Web Accessibility Checker — incorrect ARIA is worse than no ARIA
• Test with voice control software (Dragon NaturallySpeaking, Voice Control on macOS)
• Ensure custom widgets work with switch access devices

Which AAA Criteria to Implement First

Full AAA conformance is unrealistic for most sites. But selective AAA adoption delivers outsized returns. Here is a prioritized implementation order based on user impact per effort:

Tier 1: Low effort, high impact (do now)

• 1.4.6 Enhanced contrast (7:1) — change a few CSS values. Benefits every user with less-than-perfect vision. Test with our contrast checker.
• 2.4.8 Breadcrumbs — standard navigation pattern. Helps everyone orient themselves.
• 2.4.10 Section headings — you probably already have these if you follow WCAG 2.2 AA requirements.
• 2.3.3 Respect prefers-reduced-motion — a few lines of CSS. Critical for vestibular disorders.
• 3.1.4 Abbreviation expansion — add <abbr> tags. Five minutes per page.

Tier 2: Moderate effort, high impact (next quarter)

• 2.2.4 Suppressible interruptions — let users dismiss pop-ups and suppress notifications. Benefits everyone, especially users with attention disabilities.
• 2.2.5 Re-authentication without data loss — save form state server-side. Prevents frustration for all users.
• 2.4.9 Self-sufficient link text — audit and rewrite generic links. Improves navigation for screen reader users and benefits SEO.
• 1.4.8 Visual presentation controls — provide a text customization panel (line spacing, width, colors). Major win for dyslexic users.
• 3.3.6 Error prevention for all forms — add confirmation steps. Reduces errors for everyone.

Tier 3: High effort, targeted impact (long-term)

• 1.2.6 Sign language — requires video production budget. Essential for Deaf users who prefer sign language.
• 3.1.5 Reading level — requires content rewriting or dual versions. Benefits cognitive disabilities and non-native speakers.
• 1.2.7 Extended audio description — requires video re-editing. Benefits blind users consuming complex visual content.

Testing AAA Conformance

Automated tools catch some AAA criteria but miss most of them. Here is what can and cannot be automated:

For automated testing, run your site through the Web Accessibility Checker — it flags AAA contrast failures and several structural AAA criteria. For manual testing, WCAG 2.2 AAA requires real users. Recruit testers who use screen readers, sign language, and voice control daily. Their feedback reveals issues no tool can detect.

If you are coming from AA compliance, the accessibility audit checklist provides a structured framework that extends to AAA criteria.

The Business Case for Exceeding AA

AAA is not legally required. So why invest? Three reasons that hold up in boardroom discussions:

1. Market differentiation. When every competitor hits AA — the legal minimum — AAA features become a competitive advantage. Government procurement in several EU countries (notably Germany under the BFSG and France under RGAA) increasingly scores accessibility beyond minimum compliance. An agency that demonstrates AAA features in its proposal wins points over AA-only competitors. More on this in our European Accessibility Act guide.

2. Larger addressable audience. AA serves users with moderate disabilities. AAA additionally serves users with severe visual impairments (7:1 contrast), cognitive disabilities (reading level, no timing, suppressible interruptions), and Deaf users who rely on sign language rather than text. The WHO estimates 1.3 billion people live with significant disability. AAA features reach portions of that population that AA does not.

3. Reduced support burden. Many AAA criteria — suppressible interruptions, re-authentication without data loss, self-sufficient link text, error prevention on all forms — reduce support tickets for all users. These are not just accessibility features; they are usability features that happen to be defined in WCAG.

Common Misconceptions About AAA

Several myths prevent teams from adopting any AAA criteria:

"AAA means ugly design." Enhanced contrast (7:1) does not mean black and white only. A dark navy (#1B2A4A) on white achieves 12.5:1. A dark forest green (#1B4332) on white achieves 11.2:1. Brand colors work at AAA with minor adjustments.

"AAA is all or nothing." There is no regulatory or reputational penalty for claiming partial AAA conformance. You can state "This site conforms to WCAG 2.2 Level AA, with the following Level AAA criteria also met: 1.4.6, 2.4.8, 2.4.9, 2.4.10, 3.1.4." This is transparent and credible. The accessibility statement template on our site includes a section for declaring AAA criteria met beyond AA conformance.

"Our users don't need it." You do not know the full disability profile of your audience. Analytics does not capture whether a user is Deaf, has dyslexia, or uses a screen reader. Accessibility is not about known user demographics — it is about ensuring the unknown users are not silently excluded.