WCAG 2.2 AA: The Complete Checklist

WCAG 2.2, published in October 2023, is the latest version of the Web Content Accessibility Guidelines. It adds 9 new success criteria to WCAG 2.1, bringing the total Level AA criteria count to 55.

What changed from WCAG 2.1

WCAG 2.2 added these new success criteria:

• •2.4.11 Focus Not Obscured (Minimum) (AA) — When a component receives focus, it's not entirely hidden by author-created content — (AA) — When a component receives focus, it's not entirely hidden by author-created content
• •2.4.12 Focus Not Obscured (Enhanced) (AAA) — No part of the focused component is hidden — (AAA) — No part of the focused component is hidden
• •2.4.13 Focus Appearance (AAA) — Focus indicators meet minimum size and contrast requirements — (AAA) — Focus indicators meet minimum size and contrast requirements
• •2.5.7 Dragging Movements (AA) — Any action that uses dragging can also be done with a single pointer — (AA) — Any action that uses dragging can also be done with a single pointer
• •2.5.8 Target Size (Minimum) (AA) — Interactive targets are at least 24x24 CSS pixels — (AA) — Interactive targets are at least 24x24 CSS pixels
• •3.2.6 Consistent Help (A) — Help mechanisms appear in the same relative order across pages — (A) — Help mechanisms appear in the same relative order across pages
• •3.3.7 Redundant Entry (A) — Information previously entered is auto-populated or available for selection — (A) — Information previously entered is auto-populated or available for selection
• •3.3.8 Accessible Authentication (Minimum) (AA) — No cognitive function test required for authentication — (AA) — No cognitive function test required for authentication
• •3.3.9 Accessible Authentication (Enhanced) (AAA) — Stricter version of 3.3.8 — (AAA) — Stricter version of 3.3.8

WCAG 2.2 also removed **4.1.1 Parsing** (which was about valid HTML) since modern browsers and assistive technologies handle malformed markup gracefully.

The four principles (POUR)

### Perceivable Content must be presentable to all users:

• •1.1.1 Non-text Content — All images, icons, and non-text content have text alternatives — — All images, icons, and non-text content have text alternatives
• •1.2.1-1.2.5 Time-based Media — Audio/video content has captions, audio descriptions, and transcripts — — Audio/video content has captions, audio descriptions, and transcripts
• •1.3.1-1.3.5 Adaptable — Content structure is programmatically determinable; meaningful sequence is preserved — — Content structure is programmatically determinable; meaningful sequence is preserved
• •1.4.1-1.4.13 Distinguishable — Color contrast ratios met (4.5:1 for text, 3:1 for large text); text resizable to 200%; content reflows at 320px width — — Color contrast ratios met (4.5:1 for text, 3:1 for large text); text resizable to 200%; content reflows at 320px width

### Operable Interface components must be operable:

• •2.1.1-2.1.4 Keyboard — All functionality available via keyboard; no keyboard traps — — All functionality available via keyboard; no keyboard traps
• •2.2.1-2.2.2 Enough Time — Users can extend time limits; auto-updating content can be paused — — Users can extend time limits; auto-updating content can be paused
• •2.3.1 Seizures — No content flashes more than 3 times per second — — No content flashes more than 3 times per second
• •2.4.1-2.4.11 Navigable — Skip links, meaningful page titles, logical focus order, visible focus indicators — — Skip links, meaningful page titles, logical focus order, visible focus indicators
• •2.5.1-2.5.8 Input Modalities — Touch targets adequate size; alternatives to complex gestures; dragging alternatives provided — — Touch targets adequate size; alternatives to complex gestures; dragging alternatives provided

### Understandable Content and interface must be understandable:

• •3.1.1-3.1.2 Readable — Page language specified; language of parts identified — — Page language specified; language of parts identified
• •3.2.1-3.2.6 Predictable — No unexpected context changes on focus/input; consistent navigation; consistent help placement — — No unexpected context changes on focus/input; consistent navigation; consistent help placement
• •3.3.1-3.3.8 Input Assistance — Error identification; labels and instructions; error suggestions; accessible authentication — — Error identification; labels and instructions; error suggestions; accessible authentication

### Robust Content must work with assistive technologies:

• •4.1.2-4.1.3 Compatible — All UI components have proper name, role, value; status messages programmatically determinable — — All UI components have proper name, role, value; status messages programmatically determinable

Testing approach

About 30% of WCAG criteria can be fully automated. Another 30% can be partially automated with manual verification. The remaining 40% require manual testing.

Access Audit handles the automated and partially automated checks, then provides structured manual testing checklists for the rest — giving you complete coverage across all criteria.