Home › WCAG 2.2 checklist

WCAG 2.2 checklist: what changed and what to check

WCAG 2.2 (the current W3C recommendation) adds nine success criteria on top of 2.1. Here's what's new, in plain English.

The nine new WCAG 2.2 success criteria

• 2.4.11 Focus Not Obscured (Minimum): when an element is focused, it can't be fully hidden behind a sticky header, cookie bar or chat widget.
• 2.4.13 Focus Appearance: the keyboard focus indicator must be large and contrasty enough to actually see.
• 2.5.7 Dragging Movements: anything you do by dragging (sliders, reordering) must also work with a simple click/tap alternative.
• 2.5.8 Target Size (Minimum): tap targets should be at least 24×24 CSS pixels (or have enough spacing).
• 3.2.6 Consistent Help: help/contact mechanisms appear in a consistent place across pages.
• 3.3.7 Redundant Entry: don't make users re-enter information they already gave in the same process.
• 3.3.8 Accessible Authentication (Minimum): no cognitive test (remembering, transcribing, solving a puzzle) required to log in; allow paste and password managers.
• Plus 2.4.12 & 3.3.9 at AAA: enhanced focus and authentication.

How much of this can a scanner check?

Automated tools reliably cover the objective 2.2 additions like target size and focus contrast, plus everything carried over from 2.1 (contrast, names, roles, alt text). The judgement-based criteria (consistent help, redundant entry) need a human pass. Honest scope: automated testing catches roughly 30-40% of WCAG issues, and we surface those and help you triage the rest, no fake "compliant" badge.

Where 2.2 fits the bigger picture

Use this alongside our ADA compliance checklist. If you're US public-sector, map it to Section 508; if you sell in the EU, the European Accessibility Act references these standards.

Scan your site against WCAG 2.2

AdaClear runs an up-to-date WCAG 2.1/2.2 ruleset, gives you a prioritized fix list, and re-scans continuously. Start with a free scan below.