Skip to content

Accessibility

WCAG conformance levels: A, AA and AAA

What WCAG levels A, AA and AAA require: criteria counts per version, the 24 that AA adds, why AAA is rarely required, and the level the main laws ask for.

Your UX Agent teamProduct
14 min read

WCAG has three conformance levels: A, AA and AAA. They are cumulative. In WCAG 2.2, a page meets Level A when it satisfies all 31 Level A success criteria, Level AA when it satisfies those and the 24 at Level AA, 55 in all, and Level AAA when it satisfies all 86. There is nothing in between. A page that meets every A criterion and all but one AA criterion can conform at Level A at most, not AA, unless a conforming alternate version meets AA.

Level AA is the level most rules ask for. The European standard EN 301 549, the UK’s public-sector regulations and the US rules for state and local government websites and federal agencies all take in WCAG’s Level A and AA criteria, each in its own WCAG version. Level AAA is rarely required of a whole site, and WCAG itself advises against making it the rule.

How many criteria each level takes

VersionLevel ALevel AALevel AAA
WCAG 2.0253861
WCAG 2.1305078
WCAG 2.2315586
Success criteria a page has to satisfy to conform at each level. The counts are cumulative: Level AA includes every Level A criterion. WCAG 2.2’s counts leave out 4.1.1 Parsing, which it removed.

Per level, WCAG 2.2 has 31 criteria at A, 24 at AA and 31 at AAA; WCAG 2.1 has 30, 20 and 28; WCAG 2.0 has 25, 13 and 23. To test a page against the 55, work through our WCAG 2.2 checklist, with a failing and a fixed example for each A and AA criterion.

WCAG 2.2 removed one criterion, 4.1.1 Parsing, as obsolete, and says that authors required by policy to conform with WCAG 2.0 or 2.1 “may need to continue to test and report 4.1.1”. So WCAG 2.2 Level AA covers 49 of WCAG 2.1’s 50 A and AA criteria, plus six new ones.

A level is not a severity

It is tempting to read Level A as “most important” and AAA as “nice to have”. W3C’s Understanding Conformance says WCAG 2 “does not suggest any particular level of priority or severity. Every criterion is important to one or more user groups.” How serious a failure is depends on how often it occurs and on what fails.

A level records how widely a criterion can be required: whether assistive technology can work around a failure, whether all content can meet it, whether it limits design. We list those factors in our introduction to how WCAG is built. So fix in order of harm, not of level: an AA contrast failure on a checkout button can stop more people than an A failure on a footer link. And which level to aim for is, in W3C’s words, “fundamentally a policy decision”, made by a law, a contract or you.

What Level AA adds to Level A

The gap between A and AA is 24 criteria in WCAG 2.2. Thirteen date from WCAG 2.0, seven were added in 2.1 and four in 2.2. Each is given here in plain words; the criterion’s own text carries the exceptions.

Video and audio

Layout, text and colour

  • 1.3.4 Orientation: the page works in portrait and landscape, unless one orientation is essential.
  • 1.4.3 Contrast (Minimum): text has a contrast ratio of at least 4.5:1, or 3:1 if it is large.
  • 1.4.4 Resize Text: text can be resized to 200 percent without losing content or functions.
  • 1.4.5 Images of Text: text is real text, not a picture of it, unless the presentation is essential, as in a logo, or can be customised.
  • 1.4.10 Reflow: content fits a width of 320 CSS pixels without scrolling sideways, except parts that need two dimensions, such as maps and data tables.
  • 1.4.11 Non-text Contrast: what identifies a control and its state, and the parts of a graphic needed to understand it, have at least 3:1 against the colours next to them.
  • 1.4.12 Text Spacing: nothing is lost when a reader increases line, paragraph, letter and word spacing to the values the criterion sets.
  • 1.4.13 Content on Hover or Focus: tooltips and similar pop-ups can be dismissed without moving the pointer or focus, can be hovered, and stay until the reader moves away or dismisses them.

Forms, errors and sign-in

  • 1.3.5 Identify Input Purpose: fields asking for the user’s own details, such as email or postcode, say so in code, usually with autocomplete.
  • 3.3.3 Error Suggestion: when a form detects an error and knows the fix, it suggests it, unless that would undermine security or purpose.
  • 3.3.4 Error Prevention (Legal, Financial, Data): a submission that makes a legal commitment or a payment, changes stored data or submits test answers can be reversed, is checked with a chance to correct, or can be reviewed and confirmed first.
  • 3.3.8 Accessible Authentication (Minimum): no sign-in step depends on remembering, transcribing or solving something, unless it offers another method or help, such as a password manager filling the field, or only asks you to recognise objects or content you provided.

Keyboard, focus and pointer

  • 2.4.7 Focus Visible: keyboard users can see where focus is.
  • 2.4.11 Focus Not Obscured (Minimum): a focused control is never completely hidden by the page’s own content, such as a sticky header or a cookie banner.
  • 2.5.7 Dragging Movements: anything done by dragging can also be done with a single pointer and no dragging, such as clicks or taps, unless dragging is essential.
  • 2.5.8 Target Size (Minimum): targets are at least 24 by 24 CSS pixels or spaced far enough from other targets, with exceptions such as links in a sentence.

Navigation and consistency

Language and status messages

  • 3.1.2 Language of Parts: a passage in another language is marked with its language, except names, technical terms and borrowed words.
  • 4.1.3 Status Messages: messages such as “Added to basket” reach screen reader users without moving focus, through a role such as status.

Some of these can be measured from a rendered page: a contrast ratio, a target’s size, sideways scrolling at 320 CSS pixels, a missing autocomplete. Others are judgements: whether a heading describes its topic, whether captions match the speech, whether two buttons do the same job. Plan for manual review of much of the AA list.

Level AAA: why it is rarely required

WCAG’s conformance section says, in a note: “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.”

Some AAA criteria ask for material made for every item of a kind, such as sign language interpretation for all prerecorded audio in synchronized media (1.2.6). Others depend on the content itself: 3.1.5 Reading Level asks for supplemental content or a simpler version wherever text needs reading ability beyond lower secondary education. A whole-site AAA rule would apply all 31 to every page.

That is no reason to ignore AAA. WCAG encourages authors to report “any progress toward meeting success criteria from all levels beyond the achieved level of conformance”.

AAA criteria close to what AA already asks

Several AAA criteria ask for the same thing as an A or AA criterion, with fewer exceptions or in more places:

  • 2.4.12 Focus Not Obscured (Enhanced). No part of a focused control is hidden by the page’s own content; 2.4.11 only asks that it is not entirely hidden.
  • 3.3.6 Error Prevention (All). The same options as 3.3.4 (reversible, checked or confirmed) for every page that asks the user to submit information.
  • 2.4.9 Link Purpose (Link Only). A link’s purpose can be identified from its text alone; 2.4.4 at Level A also accepts its programmatically determined context, such as the sentence or list item it sits in.
  • 2.3.2 Three Flashes. Nothing flashes more than three times in any one second. 2.3.1 at Level A also allows flashes below the flash thresholds; this one does not. A page with nothing that flashes meets it.
  • 1.4.6 Contrast (Enhanced). 7:1 for text and 4.5:1 for large text, set in your colour palette; see how the 4.5:1 and 7:1 ratios are worked out.

The five conformance requirements

Meeting the criteria is the first of five requirements in section 5.2 of WCAG 2.2. A page conforms only when it meets all five.

  1. Conformance level. One level is met in full, by the page or through a conforming alternate version (below).
  2. Full pages. Conformance “cannot be achieved if part of a web page is excluded”. Every layout a responsive page shows at different screen sizes must conform too.
  3. Complete processes. If one page of a process fails, no page in it conforms. WCAG’s example is an online store, from selecting products to the checkout.
  4. Only accessibility-supported ways of using technologies. A criterion can only be met in a way that works with users’ assistive technologies and browsers’ accessibility features. Anything provided otherwise must also be available in a way that does.
  5. Non-interference. Content that is not accessibility supported, or does not conform, must not block the rest of the page. Four criteria apply to all content for this reason: 1.4.2 Audio Control, 2.1.2 No Keyboard Trap, 2.2.2 Pause, Stop, Hide and 2.3.1 Three Flashes or Below Threshold. An embedded player that traps the keyboard stops the whole page from conforming.

The conforming alternate version

A page that misses a level can still conform through a separate version that meets it. The alternate must conform at the level, give all the same information and functionality in the same human language, and be as up to date. And the conforming version must be reachable from the non-conforming page through an accessibility-supported mechanism, or the non-conforming page reachable only from the conforming version or from a conforming page that also links to it. A separate “accessible version” that lags behind the main site does not qualify.

Conformance claims and partial conformance

WCAG 2.2 says: “Conformance claims are not required. Authors can conform to WCAG 2.2 without making a claim.” A claim you do make must include its date; the guidelines’ title, version and address, “Web Content Accessibility Guidelines 2.2 at https://www.w3.org/TR/WCAG22/”; the level; a concise description of the pages covered, including whether subdomains are; and the web content technologies relied upon. A conformance logo counts as a claim. A claim is also not the accessibility statement a law may require; the law sets that document’s content.

Statements of partial conformance

  • Third-party content (5.4). For pages that later get content you do not control, such as comments or inserted advertisements: if you monitor them and repair or remove non-conforming content within two business days, you can claim conformance on best knowledge. Otherwise you can state: “This page does not conform, but would conform to WCAG 2.2 at level X if the following parts from uncontrolled sources were removed.” Those parts must be outside your control and described so users can identify them.
  • Language (5.5). “This page does not conform, but would conform to WCAG 2.2 at level X if accessibility support existed for the following language(s):”

Neither is a lower level: each says the page does not conform, and why.

Which level the law asks for

WCAG defines conformance; a law or a contract decides whether you need it, in which version and with which exceptions:

  • EU public sector. The Web Accessibility Directive, through national law. EN 301 549 V3.2.1, cited under it, has web requirements that take in WCAG 2.1’s Level A and AA criteria.
  • EU, the European Accessibility Act. The Act names no WCAG version. A harmonised standard gives a presumption of conformity only once it is cited under the Act, and none is cited yet (as of November 2026). EN 301 549 V4.1.1, published in September 2026, takes in WCAG 2.2’s Level A and AA criteria for web pages and awaits citation.
  • UK public sector. The regulations presume a public sector website or app meets the legal accessibility requirement to the extent that it conforms to WCAG’s Level A and AA success criteria, “as amended from time to time”. GOV.UK’s guidance names WCAG 2.2 AA.
  • US state and local governments. Under Title II of the Americans with Disabilities Act, the Justice Department’s 2024 rule makes WCAG 2.1 Level AA the technical standard for their web content and mobile apps.
  • US federal agencies and their suppliers. The Section 508 standards require public-facing electronic content, and non-public-facing content in nine kinds of official communication, among them notices, decisions, forms and intranet pages, to meet the WCAG 2.0 Level A and AA success criteria, together with the requirements WCAG 2.0 sets for meeting them, such as full pages and complete processes.
  • US businesses open to the public. Title III of the Americans with Disabilities Act names no technical standard in a regulation; the Justice Department’s guidance points to WCAG and the Section 508 standards, which take in the WCAG 2.0 criteria.
  • Ontario. The web rule requires most organisations it covers to meet WCAG 2.0 Level AA except 1.2.4 and 1.2.5; the Government of Ontario and the Legislative Assembly must meet full Level AA.

Where a rule names WCAG 2.0 or 2.1, you may still need to test and report 4.1.1 Parsing. W3C has since added a note to both versions, for WCAG 2.0 as an erratum, that it should be considered always satisfied for any content using HTML or XML. A rule that incorporates an edition from before that note, such as EN 301 549 V3.2.1, still lists it without the note. None of these asks for AAA across a site, and each law sets its own scope, dates, exceptions and documents, so check the one that applies to you. We compare who the EU, US and Ontario rules cover and how they are enforced.

Frequently asked questions

What are the levels of accessibility in WCAG?

WCAG has three conformance levels: A, AA and AAA. In WCAG 2.2, 31 success criteria are at Level A, 24 at Level AA and 31 at Level AAA, 86 in all. The levels are cumulative, so each one includes the criteria of the levels below it.

What is WCAG level AA?

Level AA is the middle conformance level. A page meets it when it satisfies every Level A and Level AA success criterion, 55 in WCAG 2.2, or has a conforming alternate version that does, and meets WCAG’s other conformance requirements, such as full pages and complete processes. Most laws and standards that name WCAG ask for it.

Does Level AA include Level A?

Yes. A page cannot meet Level AA without meeting every Level A criterion. A page that meets all the AA criteria but misses one at Level A conforms at no level, unless it has a conforming alternate version.

Is WCAG Level AAA required?

Rarely for a whole site. WCAG itself does not recommend requiring Level AAA conformance as a general policy for entire sites, because some content cannot meet every AAA criterion. None of the laws and standards in this post asks for AAA; those that name a level ask for A and AA, or slightly less. Meeting single AAA criteria where you can is still worthwhile.

Can a site be partly AA?

Some pages of a site can conform at Level AA while others do not, because conformance is decided page by page, and a claim must say which pages it covers. A single page cannot be partly AA. For content you do not control, WCAG allows a statement of partial conformance, which says the page does not conform and which parts stop it.