What Changed in EN 301 549 V4.1.1 (WCAG 2.2)
The European accessibility standard was updated in September 2026. Here is what changed for web content, what it means for the European Accessibility Act, and what to test now.
The short answer
EN 301 549 V4.1.1 was published in September 2026. Its requirements for web content are based on WCAG 2.2 AA, where the current version, V3.2.1, is based on WCAG 2.1 AA. It adds six WCAG 2.2 criteria for web content, drops the obsolete Parsing criterion and updates the user preferences requirements. Until the European Commission cites V4.1.1 in the Official Journal of the EU, V3.2.1 remains the version that gives a presumption of conformity with the European Accessibility Act.
Why the version matters
EN 301 549 is the European standard for ICT accessibility. Following a version of it that the Commission has formally cited gives you a presumption of conformity with laws such as the European Accessibility Act and the Web Accessibility Directive. That is why V3.2.1 still counts today, even though V4.1.1 exists.
The six WCAG 2.2 criteria V4.1.1 adds for the web
| Criterion | Level | What it requires | What to check |
|---|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | A focused item is not entirely hidden by other content. | Tab through pages with sticky headers, cookie banners and chat bubbles. |
| 2.5.7 Dragging Movements | AA | Anything done by dragging also works with a single click or tap. | Price sliders, sortable lists and drag-and-drop uploads. |
| 2.5.8 Target Size (Minimum) | AA | Pointer targets are at least 24 by 24 CSS pixels, with exceptions. | Small icon buttons, quantity steppers and close buttons. |
| 3.2.6 Consistent Help | A | Help options appear in the same place across pages. | Contact link, chat and FAQ position on every template. |
| 3.3.7 Redundant Entry | A | Users aren't asked to re-enter information they already provided in the same process. | Checkout address, billing and shipping, multi-step forms. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logging in doesn't depend on remembering or transcribing something, unless there is an alternative. | Password fields that block paste or password managers, and CAPTCHA puzzles. |
What was removed
V4.1.1 drops the Parsing criterion (4.1.1 in WCAG 2.1), which WCAG 2.2 removed because modern browsers and assistive technologies handle parsing errors. V3.2.1 still lists it, which is why I check Parsing for engagements under that version.
What to do now
- Test against WCAG 2.2 AA. It covers the web requirements in V4.1.1 and, apart from Parsing, those in V3.2.1, so one round of testing serves both.
- Fix the six new criteria first if you have a store, because sticky headers, sliders, small icon buttons and checkout forms are common failures.
- Keep your accessibility information current. If you publish a conformance statement, note which version of the standard you tested against.
- Watch for the Commission's citation of V4.1.1 in the Official Journal, which is when it starts to give a presumption of conformity.
Sources
- European Commission, AccessibleEU: EN 301 549 has been updated (7 September 2026)
- ETSI EN 301 549 V4.1.1 (2026-09)
For the full picture, see the EU audit page and the European Accessibility Act checklist for online stores.
This article is general information, not legal advice. For questions about your legal obligations or a claim you have received, talk to an attorney.