European Union (harmonised standard) · 2014 (v3.2.1 current)
EN 301 549 — Accessibility requirements for ICT products and services (EN 301 549)
EN 301 549 is the harmonised European standard for digital accessibility, maintained jointly by ETSI, CEN, and CENELEC, that incorporates WCAG 2.1 AA for web and mobile content and adds requirements for hardware, software, documentation and support — and is the technical reference for both the European Accessibility Act and the Web Accessibility Directive.
What is EN 301 549?
EN 301 549 v3.2.1 (October 2021) is the current operative version. It directly references WCAG 2.1 AA for content and adds chapters for hardware (5), software (11), documentation (12), and ICT support (13). Conformance creates a presumption of conformity with the EAA and WAD.
Who does EN 301 549 apply to?
- Public-sector bodies (via WAD)
- EAA-covered products and services
- EU public procurement of ICT
Scope
- Web content
- Non-web documents (PDF, EPUB)
- Software (native apps, OSes)
- Hardware (kiosks, devices)
- Documentation
- ICT support services
Penalties for non-compliance
- Inherited from referencing law (WAD or EAA per member state)
How to comply with EN 301 549
- Identify in-scope chapters. Map your product across chapters 5–13. A web app covers chapters 9, 11, 12.
- Test WCAG 2.1 AA. Chapter 9 references WCAG directly.
- Cover hardware/software. Add chapter 5/11 requirements where applicable.
- Document conformance. Produce VPAT 2.5 EU or equivalent ACR.
Comparisons
- EN 301 549 vs WCAG 2.1: Chapter 9 of EN 301 549 references WCAG 2.1 AA directly.
- EN 301 549 vs EAA: EAA references EN 301 549 as its harmonised standard. Conformance to EN creates presumption of conformance to EAA.
- EN 301 549 vs Section 508: Intentionally harmonised in 2017. A combined VPAT covers both.
Authoritative sources
- EN 301 549 v3.2.1 — ETSI
A note on widgets and overlays
Can an accessibility widget make your site compliant?
No. Widgets adjust how content renders for individual visitors — text size, contrast modes, dyslexia-friendly fonts. They do not remediate the underlying source code. WCAG conformance is graded at source level, and US federal courts (Murphy v. Eyebobs, Suarez v. Camping World, Hernandez v. Caesars) have repeatedly held that the presence of an overlay does not preclude ADA liability.
Our product produces an IAAP-format audit report with source-level remediation guidance. If you want a preferences panel for end users, ship one separately — opt-in, disclosed, and never marketed as a compliance solution.
See the Overlay Fact Sheet, signed by 900+ accessibility professionals.
FAQ
EN 301 549 — frequently asked questions
Cited answers. Sourced. Updated as standards and case law change.
What is the current version of EN 301 549?
EN 301 549 v3.2.1, published October 2021. Updates expected to track WCAG 2.2 in coming revisions.
Does EN 301 549 conformance prove EAA compliance?
Conformance to EN 301 549 creates a "presumption of conformity" with the EAA — the regulatory shortcut. Market surveillance can still challenge a specific defect.
Can I use a US VPAT for EN 301 549?
Use VPAT 2.5 EU (or 2.5 INT for global) — it maps to EN 301 549 chapters. The base US-only VPAT does not.
Get an EN 301 549-grade audit. In hours.
IAAP-format report. AccessivePath maps findings to EN 301 549 and every related standard simultaneously.
founders@accessivepath.com · +977 9851094056