Nodea — logo

WCAG 2.2

WCAG 2.2 is the latest published version of the WCAG guidelines, which specify how to create accessible web content. It does not replace earlier versions but extends them: it stays backward compatible and adds several new success criteria, clarifying requirements in areas that were previously not covered thoroughly enough.

What WCAG 2.2 brings

The new criteria emphasise, among other things, touch and motor support: a minimum size and spacing for clickable areas, so they can be tapped accurately without mistakes. Requirements for focus indicator visibility are also clarified — a user navigating by keyboard must clearly see which element is active. Further guidelines address consistent help available in the same place across subpages, and reducing situations in which a user must repeatedly enter the same data during a process.

Significance for sites

WCAG 2.2 is gradually becoming the reference point in accessibility regulations and audits, so new projects are worth planning around it from the outset. The changes directly improve UX — larger touch areas and clear focus are convenient for everyone, not only for people with disabilities, and they force more careful UI design. For site owners, conformance with WCAG 2.2 is both a matter of meeting obligations arising from digital accessibility and a real benefit in the form of a more usable, more widely accessible product. For teams, this means it is worth following the evolution of the guidelines and treating accessibility as an element of product quality rather than a one-off box to tick at launch.

Powiązane pojęcia

Najczęstsze pytania

Does WCAG 2.2 replace WCAG 2.1?

No, it extends it — WCAG 2.2 is backward compatible and adds new success criteria. A site meeting WCAG 2.2 at a given level also meets earlier versions at that level.