WCAG 2.2, published by the W3C in October 2023, is the latest version of the Web Content Accessibility Guidelines. It builds on WCAG 2.1 by adding 9 new success criteria focused on users with cognitive disabilities, low vision, and those using mobile and touch devices. It also retired one criterion. Understanding these changes is critical for any organisation aiming for compliance in 2026.
A Brief History
- WCAG 2.0 (2008)— The foundational standard, organised around four principles: Perceivable, Operable, Understandable, and Robust.
- WCAG 2.1 (2018)— Added 17 new success criteria addressing mobile accessibility, low vision, and cognitive disabilities.
- WCAG 2.2 (2023)— Added 9 new success criteria, removed 1, and strengthened focus on cognitive accessibility and usability.
The 9 New Success Criteria in WCAG 2.2
2.4.11 Focus Not Obscured (Minimum) — Level AA
When a component receives keyboard focus, it must not be entirely hidden by other content such as sticky headers, footers, or modal overlays. This ensures keyboard users can always see where they are on the page.
2.4.12 Focus Not Obscured (Enhanced) — Level AAA
The enhanced version requires that no part of the focused element is hidden by author-created content. This is the stricter version of 2.4.11.
2.4.13 Focus Appearance — Level AAA
Focus indicators must meet minimum size and contrast requirements, ensuring keyboard focus is always clearly visible. While AAA, this is widely considered best practice.
2.5.7 Dragging Movements — Level AA
Any functionality that uses dragging (drag-and-drop interfaces, sliders) must also be achievable through a single pointer without dragging. This benefits users with motor disabilities and touchscreen users.
2.5.8 Target Size (Minimum) — Level AA
Interactive targets must be at least 24×24 CSS pixels, or have sufficient spacing between them. This helps users with motor impairments and those using touch devices. Exceptions exist for inline links and elements where size is essential.
3.2.6 Consistent Help — Level A
If a website provides help mechanisms (contact info, chat, FAQ links), they must appear in a consistent location across pages. Users with cognitive disabilities depend on predictable placement of help features.
3.3.7 Redundant Entry — Level A
Information that the user has previously entered in the same process must be auto-populated or available for selection, rather than requiring re-entry. This reduces cognitive load and benefits everyone.
3.3.8 Accessible Authentication (Minimum) — Level AA
Cognitive function tests (such as remembering passwords or solving puzzles) must not be the sole method of authentication. Alternatives like password managers, passkeys, or third-party authentication must be supported.
3.3.9 Accessible Authentication (Enhanced) — Level AAA
The enhanced version prohibits any cognitive function test in the authentication process, even object recognition or personal content identification.
What Was Removed: 4.1.1 Parsing
WCAG 2.2 retired Success Criterion 4.1.1 Parsing, which required valid HTML markup (no duplicate IDs, proper nesting, etc.). Modern browsers and assistive technologies have become robust enough to handle minor parsing errors, making this criterion obsolete. However, good coding practices remain important for overall accessibility.
Practical Impact on Real Websites
The most impactful changes for typical websites and web applications are:
- Sticky headers and cookie banners must not cover focused elements (2.4.11)
- Drag-and-drop interfaces need single-click alternatives (2.5.7)
- Touch targets (buttons, links) need to be at least 24×24px or well-spaced (2.5.8)
- Help links and contact info must appear in the same location on every page (3.2.6)
- Multi-step forms must not ask for the same information twice (3.3.7)
- Login flows must support password managers and not rely solely on CAPTCHAs (3.3.8)
Which Regulations Now Reference WCAG 2.2?
Regulatory adoption of WCAG 2.2 is accelerating worldwide:
- SEBI (India)— The 2024 circular explicitly references WCAG 2.2 AA for all regulated entities.
- European Accessibility Act (EU)— While EN 301 549 currently maps to WCAG 2.1, the upcoming revision is expected to incorporate WCAG 2.2 criteria.
- ADA (US)— Courts and the DOJ increasingly reference WCAG 2.2 as the benchmark, though Title II rules currently cite WCAG 2.1 AA.
- Section 508 (US Federal)— An update aligning with WCAG 2.2 is anticipated.
- AODA (Canada)— Still references WCAG 2.0 AA, but organisations are advised to target 2.2 for future-proofing.
Should You Audit Against 2.1 or 2.2?
If you are commissioning an accessibility audit in 2026, audit against WCAG 2.2 AA. It is backward-compatible with 2.1 and 2.0, so you will cover all previous criteria plus the new ones. This future-proofs your compliance as regulations catch up to the latest standard.
Ready to get compliant?
Get a free preliminary accessibility check for your website — results delivered in 24 hours.
Get Free Preliminary Audit