EN 301 549 is a European standard specifying accessibility requirements for
information and communications technology (ICT) products and services. It is
published by the European Telecommunications Standards Institute (ETSI) and
referenced by both the Web Accessibility Directive and the European
Accessibility Act as the harmonised technical standard for digital
accessibility compliance in the EU.
[1]
EN 301 549 covers a broader range of ICT than WCAG alone. Its requirements
are organised into chapters addressing different types of technology:
| Chapter | Coverage |
|---|---|
| 4 | Functional performance statements |
| 5 | Generic requirements |
| 6 | ICT with two-way voice communication |
| 7 | ICT with video capabilities |
| 8 | Hardware |
| 9 | Web content — incorporates WCAG 2.1 |
| 10 | Non-web documents |
| 11 | Software (including mobile apps) |
| 12 | Documentation and support services |
| 13 | ICT providing relay or emergency services |
| [2] |
Chapter 9 of EN 301 549 incorporates WCAG 2.1 Level A and AA by reference
for web content. This means that for websites and web applications, meeting
WCAG 2.1 AA satisfies the web content requirements of EN 301 549.
However EN 301 549 goes beyond WCAG for non-web content. Chapter 10 applies
WCAG-derived criteria to documents such as PDFs, Word files, and
spreadsheets. Chapter 11 applies similar criteria to native mobile
applications and desktop software.
[1]
EN 301 549 has been updated several times since its initial publication:
| Version | Published | Key changes |
|---|---|---|
| V1.1.2 | 2015 | Initial publication |
| V2.1.2 | 2018 | Updated to reference WCAG 2.1 |
| V3.1.1 | 2019 | Restructured and expanded |
| V3.2.1 | 2021 | Current version referenced by the Web Accessibility Directive |
Because Chapter 9 of EN 301 549 maps directly to WCAG 2.1 AA, automated
accessibility scanning tools that test against WCAG 2.1 also satisfy the
web content requirements of EN 301 549. Tools such as a11ytest.ai include
EN 301 549 in their tag set, allowing organisations to confirm coverage
against the standard in a single scan.
[3]
The non-web chapters (10 and 11) require separate testing approaches for
documents and native applications that go beyond standard web scanning.
Last edited Apr 7, 2026, 7:21 PM · P**** J****