WCAG 2.2 became a W3C Recommendation in October 2023, adding new success criteria that matter a lot for designers. Here's what changed and a practical checklist you can use on every project.
What's new in WCAG 2.2
| Criterion | Level | What it means for designers |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | Keyboard focus mustn't be fully hidden by sticky headers, banners or chat widgets |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA | Focus mustn't be hidden at all |
| 2.4.13 Focus Appearance | AAA | Focus indicators must be large and high-contrast enough |
| 2.5.7 Dragging Movements | AA | Anything done by dragging needs a single-pointer alternative, like buttons |
| 2.5.8 Target Size (Minimum) | AA | Targets at least 24 × 24 CSS pixels, with some exceptions |
| 3.2.6 Consistent Help | A | Help options appear in the same place across pages |
| 3.3.7 Redundant Entry | A | Don't make people re-enter information they already gave |
| 3.3.8 Accessible Authentication (Minimum) | AA | Login can't depend on memory or puzzles alone; allow paste and password managers |
| 3.3.9 Accessible Authentication (Enhanced) | AAA | Stricter version of the above |
WCAG 2.2 also removed 4.1.1 Parsing, which is no longer needed.
Core checklist for every screen
Perceivable
- Text contrast at least 4.5:1 (3:1 for large text). See the colour contrast guide.
- UI components and meaningful icons at least 3:1.
- Meaningful images have alt text.
- Colour is never the only way to show information.
- Videos have captions.
Operable
- Everything works with a keyboard.
- Focus is clearly visible and not hidden by sticky elements (new in 2.2).
- Touch targets at least 24 × 24, ideally 44 to 48 (new in 2.2).
- Dragging has a button alternative (new in 2.2).
- Animations respect reduced motion. See accessible motion design.
Understandable
- Clear labels and instructions on forms.
- Errors explain what went wrong and how to fix it.
- Help is in a consistent place (new in 2.2).
- No re-entering the same information (new in 2.2).
- Login allows paste and password managers (new in 2.2).
Robust
- Components have correct names, roles and states for screen readers.
Tip
Check the sticky header, cookie banner and chat widget on every page with a keyboard. They're the most common cause of the new "focus not obscured" failures.
FAQ
What is new in WCAG 2.2?
New success criteria for focus not being obscured, focus appearance, dragging alternatives, minimum target size, consistent help, avoiding redundant entry and accessible authentication. The obsolete 4.1.1 Parsing criterion was removed.
What is the WCAG 2.2 minimum target size?
Success criterion 2.5.8 requires targets to be at least 24 × 24 CSS pixels at Level AA, with exceptions such as enough spacing around smaller targets or inline links in text.
Is WCAG 2.2 required by law?
Requirements depend on the country and sector. Many laws and policies reference WCAG at Level AA, and newer ones increasingly point to WCAG 2.2. Check the rules that apply to your organisation.
Key takeaways
- WCAG 2.2 adds new criteria for focus, dragging, target size, help, redundant entry and login.
- Check sticky elements don't hide keyboard focus.
- Make targets at least 24 × 24, ideally bigger.
- Allow paste and password managers at login.
- Use the checklist on every screen, not just before launch.
What to do next
Run the new WCAG 2.2 checks on your login and checkout flows first. For a full accessibility and usability review, see our UX audit service.