EN 301 549 is the European standard for digital accessibility. It sets technical requirements for information and communication technology (ICT) products and services to ensure equal access for people with disabilities. The current version (V3.2.1, published March 2021) incorporates WCAG 2.1 Level AA standards. Version 4.1.1, expected in 2026, will incorporate WCAG 2.2. Conforming to EN 301 549 supports compliance with both the Web Accessibility Directive and European Accessibility Act.
Key insights
- EN 301 549 provides technical accessibility criteria for a wide range of products and services, including websites, mobile applications, non-web software, operating systems, electronic documents, mobile devices, and telecommunications services.
- Private businesses that serve European consumers should conform with EN 301 549 to comply with the European Accessibility Act, which became enforceable on June 28, 2025.
- Public-sector organizations in the European Union (EU) should also meet EN 301 549 standards to comply with the EU Web Accessibility Directive. Vendors may also need to conform to sell ICT products and services to public entities.
- While the current version incorporates WCAG 2.1 AA, EN 301 549 V4.1.1 (expected 2026) will incorporate WCAG 2.2 Level AA, which includes six new success criteria.
- Organizations should target WCAG 2.2 Level AA compliance now to prepare for V4.1.1 adoption.
EN 301 549 standards and requirements
EN 301 549 is the harmonized European standard for digital accessibility. It sets guidelines and requirements for information and communication technology (ICT) to make products and services accessible to people with disabilities. This critical accessibility standard covers various types of ICT, including websites, software apps, mobile apps, electronic documents, and more.
EN 301 549 is based on existing accessibility standards and guidelines, such as the Web Content Accessibility Guidelines (WCAG). WCAG guidelines, developed by the World Wide Web Consortium (W3C), a global web standards organization, cover text alternatives, keyboard accessibility, and design that supports device independence. Conformance with EN 301 549 is the presumptive standard for compliance with the European Web Accessibility Directive (WAD) and the European Accessibility Act (EAA).
What EN 301 549 covers
EN 301 549 applies to the full spectrum of ICT products and services. This includes websites, native mobile apps, non-web software, operating systems, electronic documents (such as PDFs and office files), mobile devices, computers, self-service terminals, and telecommunications services. The standard's comprehensive scope is intended to ensure that people with disabilities have equitable access across all platforms and device types, whether checking a government website, using a banking app, or interacting with a self-service kiosk.
What does EN 301 549 require?
EN 301 549 outlines various requirements (called “clauses”) that digital products and services must meet to be considered accessible. These requirements are based on the same four principles used in WCAG, known as the “POUR principles.”
- Perceivable: Information and user interface features must be perceivable to all users, including people with disabilities. Requirements include providing alternatives for non-textual content like images, videos, and audio.
- Operable: Digital products should be operable through different input methods, including voice commands, keyboard navigation, and gestures. Users should be able to navigate and interact with the content without barriers.
- Understandable: Content and controls must be comprehensible to all users, regardless of their cognitive abilities or language proficiency. Clear instructions, error messages, and navigation mechanisms are essential for ensuring comprehension.
- Robust: Digital products should be robust enough to withstand technological changes and adapt to different assistive technologies used by people with disabilities. This helps ensure that the content stays accessible over time.
WCAG 2.1 vs WCAG 2.2: What to expect in Version 4.1.1
The upcoming EN 301 549 V4.1.1 will incorporate WCAG 2.2 Level AA standards. Compared to WCAG 2.1, WCAG 2.2 introduced six new success criteria designed to address modern user interface challenges:
| Success Criterion | Level | Target user benefit |
|---|---|---|
| Focus Not Obscured (Minimum) | AA | Ensures keyboard focus indicators remain visible for users navigating without a mouse |
| Dragging Movements | AA | Requires alternatives to drag-and-drop for users with motor disabilities |
| Target Size (Minimum) | AA | Ensures clickable elements are large enough for users with limited dexterity or using mobile devices |
| Consistent Help | A | Places help mechanisms in consistent locations for users with cognitive disabilities |
| Redundant Entry | A | Eliminates repetitive data entry within a process for users with cognitive or motor disabilities |
| Accessible Authentication (Minimum) | AA | Requires authentication methods that don't rely solely on cognitive function tests or memory |
WCAG 2.2 also removes Success Criterion 4.1.1 (Parsing), which became obsolete with modern browser error handling. These updates particularly benefit users with cognitive disabilities and those using touch-based mobile devices.
Beyond WCAG: Additional EN 301 549 requirements
While WCAG focuses primarily on web content, EN 301 549 more broadly addresses ICT accessibility requirements. The standard extends beyond WCAG in several critical areas that affect how organizations implement digital accessibility.
Biological data and biometric authentication: EN 301 549 requires that if a device uses biological data for identification—such as facial recognition or fingerprints—it must provide at least one alternative authentication method that does not rely on those specific biological features. This ensures users with disabilities affecting biometric recognition can still access secured systems.
Real-Time Text (RTT) for telecommunications: Clause 6.2 of EN 301 549 has been substantially revised in more recent versions to require synchronization of audio, high-quality video, and Real-Time Text for "total conversation" accessibility. This affects telecommunications providers and smartphone manufacturers, requiring platforms to support RTT so individuals who are deaf or hard of hearing can communicate as fluently as those using voice.
Hardware and software requirements: The standard includes requirements for computers, mobile devices, operating systems, and web browsers that affect how end users access websites. These provisions ensure the underlying technology stack supports assistive technologies rather than creating barriers at the platform level.
Compatibility with assistive technologies: EN 301 549 strongly emphasizes the need for websites and other digital products to be compatible with standard assistive technologies. It transcends WCAG guidelines to ensure people can use websites seamlessly with screen readers, magnification software, and other assistive tools. This compatibility requirement applies across web and non-web software.
Telecommunications standards: The standard addresses making telecommunications services accessible, which impacts websites offering communication features such as video conferencing, chat, or voice calling. These requirements ensure communication tools remain accessible regardless of platform.
Non-web documents and software: Although WCAG 2.1 and 2.2 have begun to address the accessibility of non-web documents and software accessed via the web, EN 301 549 has specific requirements for documents (like PDFs or office documents) and software used to access or interact with web content. These provisions extend accessibility mandates beyond browser-based experiences.
History of EN 301 549 standards
The European Telecommunications Standards Institute (ETSI), the European Committee for Electrotechnical Standardization (CENELEC), and the European Committee for Standardization (CEN) released EN 301 549 in 2014. These official groups are responsible for producing and defining voluntary standards for the EU and the European Free Trade Association (EFTA).
EN 301 549 has been updated four times, most recently in 2021, to support the European Directive 2016/2102 on the accessibility of public sector bodies' websites and mobile applications (the Web Accessibility Directive, or WAD). EN 301 549 V3.2.1, published in March 2021, was cited in the Official Journal of the EU via Implementing Decision (EU) 2021/1339 on August 18, 2021, and is the current latest version in legal effect. The 2018 update uses WCAG 2.1 Level AA standards.
27 EU Member States and other diplomatic organizations including the European Free Trade Union (EFTA) countries (Iceland, Norway, Liechtenstein), Turkey, India, and Australia adopted EN 301 549. Canada adopted it as a National Standard (CAN/ASC-EN 301 549:2024) in May 2024, and Australia uses it voluntarily for government agencies and public procurement. By embracing this standard, these countries simplify trade with the EU and make their products more accessible to everyone.
EN 301 549 revision V4.1.1 is expected for publication in 2026.
How EN 301 549 relates to the Web Accessibility Directive and European Accessibility Act
Web Accessibility Directive (public sector)
The Web Accessibility Directive (2016/2102) requires public sector bodies in Europe to make their websites and mobile applications accessible to people with disabilities. It has been fully operational since 2021, with Member States conducting monitoring and reporting every three years. Conformance with EN 301 549 is the best way for organizations to demonstrate compliance with the directive.
The European Commission published the second cycle of monitoring reports (covering 2022–2024) on February 13, 2025. A 2022 eGovernment Benchmark found only 16% of evaluated government agencies websites passed all selected automated accessibility criteria, highlighting persistent gaps despite legal requirements.
The directive has increased accessibility awareness and harmonized national law across the public sector, though implementation challenges remain.
European Accessibility Act (private sector)
The European Accessibility Act (EAA) extends the WAD’s accessibility requirements to the private sector across specific product and service categories. While the WAD covers public-sector websites and apps, the EAA covers a wide range of consumer-facing products and services, including: e-commerce, banking, telecommunications, transport services, e-books, and audiovisual media services.
The EAA became enforceable on June 28, 2025, making digital accessibility mandatory for many businesses selling products and services to EU consumers.
Businesses should use EN 301 549 as their technical reference for compliance. EN 301 549 V4.1.1 is specifically designed to support both directives through separate mapping annexes.
EAA transition periods for legacy systems
The EAA provides grace periods for organizations to bring some legacy products and services into compliance:
- Service contracts agreed before June 28, 2025 may continue until expiration but no later than June 28, 2030.
- Products already in use for service provision before the enforcement date may continue until the same 2030 deadline.
- Self-service terminals already deployed may remain in service until the end of their useful life (maximum 20 years, ultimate deadline: 2045).
These transition periods apply only to existing digital assets. Any new digital products or services launched in 2026 or later must be fully accessible from day one.
Microenterprise exemptions to the EAA
Microenterprises (fewer than 10 employees and annual turnover or balance sheet total not exceeding €2 million) are exempt from EAA service-related obligations. However, product requirements may still apply.
Many B2B contracts still require EN 301 549 conformance regardless of company size, so organizations approaching the microenterprise threshold should begin accessibility planning early.
European Accessibility Act: Enforcement and compliance in 2026
EAA enforcement timeline
The EAA became enforceable on June 28, 2025. All 27 EU Member States have transposed the directive into national law.
Early enforcement focused on procedures and complaint handling, but active market surveillance and enforcement actions accelerated in late 2025 and early 2026.
Penalties for non-compliance by Member State
| Member State | Penalty |
|---|---|
| Netherlands | Up to €90,000 |
| France | Fine of at least €75,000, not exceeding €300,000 per violation |
| Germany | From €10,000 to €100,000 per violation |
| Ireland | A fine not exceeding €60,000 |
| Italy | €5,000–€40,000 per violation (EAA) + up to 5% of turnover (Stanca Law) |
In addition to fines, the EAA and each Member State provide for the suspension or withdrawal of non-compliant products or services from the market.
These consequences represent the legal risk organizations face for failing to demonstrate compliance with requirements. Regulators have signaled that the decisive enforcement question is not "are you fully compliant?" but "what have you been doing since accessibility became mandatory?" Organizations demonstrating active monitoring and progressive remediation to conform with EN 301 549 are in materially stronger positions.
Real enforcement: Cases from 2023–2026
Enforcement actions have moved from theoretical to operational across multiple EU countries:
France: In November 2025, disability rights organizations ApiDV and Droit Pluriel filed emergency injunctions against four major grocery retailers (Auchan, Carrefour, E. Leclerc, and Picard Surgelés) for digital discrimination against users with visual disabilities. These cases are expected to reach judgment in 2026, potentially establishing precedents for interim relief where courts force immediate remediation rather than just issuing fines.
Spain: The National High Court upheld a €90,000 fine against Vueling Airlines in 2024 for an inaccessible website, with the airline also banned from receiving public funds for six months. This case demonstrates that penalties extend beyond financial sanctions to include operational restrictions affecting business sustainability.
Netherlands: The Authority for Consumers and Markets (ACM) set an October 2025 deadline for non-compliance reporting. Companies failing to respond face targeted audits beginning in early spring 2026. The ACM has completed its first round of reviews and is prioritizing enforcement actions against non-responsive organizations.
Sweden: The Swedish Post and Telecom Agency (PTS) began active market surveillance of e-commerce sites in 2025, with inspections continuing throughout 2026. The focus is on whether retailers have published mandatory accessibility statements required by the EAA.
The standards gap challenge
The EAA's essential requirements are defined in the directive itself (Annex I), and regulators can assess conformity against those requirements directly. While not explicitly stated, EN 301 549 v3.2.1, which incorporates WCAG 2.1 AA, is the current technical benchmark for compliance with these requirements. However, the updated V4.1.1, developed under European Commission Standardisation Request M/587, incorporates WCAG 2.2. This new version remains in progress with publication expected in 2026.
To stay ahead of evolving requirements, organizations should treat WCAG 2.2 Level AA as their practical target now, even though the current harmonized standard references WCAG 2.1. The European Commission notes that Member States are free to already use WCAG 2.2 voluntarily, and since WCAG 2.2 contains no breaking changes from WCAG 2.1, early adoption eliminates the remediation scramble if V4.1.1 becomes the new compliance benchmark. The W3C reinforced this trajectory when it published an updated WCAG2ICT Note on August 21, 2025, and WCAG 2.2 gained further institutional weight through its approval as ISO/IEC 40500:2025 on October 21, 2025.
How to meet EN 301 549 standards
Gap analysis and testing approaches
Organizations should conduct gap analysis combining automated and manual testing. Automated tools catch many common accessibility issues but are insufficient alone. Manual expert testing with screen readers (NVDA, JAWS, VoiceOver, TalkBack), keyboard-only navigation, and real-user testing with people with disabilities remains essential for conformance. Testing must cover websites, mobile apps, non-web documents, and non-web software per EN 301 549 scope. Organizations should establish baseline assessments, prioritize remediation based on user impact, and conduct regular audits to maintain compliance over time.
Building accessibility into design and development pipelines
Organizations should build accessibility testing into design and development pipelines rather than relying on post-launch audits. Train design and development teams on accessibility principles and integrate automated testing into continuous integration workflows. True conformance requires addressing source code and content structure at the design and development stages.
In addition to fines, the EAA and each Member State provide for the suspension or withdrawal of non-compliant products or services from the market.
These consequences represent the legal risk organizations face for failing to demonstrate compliance with requirements. Regulators have signaled that the decisive enforcement question is not "are you fully compliant?" but "what have you been doing since accessibility became mandatory?" Organizations demonstrating active monitoring and progressive remediation to conform with EN 301 549 are in materially stronger positions.
Real enforcement: Cases from 2023–2026
Enforcement actions have moved from theoretical to operational across multiple EU countries:
France: In November 2025, disability rights organizations ApiDV and Droit Pluriel filed emergency injunctions against four major grocery retailers (Auchan, Carrefour, E. Leclerc, and Picard Surgelés) for digital discrimination against users with visual disabilities. These cases are expected to reach judgment in 2026, potentially establishing precedents for interim relief where courts force immediate remediation rather than just issuing fines.
Spain: The National High Court upheld a €90,000 fine against Vueling Airlines in 2024 for an inaccessible website, with the airline also banned from receiving public funds for six months. This case demonstrates that penalties extend beyond financial sanctions to include operational restrictions affecting business sustainability.
Netherlands: The Authority for Consumers and Markets (ACM) set an October 2025 deadline for non-compliance reporting. Companies failing to respond face targeted audits beginning in early spring 2026. The ACM has completed its first round of reviews and is prioritizing enforcement actions against non-responsive organizations.
Sweden: The Swedish Post and Telecom Agency (PTS) began active market surveillance of e-commerce sites in 2025, with inspections continuing throughout 2026. The focus is on whether retailers have published mandatory accessibility statements required by the EAA.
The standards gap challenge
The EAA's essential requirements are defined in the directive itself (Annex I), and regulators can assess conformity against those requirements directly. While not explicitly stated, EN 301 549 v3.2.1, which incorporates WCAG 2.1 AA, is the current technical benchmark for compliance with these requirements. However, the updated V4.1.1, developed under European Commission Standardisation Request M/587, incorporates WCAG 2.2. This new version remains in progress with publication expected in 2026.
To stay ahead of evolving requirements, organizations should treat WCAG 2.2 Level AA as their practical target now, even though the current harmonized standard references WCAG 2.1. The European Commission notes that Member States are free to already use WCAG 2.2 voluntarily, and since WCAG 2.2 contains no breaking changes from WCAG 2.1, early adoption eliminates the remediation scramble if V4.1.1 becomes the new compliance benchmark. The W3C reinforced this trajectory when it published an updated WCAG2ICT Note on August 21, 2025, and WCAG 2.2 gained further institutional weight through its approval as ISO/IEC 40500:2025 on October 21, 2025.
How to meet EN 301 549 standards
Gap analysis and testing approaches
Organizations should conduct gap analysis combining automated and manual testing. Automated tools catch many common accessibility issues but are insufficient alone. Manual expert testing with screen readers (NVDA, JAWS, VoiceOver, TalkBack), keyboard-only navigation, and real-user testing with people with disabilities remains essential for conformance. Testing must cover websites, mobile apps, non-web documents, and non-web software per EN 301 549 scope. Organizations should establish baseline assessments, prioritize remediation based on user impact, and conduct regular audits to maintain compliance over time.
Building accessibility into design and development pipelines
Organizations should build accessibility testing into design and development pipelines rather than relying on post-launch audits. Train design and development teams on accessibility principles and integrate automated testing into continuous integration workflows. True conformance requires addressing source code and content structure at the design and development stages.
Establishing user feedback mechanisms
Establish feedback mechanisms for users to report accessibility barriers. Ensure that these mechanisms are accessible, and that there is a process in place for prioritizing and addressing feedback from users.