The Web Content Accessibility Guidelines (WCAG) 2.2 became a W3C Recommendation in October 2023. If your last accessibility audit was against WCAG 2.0 or 2.1, your next redesign is the right moment to catch up. WCAG 2.2 keeps everything from 2.1 and adds nine new success criteria. Six of them are at levels A and AA, the levels most Canadian rules and procurement contracts point to.
Here is what each of those six means in practice, and where we see teams trip up.
1. Focus not obscured (AA)
When someone moves through a page with the keyboard, the element they are on must not be completely hidden by something else. The usual culprits are sticky headers, cookie banners and chat widgets that cover the button the person just tabbed to. Fix it with scroll padding, by making banners dismissible, or by keeping sticky bars small.
2. Dragging movements (AA)
Anything you can do by dragging must also be possible with a single tap or click. Think sliders, reorderable lists, map pins and file drop zones. Add plus and minus buttons, up and down controls, or a regular file picker next to the drag area.
3. Target size, minimum (AA)
Buttons and links need to be at least 24 by 24 CSS pixels, or have enough space around them that a 24-pixel circle doesn't overlap a neighbouring target. Small icon buttons, close buttons and links packed tightly in tables fail most often. Inline links inside a sentence are exempt.
4. Consistent help (A)
If you offer help, such as a phone number, a contact link or a chat, put it in the same place on every page where it appears. People who struggle with a task should not have to hunt for help in a different spot each time.
5. Redundant entry (A)
Don't ask people for the same information twice in one process. If they gave their address on step two, fill it in for them on step four, or let them pick it. Exceptions are narrow: security re-entry and information that is no longer valid.
6. Accessible authentication, minimum (AA)
Logging in must not depend on a memory or puzzle test, unless there is another way to do it. In practice: allow password managers and pasting, don't block autofill, and offer an alternative to image puzzles. Email links, passkeys and one-time codes that can be copied all help.
One criterion was removed
WCAG 2.2 also drops 4.1.1 Parsing, which checked for HTML errors that modern browsers and assistive technology now handle on their own. That doesn't make valid code optional; it just means it is no longer tested on its own.
What to do next
- Add the six criteria to your design system's checklist, so new components meet them by default.
- Check your sticky header, cookie banner and chat widget against focus not obscured.
- Measure your smallest buttons and icon links.
- Walk through your longest form and look for anything you ask twice.
- Try logging in with a password manager and with paste.
Meeting WCAG 2.2 AA also meets 2.1 and 2.0, so targeting 2.2 now saves you a second round of fixes later. If you'd like a second pair of eyes, our audits test against WCAG 2.2 AA and include testing with people who use assistive technology.