EN 301 549 Explained: The Technical Standard Behind EU Accessibility Law
EN 301 549 compliance explained — how it maps to WCAG 2.1 AA, which EU laws require it, what ICT it covers, and how to achieve presumption of conformity.
What EN 301 549 actually is
EN 301 549 is a European harmonized standard developed by ETSI (the European Telecommunications Standards Institute) in collaboration with CEN and CENELEC. It defines accessibility requirements for ICT products and services. The current version is EN 301 549 v3.2.1, published in 2021.
Unlike WCAG — which focuses specifically on web content — EN 301 549 covers the full breadth of ICT: websites, web applications, mobile apps, software, hardware, documents, and telecommunications. This makes it the most comprehensive accessibility standard in current use.
How it connects to EU law
Two major EU laws reference EN 301 549:
- Web Accessibility Directive (2016/2102): Requires all EU public sector bodies — government websites, public institutions — to conform to EN 301 549. Applies to web, mobile apps, and intranets. Enforcement has been active since 2020.
- European Accessibility Act (EAA, 2019/882): Requires private sector companies selling covered products and services in the EU to meet accessibility requirements. EN 301 549 is the referenced standard. Enforceable since June 28, 2025.
Conforming to EN 301 549 creates presumption of conformity— meaning regulators presume you meet the law's accessibility requirements without additional scrutiny.
What the standard covers
EN 301 549 is organized into chapters by ICT type:
- Chapter 5: General requirements (functional performance statements)
- Chapter 6: ICT with two-way voice communication
- Chapter 7: ICT with video capabilities
- Chapter 8: Hardware
- Chapter 9: Web content (incorporates WCAG 2.1)
- Chapter 10: Non-web documents
- Chapter 11: Software and mobile apps (incorporates WCAG 2.1)
- Chapter 12: Documentation and support services
- Chapter 13: ICT providing relays or emergency services
Functional performance statements (Chapter 5) describe accessibility in outcome terms — for example, the ability to use ICT without vision, without hearing, or with limited reach. These apply when specific criteria do not, and provide a fallback evaluation framework.
How it maps to WCAG
For web content (Chapter 9) and software/apps (Chapter 11), EN 301 549 directly incorporates WCAG 2.1 Level AA by reference. This means:
- Meeting WCAG 2.1 AA satisfies EN 301 549 for web and app content
- Meeting WCAG 2.2 AA exceeds the EN 301 549 requirement (all versions are backward compatible)
- EN 301 549 adds requirements beyond WCAG for hardware, voice communication, and documents
For organizations with purely digital products, WCAG 2.1 or 2.2 AA compliance is the practical path to EN 301 549 conformance.
Who needs to meet it
| Organization Type | Applicable Law | EN 301 549 Obligation |
|---|---|---|
| EU public sector bodies | Web Accessibility Directive | Mandatory for web and mobile |
| Private sector (EU, selling covered products/services) | EAA | Required for covered ICT |
| Non-EU companies with EU customers | EAA (extraterritorial) | Required for covered ICT sold in EU |
| Federal vendors (US) | Section 508 (separate) | Covered by VPAT v2.5 EN 301 549 column |
How to conform
- 1. Identify applicable chapters — Map your ICT portfolio to EN 301 549 chapters. A web app maps primarily to Chapter 9. A mobile app to Chapter 11. A hardware device to Chapter 8.
- 2. Audit to WCAG 2.1 AA — For digital products, this covers Chapters 9 and 11 in full.
- 3. Address non-web requirements — Review Chapter 10 for PDF/document accessibility, Chapter 6 for voice products, Chapter 7 for video.
- 4. Complete a conformance report — For public sector, this is an Accessibility Statement. For private sector procurement, use VPAT v2.5 with the EN 301 549 column completed.
- 5. Maintain documentation for 5 years — Required under the EAA for all covered products and services.
- 6. Run continuous audits — Conformance is not a one-time achievement. Test on every release cycle.
Wondering where your site actually stands?
Drop in a URL. Zylyn scans against WCAG 2.2 in 90 seconds, with issues grouped by severity.
How Zylyn gets you compliant.
Three tools, one platform. Use the audit to find what's broken, the widget for instant user-facing relief, and the reports to track real progress in code.
Free WCAG Audit
Scan any URL against WCAG 2.2 in 90 seconds. Issues are grouped by severity with code-ready fix suggestions and direct links to the relevant criterion.
Start a free scan- Most Popular
Accessibility Widget
User-first controls for text size, contrast, motion, font, and cursor. One-line install. Gives real users immediate relief while you fix the underlying code.
See the widget Audit Reports
Export findings to PDF or CSV. Schedule re-scans, track progress over time, and push remediation tasks into your existing workflow tools.
See a sample
Achieve EN 301 549 conformance with Zylyn
Services that test and document conformance for EU regulatory requirements.
- ServiceEN 301 549 Testing
WCAG 2.1 AA testing with conformance documentation backed by real test evidence — ready for EAA regulatory scrutiny.
- ServiceVPAT & ACR Services
Conformance documentation retained for the mandatory 5-year EU regulatory period.
- AdvisoryAccessibility Consulting
End-to-end EN 301 549 programme design covering web, mobile, hardware, and documents.
Real teams, real results.
Companies use Zylyn to cut manual testing time, ship accessibly, and stay ahead of demand letters.
“We've reduced manual accessibility testing time by over 70%. Zylyn flags issues in real-time and suggests fixes. Our audit process is now faster and more reliable than anything we had before.”
Frequently asked questions
Common questions about EN 301 549, its relationship to WCAG, and how it connects to EU law.
EN 301 549 is a European harmonized standard that defines accessibility requirements for ICT products and services — including websites, mobile apps, software, and hardware. It is the technical standard referenced by the European Accessibility Act and the Web Accessibility Directive.
EN 301 549 v3.2.1, published in 2021, is the current version. It incorporates WCAG 2.1 Level AA as the basis for web and mobile accessibility requirements.
For web content, EN 301 549 directly incorporates WCAG 2.1 Level AA. Meeting WCAG 2.1 AA satisfies the web accessibility requirements of EN 301 549. The standard also covers non-web ICT not addressed by WCAG alone.
Presumption of conformity means that if your product meets EN 301 549, EU regulators presume it meets the EAA's accessibility requirements without needing to independently verify it. This is a significant compliance advantage.
The Web Accessibility Directive (2016/2102) requires public sector bodies to conform to EN 301 549. The European Accessibility Act (EAA, 2019/882) references EN 301 549 for private sector products and services.
Yes. EN 301 549 includes Chapter 11 specifically for mobile applications, incorporating WCAG 2.1 Level AA along with additional mobile-specific requirements.
Functional performance statements in EN 301 549 describe accessibility outcomes in terms of user ability — for example, the ability to use a product without vision. They provide a framework for evaluating ICT that doesn't fit neatly into specific technical criteria.
The VPAT (v2.5) includes an EN 301 549 section, so completing a full VPAT ACR covers both Section 508 and EN 301 549 in one document. If you only have a Section 508 VPAT, you will need to add the EN 301 549 / EAA column for EU compliance.
Find out where your site stands — in 90 seconds.
One URL. One scan. A prioritized list of what to fix and how, sent straight to your inbox.
Keep reading
Recent guides from the Zylyn Knowledge Hub.