EU harmonized accessibility standard
EN 301 549
The European harmonized standard for ICT accessibility, published by ETSI. Currently at v3.2.1, it references WCAG 2.1 AA for web and is the technical benchmark for the European Accessibility Act. Version 4.1.1, scheduled for October 2026, will reference WCAG 2.2 and harmonize with the EAA.
What is EN 301 549?
EN 301 549 (European Standard for 'Accessibility requirements for ICT products and services') is published by ETSI (European Telecommunications Standards Institute) and provides the technical specifications that underpin EU accessibility legislation. Version 3.2.1 (2021) is the current harmonized standard. It references WCAG 2.1 AA in Chapter 9 (web content), and adds requirements in Chapter 10 (non-web documents), Chapter 11 (non-web software), Chapter 12 (documentation and support services), and Chapter 13 (ICT services involving real-time communication). The standard covers the widest scope of any major accessibility standard — websites, mobile apps, PDFs, desktop software, ATMs, ticketing machines, and telecoms services.
EN 301 549 compliance is required for: (1) all EU public sector bodies under the Web Accessibility Directive (WAD) 2016/2102; (2) private sector companies within the scope of the European Accessibility Act (Directive 2019/882), applicable from 28 June 2025 — covering e-commerce, banking, transport, telecom, audiovisual services, and e-books targeted at EU consumers; (3) manufacturers of ICT hardware and software distributed in the EU who wish to self-declare conformance. Member states may also reference EN 301 549 in national transpositions. In France, EN 301 549 underlies the RGAA; in Germany, it underlies BITV 2.0.
The European Commission mandates harmonized standards under the EAA through standardization request M/587 to ETSI and CEN/CENELEC. EN 301 549 v4.1.1, anticipated for October 2026, will update the WCAG reference from 2.1 to 2.2 and incorporate harmonization with EAA requirements, including real-time text and relay services. Until v4.1.1 is published in the Official Journal of the EU (OJ), v3.2.1 remains the normative reference. Organizations that already comply with EN 301 549 v3.2.1 will need to address 6 new WCAG 2.2 Level AA criteria to meet v4.1.1.
Key criteria
The 10 requirements most frequently flagged in automated audits by scan-access.com.
- 9.1.1.1
Non-text Content (Chapter 9 — Web)
All non-text content must have a text alternative. Corresponds directly to WCAG 2.1 SC 1.1.1. Chapter 9 of EN 301 549 maps 1:1 to WCAG 2.1 AA criteria.
Official spec →WCAG 1.1.1 - 9.1.4.3
Contrast (Minimum) — Web
Text contrast ratio must be at least 4.5:1 for normal text and 3:1 for large text. Among the highest-frequency violations in automated scans.
Official spec →WCAG 1.4.3 - 10.1.1.1
Non-text Content (Chapter 10 — Documents)
Chapter 10 extends web WCAG requirements to non-web documents (PDFs, Office files). Image alt text in PDFs is separately assessed under EN 10.x criteria.
Official spec →WCAG 1.1.1 - 11.1.1.1
Non-text Content (Chapter 11 — Software)
Chapter 11 applies WCAG principles to native software UIs. Platform accessibility APIs (MSAA, AT-SPI, NSAccessibility) are used to expose name, role, value.
Official spec →WCAG 1.1.1 - 9.2.1.1
Keyboard Accessible — Web
All web functionality must be operable via keyboard. Custom interactive widgets (menus, dialogs, sliders) must expose keyboard interaction patterns.
Official spec →WCAG 2.1.1 - 9.4.1.2
Name, Role, Value — Web
All UI components (inputs, buttons, custom controls) must expose name, role, and state to assistive technologies via valid ARIA or native HTML semantics.
Official spec →WCAG 4.1.2 - 12.1.1
Accessibility documentation
Product documentation and support services must list the accessibility features of the ICT product, enabling users to activate them.
- 13.1
Real-time text (RTT)
Products providing real-time text communication (chat, telephony) must support RTT interoperability for users who cannot use voice.
- 9.2.4.3
Focus Order — Web
If the reading order affects meaning, focus must follow a logical sequence. Key for dynamic interfaces with modals, overlays, and toast notifications.
Official spec →WCAG 2.4.3 - 9.3.3.1
Error Identification — Web
Input errors must be described to the user in text, identifying the item in error and the nature of the error. Critical for checkout and registration forms.
Official spec →WCAG 3.3.1
How scan-access.com covers EN 301 549
scan-access.com coverage
scan-access.com covers Chapter 9 (web) EN 301 549 criteria automatically
scan-access.com's axe-core engine covers EN 301 549 Chapter 9 criteria — the web content chapter — with the same ~35% automated coverage as WCAG 2.2 AA (since Chapter 9 maps 1:1 to WCAG 2.1 AA). Every finding is tagged with both the EN 301 549 criterion ID and its WCAG equivalent, making it straightforward to compile EU compliance evidence. Chapter 10 (non-web documents) and Chapter 11 (software) are not in scope for web scanning tools; they require specialized PDF auditing (e.g., PAC3, axe PDF) and native app testing. The legal-defense PDF export includes EN 301 549 chapter references, suitable for EU public procurement attestations.
Free scan against EN 301 549. No account required.
Frequently asked questions
What is EN 301 549?
EN 301 549 is the European harmonized standard for ICT accessibility, published by ETSI. It provides technical requirements for websites, mobile apps, software, PDFs, and hardware (ATMs, kiosks). For web content, Chapter 9 maps directly to WCAG 2.1 AA. It is the technical reference standard for the EU Web Accessibility Directive and the European Accessibility Act.
Is EN 301 549 the same as WCAG?
Not exactly. EN 301 549 incorporates WCAG 2.1 AA by reference in Chapter 9 (web), but extends coverage to non-web content (documents, software, telecoms, hardware) in chapters 10–13. Chapter 9 criteria are identical to WCAG 2.1 success criteria. Organizations auditing web content can treat EN 301 549 Chapter 9 as equivalent to WCAG 2.1 AA.
When will EN 301 549 v4.1.1 be published?
EN 301 549 v4.1.1 is anticipated for October 2026, following publication in the Official Journal of the EU. The main changes include: (1) updating the WCAG reference from 2.1 to 2.2 (adding 6 new Level AA criteria); (2) enhanced real-time text requirements; (3) harmonization with EAA product requirements. Until v4.1.1 is cited in the OJ, v3.2.1 remains the normative harmonized standard.
Does EN 301 549 cover mobile apps?
Yes. Chapter 11 of EN 301 549 ('Non-web software') covers native mobile applications (iOS, Android). It maps WCAG principles to platform-specific accessibility APIs. Mobile app compliance requires testing with platform tools (Accessibility Inspector on iOS, TalkBack on Android) in addition to automated web scanning.
Who must comply with EN 301 549?
EU public sector bodies must comply under the Web Accessibility Directive (WAD, 2016/2102). Private sector companies in scope of the EAA (e-commerce, banking, transport, telecoms, audiovisual, e-books targeting EU consumers) must comply from 28 June 2025. Hardware manufacturers who self-declare CE marking for ICT products should also reference EN 301 549.
Related standards
WCAG 2.2 AA
EN 301 549 Chapter 9 maps directly to WCAG. v4.1.1 will reference WCAG 2.2.
European Accessibility Act
The EAA mandates EN 301 549 as its technical reference standard for private sector.
BITV 2.0
Germany's BITV 2.0 transposes EN 301 549 for German public sector organizations.
Stanca / AGID
Italy's Stanca law references EN 301 549 as its technical benchmark.