WCAG 2.2 builds on 2.1 rather than replacing it. If you were already targeting 2.1 AA, most of your work carries over. The new success criteria mostly tighten up areas that were previously ambiguous.
Focus Not Obscured
A newly focused element, like a form field after tabbing to it, can no longer be completely hidden behind a sticky header or cookie banner. If your site has sticky UI, this is worth testing directly with a keyboard.
Target Size (Minimum)
Interactive targets need to be at least 24x24 CSS pixels in most cases, close to but not identical to the 48x48px touch-target guidance many mobile design systems already use.
Consistent Help
If you offer a help mechanism, such as a contact link, chat widget, or FAQ link, it needs to appear in the same relative place across pages, not move around.
- Test with a keyboard only (no mouse) across your whole site
- Check that focus is never fully hidden behind sticky headers or banners
- Measure your smallest tap targets against the 24px minimum