What WCAG 2.2 Changed

WCAG 2.2 became a W3C Recommendation in October 2023. If you're conformant to 2.1 Level AA, you're most of the way there — the delta is six new criteria at A and AA, plus one removal.

Worth understanding anyway, because the additions tell you where the standard is heading.

The six additions at Level A and AA

3.2.6 Consistent Help (Level A). If you offer help — a contact number, a chat widget, a help link — it has to appear in the same relative place on every page that has it. Cheap to satisfy, and it matters more than it sounds for users who navigate by memory.

3.3.7 Redundant Entry (Level A). Don't make people re-enter information they already gave you in the same process. Every multi-step application that asks for an address three times now fails a Level A criterion.

2.4.11 Focus Not Obscured, Minimum (Level AA). The focused element can't be entirely hidden behind other content. Sticky headers, cookie banners, and chat bubbles are the usual culprits — a keyboard user tabs somewhere and the thing they're on is underneath your announcement bar.

2.5.7 Dragging Movements (Level AA). Anything operated by dragging needs a non-drag alternative. Reorderable lists, kanban boards, and sliders all need a button or input path.

2.5.8 Target Size, Minimum (Level AA). Interactive targets need to be at least 24 by 24 CSS pixels, or spaced to reach that effective size. Dense icon rows and cramped mobile pagination are the common failures.

3.3.8 Accessible Authentication, Minimum (Level AA). Login can't require a cognitive function test — remembering, transcribing, or solving a puzzle — unless there's an alternative. In practice: stop blocking paste in password fields, and stop using image-recognition CAPTCHA as the only gate.

The removal: 4.1.1 Parsing

4.1.1 Parsing is obsolete and removed in 2.2. Modern browsers and assistive technology handle the markup errors it was written to catch, so it had become a criterion that generated findings without corresponding user harm. If an audit is still citing it, the audit is out of date.

The pattern in the additions

Look at what these have in common. Redundant Entry and Accessible Authentication address cognitive load. Dragging Movements and Target Size address motor ability. Consistent Help addresses predictability.

The earlier versions of WCAG were strongest on blindness and low vision and weakest on cognitive and motor disability. 2.2 starts closing that gap, and it's a reasonable bet that future revisions continue in the same direction.

Which version you're actually obligated to meet

Almost certainly 2.1. The ADA Title II rule cites WCAG 2.1 Level AA. Section 508 incorporates Level AA through the Revised 508 Standards. EN 301 549, which underpins European Accessibility Act conformance, tracks Level AA. Most settlements and procurement requirements cite 2.1.

So the practical recommendation for most organizations is split:

• Audit and report against 2.1 AA, because that's what your obligations reference and what a regulator or plaintiff will measure you against.
• Design and build new work to 2.2 AA, because the additions are nearly free at design time and expensive to retrofit. Target size and focus visibility are design decisions, not engineering ones.

The practical read

If you're starting from nothing, don't let the version question slow you down. The gap between "no accessibility work" and "conformant to 2.1 AA" is vastly larger than the gap between 2.1 and 2.2.

Get to 2.1 AA. Build new things to 2.2. Revisit when a regulation moves.