Insights
WCAG 2.2: what actually changed, in plain language
WCAG 2.2 is the current version of the Web Content Accessibility Guidelines. If you have been working to WCAG 2.1, the good news is that 2.2 is an addition, not a rewrite. It keeps everything from 2.1 and adds nine new checks. Here is what they cover, in plain terms.
The theme: less friction for more people
Most of the new criteria help people with limited mobility, low vision, and cognitive differences. The pattern is simple. Do not make people work harder than they need to.
The new checks, briefly
- Focus is always visible and not hidden. When someone tabs through your page, the highlighted element must not be covered by a sticky header or a cookie banner.
- Bigger, easier targets. Buttons and links should be large enough, or spaced enough, to tap without hitting the wrong one.
- Dragging has an alternative. If something needs a drag, there must be a simple tap or click way to do it too.
- Do not make people remember things. Avoid forcing users to memorize a code from one step to use in the next. Let them copy it, or carry it forward for them.
- Do not make people re-enter information they already gave you earlier in the same process.
- Help is in a consistent place. If you offer help, keep it in the same spot across pages.
- Accessible authentication. Do not force people to solve a puzzle or transcribe something just to log in. Allow password managers and simpler options.
What to do about it
You do not need to panic. Start with an audit against WCAG 2.2 AA, get a prioritized list, and fix the highest-impact items first. Most sites that already meet 2.1 are a few focused changes away from 2.2.
If you want a clear read on where you stand, that is exactly what our audits give you.