Overview - EN 301 549
The European standard for ICT accessibility, referenced by the Web Accessibility Directive and the European Accessibility Act. Here's how its clauses map onto web content, documents and software.
EN 301 549 is organised into numbered clauses rather than a single flat checklist. Four clauses carry almost all of the day-to-day content requirements - Clause 9 for web, Clause 10 for non-web documents, Clause 11 for software including mobile apps. Clause 12 requires that the documentation and support services are themselves accessible.
A further set of clauses apply only in specific situations, such as hardware and video.
Core content clauses
- Clause 9
Web
Incorporates WCAG 2.1 Level A and AA by reference for websites and web applications, clause-by-clause mapped to the matching WCAG success criterion.
- Clause 10
Non-web documents
Applies WCAG-equivalent requirements to electronic documents distributed as part of a product or service - PDF, Word, ePub, spreadsheets and similar formats.
- Clause 11
Software
Covers non-web software - native mobile apps, desktop applications, operating systems - restating WCAG-equivalent criteria in software terms, plus platform accessibility API requirements.
Supporting clauses
These apply alongside Clauses 9–11 depending on what the product or service actually does - a kiosk with a camera and a card reader may bring in hardware, video and voice-communication requirements on top of its software ones.
- Clause 5
Generic requirements
Baseline requirements across ICT types: closed functionality, biometrics, privacy, colour/contrast, operable parts.
- Clause 6
Two-way voice communication
Real-time text and captioned-call requirements for ICT with voice communication.
- Clause 7
Video
Captions, audio description, sign language and accessible media player controls.
- Clause 8
Hardware
Physical access requirements: controls, connectors, tactile indicators, key repeat.
- Clause 12
Documentation & support services
Help desks, user guides and product documentation must themselves be accessible.
- Clause 13
Relay & emergency service access
ICT with two-way communication must not block access to relay or emergency services.
Go deeper
Web →
The full requirements for websites and web applications under Clause 9, and how the WCAG principles apply.
Non-web →
Native apps, kiosks, hardware, documents and support services under Clauses 5–8 and 10–13.
Resources
External references worth keeping close - the standard itself, official EU guidance, and further reading.
EN 301 549 V4.1.1 (full standard, PDF) . opens in a new tab
ETSI
The normative text itself, published by ETSI. Everything on this site is a plain-language summary of this document - check it directly for anything you need to cite or rely on formally.
European Accessibility Act - official overview . opens in a new tab
European Commission
The European Commission's own page on the EAA: scope, covered products and services, implementation timeline and micro-enterprise exemptions.
WCAG2ICT - applying WCAG to non-web ICT . opens in a new tab
W3C Web Accessibility Initiative
W3C guidance on how WCAG success criteria translate to non-web software and documents - the basis for how Clauses 10 and 11 restate WCAG in non-web terms.
Auditsu - accessibility resources & guides . opens in a new tab
Auditsu
Practical articles on auditing for and implementing EAA, WCAG and EN 301 549 compliance.