Ability Bazaar guide
What changed from WCAG 2.1 to WCAG 2.2?
The short answer
WCAG 2.2 is backward-compatible with WCAG 2.1: content that conforms to 2.2 also conforms to 2.1, apart from the now-obsolete Parsing criterion 4.1.1. The newer standard adds nine success criteria, six at Level A or AA and three at Level AAA.
The additions focus on visible keyboard focus, alternatives to dragging, target size, consistent help, reducing repeated data entry and accessible authentication. W3C recommends using the latest WCAG version, while a law or contract may still name WCAG 2.0 or 2.1.
What are the nine new WCAG 2.2 success criteria?
| Criterion | Level | Plain-language purpose |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | Keep the focused component at least partly visible. |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA | Keep the focused component fully visible. |
| 2.4.13 Focus Appearance | AAA | Make the keyboard focus indicator large and contrasting enough. |
| 2.5.7 Dragging Movements | AA | Provide a non-dragging way to perform dragging actions. |
| 2.5.8 Target Size (Minimum) | AA | Make pointer targets sufficiently large or spaced, with defined exceptions. |
| 3.2.6 Consistent Help | A | Keep repeated help mechanisms in a consistent relative order. |
| 3.3.7 Redundant Entry | A | Avoid asking users to re-enter information already supplied in the same process. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Do not require a cognitive-function test unless an alternative or exception applies. |
| 3.3.9 Accessible Authentication (Enhanced) | AAA | Further limit cognitive-function tests in authentication. |
Sources for this section: [1]
Was anything removed?
Success Criterion 4.1.1 Parsing is obsolete in WCAG 2.2. W3C explains that modern browsers and assistive technologies no longer experience the parsing problems the criterion was designed to address. WCAG 2.2 does not require testing it, and WCAG 2.1 was updated so the criterion is treated as always satisfied.
That change does not excuse invalid markup that creates real accessibility failures. Name, role and value requirements and other criteria still apply to user-interface components.
Sources for this section: [1]
Which WCAG version should a team use?
For new work, W3C advises using WCAG 2.2 to address more current user needs. If a regulation or procurement document names WCAG 2.1, test and report that required baseline explicitly, then consider the additional 2.2 criteria as a stronger design target.
The DOJ Title II web rule names WCAG 2.1 Level A and AA. Revised Section 508 incorporates WCAG 2.0 Level A and AA. Other jurisdictions and contracts may differ, so do not infer the legal baseline from the latest W3C publication alone.
How should an existing 2.1 program move to 2.2?
- Keep the current WCAG 2.1 test library; 2.2 extends rather than replaces most of it.
- Add the six new Level A and AA criteria to design, code review and acceptance tests.
- Pay special attention to sticky headers, modal dialogs and other content that can obscure keyboard focus.
- Review drag-and-drop interactions and provide click, keyboard or text alternatives.
- Test authentication flows without relying on memory puzzles or transcription.
- Record both the contractual baseline and the newer internal target in reports.
Frequently asked questions
- How many success criteria did WCAG 2.2 add?
WCAG 2.2 added nine success criteria: six at Level A or AA and three at Level AAA.
- Does WCAG 2.2 replace WCAG 2.1?
It is the newer W3C Recommendation and is backward-compatible with 2.1, but laws and contracts may still explicitly reference an earlier version.
- Which criterion became obsolete?
Success Criterion 4.1.1 Parsing is obsolete and removed from WCAG 2.2.
Sources
- W3C WAI, What's New in WCAG 2.2
- W3C WAI, WCAG 2 Overview
- ADA.gov, First Steps Toward Complying with the Title II Web Rule
- Section508.gov, Information and Communication Technology
Sources were checked on August 21, 2026. Regulations, standards and product documentation can change; follow the linked source for the latest version.