WCAG 2.2: what changed, and what it means for your website.

A newer version of a familiar standard

The Web Content Accessibility Guidelines (WCAG) are the technical standard most accessibility audits are measured against. W3C published WCAG 2.2 as a Recommendation in October 2023. It builds on WCAG 2.1 rather than replacing it, and W3C notes that content meeting WCAG 2.2 also meets 2.1 and 2.0.

Version 2.2 adds nine success criteria and removes one. Success criterion 4.1.1 Parsing is now obsolete, because modern browsers and assistive technologies no longer rely on the issues it covered.

The additions at Level A and AA

Most organizations target Level AA, which includes Level A. These six new criteria fall within that target:

• 2.4.11 Focus Not Obscured (Minimum), AA: a focused element must not be completely hidden by other content, such as a sticky header or cookie banner.
• 2.5.7 Dragging Movements, AA: anything done by dragging, such as a slider or a sortable list, also needs a single-pointer alternative.
• 2.5.8 Target Size (Minimum), AA: pointer targets should be at least 24 by 24 CSS pixels, with defined exceptions such as sufficient spacing.
• 3.2.6 Consistent Help, A: help options that repeat across pages, such as a contact link or chat, should appear in the same relative order.
• 3.3.7 Redundant Entry, A: information a user already entered in the same process should be filled in automatically or offered for selection.
• 3.3.8 Accessible Authentication (Minimum), AA: signing in should not depend on a cognitive function test, such as solving a puzzle or memorizing a code, unless an alternative or assistance is provided.

The Level AAA additions

Three further criteria sit at Level AAA: 2.4.12 Focus Not Obscured (Enhanced), 2.4.13 Focus Appearance, and 3.3.9 Accessible Authentication (Enhanced). AAA is rarely required for an entire site, but these criteria are useful design guidance, especially the clear focus indicator described in Focus Appearance.

Where to look on your own site

• Tab through pages with a sticky header, chat widget, or cookie banner open, and confirm the focused item stays visible.
• Check sliders, carousels, maps, and drag-and-drop uploads for button or click alternatives.
• Measure small icon buttons, such as close, quantity, and social icons, especially on mobile layouts.
• Review checkout and sign-up flows for repeated questions, like entering a billing address that matches the shipping address.
• Test the login page with a password manager, and confirm that pasting a password or a one-time code works.

Choosing a target for your next audit

Some regulations and contracts still reference WCAG 2.1 Level AA. Because WCAG 2.2 builds on 2.1, an audit against 2.2 Level AA also covers the 2.1 AA criteria that remain in force. Agree on the version and level before testing begins, and record it in the audit report so everyone works to the same reference.

Reference: What’s new in WCAG 2.2, from W3C.