
Architecture, performance, security — platforms built to last
EN 301 549 v4.1.1: WCAG 2.2 becomes the European benchmark, and what merchants should prepare
By SMART SOLID SOLUTIONS
On 2 September 2026, ETSI published version 4.1.1 of the EN 301 549 standard, the European technical text on the accessibility of digital products and services. Adopted on 24 August, it follows the March 2021 edition. For an online store it changes two things: the technical baseline moves from WCAG 2.1 to WCAG 2.2, and the standard is now written for the European Accessibility Act (EAA), the directive that has applied to e-commerce since 28 June 2025.
What the new version says
- WCAG 2.2 everywhere. The chapters on the web, documents and software, mobile apps included, now point to WCAG 2.2 level AA. Six criteria are added; the former criterion 4.1.1 on code parsing is gone.
- An explicit bridge to the EAA. A new annex maps the requirements of the directive to the clauses of the standard. E-commerce is named there, with three points of attention: information about the accessibility of the products and services sold, the functions for identification, security and payment, and the identification methods, electronic signatures and payment services themselves.
- User preferences. New for the web: a page must neither block nor override the accessibility settings chosen in the browser (contrast, text size, colour filters), unless its function requires it.
- The whole journey. The standard carries over the WCAG rule on complete processes: when a page is part of a series of steps, every step has to conform. A checkout is therefore judged as one block.
The timeline, without the drama
Publication creates no new deadline. The European Commission’s AccessibleEU centre made that clear on 7 September: until version 4.1.1 is cited in the Official Journal of the European Union, edition 3.2.1, built on WCAG 2.1, remains the reference. A harmonised standard also remains a voluntary way to demonstrate conformity; it is the citation that attaches a presumption of conformity with the directive.
Three markers are worth knowing:
- 30 November 2026: the deadline set in the standard for its announcement by national standards bodies.
- 16 December 2026: the date on which Ireland’s National Disability Authority (NDA) expects the citation in the Official Journal. It is a forecast, not a commitment from the Commission.
- 31 May 2027, then 31 May 2028: publication of the national versions, then withdrawal of conflicting national standards.
In other words, the yardstick of your audits should change within weeks, not your legal obligations. But an audit report, a specification or an agency contract written today against WCAG 2.1 will be dated the day it is delivered.
Six criteria aimed at the checkout
- Focus not obscured (2.4.11). The element that receives keyboard focus must not be entirely hidden by a sticky header, a cookie banner or a chat bubble.
- Dragging movements (2.5.7). Anything done by dragging (price slider, carousel, reordering a wish list) must also be doable with a simple click or tap.
- Target size (2.5.8). At least 24 by 24 CSS pixels, or enough spacing: quantity buttons, colour swatches, the remove cross in the cart.
- Consistent help (3.2.6). The contact link or the chat stays in the same place from one page to the next.
- Redundant entry (3.3.7). Information already given in the journey is not asked for again: the shipping address is reused for billing.
- Accessible authentication (3.3.8). Signing in does not rely on memory or transcription without an alternative: pasting and password managers work, and a type-what-you-see CAPTCHA is never the only way through.
What this changes for an e-commerce CTO
These criteria are not fixed page by page. They touch shared building blocks: the theme, the component library, the payment module, the bot protection, the chat tool. Three trade-offs follow.
- Fix at the source. A target that is too small or a hidden focus is corrected once in the component, not template by template. It is the strongest argument for funding a component foundation rather than scattered patches.
- Size up third-party debt. The standard explicitly targets identification and payment. If your payment provider, your social login or your bot protection fails, your journey carries the gap. Ask each vendor for its WCAG 2.2 AA conformance status, and a date.
- Update contracts and acceptance testing. Tenders, agency specifications, the teams’ definition of done: replace WCAG 2.1 with WCAG 2.2 AA and EN 301 549 v4.1.1, and add the six criteria to the checkout regression tests.
Where to start this week
- Rerun your last audit on the six new criteria only, limited to search, product page, cart, sign-in and payment. It is a targeted gap analysis, not a new full audit.
- Walk through the checkout with the keyboard while the cookie banner and the chat are open: a hidden focus shows up very quickly.
- Check that sign-in accepts pasting and autofill, and that the bot protection offers another way through.
- Do not forget documents: invoices, return slips and terms and conditions in PDF fall under the chapter on documents, which is also aligned with WCAG 2.2.
WCAG 2.2 has existed since October 2023; what is new this year-end is that Europe is making it its official yardstick. Teams that have handled these six criteria before the citation will enter 2027 with an up-to-date file; the others will discover the gap in their next audit.
Happy to help.
Let’s discuss your project.