On September 2, 2026, EN 301 549 v4.1.1 was officially published. This represents a major update to Europe’s accessibility standard for ICT products and services, and it’s a big milestone. But in practice, it’s only the first step along a three-point timeline.
The second step is for EN 301 549 v4.1.1 to be cited in the Official Journal of the European Union (OJEU). Until that happens, it does not carry presumption of conformity, which is the legal safe harbor that comes with being a cited harmonized standard. EN 301 549 v4.1.1 is currently on track to be cited in the journal around November 30, 2026. When cited, it will become the harmonized standard that confers presumption of conformity.
The third step is when EN 301 549 v4.1.1 gets referenced in national law in each European Union (EU) country. As a reminder, EN 301 549 is the technical standard the European Commission has formally designated to support the European Accessibility Act (EAA), through standardization request M/587. However, the EAA is a directive, not a law. So while the goals it lays out are legally binding, each EU member state must enact its own regulations to ensure implementation. Those transpositions will also define when a member state expects compliance; governments commonly set lead times to allow organizations to meet the new standards.
Having read the above, your question might be: when should my organization start preparing for conformance to EN 301 549 v4.1.1? The answer is: Now. For three main reasons:
- EN 301 549 v4.1.1 will soon be the officially cited EU standard. It’s just a matter of when. If you’re building anything that you expect to last into next year, you should be building and testing to EN 301 549 v4.1.1.
- Some national transpositions don’t pin a version. Where a national law references EN 301 549 without a version number, a newly published version can become the operative benchmark with no new legislation. This means compliance requirements could hit even sooner than you might think.
- The changes are significant, and how significant depends on your scope. Real-time text requirements were substantially revised and are a big lift for telecom and hardware. For the web and digital documents, the delta is the WCAG 2.2 criteria. Conformance will take time and effort.
What is changing with EN 301 549 v4.1.1?
The following are now final in v4.1.1:
- Six new WCAG 2.2 Level A/AA success criteria
- Significantly reworked User Preferences requirements
- Updated requirements for real-time communication and real-time text
- EAA mappings in the Annexes
- Updates across web, documents, software, and other ICT
The most consequential of these changes for digital interfaces like websites and digital documents is the adoption of WCAG 2.2 Level AA, and the fact that WCAG 2.2 adds six success criteria:
- 2.4.11 Focus Not Obscured (Minimum) — Level AA. Focused components must not be entirely hidden by sticky headers, footers, or overlays.
- 2.5.7 Dragging Movements — Level AA. Any drag-based interaction needs a single-pointer alternative.
- 2.5.8 Target Size (Minimum) — Level AA. Pointer targets must meet a 24 by 24 CSS pixel minimum, subject to defined exceptions.
- 3.2.6 Consistent Help — Level A. Help mechanisms must appear in a consistent relative order across pages.
- 3.3.7 Redundant Entry — Level A. Previously entered information must be auto-populated or available for selection.
- 3.3.8 Accessible Authentication (Minimum) — Level AA. Cognitive function tests in authentication require an accessible alternative.
Having shared the above, it should be noted that meeting WCAG 2.2 Level AA is not the same as meeting EN 301 549 v4.1.1. WCAG 2.2 AA is the baseline for web, documents, and software. It doesn’t cover items such as the real-time communication changes described below. In short, testing only for WCAG 2.2 AA—where regulation calls for conformance with EN 301 549—will not be enough.
Clause 6 in EN 301 549 v4.1.1 is another notable change. It pertains to real-time, two-way communication, and its scope broadens from two-way voice communication toward real-time bidirectional communication more generally, reflecting a “Total Conversation” model in which voice, real-time text, and video operate together within a single session.
Key areas of change include:
- Substantially revised and extended Real-Time Text (RTT) requirements, including interoperability and concurrent operation with voice and video.
- Clearer expectations for the simultaneous availability of voice, text, and video channels.
- Updated requirements relating to caller identification, alerting, and call controls.
This clause applies directly to calling, messaging, contact-center, and video-conferencing products. If your organization operates in these categories, expect a meaningfully larger scope of work to achieve conformance.
What should your organization do right now?
An update this significant has a far-reaching impact and will cause disruption to your organization. Everyone from chief accessibility officers and UX leaders to legal teams, product owners, and procurement leaders will first need to understand the new standard’s requirements, and then work towards the changes needed to meet conformance.
The first and best piece of guidance we can give you is to continue meeting the legal requirements that apply to you today. At the same time, if you haven’t already moved your accessibility program toward WCAG 2.2 AA and the new EN 301 549 v4.1.1 requirements, now is the time to begin that process.
From there, consider the following:
- Build a plan: Define your approach to this change, focusing on scalability with minimal disruption. How will you inform your teams about the large-scale effort you are about to kick off? How do you best minimize the team’s perception that this is “just another accessibility project?” How will you educate everyone on the new success criteria, changes to testing, and specifics related to their role? Does your policy need updating? What is the most efficient way to complete gap analysis in your organization? How will you prioritize remediation efforts against all the other tasks your organization needs to do at year-end?
- Prepare for additional findings as you transition. The six new WCAG 2.2 criteria will likely surface issues in components that previously passed. This reflects a raised bar, not a regression in your product. But it will still require work to meet the new requirements.
- Focus on your design system as the highest-leverage place to start. Target size, dragging alternatives, and focus visibility can usually be resolved most efficiently at the component level.
- Pay early attention to real-time communication products. If your product is in scope for Clause 6 as detailed above, we recommend an early scoping conversation, as this might be a technically challenging refactor.
Nächste Schritte
We encourage you to reach out to Deque today to schedule a readiness conversation with our strategic consultancy team. We can review what the change means for your specific portfolio, and plan a transition sequence that fits your release cycle.
There is potentially a lot to tackle with this update. You need to understand the three key points along the timeline, the changes in EN 301 549, and how the new requirements will directly impact your organization.
The good news is, you can start the work now, and we’re here to help.
~
This article was co-authored by Glenda Sims, Chief Information Accessibility Officer, Deque.
