Short Answer
EN 301 549 is the European standard for accessibility of ICT products and services, published jointly by ETSI, CEN and CENELEC. It covers websites, documents, software, hardware and support services. Its web clause matches WCAG: version 3.2.1 (2021) uses WCAG 2.1, and version 4.1.1 (September 2026) aligns with WCAG 2.2 Level AA.
Key facts
- Full title
- Accessibility requirements for ICT products and services
- Published by
- ETSI, CEN and CENELEC
- Latest version
- V4.1.1 (2026-09), adopted 24 August 2026
- Previous version
- V3.2.1 (2021-03), based on WCAG 2.1
- WCAG relationship
- In V4.1.1, WCAG 2.2 Level AA is equivalent to meeting web clauses 9.1 to 9.4 and 9.6
- Used for
- Public procurement, the Web Accessibility Directive (EU) 2016/2102 and the European Accessibility Act (EU) 2019/882
- National adoption deadline for V4.1.1
- 31 May 2027; conflicting national standards withdrawn by 31 May 2028
What is EN 301 549 used for?
EN 301 549 was first written under the European Commission's mandate M 376 to set accessibility requirements for public procurement of ICT. It is now the technical reference for two EU laws: the Web Accessibility Directive, which covers public sector websites and apps, and the European Accessibility Act, which covers many consumer products and services.
Under EU law, following a harmonised standard whose reference is published in the Official Journal gives a presumption of conformity with the law's accessibility requirements. That is why buyers and regulators ask for EN 301 549 rather than WCAG alone.
What does EN 301 549 cover?
Unlike WCAG, which covers web content, EN 301 549 covers all kinds of ICT. The main clauses in V4.1.1 are:
- Clause 4: functional performance statements, such as use without vision or with limited reach and strength
- Clause 5: generic requirements, such as closed functionality and biometrics
- Clause 6: ICT supporting real-time bidirectional communication, including real-time text
- Clause 7: ICT with video capabilities, such as captions and audio description
- Clause 8: hardware
- Clause 9: web content, aligned with WCAG
- Clause 10: non-web documents, such as PDF and Office files
- Clause 11: non-web software, including native mobile apps
- Clause 12: information about products and services, such as documentation and support
- Clause 13: ICT providing relay or emergency service access
What changed in EN 301 549 V4.1.1?
The September 2026 version updates the standard in several ways. Clauses 9, 10 and 11 now align with WCAG 2.2, adding requirements such as target size, dragging movements, focus not obscured, consistent help, redundant entry and accessible authentication. Real-time text requirements were extended to total conversation. New annexes map the standard to the essential requirements of both the Web Accessibility Directive and the European Accessibility Act, and a new clause A.2 lets specific products and services be evaluated against the EAA.
V4.1.1 was adopted on 24 August 2026. National standards bodies must publish or endorse it by 31 May 2027 and withdraw conflicting national standards by 31 May 2028. Check the Official Journal of the EU for when its reference is published as a harmonised standard under each directive.
How do you test a website against EN 301 549?
For a website, clause 9 is the core: test against WCAG 2.2 Level AA (or WCAG 2.1 AA if you are working to V3.2.1). Then check the other clauses that apply to your service, such as PDF documents (clause 10), any native app (clause 11), video (clause 7) and your accessibility documentation and support (clause 12).
AccessibilityScore.in automates the WCAG checks that can be decided from code, such as contrast, names, labels, ARIA and target size, and flags uncertain results for review. The functional performance statements and most of the other clauses need manual testing.
