Kept Record

WCAG 2.2 adds nine success criteria to WCAG 2.1 and removes one.

WCAG 2.2 is the newer of the two versions of the Web Content Accessibility Guidelines that laws most often point at. It keeps the 2.1 criteria, adds nine, and drops one that had stopped doing any work. Which version a given law asks for is a question about that law, not about WCAG.

The two documents

Both versions are quoted below from their current editions. Neither replaces the other in law until a law says so.

WCAG 2.2 became a W3C Recommendation on 5 October 2023.

WCAG 2.2 was published as a "W3C Recommendation" web standard on 5 October 2023. W3C WAI, What's New in WCAG 2.2, Introduction, Updated 5 October 2023.

The edition of WCAG 2.2 in force today is the one republished on 12 December 2024.

W3C Recommendation 12 December 2024 WCAG 2.2, document header, 12 December 2024.

WCAG 2.1 was itself republished on 6 May 2025.

W3C Recommendation 06 May 2025 WCAG 2.1, document header, 6 May 2025.

What was added

The new criteria sit under existing guidelines.

WCAG 2.2 has nine success criteria that WCAG 2.1 does not.

WCAG 2.2 provides 9 additional success criteria since WCAG 2.1. W3C WAI, What's New in WCAG 2.2, Changes from WCAG 2.1 to WCAG 2.2, Updated 5 October 2023.

New criteria were added at the end of each guideline's list, so no existing criterion was renumbered.

appended to the end of the set of success criteria within their guideline WCAG 2.2, Introduction, Numbering in WCAG 2.2, 12 December 2024.

Six of the nine are at Level A or AA, the levels laws ask for: 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry, and 3.3.8 Accessible Authentication (Minimum).

2.5.7 Dragging Movements (AA) 2.5.8 Target Size (Minimum) (AA) 3.2.6 Consistent Help (A) WCAG 2.2, Introduction, New Features in WCAG 2.2, 12 December 2024.

The other three are at Level AAA: 2.4.12 Focus Not Obscured (Enhanced), 2.4.13 Focus Appearance, and 3.3.9 Accessible Authentication (Enhanced).

2.4.12 Focus Not Obscured (Enhanced) (AAA) 2.4.13 Focus Appearance (AAA) WCAG 2.2, Introduction, New Features in WCAG 2.2, 12 December 2024.

Target Size (Minimum) sets a pointer target of at least 24 by 24 CSS pixels, with exceptions, among them adequate spacing.

target for pointer inputs is at least 24 by 24 CSS pixels WCAG 2.2, Success Criterion 2.5.8 Target Size (Minimum), 12 December 2024.

Focus Not Obscured (Minimum) asks that a component with keyboard focus is not entirely hidden by the author's own content, such as a sticky banner.

the component is not entirely hidden due to author-created content WCAG 2.2, Success Criterion 2.4.11 Focus Not Obscured (Minimum), 12 December 2024.

Dragging Movements asks that anything done by dragging can also be done with a single pointer without dragging, unless dragging is essential.

can be achieved by a single pointer without dragging, unless dragging is essential WCAG 2.2, Success Criterion 2.5.7 Dragging Movements, 12 December 2024.

What was removed

One criterion from WCAG 2.0 and 2.1 is gone from 2.2. The consortium also changed how 2.1 treats it.

WCAG 2.2 removes success criterion 4.1.1 Parsing.

WCAG 2.2 has removed one success criterion, 4.1.1 Parsing WCAG 2.2, Introduction, Comparison with WCAG 2.1, 12 December 2024.

The reason given is that assistive technology no longer reads HTML directly, so the problems the criterion addressed are gone or covered elsewhere.

Assistive technology no longer has any need to directly parse WCAG 2.2, Success Criterion 4.1.1 Parsing (Obsolete and removed), Note, 12 December 2024.

The May 2025 edition of WCAG 2.1 keeps 4.1.1 but adds a note that it should be treated as always met for HTML or XML content.

should be considered as always satisfied for any content using HTML or XML WCAG 2.1, Success Criterion 4.1.1 Parsing, Note 1, 6 May 2025.

The consortium says that those required by policy to meet 2.0 or 2.1 may still need to test and report 4.1.1.

may need to continue to test and report 4.1.1. WCAG 2.2, Introduction, Comparison with WCAG 2.1, 12 December 2024.

How the two relate

The consortium describes 2.2 as a superset of 2.1 for conformance purposes. That is a statement about the guidelines; whether a law accepts 2.2 in place of 2.1 depends on the law's own words.

The consortium describes WCAG 2.2 as backwards compatible with WCAG 2.1.

WCAG 2.2 builds on and is backwards compatible with WCAG 2.1 WCAG 2.2, Introduction, Comparison with WCAG 2.1, 12 December 2024.

It intends that a site meeting 2.2 also meets 2.0 and 2.1.

sites that conform to WCAG 2.2 also conform to WCAG 2.0 and WCAG 2.1 WCAG 2.2, Introduction, Conformance to WCAG 2.2, 12 December 2024.

The conformance model, including the A, AA and AAA levels, is the same as in WCAG 2.0.

WCAG 2.2 uses the same conformance model as WCAG 2.0. WCAG 2.2, Introduction, Conformance to WCAG 2.2, 12 December 2024.

The working group recommends adopting 2.2 even where a formal obligation names an earlier version. That is a recommendation from the authors, not a legal rule.

even if formal obligations mention previous versions WCAG 2.2, Introduction, New Features in WCAG 2.2, 12 December 2024.

Which version the law asks for

The WCAG page on this site sets out which version each law names. Two examples show that the answer differs by law.

The United States rule for state and local government websites names WCAG 2.1, incorporated by reference.

Level A and Level AA success criteria and conformance requirements specified in WCAG 2.1 28 CFR 35.200(b)(1), eCFR, section last amended 20 April 2026.

The UK government's guidance for public sector bodies names WCAG 2.2 Level AA as the standard to meet.

Web Content Accessibility Guidelines (WCAG) 2.2 AA accessibility standard GOV.UK, Understanding accessibility requirements for public sector bodies, Meeting accessibility requirements, Last updated 30 September 2024.

Sources

Every source on this page was fetched and its quotation confirmed on 27 September 2026, today. That date is written by the script that checked, not by a person.

A directive binds member states, who write it into national law. The national act can name a different authority, set a different penalty, or add duties. The sources here are the directive and three national acts; yours may differ.

Nothing on this page is about a product. The record a business keeps of its own site is its own affair, and no tool makes a site meet a law.

This page describes the law as it is written in the sources cited. It is not legal advice, it does not cover every case, and national law can add to what a directive requires. It has not been reviewed by a lawyer.

This page describes what the system does, written by the people who built it. It has not been reviewed by a lawyer.