EN 301 549 -- European ICT Accessibility Standard

What EN 301 549 is

EN 301 549 is the European Standard that specifies functional accessibility requirements for Information and Communication Technology (ICT) products and services. It is developed jointly by ETSI, CEN, and CENELEC, the three recognised European Standardisation Organisations, under mandate from the European Commission. The current published version is v3.2.1, dated 2021-03^[1].

The standard is written as a catalogue of testable clauses grouped by what the ICT does rather than by who makes it. Clause 4 states functional performance outcomes (what a user with a given access need must be able to do). Clauses 5 through 13 break those outcomes into specific requirements for generic features, two-way voice communication, video, web content, non-web documents, software, documentation and support, and ICT providing relay or emergency services. Clause 14 defines conformance.

Two EU directives give EN 301 549 legal weight. Directive (EU) 2016/2102, the Web Accessibility Directive, requires public-sector websites and mobile applications across the EU to meet accessibility requirements and names EN 301 549 as the harmonised standard that provides presumption of conformity^[2]. Directive (EU) 2019/882, the European Accessibility Act, extends accessibility obligations to a defined set of private-sector products and services (consumer banking, e-commerce, e-readers, self-service terminals, passenger transport information, and more) placed on the EU market on or after 28 June 2025^[3].

How it relates to WCAG

For web content, clause 9 of EN 301 549 adopts WCAG 2.1 Level A and Level AA success criteria by reference, and clause 10 does the same for non-web documents^[1]. A web page that conforms to WCAG 2.1 AA satisfies clause 9. The inverse does not hold: satisfying clause 9 alone does not satisfy the rest of the standard, and many systems covered by the Web Accessibility Directive or the European Accessibility Act include components outside scope of WCAG.

The clauses that add requirements WCAG does not cover include:

• Clause 5 -- generic requirements. Closed functionality, biometrics, preservation of accessibility information across conversions, operable parts, hardware input mechanisms, privacy of assistive technology output.
• Clause 6 -- two-way voice communication. Real-time text (RTT) transmission, caller identification in an accessible form, alternatives to voice-only calling, video communication quality sufficient for sign language.
• Clause 7 -- video capabilities. Caption processing, audio description processing, and user controls for both.
• Clause 8 -- hardware. Physical controls, tactile indicators, mechanical operation, privacy (audio output via standard connectors so users can plug in their own headphones or hearing-aid interfaces).
• Clause 11 -- software. Platform accessibility services, user preferences, authoring tools, and non-web software requirements for screen-reader interoperability, gesture alternatives, and assistive-technology APIs.
• Clause 12 -- documentation and support services. Product documentation must itself be accessible; support services (help desks, relay, training) must accommodate disabled users.
• Clause 13 -- ICT providing relay or emergency services. Access to emergency services for deaf, hard-of-hearing, and speech-disabled users.

A team that ships WCAG 2.1 AA web content but also distributes PDFs, operates a contact centre, or ships any device with physical controls is in scope for clauses beyond clause 9 whenever the Web Accessibility Directive or European Accessibility Act applies to them.