EN 301 549 V4.1.1: What Changes for Online Shops

This article puts EN 301 549 V4.1.1 into context. It shows what changes compared with the previous version, which six success criteria are new, when the standard takes legal effect and what online shop operators should check now. The research is current as of October 23, 2026. The assessment of its legal effect may change once the European Commission lists the standard in the Official Journal.

What does EN 301 549 V4.1.1 change compared with the previous version?

EN 301 549 V4.1.1 raises the requirements for web content from WCAG 2.1 to WCAG 2.2, in each case at levels A and AA. According to the National Disability Authority (September 2, 2026), this also applies to the clauses on documents and software. Accessibility.build assigns them to clauses 9 (web), 10 (non-web documents) and 11 (software). The previous version, V3.2.1, dates from 2021 and is based on WCAG 2.1.

According to Davis Wright Tremaine (September 18, 2026), the standards organizations formally adopted V4.1.1 on August 24, 2026 and published it shortly afterwards. Besides the move to WCAG 2.2, the sources we read mainly name three changes:

• ✓ EAA mapping: V4.1.1 is the first version designed for the European Accessibility Act. A new annex maps the requirements of the law to the clauses of the standard (National Disability Authority), and the standard also describes a method for assessing whether individual products and services conform (Davis Wright Tremaine).
• ✓ Real-time communication: Clause 6 has been expanded significantly (Deque, September 8, 2026). It mainly affects telephony, messaging, contact center and video conferencing products. For a typical online shop, it is rarely the focus.
• ✓ User preferences: According to the analysis by Accessibility.build (as of October 19, 2026), web pages should not override users' display settings, such as forced colors, without good reason. The new clause is numbered 9.7.

Deque stresses an important distinction: meeting WCAG 2.2 AA is not the same as meeting EN 301 549 V4.1.1. For websites and digital documents, the difference from the previous version consists mainly of the new WCAG 2.2 criteria. Anyone offering products with real-time communication or hardware must also observe further clauses.

Which six WCAG 2.2 criteria are new?

Deque names six new WCAG 2.2 success criteria at level A and AA (article of September 8, 2026). The table summarizes them and adds one e-commerce scenario for each. The scenarios are examples and do not describe real cases.

According to Accessibility.build, anyone who already meets WCAG 2.1 AA only needs to add these six criteria. The former criterion 4.1.1 Parsing has been removed. Deque points out that the new success criteria can reveal problems in components that passed before. That reflects a higher bar, not a step backwards.

Two details help with the assessment. For focus, level AA requires that an element is not entirely hidden, so partial overlap still passes. For target size, the criterion has exceptions, including sufficient spacing, inline links, equivalent controls and cases where the browser determines the size (Accessibility.build). For authentication, Accessibility.build lists exceptions for an available alternative, for assistive mechanisms, for object recognition and for personal content.

In our assessment, half of the criteria concern processes rather than individual pages. Consistent help, redundant entry and accessible authentication can therefore only be checked by walking through the cart, checkout and customer account. Testing the home page is not enough. Our lexicon explains what level AA means in detail under WCAG level AA. For a practical guide, see our article Achieving WCAG compliance step by step.

When does EN 301 549 V4.1.1 take legal effect?

EN 301 549 V4.1.1 is not legally binding yet. A harmonized standard triggers the presumption of conformity under Section 4 of Germany's Accessibility Strengthening Act (BFSG) only once its reference is published in the Official Journal of the European Union. The sources we read had not reported such a publication for V4.1.1 as of October 23, 2026. Deque describes three steps:

• ✓ Publication: The standard has been available since September 2, 2026.
• ✓ Citation in the Official Journal: Only this creates the presumption of conformity. It is expected for the end of 2026.
• ✓ Reference in national law: Member states transpose the directive and decide when they expect conformity.

The sources contradict each other on the timing of the citation. The National Disability Authority expects it on December 16, 2026, while Deque names around November 30, 2026. Accessibility.build, which analyzed the text of the standard, classifies November 30 as a deadline for national standards bodies and not as a date in the Official Journal. A binding date is therefore not documented.

The previous version, V3.2.1, is published in the Official Journal through Implementing Decision (EU) 2018/2048 as amended by Decision (EU) 2021/1339 (EUR-Lex). That decision was adopted in support of Directive (EU) 2016/2102 for public sector bodies. Accessibility.build concludes that no version of the standard has so far been cited under the European Accessibility Act. Other sources describe V3.2.1 more loosely as the current reference. How this works out in detail is not conclusively settled. The Commission's decision on citation under the EAA will be decisive.

The Federal Agency for Accessibility (Bundesfachstelle Barrierefreiheit) writes on its page on norms and standards (last updated July 27, 2026) that, until the planned harmonized standards are published in the Official Journal, the current EN 301 549 and the WCAG serve as the relevant guidance for implementing the BFSG. Without the presumption of conformity, accessibility can also be achieved in other ways. The economic operator must then prove conformity itself. Section 3 of the ordinance to the BFSG also requires the state of the art to be observed and assigns the Bundesfachstelle the task of publishing the standards to be observed.

Deque also points out that in member states whose law names the standard without a version number, a new version can become the benchmark without new legislation. Whether authorities in Germany already regard WCAG 2.2 AA as the state of the art within the meaning of Section 3 BFSGV has not been clarified. For enforcement in other EU countries, see our article One year of the European Accessibility Act: enforcement in Europe. The interim review of BFSG market surveillance summarizes the situation in Germany.

What online shop operators should check now

There is no new deadline, but there is a clear planning target: new projects, relaunches and larger theme changes should be tested against WCAG 2.2 AA. The National Disability Authority recommends factoring WCAG 2.2 AA and the new requirements of the standard into planning and procurement now. Deque advises building and testing against V4.1.1 anything that is meant to last into next year.

The following list shows which areas of an online shop are typically affected. The examples are scenarios, not case reports.

• ✓ Focus and overlays (2.4.11): Sticky headers, cookie banners and chat widgets can hide focused elements. While tabbing through product page, cart and checkout, check that every element stays visible. Background is available in our lexicon pages on keyboard accessibility and the focus indicator.
• ✓ Click targets (2.5.8): Quantity fields, remove icons, filters and icons should be at least 24 by 24 CSS pixels or have enough spacing. The criterion itself defines the exceptions.
• ✓ Checkout (3.3.7 and 3.2.6): Data already entered, such as the delivery address, should be carried over or offered for selection. The link to help should appear in the same place on every page.
• ✓ Login (3.3.8): Customer accounts and logins should be usable without cognitive test tasks. A CAPTCHA that requires typing needs an alternative.
• ✓ Dragging movements (2.5.7): Price sliders, image galleries and configurators with drag and drop need a way to operate them with a single click.
• ✓ Documents in the online shop: Manuals, data sheets or invoices as PDFs also fall under the clauses of EN 301 549 on documents, which were likewise raised to WCAG 2.2. Basics are covered in our lexicon page on PDF accessibility.
• ✓ Documentation: Test reports and the accessibility statement should state which version of the standard and which WCAG version were tested against. Davis Wright Tremaine advises reviewing compliance documentation for the new version of the standard.

SiteCockpit: keeping accessibility in view

Standards, laws and shop systems keep changing, so accessibility is not a one-off project. Every theme change in the online shop, every new app and every banner can worsen criteria such as focus, click target size or checkout flows again. A fixed process of checking, fixing and checking again helps.

• ✓ easyMonitoring: monitors your website continuously, finds errors such as invisible keyboard focus, weak contrast or missing form labels, and delivers prioritized to-dos.
• ✓ Manual audits: complement ongoing checks where flows such as checkout and login have to be assessed from start to finish.
• ✓ easyStatement: creates an up-to-date accessibility statement based on real test results.

A dashboard with conformance scores shows whether your website improves or worsens after changes. It does not replace a legal statement of conformity.

What makes sense now

No reason to panic, but real planning needs: EN 301 549 V4.1.1 is published, but it has no legal effect yet. The presumption of conformity under the European Accessibility Act arises only once the standard is cited in the Official Journal of the European Union. Germany's Accessibility Strengthening Act refers to harmonized standards for this, and the specific requirements are set out in the ordinance to the BFSG. Anyone implementing WCAG 2.2 AA today is already working to the level the Bundesfachstelle announces for the updated standard. The outlook on WCAG 3.0 is a separate matter, see our article WCAG 3.0: what businesses should prepare for now.

• ✓ Establish your status: Start with the Livecheck and check the cart, checkout and login specifically for the six new criteria.
• ✓ Fix the most common errors: Begin with hidden focus elements, click targets that are too small and duplicate entries in the checkout.
• ✓ Keep it in view: Follow the citation in the Official Journal and keep testing and documentation up to date.

Take it step by step. With easyMonitoring you keep track of your website after every change without having to set up each check from scratch.

Note: This article provides general information on the legal situation (as of 10/23/2026) and does not replace individual legal advice.