Skip to main content
Accessibility.com, LLC
Category: WCAG Principles and Conformance

Conformance Level AAA

Also known as: AAA, Level AAA, WCAG Level AAA, AAA conformance
Simply put

Conformance Level AAA is the highest of the three conformance levels defined in the Web Content Accessibility Guidelines (WCAG). To reach it, a web page must meet all the requirements at Levels A and AA plus the additional Level AAA requirements, or provide a conforming alternate version. Because some Level AAA requirements cannot be satisfied for all types of content, it is generally not recommended as a blanket policy for entire websites.

Formal definition

Level AAA is the strictest WCAG conformance level. Per the W3C's Understanding Conformance guidance, a page conforms at Level AAA when it satisfies all applicable Level A, Level AA, and Level AAA success criteria, or when a conforming alternate version that meets those criteria is provided. The W3C notes that Level AAA conformance is not recommended as a general policy for entire sites because it is not possible to satisfy all Level AAA success criteria for some content. AAA is defined consistently across WCAG 2.0, 2.1, and 2.2, though the specific success criteria available at each level differ by version. AA, not AAA, is the level most commonly cited as a target in policy and legal contexts. This entry describes the technical standard only and is not legal advice; applicable legal obligations depend on jurisdiction, regulation, and case law and should be confirmed with qualified counsel.

Why it matters

Conformance Level AAA represents the highest tier of accessibility support defined in WCAG, extending beyond the functional access provided at Levels A and AA toward more advanced accommodations. For organizations serving audiences with a broad range of disabilities, individual Level AAA success criteria can meaningfully improve the experience for users who rely on assistive technology or who benefit from enhanced readability, timing, and navigation support.

At the same time, AAA is generally not recommended as a blanket policy for entire websites. The W3C and other authorities note that it is not possible to satisfy all Level AAA success criteria for some types of content, which is why Level AA, not AAA, is the level most commonly cited as a target in policy and legal contexts. Treating AAA as a site-wide requirement can set an expectation that certain content simply cannot meet, regardless of effort.

Understanding where AAA fits helps teams make deliberate choices: they may adopt specific Level AAA criteria where they add clear value for their users, while targeting Level AA as the overall conformance goal. This entry describes the technical standard only and is not legal advice; applicable legal obligations depend on jurisdiction, regulation, and case law and should be confirmed with qualified counsel.

Who it's relevant to

Accessibility engineers and developers
Teams implementing accessibility features need to understand that AAA requires meeting all applicable A, AA, and AAA success criteria, and that AAA is defined consistently across WCAG 2.0, 2.1, and 2.2 while the specific criteria differ by version. They can apply selected Level AAA criteria where they add value for users rather than treating AAA as a universal target.
Compliance officers and policy owners
Those setting organizational accessibility policy should note that the W3C advises against requiring Level AAA as a general policy for entire sites, because some Level AAA success criteria cannot be satisfied for certain content. Level AA is the level more commonly cited as a target in policy contexts.
UX designers and content teams
Designers and content creators may find that specific Level AAA criteria improve readability, timing, and navigation for users who benefit from enhanced support, and can prioritize those criteria selectively for content where they are achievable.
Legal counsel and business leaders
Leaders evaluating accessibility goals should understand that AAA is the strictest WCAG level but is generally not recommended as a site-wide requirement. Legal obligations depend on jurisdiction, regulation, and case law and should be confirmed with qualified counsel rather than assumed from any conformance level.

Inside AAA

AAA Conformance Level
The highest of the three WCAG conformance levels (A, AA, and AAA). To claim AAA conformance, content must satisfy all applicable Level A, Level AA, and Level AAA success criteria.
Level AAA Success Criteria
A set of success criteria that go beyond Level A and AA requirements, addressing more stringent or specialized accessibility needs. Examples commonly associated with AAA include stricter color contrast thresholds, sign language interpretation for prerecorded audio, and extended user control over timing and reading level.
Relationship to Lower Levels
AAA is cumulative: it incorporates all Level A and Level AA criteria and adds further criteria on top. A page cannot conform at AAA without also meeting the lower levels for the applicable criteria.
Version Context (WCAG 2.0, 2.1, 2.2)
AAA exists as a defined conformance level across WCAG 2.0, 2.1, and 2.2, but the specific AAA success criteria differ between versions, as later versions added new criteria at various levels. The applicable criteria depend on which WCAG version is referenced.
W3C Guidance on AAA
The W3C notes that it is not recommended that 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.

Common questions

Answers to the questions practitioners most commonly ask about AAA.

Is Level AAA the conformance level organizations should target for full accessibility?
Not typically. Although Level AAA represents the highest tier of WCAG success criteria, the W3C itself notes that it is not recommended as a general policy target for entire sites or applications, because it is not possible to satisfy all AAA success criteria for some content. Level AA is the level most commonly cited as a practical target in policies, settlements, and agency guidance. Organizations may adopt individual AAA criteria where they are achievable and beneficial for their users, but treating full AAA conformance as the baseline goal generally is not realistic. This is general information and not legal advice.
Does meeting Level AAA guarantee legal compliance or immunity from accessibility claims?
No. Conformance to any WCAG level, including AAA, is a technical measure and does not by itself guarantee legal compliance or immunity from claims. The ADA is a civil rights law that does not codify a specific WCAG version in its statutory text, and courts and settlements have often referenced WCAG as a benchmark rather than treating it as an automatic safe harbor. Conformance also does not guarantee a usable experience for every user, since automated testing detects only a portion of issues and manual and assistive technology testing are needed. Consult qualified legal counsel and monitor current regulatory and case-law developments for your jurisdiction.
How should we decide which AAA success criteria to adopt?
A common approach is to identify AAA criteria that are achievable for your content type and that address the needs of your actual user base. Because some AAA criteria cannot be satisfied for all content, organizations often apply them selectively rather than across the board. Prioritizing criteria that meaningfully improve the experience for users of assistive technology, and documenting where AAA is applied, generally supports both usability and internal accountability. This is general guidance, not legal advice.
Can we mix Level AA and Level AAA in the same accessibility policy?
Yes. Many organizations set Level AA as the overall conformance target while committing to specific AAA criteria where feasible. WCAG's conformance model is cumulative, so meeting AAA for a given requirement also involves meeting the corresponding A and AA criteria within that same guideline area. Stating clearly which AAA criteria you commit to, and for which content, helps set accurate expectations and avoids overstating conformance.
How do we test for AAA conformance?
Testing for AAA generally combines the same methods used for other levels: automated checks, manual review, and testing with assistive technologies such as screen readers, magnification, and keyboard-only navigation. Automated tools detect only a portion of relevant issues, so manual and assistive technology testing are required to evaluate criteria that depend on context, meaning, or user experience. Documenting your testing methods and results for each applicable criterion supports a defensible conformance claim.
Do AAA success criteria differ between WCAG versions?
Yes. The set of success criteria, including those at Level AAA, evolved across WCAG 2.0, 2.1, and 2.2, with later versions adding criteria to address additional needs. Because a given criterion may exist in one version and not an earlier one, and because level assignments should be verified against the specific version, teams should confirm the exact version and criterion they are referencing before making a conformance claim rather than assuming criteria carry over unchanged.

Common misconceptions

AAA is the level organizations should target for legal compliance.
AA is the level most commonly cited as a target in settlements, regulations, and agency guidance. The W3C itself advises against requiring AAA as a blanket policy for entire sites, since not all AAA criteria can be met for all types of content. AAA conformance is generally pursued selectively rather than site-wide.
Achieving AAA conformance guarantees an accessible experience and immunity from legal claims.
Meeting WCAG success criteria at any level, including AAA, does not by itself guarantee usability for all users or immunity from legal claims. Automated testing detects only a portion of issues, so manual and assistive technology testing remain necessary. This is not legal advice; consult qualified counsel regarding compliance.
AAA simply means 'more of the same' checks as AA.
AAA introduces distinct, more stringent success criteria that address different or higher thresholds than AA. It is cumulative on top of A and AA, and the exact criteria vary by WCAG version (2.0, 2.1, 2.2).

Best practices

Treat AA as the general conformance target and apply AAA criteria selectively to specific content or user needs, rather than requiring AAA across an entire site.
Identify the specific WCAG version (2.0, 2.1, or 2.2) you are working against, since the AAA success criteria differ between versions.
When claiming AAA conformance for any content, confirm that all applicable Level A and Level AA criteria are also satisfied, since AAA is cumulative.
Combine automated testing with manual review and assistive technology testing, because automated tools detect only a portion of accessibility issues at any level.
Document which AAA criteria are met and where, and note content types where certain AAA criteria cannot reasonably be satisfied.
Consult qualified legal counsel and monitor current agency rulemaking and case law, as requirements evolve and conformance does not by itself establish legal compliance.