WCAG 2.2 explained: the nine new success criteria and how to meet them
Target size, focus visibility, dragging, accessible login: what changed in WCAG 2.2 and how to test it.
Key takeaways
- WCAG 2.2 became a W3C Recommendation in October 2023. It adds nine success criteria and removes one, 4.1.1 Parsing.
- Six new criteria apply at Level AA or below, the level laws and settlements expect. A site that passes 2.2 AA also passes 2.1 AA and 2.0 AA.
- Most new checks need a person: scanners miss sticky headers covering focus, tiny tap targets and login puzzles.
What WCAG 2.2 is and why it matters
The WCAG 2.2 Recommendation (opens in a new tab), published October 5, 2023, builds on 2.1 for people with low vision, cognitive disabilities and motor impairments. The W3C sums up what is new in WCAG 2.2 (opens in a new tab).
The U.S. Title II rule still references WCAG 2.1 AA. EN 301 549 V4.1.1 (opens in a new tab), published in September 2026, adopts WCAG 2.2 and becomes the EU's legal reference once formally cited. More on our WCAG compliance page.
The Level AA additions
2.4.11 Focus Not Obscured (Minimum)
A focused control can't be fully hidden by a sticky header, cookie banner or chat bubble. Add scroll-padding-top equal to the header height. See Focus Not Obscured (opens in a new tab).
2.5.7 Dragging Movements
Sliders, sortable lists and maps must also work with a single click or tap, since people with tremors often can't hold and drag. Add up and down controls or a number input. See Understanding Dragging Movements (opens in a new tab).
2.5.8 Target Size (Minimum)
Targets need 24 by 24 CSS pixels, or spacing so a 24 pixel circle on each doesn't overlap another; inline links are exempt. Footer links, pagination and banner close buttons fail most, and padding fixes them. See Understanding Target Size (Minimum) (opens in a new tab).
3.3.8 Accessible Authentication (Minimum)
Logging in can't require remembering a password or solving a puzzle without an alternative; allowing paste and password managers satisfies it. Forms that block paste, split one-time codes and CAPTCHAs with no alternative fail. See Understanding Accessible Authentication (opens in a new tab).
The Level A additions
3.2.6 Consistent Help
Help offered on several pages, like a phone number, chat or FAQ link, must appear in the same relative order each time. See Understanding Consistent Help (opens in a new tab).
3.3.7 Redundant Entry
Within one process, fill in or offer what the user already entered, like a "same as shipping" option at checkout. See Understanding Redundant Entry (opens in a new tab).
The Level AAA additions
Most laws don't require AAA. The two Enhanced criteria, 2.4.12 and 3.3.9, are stricter versions of 2.4.11 and 3.3.8.
2.4.13 Focus Appearance (opens in a new tab) is a cheap upgrade: a solid 2 pixel outline with an offset, in a color that contrasts with both the control and the page.
What WCAG 2.2 removed
4.1.1 Parsing is obsolete (opens in a new tab) because browsers and screen readers now handle markup consistently. Duplicate IDs and broken nesting are still caught by criteria such as 4.1.2 Name, Role, Value.
How to test your site for WCAG 2.2
- Scan every template. The ComplyMo Agent checks WCAG 2.2 on a schedule and keeps a dated record.
- Tab through with a sticky header visible. Nothing focused should vanish behind it.
- Measure small targets with the browser's element inspector.
- Log in with a password manager. Paste must work.
Go deeper with the W3C's How to Meet WCAG quick reference (opens in a new tab) and evaluation approaches (opens in a new tab).
Where to start this week
Fix the three issues that hit most sites: focus hidden under sticky headers, tap targets under 24 pixels, and login forms that block paste. Then cover the older failures in our guide to ADA website compliance in 2026, or start a free trial and run a WCAG 2.2 audit.
General information, not legal advice. Confirm your obligations with counsel.
