WCAG 2.0 vs 2.1 vs 2.2: which version and level actually binds you

Which WCAG version and level do you actually have to meet?#

You do not pick one. The version and the level arrive attached to an instrument. Therefore the work is finding which instrument reaches you.

WCAG, the Web Content Accessibility Guidelines, is published by the W3C. WCAG 2.2 is a W3C Recommendation. The W3C published it on 05 October 2023 and revised it on 12 December 2024, with errata only. A Recommendation is the W3C's own term of art. It means a specification has completed the W3C process and is endorsed for adoption.

What follows next is our reading rather than the W3C's. A technical specification binds nobody by itself. An obligation to meet one arrives only when a separate instrument names it. That is our reading of how obligations arise, not legal advice about your position. That instrument is a statute, a regulation, a procurement clause, or a contract you signed. Besides, the W3C draws no legal conclusion anywhere in the document, and it should not be read as drawing one.

What actually changed in WCAG 2.0 vs 2.1 vs 2.2#

Each version adds success criteria to the one before it, so the count only ever grows.

The step to 2.1 added 17 criteria. Then WCAG 2.2 added 9 and removed exactly one, 4.1.1 Parsing at Level A. As a result, the net gain from 2.1 to 2.2 is 8. These counts and the totals above come from the W3C Recommendation text for WCAG 2.2 of 05 October 2023 revised 12 December 2024, and from the W3C Web Accessibility Initiative's What's New lists for 2.1 and 2.2. Those additions are spread across all three levels. In criteria terms, seventeen additions across three levels is the entire WCAG 2.0 vs 2.1 gap.

Editions matter as much as version numbers here. WCAG 2.2 is the Recommendation of 05 October 2023, revised 12 December 2024. WCAG 2.1's current edition reads 06 May 2025. Therefore a page citing "WCAG 2.1 (2018)" quotes a document that has since been re-published. That is a signal about the page rather than about the standard.

Which instrument decides your version, and does 2.2 cover the rest?#

Build to the newest version the instrument reaching you does not forbid. The W3C states the reason plainly in WCAG 2.2, the Recommendation of 05 October 2023 revised 12 December 2024. Its sentence reads: "Content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1."

That relation runs one way only, and this next part is our entailment rather than the W3C's sentence. Conforming to 2.0 or to 2.1 does not make content conform to 2.2. At conformance level the version question therefore mostly collapses, because a page built to 2.2 satisfies the criteria sets of the earlier versions, although that does not mean an instrument naming 2.0 or 2.1 is thereby satisfied as a legal or contractual matter.

Four axes decide which instrument reaches you. First, jurisdiction. Second, sector. Third, entity type. Fourth, whether a customer's contract names a version of its own. If a given jurisdiction, sector and entity type apply, then a named instrument requires a named version at a named level.

We already publish those rows twice. For instance, our post on the June 2025 deadline and the European Accessibility Act's scope maps instruments to versions. In addition, the introduction to POUR and the first accessibility fixes carries a second mapping.

What that means for the mapping our other posts publish#

That deadline post says work done once at WCAG 2.1 Level AA also satisfies the ADA, Section 508 and AODA at once. That holds for the web-content requirement of Section 508 and AODA, each of which names a WCAG version and level that conformance at 2.1 Level AA meets. It does not hold for the ADA, which names no technical standard at all, so no level of WCAG conformance is a statutory safe harbour under it, though a Department of Justice regulation under the same statute does name one for public entities. It does not carry to EN 301 549 either. The legal detail, and the note that none of this is legal advice, sit further down.

Why does Level A say nothing about contrast?#

No version of WCAG 2 places any contrast criterion at Level A. In practice, a site claiming Level A has made no contrast commitment at all.

All three contrast criteria sit above it. Contrast is where the three levels actually diverge. Every threshold that exists sits at AA or above, and none sits at A. Each is stated in the W3C Recommendation text for WCAG 2.2 of 05 October 2023, revised 12 December 2024. In addition, the same allocation holds in 2.0 and in 2.1.

Read the scope carefully, because it is narrower than it sounds. The claim is about contrast. It covers WCAG versions 2.0, 2.1 and 2.2. However, Level A does carry other criteria bearing on visual presentation. Therefore "Level A says nothing about how it looks" would be false. This negative survives only because the criterion set is finite, numbered and levelled in three published documents. As a result, you can falsify it by naming one criterion.

Is Level AAA the goal?#

No, and the specification says so about site-wide mandates rather than about the criteria themselves.

Read what that sentence scopes. It addresses a policy requiring AAA across an entire site. However, it does not discourage meeting individual AAA criteria where they fit your content. In practice plenty of teams meet several without difficulty. Besides, the accompanying note is permissive in its own right: progress beyond the achieved level may be reported.

In short, A, AA and AAA are not bronze, silver and gold. They are three levels of one criterion set. Instead, the level attached to any single criterion is a fact about that criterion, not a ranking of ambition.

Why does target size appear twice at two different levels?#

Because two different criteria carry that name, in two versions, with two thresholds. The two criteria answer different questions at different bars. That is why the same search term turns up two unrelated numbers. Both are stated in the W3C Recommendation text for WCAG 2.2 of 05 October 2023, revised 12 December 2024.

The practical consequence is small and sharp. Quoting a criterion by name alone does not tell anyone whether you must meet it. Therefore check the number, the version and the level together. For instance, focus visibility spans several numbered criteria at different levels. We walk through that case in focus versus focus-visible in CSS.

What conformance requires beyond passing every criterion#

Conformance is a claim, not a score. It is made about full pages, and about every page in a complete process. Also, it is made under five stated requirements. Those requirements sit in the Conformance section of the W3C Recommendation for WCAG 2.2 of 05 October 2023, revised 12 December 2024. Therefore a per-criterion pass rate is not a conformance claim, and this is the part a checklist cannot express.

The five requirements, full pages, and complete processes#

The five requirements are the conformance level itself, full pages, complete processes, only accessibility-supported ways of using technologies, and non-interference. Full pages means the claim covers the whole page rather than a part of it. In addition, complete processes means every page in a multi-step flow sits inside the claim. A checkout or an application form is exactly that kind of flow.

Consequently, a partially conforming page is not a page that conforms a bit less. Instead it is a page that does not conform. For content you do not control, the specification defines a separate statement of partial conformance. Embedded and user-generated material are the usual examples. That mechanism carries its own stated conditions, and it is not a way of conforming without meeting the requirements.

One term of art matters throughout. Conformance is a technical state under those five requirements. Whereas compliance means meeting a law, which may require something narrower, broader, or differently shaped.

Accessibility supported, and why "it renders" is not the test#

Conformance counts only those uses of a web content technology that are accessibility supported. The specification defines that phrase with two limbs. Both are stranger than the plain reading.

First, the way the technology is used must have been tested for interoperability with users' assistive technology. That testing is in the human language or languages of the content. Second, the technology must have accessibility-supported user agents that are available to users. The specification satisfies that second limb by any one of four stated routes. For example, one route is native support in widely distributed user agents such as HTML and CSS. Another is support through a widely distributed plug-in. A third is availability inside a closed environment, such as a single corporate network.

Notice what the second limb is not. It is not a duty to document anything. Instead it is a condition about the user-agent ecosystem the content's audience actually has. As a result, a criterion recorded as passing on top of a use that is not accessibility supported does not count toward conformance. Meanwhile a report built from criterion checks alone cannot see that gap.

A conforming alternate version is not "a text-only page is fine"#

A conforming alternate version is a defined mechanism with its own stated conditions. Those conditions sit in the same Conformance section. Therefore it is not a general permission to ship an accessible sibling page and treat the main page as covered.

The permitted reading is conditional, and it is about the specification. A version that does not meet every one of the conditions the specification states is not a conforming alternate version. As a result, the page a reader actually reaches is the page the conformance claim stands on.

Where conformance stops being enough#

Conformance at the level an instrument names is a floor, not an outcome. A page can satisfy every applicable criterion at that level. Yet a real user may still be unable to finish the process the page exists for.

The two requirements above are why. Complete processes brings the whole flow into the claim, and accessibility supported brings real assistive technology into the test. Consequently the work that catches what a criterion sweep misses is testing with assistive technology across whole processes rather than isolated pages. Our write-up of testing methods and the boundary of automated scanner coverage goes through what that looks like.

Two different situations arrive at this point. For a site that already exists and has an audit that missed something, the relevant work is WCAG and ADA compliance: audit, fixes and re-test. For work that has not been built yet, it is accessibility testing built in from the start. Neither is required in order to conform, since conformance is a floor rather than an outcome.

The three American instruments people collapse into one#

The American position is three separate things. First, the statute. The Americans with Disabilities Act names no technical standard, in either Title II or Title III.

Second, the regulation. The United States Department of Justice's Title II rule at 28 C.F.R. part 35 subpart H requires WCAG 2.1 Level A and AA of public entities only. As promulgated, that rule set two compliance dates. They were 24 April 2026 for a public entity with a total population of 50,000 or more, and 26 April 2027 below that or for a special district government. Both were later changed by the interim final rule below.

The compliance dates, and why they are not settled#

Then 91 FR 20902, published on 20 April 2026, arrived as an interim final rule. In its own terms it operates while its comment period is open. It sets those dates at 26 April 2027 for a public entity with a total population of 50,000 or more, and 26 April 2028 below that or for a special district government. Because that interim final rule is open for comment, the operative dates are not settled and may change again. Therefore check the current Federal Register entry and the current text of 28 C.F.R. part 35 subpart H rather than any date printed here. This passage reflects the position as recorded on 08 September 2026.

Third, Title III. What is absent for private entities is a Department of Justice regulation naming a technical standard for their websites, although the ADA's application to Title III entities is not absent. Exposure reaches websites through settlements, and through individual court opinions that bind only their parties. In contrast, circuits differ on whether a website with no physical nexus is a place of public accommodation. Nothing here is a verdict about your organisation.

When this framework fails, and when you need counsel instead#

This decision procedure routes obligations that are written down. However, it cannot route the two categories below. If you are in either one, the next step is a lawyer in your own jurisdiction, not a closer reading of the criteria.

Take EN 301 549, the European standard published by CEN, CENELEC and ETSI. Its equivalence to WCAG 2.1 Level AA is one-directional, and it covers clause 9 only. Clauses 10, 11 and 5 to 8 have no WCAG counterpart. Consequently, a product can conform to WCAG 2.1 Level AA and still fail EN 301 549 comprehensively. Version 4.1.1, adopted on 24 August 2026, aligns to WCAG 2.2. Still, its legal effect is conditional on citation in the Official Journal of the European Union rather than automatic on adoption. That is the case where "fix it once at 2.1 AA" does not carry across.

An obligation can also arrive entirely through a customer's procurement clause or a contract. No analysis of statutes or regulations will surface it. Besides, it may name a version and level that neither your jurisdiction nor your sector would have selected. Read the contract.

Finally, none of the above is an individualised compliance verdict, and that is a refusal rather than a caveat. Three situations sit outside it. First, when the obligation is contested rather than written down. Second, when a regulator or an opposing party has already made contact. Third, when the answer turns on facts about one organisation rather than on what a specification says. In each of those, the right next step is counsel in your own jurisdiction.