NEW: AudioEye launches Agentic Audits and SDK MCP
Read moreEN 301 549 v4.1.1: What Changed and What It Means for You
EN 301 549 v4.1.1, published in September 2026, updates the EU accessibility standard to WCAG 2.2 and adds six new requirements. It isn’t legally required yet, so v3.2.1 still applies for now. Below, we’ll cover what changed, when it applies, and how to prepare.
Author: Missy Jensen, Senior Content Strategist: AI Search and Discovery
Published: 10/15/2026
)
For more than five years, accessibility in the EU had a fixed point of reference: EN 301 549 v3.2.1 and the Web Content Accessibility Guidelines (WCAG) 2.1 behind it. Teams built their audits, checklists, and roadmaps around it.
Meanwhile, the guidelines underneath it kept moving. The W3C published WCAG 2.2 in October 2023, adding new criteria for things like keeping focused items visible, making buttons easier to tap, and simplifying logins. For nearly three years, Europe’s official standard didn’t reflect those new criteria.
In September 2026, that changed. EN 301 549 v4.1.1 updates the standard to WCAG 2.2, adds six new requirements, and is the first version built for the European Accessibility Act (EAA). For now, v3.2.1 still applies, but the next benchmark is already here, and it’s worth understanding before it becomes official.
What Changed in EN 301 549 v4.1.1?
EN 301 549 v4.1.1(opens in a new tab)(downloads a file) replaces WCAG 2.1 with WCAG 2.2 as its benchmark for websites, software, and digital documents. In practice, that comes down to five changes: six new requirements, one removed requirement, user preference requirements, revised real-time text requirements, and a new annex tied to the EAA.
Six New Requirements from WCAG 2.2
The update adds six new accessibility requirements, all drawn from WCAG 2.2. Here’s what each one asks for:
Why Six and Not Nine?
WCAG 2.2 added nine new success criteria in total, but three of them are Level AAA. EN 301 549 builds on WCAG’s Level A and AA, so only the six at those levels carry over. The standard lists WCAG 2.2’s AAA criteria in an informative clause, meaning they’re guidance rather than requirements.
4.1.1 Parsing Has Been Removed
The update also removes the success criterion 4.1.1 Parsing, which required clean, error-free HTML markup. The W3C marked it obsolete in WCAG 2.2 because browsers now handle markup errors on their own, and assistive technologies get their information from the browser rather than reading the code directly.
This is the one change that reduces testing work. Keep in mind, though, that Parsing is still part of v3.2.1, which remains the current reference standard.
Better Support for Users’ Accessibility Preferences
EN 301 549 already required software to follow the settings people choose on their devices, such as color, contrast, font size, and focus cursor. Version 4.1.1 extends user preference requirements to web pages and non-web documents, so websites and documents must better respect the accessibility settings people have chosen.
Revised Real-Time Text Requirements
For communication tools, the requirements for real-time text (RTT), text that’s sent as it’s typed during a call, have been significantly revised. They now extend to total conversation, which combines video, real-time text, and voice in the same call.
A New Annex for the European Accessibility Act
EN 301 549 v4.1.1 is the first version developed specifically with the European Accessibility Act in mind. It includes a new annex (Annex ZB) that maps the standard’s requirements to the Act, plus new tables in clause A.2 for evaluating whether specific products and services conform. For private-sector teams, that makes the standard much easier to use as a compliance roadmap.
)
Is EN 301 549 v4.1.1 Legally Required Yet?
Not yet. Until the European Commission officially cites EN 301 549 v4.1.1 in the Official Journal of the European Union, EN 301 549 v3.2.1, based on WCAG 2.1 Level AA, remains the current reference for both the EAA and the Web Accessibility Directive(opens in a new tab).
The Official Journal is the EU’s official publication for laws and legal notices. A standard gains legal weight only when the Commission cites it. Here’s how that plays out:
Today: EN 301 549 v3.2.1 is the version organizations should measure against.
Once v4.1.1 is officially cited: Meeting it will give organizations a presumption of conformity with both the EAA and Web Accessibility Directive, meaning they’re assumed to meet the accessibility requirements the standard covers.
Deadlines: There is no new compliance deadline tied to this publication as of the time of this writing.
As of publication, the Commission hasn’t announced when v4.1.1 will be cited. But the direction is set. According to the Commission, the new version confirms WCAG 2.2 as the future of accessibility in Europe and gives organizations a clear target for their compliance efforts.
EN 301 591 v3.2.1 vs. v4.1.1
The two versions will overlap until the Commission officially cites v4.1.1. Here’s how they compare side by side.
What Does EN 301 549 v4.1.1 Mean for Your Organization?
The update affects everyone who relies on EN 301 549, but what it means day to day depends on why you follow the standard.
Businesses covered by the EAA. If you offer covered services to consumers in the EU, such as online stores, banking apps, or phone and internet services, the EAA applies to you, regardless of where you’re based. Nothing changes legally today. But v4.1.1 is the version built for the EAA, so it’s the one your compliance work will ultimately be measured against.
Public sector bodies under the WAD. EN 301 549 v3.2.1 has been the standard for public sector websites and apps since August 2021. When v4.1.1 is officially cited, it will also become the new benchmark for the presumption of conformity under the WAD.
Procurement teams and suppliers. EN 301 549 was originally developed as a standard for purchasing accessible technology. The Commission specifically recommends reviewing procurement processes and supplier requirements as part of preparing for v4.1.1. If you buy or sell digital products in the EU, expect accessibility requirements in contracts and tenders to start referencing WCAG 2.2.
EN 301 549 v4.1.1 Preparation Checklist
While there’s no deadline for v4.1.1, the European Commission recommends that organizations start preparing now. This checklist builds on the Commission’s guidance:
Review your websites and digital documents against WCAG 2.2. Start with the six new requirements, since those are the gap between v3.2.1 and v4.1.1.
Update your testing processes and audit checklists. Add the new requirements, and note that 4.1.1 Parsing will drop off once v4.1.1 is officially cited.
Review procurement processes and supplier requirements. Make sure the products and services you buy can meet WCAG 2.2.
Check your PDFs, Office files, and other documents. The new accessibility expectations apply to documents, not just websites.
Watch for the Official Journal citation. That’s when v4.1.1 takes legal effect for presumption of conformity.
Several of the new requirements, like focus visibility and accessible login flows, depend on how real people experience a page, which is where automated testing needs expert review. Automation covers your content at scale, while expert testers, using assistive technology, catch the issues that require human judgment.
Get Ahead of EN 301 549 v4.1.1
Most accessibility changes arrive with a deadline attached. This one doesn't, and that's the opportunity. The six new requirements are known, the direction is confirmed, and there's time to work them into your normal testing and release cycles instead of scrambling once v4.1.1 is officially cited. The work pays off right away, too, since the new requirements address problems your users already run into.
But getting ahead of the update means knowing more than whether your site passes a test.
A scan can confirm that a login form exists. It can't tell you whether someone using a screen reader can actually get through it.
AudioEye gives you both answers: automated testing across your entire site, plus certified experts who test with assistive technology to verify accessibility rather than assume it. The result is up to 400% more legal protection than automation-only approaches. And as your content changes and v4.1.1 takes effect, Active Monitoring keeps you ready.
Get ahead of EN 301 549 v4.1.1. Talk to an expert about your WCAG 2.2 readiness.
Frequently Asked Questions
Share Article
)
)
)