Devii · UI & UX · 2026-03-18 · 7 min read
WCAG 2.2 In 2026: Targets, Auth, Dragging-And How Teams Actually Audit
WCAG 2.2 is a W3C Recommendation (2023); in 2026 it is a common contract baseline alongside EN 301 549 and evolving national rules.
The W3C published **WCAG 2.2** as a Recommendation in **September 2023**. It adds success criteria such as **2.5.8 Target Size (Minimum)** for pointer targets, **3.3.7 Redundant Entry**, and **3.3.8 Accessible Authentication** (with a timed-exception variant). By **2026** most public-sector and enterprise RFPs reference **2.2** explicitly-treat 2.1-only checklists as incomplete for new work.
Use the official **quick reference** and **understanding** documents so implementations map to normative text, not vendor marketing summaries. Map criteria to components in your design system (buttons, modals, auth flows) rather than auditing page-by-page ad hoc.
Pair WCAG work with **assistive technology** smoke tests (screen readers, keyboard-only, voice control where relevant). Automated scanners catch only a fraction of failures-especially focus order, live regions, and custom component state.