WCAG 2.2 Has 9 New Criteria — Most Scanners Still Miss Them. Here's What They Are and How to Fix Them

WCAG 2.2 shipped back in October 2023 with 9 new success criteria on top of WCAG 2.1. Almost two years later, most automated accessibility scanners still only catch one or two of them — the rest get punted to "manual review."

We just wrote up a deep dive into all 9 new criteria: what each one means in plain English, the most common real-world violations, and how to fix them. It's useful as a checklist regardless of which tools you use.

Here are the 3 highest-impact things you can check right now:

1. Your login form — Does autocomplete="current-password" exist? Does paste work on the password field? If you're blocking paste or setting autocomplete="off", you're failing 3.3.8 (Accessible Authentication).

2. Your help link — Is it in the same spot (header/footer) on every page? If it's in the nav on one page and buried in the body on another, that's a 3.2.6 (Consistent Help) issue.

3. Any drag interaction — Can a keyboard user do the same thing without dragging? If your Kanban board or sortable list has no keyboard alternative, that's a 2.5.7 (Dragging Movements) failure.

The full article covers all 9 criteria including Focus Not Obscured, Focus Appearance, Target Size (Minimum), Redundant Entry, and both levels of Accessible Authentication — with code examples and fixes for each.

👉 Read the full breakdown here

Would love to hear from anyone who's been auditing against WCAG 2.2 — what's been the hardest criterion to get right on your projects?