EN 301 549: The EU's ICT Accessibility Standard, Explained
Reviewed by Khushwant Parihar, CPACC
Updated
EN 301 549 is the harmonized European standard that defines what “accessible” means for technology in EU law. It sits behind both the Web Accessibility Directive and the European Accessibility Act, incorporates WCAG 2.1 Level AA for web content, and extends comparable requirements to documents, software, hardware, and support services. If you sell into Europe, this is the standard your conformance claims map to.
Not legal advice. This guide is educational information about EN 301 549 and the EU laws that reference it, not legal advice. Which version of the standard applies, and how, depends on the law, the member state, and your product, so consult a qualified lawyer for compliance decisions.
What EN 301 549 is
Formally titled “Accessibility requirements for ICT products and services,” EN 301 549 is a European standard produced jointly by ETSI, CEN, and CENELEC, the three official European standardization organizations, under mandates from the European Commission. It began life as Europe's answer to the US Section 508 standards: a single technical yardstick that public buyers and regulators could reference instead of writing their own accessibility specifications.
Its legal significance comes from harmonization. When the European Commission cites a version of the standard in the Official Journal of the EU as a harmonized standard for a given law, conforming to it creates a presumption of conformity with that law's accessibility requirements. That makes EN 301 549 the safe, well-lit path to compliance with:
- the Web Accessibility Directive (Directive (EU) 2016/2102), which covers EU public-sector websites and mobile apps, and
- the European Accessibility Act (Directive (EU) 2019/882), which extends accessibility duties to private-sector products and services from June 28, 2025. No edition is cited under the EAA yet; V4.1.1 is expected to be the first, and Ireland's National Disability Authority expects its Official Journal citation on 16 December 2026.
How the standard is structured
| Chapter | Topic | What it covers |
|---|---|---|
| Ch. 4–5 | Functional performance & generic requirements | Usage without vision, with limited hearing, without speech, with limited manipulation or strength, and more; requirements that apply across all ICT |
| Ch. 6–7 | Two-way voice & video capabilities | Real-time text, audio quality, captioning and audio description capabilities for ICT that handles voice or video |
| Ch. 8 | Hardware | Physical ICT: self-service terminals, kiosks, devices with operable parts and displays |
| Ch. 9 | Web | Websites and web applications: incorporates WCAG 2.1 Level A and AA success criteria (WCAG 2.2 in v4.1.1) |
| Ch. 10 | Non-web documents | PDFs, Office documents, e-books and other non-web documents, via adapted WCAG criteria |
| Ch. 11 | Software | Native mobile and desktop apps and other non-web software, via adapted WCAG criteria plus assistive-technology interoperability |
| Ch. 12–13 | Documentation, support & relay services | Accessible product documentation, accessible support channels, and relay/emergency service access |
Highlighted rows (chapters 9, 10, and 11) are the ones most digital product teams work with day to day.
The WCAG connection
For web content, EN 301 549 does not reinvent anything: chapter 9 incorporates the WCAG 2.1 Level A and AA success criteria. A website that conforms to WCAG 2.1 AA satisfies the web chapter outright. The standard's real added value is everywhere WCAG stops:
- Chapter 10 applies adapted WCAG criteria to non-web documents: PDFs, Office files, e-books.
- Chapter 11 applies adapted criteria to native software and mobile apps, and adds requirements such as interoperability with assistive technologies and preservation of platform accessibility features.
- Functional performance statements (chapter 4) describe outcomes (usable without vision, without hearing, with limited manipulation) that act as a benchmark where specific technical provisions do not apply.
- Chapters 6–8 and 12–13 reach voice and video communication, hardware such as kiosks and terminals, product documentation, and support services.
Since WCAG 2.2 is backwards-compatible with 2.1, auditing against the WCAG 2.2 AA checklist covers the EN 301 549 web baseline while future-proofing your conformance as the standard is revised to track newer WCAG versions.
Versions of EN 301 549
| Version | What changed |
|---|---|
| v1.1.2 (2015) | First edition; aligned with WCAG 2.0 for web content |
| v2.1.2 (2018) | First version harmonized for the Web Accessibility Directive; introduced WCAG 2.1 alignment |
| v3.1.1 (2019) | Restructured and extended requirements across document and software chapters |
| v3.2.1 (2021) | Current baseline cited for the Web Accessibility Directive; WCAG 2.1 A/AA for web, documents, and software |
| v4.1.1 (September 2026) | Published by ETSI on 2 September 2026: aligns web, document, and software chapters with WCAG 2.2, adds Annex ZB mapping requirements to the EAA, and rewrites the real-time text clause. Not yet cited in the Official Journal as of 11 November 2026 (Ireland's National Disability Authority expects 16 December 2026) |
Version 3.2.1 (March 2021) is the established baseline. Version 4.1.1, produced under the European Commission's standardisation request M/587 and published on 2 September 2026, is the edition aligned to the European Accessibility Act. When citing the standard in contracts or conformance reports, always name the exact version and check the Official Journal for the version currently harmonised for the law you care about.
EN 301 549 v4: exactly what is changing
Status as of 11 November 2026: ETSI published EN 301 549 V4.1.1 (2026-09) on 2 September 2026, after the national vote on the V4.1.0 final draft. It has NOT yet been cited in the Official Journal; Ireland's National Disability Authority expects that on 16 December 2026. Until then, v3.2.1 remains the version cited for the Web Accessibility Directive, and no version is cited under the European Accessibility Act, so the EAA's presumption of conformity is not yet available through any edition. Test against WCAG 2.2 AA now, and cite the version you tested against.
These changes come from the standard itself, produced by ETSI under the Commission's standardisation request M/587, not from second-hand summaries. We read them first in the V4.1.0 final draft and re-checked them against the published V4.1.1:
- WCAG 2.2 alignment. Clauses 9 (web), 10 (documents), and 11 (software) are updated to align with WCAG 2.2, referenced as the W3C Recommendation of 12 December 2024 and as ISO/IEC 40500:2025. WCAG 2.2 is now also an ISO standard, which matters for procurement language.
- A dedicated EAA mapping. A new Annex ZB maps the standard's requirements to the European Accessibility Act across five tables covering products and services, and a new clause A.2 lets a specific product or service be evaluated for EAA conformance. Today's v3.2.1 was harmonized for the Web Accessibility Directive; v4 is built to serve the EAA directly.
- Real-time text rewritten. Clause 6.2 on real-time text is significantly revised and extended to cover total conversation, which connects to the EAA's June 2027 date for accessible answering of 112 emergency communications.
- Web Accessibility Directive mapping refreshed. A new Annex ZA replaces the old Annex A for the 2016/2102 Directive mapping.
That is the summary. The clause-level detail, including the six WCAG 2.2 criteria now required, the user-preferences rework, the total conversation and real-time text rewrite with its link to the EAA's 28 June 2027 date for 112 calls, Annex ZB and the clause A.2 conformance tables, and a migration list for teams on v3.2.1, is in our EN 301 549 V4.1.1 clause-by-clause guide.
Practical takeaway: if you are remediating now, audit against the WCAG 2.2 AA checklist rather than 2.1. WCAG 2.2 is backwards-compatible with 2.1, so work done against 2.2 satisfies today's v3.2.1 and is already aligned with where v4 lands. To work through the standard itself, clause by clause, use our free interactive EN 301 549 checklist with both editions, 285 requirements in v3.2.1 and 319 in v4.1.1, every new or changed v4 row flagged, product-type and EAA conformance-table scopes, and Excel export.
Who needs EN 301 549
- EU public-sector bodies: websites and mobile apps must meet the harmonized standard under the Web Accessibility Directive, with a published accessibility statement and a feedback mechanism, monitored by national authorities.
- Businesses covered by the EAA: e-commerce, consumer banking, e-books, telecoms, transport services, and manufacturers of covered devices use EN 301 549 conformance as their technical benchmark, which becomes a formal presumption-of-conformity route once V4.1.1 is cited in the Official Journal. See the EAA compliance guide for scope and deadlines.
- Vendors selling ICT to European public buyers: public procurement rules require accessible ICT, and buyers request conformance evidence against the standard, typically as an ACR on the VPAT EU edition (the EU counterpart to the US Section 508 VPAT).
- Non-EU companies serving EU customers: the laws that reference the standard apply based on where the product or service is offered, not where the company sits.
Conforming in practice
For a typical website or app, EN 301 549 conformance work is WCAG conformance work with a wider perimeter: audit web content against WCAG 2.1/2.2 AA, apply the adapted criteria to your mobile apps and customer-facing documents, verify assistive technology compatibility, and make sure support channels and documentation are accessible. Then document it (an accessibility statement for regulators and users, an ACR for procurement) and wire accessibility checks into your release process so conformance survives the next sprint. Litigation risk looks different in Europe than the US lawsuit wave (tracked in our lawsuit tracker), but regulator complaints and market-surveillance action follow the same trail of unfixed barriers.
Map your product against EN 301 549
Start with a WCAG audit of your web content, check your PDFs against the document requirements, and get expert help assembling conformance documentation for EU markets.
Frequently asked questions
What is EN 301 549 in plain terms?
EN 301 549, 'Accessibility requirements for ICT products and services,' is the European standard that defines what 'accessible' means for technology in EU law. It was developed jointly by the European standards organizations ETSI, CEN, and CENELEC under a mandate from the European Commission. Where US rules point to WCAG for web content, EU laws point to EN 301 549, which itself incorporates WCAG 2.1 Level A and AA for web content and extends similar requirements to documents, software, hardware, and support services. Conforming to it gives a legal presumption that you meet the accessibility requirements of the EU laws that reference it.
How does EN 301 549 relate to WCAG 2.1 AA?
Chapter 9 of EN 301 549 incorporates the WCAG 2.1 Level A and AA success criteria directly for web content: if your site conforms to WCAG 2.1 AA, you satisfy the web chapter. Chapters 10 (non-web documents) and 11 (software, including mobile apps) apply adapted versions of the same criteria to those contexts. So WCAG 2.1 AA is the core of EN 301 549 but not the whole of it: the standard also covers functional performance, hardware, two-way communication, video capabilities, and documentation and support services that WCAG never addressed.
What is the current version of EN 301 549?
Version 3.2.1, published in March 2021, is the established baseline and the version harmonized in the Official Journal of the EU for the Web Accessibility Directive. It aligns web, document, and software requirements with WCAG 2.1. ETSI published V4.1.1 on 2 September 2026: it aligns the standard with WCAG 2.2 and adds a dedicated mapping to the European Accessibility Act. V4.1.1 has not yet been cited in the Official Journal; Ireland's National Disability Authority expects the citation on 16 December 2026. Until then no version of EN 301 549 is cited under the EAA, and v3.2.1 remains the version cited for the Web Accessibility Directive. Conformance claims should always name the version they were tested against.
Who needs to conform to EN 301 549?
Three main groups. First, EU public-sector bodies: the Web Accessibility Directive requires their websites and mobile apps to meet the harmonized standard. Second, businesses covered by the European Accessibility Act (e-commerce, banking, e-books, transport, telecoms, and covered products), since EN 301 549 is the technical benchmark regulators and buyers use, and V4.1.1 is due to become the EAA's harmonised standard once it is cited in the Official Journal. Third, vendors selling ICT to European public-sector buyers, who are routinely asked for EN 301 549 conformance evidence in procurement (the VPAT EU edition exists exactly for this). Non-EU companies serving EU customers in covered sectors are included.
Is EN 301 549 a law?
No. It is a technical standard, not legislation. Its legal force comes from the laws that reference it: the Web Accessibility Directive (2016/2102) for public-sector websites and apps, and the European Accessibility Act (2019/882) for private-sector products and services. When a version of the standard is cited in the Official Journal of the EU as a harmonized standard, conforming to it creates a presumption of conformity with the corresponding law. You can also comply with those laws by other means, but you then carry the burden of demonstrating the requirements are met without the standard's safe harbor.
What do chapters 9, 10, and 11 cover?
These are the three chapters most digital teams work with. Chapter 9 (Web) applies WCAG 2.1 A and AA success criteria to web pages. Chapter 10 (Non-web documents) applies adapted WCAG criteria to documents that are not web pages (PDFs, Office files, e-books), whether distributed on the web or elsewhere. Chapter 11 (Software) applies adapted criteria to non-web software, including native mobile and desktop apps, and adds requirements like interoperability with assistive technology and accessible authoring tools. The adaptations mostly replace web-specific wording; the substance of the criteria stays the same.
How do I test and document EN 301 549 conformance?
For web content, test against WCAG 2.1 AA (or 2.2 AA for headroom) using a combination of automated scanning, manual expert review, and assistive-technology testing; chapter 9 is satisfied by WCAG conformance. For apps and documents, apply the adapted criteria of chapters 11 and 10 respectively. Document the results in an accessibility statement (mandatory for public-sector bodies under the Web Accessibility Directive, and expected under the EAA's service-information requirements) or, for procurement, in an ACR using the VPAT EU edition, which mirrors the standard's clause structure.