WCAG 2.1 vs 2.2: What Changed and Why It Matters

WCAG 2.2 became a W3C Recommendation in October 2023. If your site was audited against WCAG 2.1, it may already fail on criteria that now define legal compliance in the EU, UK, and increasingly in US enforcement actions. This guide walks through every change — what was added, what was removed, and what each criterion means in practice.

Quick Background: What WCAG 2.1 Added

WCAG 2.1 (published 2018) extended the original 2.0 standard with 17 new success criteria focused on three underserved groups:

Mobile users — touch gestures, screen orientation, pointer precision
Low vision users — reflow, non-text contrast, text spacing
Cognitive and language disabilities — timeouts, status messages

WCAG 2.2 builds directly on 2.1. Every 2.1 requirement still applies. The question is: what did 2.2 add on top?

What WCAG 2.2 Added: 9 New Success Criteria

2.4.11 Focus Not Obscured (Minimum) — Level AA

When a component receives keyboard focus, it must not be entirely hidden by other content (sticky headers, cookie banners, chat widgets). At least part of the focused element must remain visible.

Common failure: A fixed navigation bar covers the focused form field when a user tabs through a page.

2.4.12 Focus Not Obscured (Enhanced) — Level AAA

Stricter version of 2.4.11 — the focused component must be fully visible, not just partially.

2.4.13 Focus Appearance — Level AA

Keyboard focus indicators must meet minimum size and contrast thresholds:

The focus indicator area must be at least as large as a 2 CSS pixel perimeter around the component
The contrast between focused and unfocused states must be at least 3:1

This goes further than the existing 2.4.7 (Focus Visible), which only required a focus indicator to exist at all.

Common failure: A thin 1px dotted outline with low contrast passes 2.4.7 but fails 2.4.13.

2.5.7 Dragging Movements — Level AA

Any action that requires dragging must also be achievable with a single pointer (tap or click). This serves users with motor impairments who cannot reliably control drag operations.

Example: A sortable list must offer an alternative (such as up/down buttons) for users who cannot drag items.

2.5.8 Target Size (Minimum) — Level AA

Interactive targets (buttons, links, form controls) must be at least 24×24 CSS pixels — or have sufficient spacing from adjacent targets so that the total activation area meets the threshold.

This is the minimum version. The enhanced criterion (2.5.5, carried over from 2.1 at Level AAA) recommends 44×44px.

Common failures: Icon-only buttons, close (×) icons, and inline text links in tight navigation menus.

3.2.6 Consistent Help — Level A

If a website offers a help mechanism (phone number, chat link, contact form, FAQ link), it must appear in the same relative position across pages where it is present. Users with cognitive disabilities often depend on predictable placement.

3.3.7 Redundant Entry — Level A

Information that a user has already submitted in the same session must not be required again — unless re-entering it is essential (e.g. a password confirmation field) or the data is security-sensitive.

Example: A multi-step checkout should not ask for the billing address on step 3 if the user already entered it on step 1.

3.3.8 Accessible Authentication (Minimum) — Level AA

Authentication steps must not rely on a cognitive function test — recognising objects, transcribing characters, or solving puzzles — unless an alternative is provided or the test is to recognise user-controlled content (such as a photo the user uploaded).

Common failures: CAPTCHAs that require identifying distorted text with no audio alternative, or “click all images with traffic lights” challenges.

3.3.9 Accessible Authentication (Enhanced) — Level AAA

The enhanced version removes even the exception for user-controlled content. No cognitive function test is permitted in the authentication flow.

What WCAG 2.2 Removed: 4.1.1 Parsing

WCAG 2.1 included 4.1.1 Parsing (Level A), which required well-formed HTML — unique element IDs, properly nested tags, and complete start/end tag pairs. Modern browsers had become so good at silently fixing malformed HTML that this criterion became unmeasurable in practice.

In WCAG 2.2, 4.1.1 Parsing is marked obsolete and always considered satisfied. You no longer need to audit for it, though writing clean HTML remains best practice.

Summary Table

Criterion	Level	Topic
2.4.11 Focus Not Obscured (Min)	AA	Keyboard focus
2.4.12 Focus Not Obscured (Enhanced)	AAA	Keyboard focus
2.4.13 Focus Appearance	AA	Focus indicator
2.5.7 Dragging Movements	AA	Pointer input
2.5.8 Target Size (Minimum)	AA	Touch targets
3.2.6 Consistent Help	A	Predictability
3.3.7 Redundant Entry	A	Forms
3.3.8 Accessible Authentication (Min)	AA	Login / CAPTCHA
3.3.9 Accessible Authentication (Enhanced)	AAA	Login / CAPTCHA
~~4.1.1 Parsing~~	A	Removed

Who Needs to Upgrade?

Practically everyone. WCAG 2.2 is now the baseline referenced by:

The European Accessibility Act (EAA), in force from June 2025
The EN 301 549 harmonised standard (updated to reference WCAG 2.2)
UK Public Sector Bodies Accessibility Regulations (updated guidance)
Many US state laws and DOJ informal enforcement positions

If your last full audit was against WCAG 2.1 AA, focus your upgrade effort on these five criteria that affect most sites: 2.4.11, 2.4.13, 2.5.8, 3.3.8, and 3.3.7 (if you have multi-step forms or checkouts).

How to Audit for the New Criteria

Most automated scanners now flag 2.5.8 (target size) and partial cases of 2.4.13 (focus appearance). However, the following require manual testing:

2.4.11 / 2.4.12 — Tab through every page with sticky headers/footers active and confirm focused elements are visible
2.4.13 — Measure focus indicator dimensions and contrast with browser DevTools or a contrast checker
2.5.7 — Identify every drag interaction and verify a pointer-only alternative exists
3.2.6 — Check that help links appear in consistent positions across pages
3.3.7 — Walk through all multi-step flows and confirm no data is requested twice
3.3.8 — Test every login, registration, and verification step for cognitive function tests

WCAG 2.2 is not a wholesale redesign — it is a targeted set of additions addressing real barriers that 2.1 missed. The good news is that most of the new AA criteria can be resolved with focused remediation work rather than a full site rebuild.