Quick answer
WCAG 2.2 is the latest version of the Web Content Accessibility Guidelines, published by the W3C in 2023. It adds new success criteria on focus visibility, target size, dragging and sign-in, and builds on earlier versions. Level AA is the common benchmark.
Key takeaways
- WCAG 2.2 builds on 2.0 and 2.1.
- Level AA is the usual target.
- It adds criteria for mobile use and cognitive load.
- Combine automated checks with manual testing.
What is new in WCAG 2.2?
| Criterion | In plain terms |
|---|---|
| Focus not obscured | Keyboard focus should not be hidden by sticky headers |
| Target size (minimum) | Tap targets at least 24 by 24 CSS pixels |
| Dragging movements | Offer a simple alternative to dragging |
| Consistent help | Keep help options in a consistent place |
| Redundant entry | Do not ask for the same information twice |
| Accessible authentication | Do not rely on memory tests to sign in |
Why does it matter?
- Many Australians live with a disability.
- The Disability Discrimination Act applies to websites.
- Accessible sites are easier for everyone, including on mobile.
- Clear structure also helps search engines.
What should you fix first?
- Colour contrast of at least 4.5 to 1 for body text.
- Full keyboard access and visible focus.
- Alt text for meaningful images.
- Labels on every form field.
- Headings in logical order.
- Captions for video.
How do you test?
Run an automated tool, then check manually. Tab through every page without a mouse, zoom to 200 percent and try a screen reader.
Automated tools find only a portion of issues, so manual checks are essential.
Make it part of the process
Add accessibility to design reviews and your definition of done. Building in WCAG 2.2 from the start is far easier than fixing a finished site.
Quick wins you can do this week
- Make sure your sticky header does not cover focused links.
- Enlarge small tap targets.
- Add visible labels to forms.
- Allow password managers and pasting in login fields.
Each fix helps real people straight away. Keep a simple log of changes, because it will help when you review progress.
Bottom line
Accessibility helps every visitor. Fix the basics first: contrast, keyboard use, labels and clear structure, then test with real assistive technology.
Sources and further reading
- W3C: Web Content Accessibility Guidelines 2.2
- W3C: What's new in WCAG 2.2
- Australian Human Rights Commission: Disability
Checked against the sources above and our own project experience. Last reviewed 7 October 2026.
