WCAG 2.2 AA Checklist: The Practical Version for Teams
WCAG 2.2 Level AA adds new criteria for focus visibility, dragging, and target size on top of WCAG 2.1. This checklist groups the requirements under the four POUR principles so your team can test and fix systematically.
WCAG 2.2 became the recommended standard and adds nine new success criteria to WCAG 2.1. If you already conform to 2.1 AA, the jump to 2.2 AA is small but meaningful — especially around keyboard focus and touch targets. Here is a working checklist grouped by the four POUR principles.
Perceivable
- Every meaningful image has descriptive alt text; decorative images use empty alt.
- Color is never the only way information is conveyed.
- Text contrast is at least 4.5:1 (3:1 for large text); UI components and graphics meet 3:1.
- Content reflows to 320px width without horizontal scrolling or loss of content.
- Video has captions and audio has transcripts.
Operable
- All functionality works with a keyboard alone, with no traps.
- Focus order is logical and the focus indicator is clearly visible (2.2: Focus Not Obscured).
- Interactive targets are at least 24×24 CSS pixels (2.2: Target Size Minimum).
- Any drag operation has a single-pointer alternative (2.2: Dragging Movements).
- Users are not required to remember information across steps (2.2: Redundant Entry, Accessible Authentication).
Understandable
- The page language is set programmatically.
- Labels and instructions are provided for inputs; errors are identified in text.
- Navigation is consistent across pages; components that repeat behave consistently.
- Help mechanisms (contact, FAQ) appear in a consistent location (2.2: Consistent Help).
Robust
- Markup is valid and elements are properly nested.
- Name, role, and value are exposed for all UI components (correct ARIA).
- Status messages are announced to assistive tech without moving focus.
What's new in WCAG 2.2 specifically
The headline additions at Level AA are Focus Not Obscured (Minimum), Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry, and Accessible Authentication (Minimum). Most teams find target size and focus visibility are the criteria they most often fail.
Tip: automated scanners reliably catch contrast, missing labels, and target-size issues. Keyboard and focus checks still need a human pressing Tab through the page.
How to use this checklist
- Run an automated scan to clear the machine-detectable items in bulk.
- Walk the page with only a keyboard, then with a screen reader.
- Fix issues in components (design system) so fixes propagate everywhere.
- Re-scan on a schedule to catch regressions.
Frequently asked questions
- What is the difference between WCAG 2.1 and 2.2?
- WCAG 2.2 keeps all of 2.1 and adds nine new success criteria, including Focus Not Obscured, Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry, and Accessible Authentication.
- What does WCAG AA require for color contrast?
- At least 4.5:1 contrast for normal text, 3:1 for large text (18pt or 14pt bold), and 3:1 for meaningful UI components and graphical objects.
- Can a tool check my whole site against WCAG 2.2 AA?
- Automated tools catch roughly a third of issues — contrast, missing labels, target size, and structure. The rest, like logical focus order and meaningful alt text, require human review.
See where your site stands — free
Run an instant WCAG 2.2 AA scan and get a severity-ranked report with AI fix suggestions in seconds. No overlay, no false promises.