WCAG 2.2: the nine new success criteria, in plain language

WCAG 2.2 became a W3C Recommendation in October 2023. It builds on 2.1, so a site that meets 2.2 AA also meets 2.1 AA. It adds nine success criteria and removes one, 4.1.1 Parsing, which modern browsers made obsolete.

Level A

• 3.2.6 Consistent Help. If you offer help (a phone number, a chat, a contact link), put it in the same relative place on every page.
• 3.3.7 Redundant Entry. Don't make people type the same information twice in one process. Pre-fill it or let them pick it.

Level AA

• 2.4.11 Focus Not Obscured (Minimum). When something receives keyboard focus, it can't be entirely hidden by sticky headers, cookie banners or chat widgets.
• 2.5.7 Dragging Movements. Anything you can do by dragging (sliders, sortable lists, maps) also needs a single-pointer alternative, like clicking or tapping.
• 2.5.8 Target Size (Minimum). Pointer targets should be at least 24 by 24 CSS pixels, or have enough spacing around them, with a few exceptions such as links inside a sentence.
• 3.3.8 Accessible Authentication (Minimum). Signing in can't depend on a cognitive function test, like remembering a password or solving a puzzle, unless there's an alternative. Allowing paste and password managers usually covers it.

Level AAA

• 2.4.12 Focus Not Obscured (Enhanced). No part of the focused element is hidden.
• 2.4.13 Focus Appearance. The focus indicator is large enough and contrasts enough to be easy to see.
• 3.3.9 Accessible Authentication (Enhanced). Like 3.3.8, without the object and personal-content exceptions.

Where sites usually fall short

In practice, the new AA criteria that trip people up most are focus hidden behind sticky headers and cookie banners, icon buttons smaller than 24 pixels, and sign-in forms that block paste. All three are usually quick to fix once they've been found.