WCAG 2.1 vs 2.2: versions and what is new in WCAG 2.2
Updated October 14, 2026 · 6 min read
There are three published versions of WCAG 2: 2.0 (2008), 2.1 (2018) and 2.2 (2023). Each one keeps the criteria of the previous version and adds new ones. WCAG 2.2 is the latest version: it adds nine success criteria and removes one, 4.1.1 Parsing. This page lists exactly what changed, which version the European standard EN 301 549 and US rules use, and where WCAG 3 stands.
This is general information, not legal advice. For an introduction to the guidelines, see what WCAG is.
WCAG versions at a glance
| Version | W3C Recommendation | Criteria (A / AA / AAA) | Used by |
|---|---|---|---|
| WCAG 2.0 | 11 December 2008 | 25 / 13 / 23 = 61 | Section 508 (US federal), ISO/IEC 40500:2012 |
| WCAG 2.1 | 5 June 2018 | 30 / 20 / 28 = 78 | EN 301 549 V3.2.1, ADA Title II rule |
| WCAG 2.2 | 5 October 2023 | 31 / 24 / 31 = 86 | EN 301 549 V4.1.1, ISO/IEC 40500:2025 |
The W3C updated WCAG 2.2 on 12 December 2024 and encourages everyone to use the latest version. WCAG 2.2 is also an ISO standard: ISO/IEC 40500:2025 is identical to the October 2023 version of WCAG 2.2.
Because each version builds on the previous one, a page that meets WCAG 2.2 AA also meets the success criteria of WCAG 2.1 AA and 2.0 AA. The one exception is 4.1.1 Parsing, which exists only in 2.0 and 2.1.
What WCAG 2.1 added
WCAG 2.1 added 17 success criteria, mostly for mobile use, low vision and cognitive disabilities. The ones at levels A and AA are those you meet most in audits:
- Level A: 2.1.4 Character Key Shortcuts, 2.5.1 Pointer Gestures, 2.5.2 Pointer Cancellation, 2.5.3 Label in Name, 2.5.4 Motion Actuation.
- Level AA: 1.3.4 Orientation, 1.3.5 Identify Input Purpose, 1.4.10 Reflow, 1.4.11 Non-text Contrast, 1.4.12 Text Spacing, 1.4.13 Content on Hover or Focus, 4.1.3 Status Messages.
- Level AAA: 1.3.6 Identify Purpose, 2.2.6 Timeouts, 2.3.3 Animation from Interactions, 2.5.5 Target Size, 2.5.6 Concurrent Input Mechanisms.
What's new in WCAG 2.2: the nine new criteria
| Criterion | Level | What it asks in short |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | A focused element is not entirely hidden by sticky headers, banners or chat bubbles |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA | No part of the focused element is hidden |
| 2.4.13 Focus Appearance | AAA | The focus indicator has a minimum size and contrast |
| 2.5.7 Dragging Movements | AA | Anything done by dragging also works with single clicks or taps |
| 2.5.8 Target Size (Minimum) | AA | Targets are at least 24 by 24 CSS pixels or have enough spacing, with exceptions |
| 3.2.6 Consistent Help | A | Help options, such as contact details or a chat, appear in the same relative place |
| 3.3.7 Redundant Entry | A | Information already entered in a process is filled in or offered again |
| 3.3.8 Accessible Authentication (Minimum) | AA | Login does not depend on a cognitive test unless an alternative or help is available |
| 3.3.9 Accessible Authentication (Enhanced) | AAA | As 3.3.8, without the exceptions for object and personal content recognition |
So for level AA, WCAG 2.2 adds six criteria: four at AA and two at A. Our explanations: 2.4.11 Focus Not Obscured, 2.5.7 Dragging Movements, 2.5.8 Target Size, 3.2.6 Consistent Help, 3.3.7 Redundant Entry and 3.3.8 Accessible Authentication.
On a typical online shop the new AA criteria show up as cookie banners covering the focused button, price sliders without a click alternative, tiny quantity steppers and colour swatches, a billing form that asks again for the shipping address, and login forms that block pasting a password. Our WCAG 2.2 checklist for online shops goes through them.
What was removed: 4.1.1 Parsing
4.1.1 Parsing asked for markup without errors such as unclosed elements or duplicate attributes. The W3C marked it obsolete and removed it from WCAG 2.2, because browsers and assistive technologies now handle these errors themselves. Problems that still affect people, such as duplicate IDs that break the link between a label and its field, are covered by other criteria like 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value.
WCAG 2.1 vs 2.2: what it means for your site
- If your site meets WCAG 2.1 AA, the additional work for 2.2 AA is limited and concrete: focus versus sticky elements, larger targets, alternatives to dragging, consistent help, no retyping, friendlier login.
- If your site has not been checked yet, test against 2.2 AA right away. There is no benefit in aiming for the older version.
- If a contract or law names WCAG 2.1, meeting 2.2 AA still covers it.
Which version EN 301 549 and US rules use
In the European Union, the European Accessibility Act relies on the harmonised standard EN 301 549. The version cited as harmonised, V3.2.1, uses WCAG 2.1 AA. V4.1.1, published in September 2026, moves to WCAG 2.2 AA; its citation in the EU's Official Journal is expected in late 2026. Details: EN 301 549 V4.1.1 and WCAG 2.2.
In the United States, Section 508 refers to WCAG 2.0 AA, the ADA Title II rule for state and local governments to WCAG 2.1 AA, and for private businesses WCAG 2.1 or 2.2 AA is the practical reference. See ADA website compliance.
WCAG 3: status
WCAG 3 is a working draft. The W3C published a new draft in September 2026 and states that WCAG 3 is not expected to be a completed W3C standard for a few more years. It is planned with a different structure and scoring model, and it will not automatically replace WCAG 2.2 in laws. For now, every regulation we know of refers to WCAG 2.x.
How Pandus tests the versions
Our checker runs automated tests for WCAG 2.2 levels A and AA and maps each finding to WCAG 2.0, 2.1 and 2.2 and to both EN 301 549 V3.2.1 and V4.1.1. Of the six new A and AA criteria, our automated rules test only 2.5.8 Target Size; the others need a person. Try the free WCAG checker, compare WCAG levels A, AA and AAA and follow how to test WCAG for the manual part. It is an automated check, not a full audit, and not legal advice.
Frequently asked questions
What is the latest version of WCAG?
WCAG 2.2. It became a W3C Recommendation on 5 October 2023 and was updated on 12 December 2024. WCAG 3 is a working draft and not a finished standard.
What's new in WCAG 2.2?
Nine new success criteria: 2.4.11, 2.5.7, 2.5.8 and 3.3.8 at level AA, 3.2.6 and 3.3.7 at level A, and 2.4.12, 2.4.13 and 3.3.9 at level AAA. 4.1.1 Parsing was removed.
How many success criteria does WCAG 2.2 have?
86 in total: 31 at level A, 24 at level AA and 31 at level AAA. Level AA conformance means meeting the 55 A and AA criteria.
If my site meets WCAG 2.2 AA, does it meet WCAG 2.1 AA?
Yes, for the success criteria. WCAG 2.2 keeps every 2.1 criterion except 4.1.1 Parsing, which the W3C considers obsolete because browsers and assistive technologies now handle the markup errors it was about.
Which WCAG version does EN 301 549 use?
V3.2.1, the version cited as harmonised under the European Accessibility Act, uses WCAG 2.1 AA. V4.1.1, published in September 2026, uses WCAG 2.2 AA; its citation in the Official Journal is expected in late 2026.
When will WCAG 3 replace WCAG 2.2?
Not soon. WCAG 3 is a working draft, and the W3C says it is not expected to be a completed standard for a few more years. Laws refer to WCAG 2.x.
Sources
- W3C, WCAG 2 overview (versions and dates, ISO/IEC 40500:2025): https://www.w3.org/WAI/standards-guidelines/wcag/
- W3C, What's new in WCAG 2.2: https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/
- W3C, WCAG 3 introduction: https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/
- National Disability Authority (Ireland), EN 301 549 published: https://nda.ie/news/en301549-published