EN 301 549 – The European Standard for Digital Accessibility
The EN 301 549 standard defines binding accessibility requirements for ICT products and services in Europe. It is the technical backbone behind the EAA, BFSG and BITV 2.0 – and specifies what websites, apps, software and documents must deliver to ensure equal access for people with disabilities.
The key facts at a glance
EN 301 549 summarised
These four points summarise what the standard regulates and why it serves as the technical foundation behind several European laws.
-
Published by ETSI together with CEN and CENELEC
-
Fully integrates WCAG 2.1 as the basis for web content
-
Harmonised in the EU Official Journal on 18 August 2021
-
Successor version with WCAG 2.2 (v4.1.1) announced for 2026 – not yet harmonised
European harmonised standard
Applies to web, apps, software & documents
Technical basis of BFSG & BITV 2.0
Currently valid: Version 3.2.1
What is EN 301 549?
EN 301 549 is a European harmonised standard that defines accessibility requirements for ICT products and services. Published by the European Telecommunications Standards Institute (ETSI), it serves as the central technical reference for accessible access to digital offerings across Europe.
The currently valid Version 3.2.1, published in 2021, fully integrates WCAG 2.1 as the requirements basis for web-based content and extends it with requirements for non-web software, mobile applications, hardware, documents and services. EN 301 549 therefore covers the entire spectrum of digital ICT products.
As a harmonised standard, it forms the technical foundation for implementing the European Accessibility Act (EAA), the Accessibility Strengthening Act (BFSG) and BITV 2.0. Demonstrating compliance with EN 301 549 constitutes the legally recognised conformity proof for digital accessibility requirements. Public sector bodies also use this standard as the reference for accessible access to their digital services.
What does EN 301 549 cover?
Unlike WCAG, which focuses exclusively on web content, EN 301 549 applies to the full spectrum of digital ICT products and services – including web applications, mobile apps, software products and digital services for end users:
-
Websites & web applications – full WCAG 2.1 Level AA integration
-
Mobile applications & apps – accessible access on all devices
-
Software & desktop applications – operability and compatibility with assistive technologies
-
Documents & PDFs – accessible formats for all users
-
Products & hardware – physical ICT products with digital interfaces
-
Services – digital service offerings and support processes
Version 3.2.1 – currently valid
Requirements of EN 301 549 at a glance
The standard is structured into chapters that each define specific requirements for different ICT categories. For web content and non-web software, the four WCAG principles serve as the benchmark – supplemented by standard-specific accessibility requirements. Each chapter defines its own criteria, for example for colour contrast, keyboard navigation or form validation. A successor version (v4.1.1) referencing WCAG 2.2 is announced for 2026 but has not yet been harmonised in the EU Official Journal and is therefore not yet legally binding.
-
Web content: full compliance with WCAG 2.1 conformance level AA
-
Non-web documents: WCAG criteria adapted for offline content and PDFs
-
Software & apps: operability, compatibility with assistive technology
-
Two-way communication: real-time accessibility for voice and video telephony
-
Hardware: physical operability and tactile recognisability
-
Support services: accessible product information and documentation
Practical examples: how EN 301 549 applies in reality
A concrete example makes the standard's requirements tangible: a bank launching a new banking app must verify that all functions meet the EN 301 549 criteria – from keyboard navigation to screen reader output. These criteria apply regardless of whether the product is a web application, a mobile application or another digital service. They are formulated in a technology-neutral way. ETSI publishes detailed information on individual chapters in its official specification documents.
Example: banking app
A mobile application must meet WCAG criteria for operability – including full keyboard navigation and sufficient colour contrast.
Example: government portal
Public sector bodies must ensure accessible access to their digital services – the same standard applies as in the private sector.
Example: software update
Every new version of software or an app must continue to meet requirements – accessibility does not end at the first release.
Example: documents
PDFs and other documents offered as part of a digital product must also be accessible – not just the website itself.
SiteCockpit Service
Have your EN 301 549 conformity assessed professionally
EN 301 549, BFSG and BITV 2.0 – how do they relate?
EN 301 549 is not a standalone law but the technical standard referenced by European and German legislation on digital accessibility. For public sector bodies, the related EU directive is known as the "Web Accessibility Directive" and also refers to this standard. The relationship at a glance:
-
EU Directive / European Accessibility Act (EAA): defines the legal objective – EN 301 549 provides the technical path
-
BFSG (Germany): obliges private companies – EN 301 549 is the conformity proof
-
BITV 2.0 (Federal): obliges federal authorities – EN 301 549 as the technical reference
-
WCAG 2.1: fully integrated into EN 301 549 – no contradiction, but an extension
Frequently asked questions about EN 301 549
WCAG (Web Content Accessibility Guidelines) defines requirements exclusively for web content. EN 301 549 fully integrates WCAG 2.1 and extends it to all ICT categories: software, apps, hardware, documents and services. EN 301 549 is therefore the more comprehensive standard – WCAG is a subset of it.