EU accessibility standard EN 301 549 moves to WCAG 2.2

The technical standard that defines digital accessibility across the EU has a new version, and it now aligns with WCAG 2.2. EN 301 549 V4.1.1 adds six success criteria that were not in the version most multi-location brands built their location pages and store locators against. Publication is not the same as legal effect, so the practical question for a central team is what to fix now and what to plan for.

What happened

ETSI published EN 301 549 V4.1.1 in September 2026, revising the requirements for web content, documents and software to match WCAG 2.2. WCAG 2.2 introduces six additional Level A and AA success criteria beyond WCAG 2.1: Focus Not Obscured (Minimum), Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry, and Accessible Authentication (Minimum). EN 301 549 is maintained jointly by ETSI, CEN and CENELEC as the harmonised European standard for accessibility.

Publication by the standards bodies is a separate step from the version being cited in the Official Journal of the European Union, which is what confers a presumption of conformity with the EU’s accessibility requirements. The underlying obligations already apply to covered organisations, so the new criteria signal where the conformity benchmark is moving rather than switching any duty on or off.

Why it matters

EN 301 549 is the reference standard used to demonstrate conformity with the EU’s accessibility rules, including the Web Accessibility Directive and the European Accessibility Act. The WCAG 2.2 additions are practical rather than abstract. Target Size and Dragging Movements govern pointer interactions (touch, mouse or pen), Consistent Help and Redundant Entry govern forms, and Accessible Authentication governs login. For a store locator or a set of location pages, these are exactly the interactions a customer performs to find or contact a branch.

What this means for multi-location brands

For a chain running hundreds or thousands of location pages, accessibility is an estate-wide property, not a page-by-page fix. WCAG 2.2’s additions land on shared components: the map and filter controls in a store locator, the tap-target size on a location page, and the contact and login forms that repeat across every site. Correct them once in the template and the fix propagates to every location. Miss them and the same defect repeats at scale, so a single complaint can surface a fault that runs across the whole estate.

Treat the new version as a planning input. Audit the shared components behind your location listings against the six new criteria now, prioritise the ones customers touch most (tap targets, forms, help), and keep one source of truth for location data and page structure so remediation is a template change rather than a separate project in every market. Enterprise brands operating across the EU should track when the updated standard is cited in the Official Journal, because that citation is what makes conforming to the new version a presumption of conformity. A coordinated European presence makes that far easier to manage than patching country by country.

The bottom line

The direction is set: the EU’s accessibility standard is moving to WCAG 2.2. The multi-location brands that audit their shared templates against the new criteria now will not be scrambling when that version becomes the reference for presumption of conformity.