WCAG 2.2: what changes and why you should update your audit now

WCAG 2.2 became an official W3C recommendation in October 2023, but most product teams have not yet updated their audits. The most common reason I hear: “We did this last year with 2.1 — do we really have to redo it already?” The short answer is yes. The longer answer is: it depends on how exposed your product is to the patterns the new criteria address.

This article is not a list of all the new criteria with abstract explanations. It is a practical guide to understanding which criteria concretely affect the most common products, and how to approach the changes incrementally without blocking your development team.

The nine new criteria at a glance

WCAG 2.2 introduces nine new success criteria compared to version 2.1. Seven are at level A or AA — meaning they are required for standard conformance. Two are at level AAA. The most impactful ones are worth knowing well.

2.4.11 — Focus Not Obscured (AA). When a component receives keyboard focus, it must not be completely hidden by other content — a sticky banner at the top of the page, a notification bar at the bottom. This is the criterion I find violated most often in products with sticky headers.

2.4.13 — Focus Appearance (AA). The most technical and the most underestimated. The focus indicator must have a minimum area equal to the perimeter of the component multiplied by 2px, and a contrast ratio of at least 3:1 between focused and unfocused states. The classic 1px outline is no longer sufficient. You need a visible, thick ring with good contrast.

2.5.7 — Dragging Movements (AA). All functions that require dragging must have an accessible alternative that works with a single pointer. This affects sortable lists, custom sliders, calendars with drag-to-select, and any interface relying on drag gestures.

2.5.8 — Target Size (Minimum) (AA). The minimum clickable target must be at least 24×24 CSS pixels. Many common icon button patterns fall below this threshold.

3.3.7 — Redundant Entry (A). Information already entered in a multi-step process must not be requested again. This affects checkout flows, configuration wizards, and any multi-step form.

Where to look for the most common violations

Not all products are exposed in the same way. The high-risk patterns for WCAG 2.2 are:

• Navigation with sticky headers — frequent violation of 2.4.11
• Custom focus outlines removed or minimised — violation of 2.4.13
• Drag-and-drop without alternatives — violation of 2.5.7
• Icon buttons smaller than 24px — violation of 2.5.8
• Multi-step forms that re-ask for data — violation of 3.3.7

How to structure the update audit

There is no need to redo a full audit from scratch. The approach I use is a differential audit: start from the documentation of the existing 2.1 audit and verify specifically the nine new criteria, plus the removal of criterion 4.1.1 (Parsing), which WCAG 2.2 has officially deprecated.

The process follows four phases: inventory of at-risk patterns; manual keyboard testing; touch target measurement on mobile; review of multi-step flows.

Accessibility is not a sprint you do once. It is ongoing maintenance, like security. Every release can introduce new violations.

Focus Appearance in practice: the numbers

Criterion 2.4.13 requires a calculation. The formula: focus indicator area ≥ component perimeter × 2px. For a button measuring 120px×40px, the perimeter is 320px, so the minimum area must be 640px². A 3px outline is comfortably safe. A 1px outline — still the default for many teams — is not.

In practical terms, moving to a 2–3px ring with a contrasting colour is not a rewrite — it is a change to a few lines of CSS in the design system. If you are using a token system, updating the focus tokens globally is all it takes.

The European regulatory context

The European Accessibility Act came into force in June 2025 for digital products and services. The technical reference standard EN 301 549 cites WCAG 2.1 as the minimum baseline, but many national implementations are aligning with 2.2. Teams operating in regulated sectors — healthcare, finance, public administration — face a legal obligation that goes well beyond good design practice.

Updating your audit now is not just the right thing to do. It is also protection against growing legal exposure in a regulatory environment that is tightening fast.