Guide
A Complete Guide to EN 301 549 Standards and Compliance
)
On this page
EN 301 549 is the harmonised European standard for ICT accessibility. This guide breaks down what EN 301 549 is, how it relates to WCAG and EU/UK law, and what your organisation needs to do to meet today’s requirements. You’ll also learn which products and services it covers, which accessibility laws reference it, and practical steps to maintain ongoing compliance.
What is EN 301 549?
There are approximately 1.3 billion people worldwide living with a disability — that is one in six people navigating the internet with tools, technologies, and workarounds that most digital products simply do not consider. Whether it is low vision, hearing loss, cognitive differences, or motor limitations, these disabilities directly shape how people experience your content, software, hardware, and services.
If your digital products are not accessible, you are not just creating a poor user experience. You are excluding a significant portion of your potential audience and, increasingly, exposing your organisation to legal risk. The fix is to build accessibility in from the start and test against the barriers that users with disabilities encounter every day. This expands your audience, strengthens your legal position, and creates a genuinely more inclusive experience.
That is where EN 301 549 comes in. Developed by ETSI (European Telecommunications Standards Institute) in collaboration with CEN and CENELEC, EN 301 549 is the harmonised European standard that specifies accessibility requirements for all ICT products and services. It goes further than WCAG, extending beyond web content to cover hardware, software, mobile apps, documents, telecommunications, and more.
In this guide, we will walk you through EN 301 549 V3.2.1, the principles behind its requirements, and how it supports both legal compliance and the creation of accessible, inclusive digital experiences across EU and UK markets.
What is EN 301 549?
EN 301 549 is an internationally recognised standard created by European standardisation bodies to make ICT products and services accessible to people with disabilities. The standard provides clear, testable requirements for designing and building technology that works for everyone, including people who use assistive technologies.
The standard covers a broad range of ICT including:
Websites and web applications
Mobile applications
Desktop and embedded software
Non-web documents such as PDFs, Word files, and spreadsheets
Hardware including computers, smartphones, kiosks, and ATMs
Telecommunications equipment and services
Two-way communication and relay services
Documentation and customer support services
EN 301 549 directly incorporates the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA in full within Chapter 9 (Web) and Chapter 11 (Non-web software). This means that if your organisation already works towards WCAG 2.1 Level AA for web content, you are well positioned for EN 301 549 conformance across your web properties. However, EN 301 549 extends significantly beyond what WCAG covers, addressing hardware, documents, and communications infrastructure that WCAG does not touch.
The current version is EN 301 549 V3.2.1, published in 2021. Version 4.1.1 is in development and expected in 2026, with planned support for WCAG 2.2 and the European Accessibility Act.
What is EN 301 549 Conformance?
Although "EN 301 549 compliance" is a commonly used phrase, "EN 301 549 conformance" is technically more accurate. The standard itself is not a law. It is a technical framework that laws and regulations reference to define what accessible ICT looks like in practice.
Conformance with EN 301 549 means your ICT products and services meet the standard's testable criteria. It is the recognised way to demonstrate that your organisation has met its obligations under laws such as the European Accessibility Act, the EU Web Accessibility Directive, and the UK Public Sector Bodies Accessibility Regulations.
EN 301 549 is self-scoping by design. This means that not every requirement applies to every product. Each clause begins with a precondition, such as "Where ICT provides a visual interface..." and the requirement only applies if that precondition is true for your product or service. This makes the standard more precise but also means organisations must carefully assess which clauses apply to their specific ICT estate.
The four key principles underlying EN 301 549
EN 301 549 is built on the same four principles that underpin WCAG: Perceivable, Operable, Understandable, and Robust (POUR). These apply specifically to web and non-web software content within the standard.
Perceivable All information and interface components must be presentable to users in ways they can perceive. Nothing should be invisible to any of their senses, and content should not rely on a single sensory mode.
Practical examples include:
Providing text alternatives for images, graphs, and non-text content
Adding captions and audio descriptions to video content
Ensuring sufficient colour contrast between text and background
Making content adaptable so it can be presented in different ways without losing meaning
Operable Users must be able to interact with and navigate all ICT. Interface components and navigation must work across the full range of input methods and assistive technologies people use.
Practical examples include:
Making all functionality operable by keyboard alone
Avoiding content that flashes more than three times per second
Providing users enough time to read and use content
Ensuring focus indicators are clearly visible for keyboard users
Understandable Content and interfaces must be clear and predictable. Users should be able to understand both the information presented and how the interface works.
Practical examples include:
Specifying the language of content so screen readers apply the correct pronunciation
Using consistent navigation across pages and screens
Providing clear instructions and accessible labels for all form inputs
Writing meaningful, actionable error messages
Robust Content must be robust enough to work reliably with current and future assistive technologies. This includes ensuring compatibility with screen readers, voice control software, braille displays, and other assistive tools.
Practical examples include:
Establishing the name, role, and value of each user interface element programmatically
Ensuring status messages can be read by assistive technologies without requiring focus
Building to recognised standards so content remains accessible as technology evolves
EN 301 549 conformance structure
Unlike WCAG which uses Level A, AA, and AAA, EN 301 549 uses a pass/fail conformance model based on self-scoping clauses. Conformance is achieved when a precondition applies to your product and the corresponding test in Annex C is passed. When the precondition does not apply, the requirement is not relevant to that product.
For web and mobile content, the minimum standard for EU and UK legal compliance is the criteria equivalent to WCAG 2.1 Level AA, as incorporated in EN 301 549 Chapters 9 and 11. Organisations should use this as their baseline and assess additional chapters based on the nature of their ICT products.
)
How Does EN 301 549 Affect Accessibility Laws?
EN 301 549 is not a law in itself, but it is the technical standard that EU and UK accessibility laws rely on to define what compliant ICT looks like. Meeting EN 301 549 is how organisations demonstrate compliance with the frameworks below.
The European Accessibility Act (EAA)
The EAA (European Accessibility Act, Directive 2019/882) is the EU’s landmark private sector accessibility legislation, which came into force in June 2025. It applies to a defined range of products and services across all EU member states, including e-commerce platforms, banking services, transport services, e-books, and consumer electronic devices.
EN 301 549 is the technical standard used to verify EAA compliance. Authorities across EU member states use EN 301 549 to assess whether products and services meet the Act’s accessibility requirements. If your products meet EN 301 549 standards, you are satisfying your legal obligations under the EAA. V4.1.1, due in 2026, is being developed specifically to formally support the EAA.
Learn more about the EAA.
The EU Web Accessibility Directive (WAD) and Public Sector Bodies Accessibility Regulations 2018
The Web Accessibility Directive (Directive 2016/2102) requires all public sector bodies across EU member states to make their websites and mobile apps accessible. In the UK, this was transposed into the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, which remains UK law post-Brexit.
EN 301 549 V3.2.1 officially supports the WAD since August 2021. Public sector bodies in both the EU and UK must meet EN 301 549 requirements, publish accessibility statements, and have those statements reviewed at least every three years. Central government, local authorities, NHS organisations, universities, and publicly funded charities all fall within scope.
Learn more about the Public Sector Bodies Accessibility Regulations.
The Equality Act 2010 (UK)
The Equality Act 2010 is the UK’s primary anti-discrimination law. It requires all organisations providing goods, services, or facilities to the public to make reasonable adjustments so that disabled people are not put at a substantial disadvantage. While the Act does not mandate EN 301 549 or WCAG specifically, conformance with EN 301 549 is strong evidence that an organisation has met its reasonable adjustments duty for digital services.
For UK organisations managing both Equality Act obligations and public sector regulations, EN 301 549 provides a single technical framework that satisfies both.
Learn more about the Equality Act 2010.
The Barrierefreiheitsstarkungsgesetz (BFSG) Germany
Germany’s BFSG transposes the European Accessibility Act into German national law, with enforcement beginning June 2025. It applies to private sector organisations providing products and services in Germany within the EAA’s defined scope. EN 301 549 is the technical standard used to demonstrate compliance with BFSG requirements, making it the practical benchmark for any organisation operating in or selling into the German market.
Learn more about the BFSG.
Loi pour une Republique Numerique (France)
France’s Digital Republic Act, together with the RGAA (Referentiel General d’Amelioration de l’Accessibilite), establishes digital accessibility requirements for public sector bodies and, increasingly, private sector organisations under the EAA. The RGAA is itself aligned with EN 301 549 and WCAG standards. French organisations and international businesses operating in France must ensure their digital products and services meet EN 301 549 requirements to satisfy both public sector regulations and EAA obligations.
Learn more about French digital accessibility laws.
Common Accessibility Barriers EN 301 549 Helps Address
EN 301 549 addresses a broad range of issues that affect how people with disabilities interact with websites, apps, software, documents, and hardware. Beyond the web-specific barriers that WCAG covers, EN 301 549 also addresses:
Non-web documents such as inaccessible PDFs, Word files, and spreadsheets that cannot be read by screen readers due to missing tags and structure
Software interfaces including desktop applications and operating systems that do not expose name, role, and value information to assistive technologies
Hardware and physical interfaces such as kiosks, ATMs, and consumer devices that lack accessible input methods or audio output
Telecommunications and two-way communication tools that do not support relay services or real-time text for users who are Deaf or hard of hearing
Biometric technology including facial recognition and fingerprint systems that must be accessible to people with disabilities
Documentation and customer support services that are not available in accessible formats, leaving users without the guidance they need
Focus and keyboard issues across software interfaces that prevent keyboard-only users from navigating or interacting with content
Time limits and automatic timeouts across applications and portals that expire without sufficient warning or the ability to extend
Authentication barriers across login and verification flows that present cognitive or motor challenges to users with disabilities
Your Path to EN 301 549 Conformance Starts with AudioEye
Meeting EN 301 549 requirements means testing your full ICT estate regularly, fixing issues correctly, and verifying that every update maintains accessibility. Without a structured process and expert support, it is easy to overlook issues or introduce new barriers across web content, documents, and software interfaces.
AudioEye makes EN 301 549 conformance achievable and maintainable with our Accessibility Platform. Our solution combines powerful automation with human-assisted AI technology and expert review, giving you full visibility into accessibility issues across your digital estate and the confidence that your content is both compliant and genuinely accessible.
With AudioEye, you can take advantage of:
Active Monitoring that continuously scans your site and content for accessibility issues
Automatic Fixes that resolve common accessibility barriers without manual intervention
Expert Audits that identify issues automated tools cannot detect, including manual testing with assistive technologies
Legal support, custom fixes, accessibility training, and ongoing reporting
Whether you are a private sector business, a public sector organisation, or an international company managing EU and UK compliance simultaneously, AudioEye provides the tools and expertise to keep your digital products aligned with EN 301 549 requirements and the laws that reference it.
Start Building for EAA Compliance
Frequently Asked Questions
AudioEye Demo
Accessibility is a journey, and we’re here to help guide you down that path.
Get in touch to see a customised approach to compliance for your organisation.