EN 301 549: The European Accessibility Standard
EN 301 549 is the harmonized European standard for ICT accessibility, referenced by the European Accessibility Act. This guide explains what it covers, how it relates to WCAG, and what you need to know for compliance.
What is EN 301 549?
EN 301 549 (full title: "Accessibility requirements for ICT products and services") is a European harmonized standard that defines accessibility requirements for information and communication technology.
It was developed by ETSI (European Telecommunications Standards Institute) and is maintained by CEN, CENELEC, and ETSI. The standard covers:
- Web content (Chapter 9)
- Documents (Chapter 10)
- Software (Chapter 11)
- Hardware (Chapters 5, 6, 7, 8)
Key Facts
Current version: v3.2.1 (2021)
Based on WCAG 2.1
Presumption of conformity
Meeting EN 301 549 = EAA compliance
Referenced globally
Used beyond EU (Australia, etc.)
Free to access
Available from ETSI website
Chapter Breakdown
EN 301 549 is organized into chapters covering different types of ICT. Not all chapters apply to every product — the key is identifying which chapters are relevant to your specific technology.
Functional Performance Statements
High-level accessibility goals that products should achieve. These are the "what" without the "how" — useful when specific technical requirements don't apply.
Generic Requirements
Requirements that apply across multiple categories, including closed functionality, biometrics, and preservation of accessibility in conversion.
ICT with Two-Way Voice Communication
Requirements for voice calls, video calls, and real-time text (RTT). Important for VoIP, video conferencing, and telecommunications.
ICT with Video Capabilities
Requirements for video playback, including captions, audio descriptions, and player controls.
Hardware
Physical product requirements including dimensions, reach, controls, and connections.
Web Content
Web accessibility requirements, directly referencing WCAG 2.1 Level AA. This is the most relevant chapter for websites and web applications.
Non-Web Documents
Accessibility requirements for documents (PDF, Word, etc.). References WCAG principles adapted for document formats.
Software
Requirements for native applications (desktop, mobile) and software platforms. Includes requirements for interoperability with assistive technologies.
Documentation and Support Services
Requirements for documentation, help desks, and support services to be accessible.
ICT Providing Relay or Emergency Service Access
Requirements for emergency services and relay services used by people with disabilities.
Chapter 9: Web Content (Deep Dive)
For websites and web applications, Chapter 9 is the most important. It directly incorporates WCAG 2.1 Level AA, meaning if you comply with WCAG 2.1 AA, you meet the EN 301 549 web requirements.
How Chapter 9 Works
Chapter 9 is structured to mirror WCAG exactly. Each clause in Chapter 9 corresponds to a WCAG success criterion:
- 9.1.x.x = WCAG Principle 1 (Perceivable)
- 9.2.x.x = WCAG Principle 2 (Operable)
- 9.3.x.x = WCAG Principle 3 (Understandable)
- 9.4.x.x = WCAG Principle 4 (Robust)
The clause text says "Web pages shall satisfy WCAG 2.1 Success Criterion X.Y.Z [conformance level]" and then quotes the WCAG requirement.
What’s the Same as WCAG
- All WCAG 2.1 Level A criteria
- All WCAG 2.1 Level AA criteria
- Technical implementation guidance
- Testing approaches
What’s Additional
- 9.6 WCAG conformance requirements
- Annex A: Testing statements
- Annex C: Determination of compliance
- Links to other chapters (video, docs)
EN 301 549 vs Pure WCAG: What’s Different?
While EN 301 549 Chapter 9 incorporates WCAG, complying with the full EN 301 549 standard is broader than just WCAG compliance. Here are the key differences:
1. Multi-Format Coverage
WCAG covers web content only. EN 301 549 also covers PDFs and documents (Chapter 10), native apps (Chapter 11), and video/audio capabilities (Chapter 7). If your product includes downloadable PDFs or a mobile app, you need to address those chapters too.
2. Functional Performance Statements
Chapter 4 provides alternative compliance paths when specific technical requirements don’t apply. These focus on outcomes (e.g., "the product can be used without vision") rather than specific techniques.
3. Support and Documentation
Chapter 12 requires your documentation and support services to be accessible. This includes user manuals, help desks, and training materials — something WCAG doesn’t directly address.
4. Version Timing
EN 301 549 v3.2.1 references WCAG 2.1, not WCAG 2.2. While WCAG 2.2 was published in 2023, EN 301 549 hasn’t been updated to reference it yet. For legal compliance, WCAG 2.1 AA is technically sufficient, but targeting 2.2 is recommended.
5. Accessibility Statement
The EAA (which references EN 301 549) requires an accessibility statement. WCAG itself doesn’t require documentation — it’s purely technical. EN 301 549 aligns with the EAA’s documentation requirements.
How to Demonstrate EN 301 549 Compliance
Compliance Documentation
EN 301 549 Annex C provides a template for documenting compliance. For each applicable clause, you document whether:
- Supports - The product meets the requirement
- Partially supports - Some aspects meet the requirement
- Does not support - The product does not meet the requirement
- —Not applicable - The requirement doesn’t apply to this product
Generate Compliance Documentation
inclly automatically maps scan results to EN 301 549 clauses and can generate compliance documentation showing which requirements are met, partially met, or failed.
Start Free ScanFrequently Asked Questions
Where can I get the full EN 301 549 document?
EN 301 549 is freely available from the ETSI website (etsi.org). Search for "EN 301 549" to find the latest version. The document is published in English, French, and German.
Is EN 301 549 only used in the EU?
No, EN 301 549 is referenced globally. Australia's Disability Discrimination Act references it, and many countries use it as a benchmark for ICT accessibility. It's becoming a de facto international standard.
Will EN 301 549 be updated to reference WCAG 2.2?
This is expected in a future update. When it happens, the WCAG 2.2 criteria will be incorporated. Since WCAG 2.2 is backwards compatible with 2.1, products meeting WCAG 2.2 will meet future EN 301 549 requirements.
Do I need third-party certification?
The EAA does not require third-party certification. Self-assessment and declaration of conformity are acceptable. However, third-party audits can strengthen your compliance position and may be required by contracts or procurement policies.
How does EN 301 549 relate to Section 508?
Section 508 is US law for federal agencies. The revised Section 508 (2017) adopted WCAG 2.0 Level AA. EN 301 549 also incorporates WCAG, so meeting one standard helps with the other. EN 301 549 is more current as it references WCAG 2.1.
Continue Learning
Explore related guides to support your European accessibility compliance.
EAA Compliance Checklist
EN 301 549 Chapter 9 web requirements mapped to WCAG 2.2 criteria.
European Accessibility Act
What US and UK businesses need to know about the EAA in 2026.
EAA vs WCAG
How the European Accessibility Act relates to WCAG and what compliance means.
WCAG 2.2 AA Checklist
All 50 Level A and AA success criteria with testing indicators.
Ready to Check Your EN 301 549 Compliance?
inclly scans your website against all EN 301 549 Chapter 9 web requirements. Results are mapped to both WCAG criteria and EN 301 549 clauses, making it easy to document compliance.