EN 301 549 is the European standard that spells out what "accessible" actually means for information and communication technology (ICT). Published by the European Telecommunications Standards Institute (ETSI) together with CEN and CENELEC, it covers websites, mobile apps, software, electronic documents, self-service kiosks, and even hardware. If a European law says your digital product must be accessible, EN 301 549 is almost always the technical yardstick used to measure it.
The standard matters because it does the translating between law and engineering. EU legislation like the Web Accessibility Directive and the European Accessibility Act (EAA) sets the legal obligation; EN 301 549 defines the testable requirements your team can actually build against. For websites and web apps, the heart of the standard is the Web Content Accessibility Guidelines (WCAG) at level AA — so if you already know WCAG, you know most of what EN 301 549 asks of a website.
This guide walks through what the standard covers, who has to follow it, how enforcement works, and the practical steps to get a website or web application into shape.
The EU's technical benchmark
EN 301 549 is a harmonized European standard: meeting it creates a presumption of conformity with EU accessibility laws such as the Web Accessibility Directive and the European Accessibility Act.
Built on WCAG 2.1 AA
For web content, the standard incorporates WCAG 2.1 Level AA success criteria directly, then adds requirements for software, documents, hardware, and support services that WCAG alone does not cover.
Public sector and beyond
Originally mandatory for EU public-sector websites and apps, the standard now reaches private businesses too, because the EAA has applied to many consumer-facing digital products and services since June 28, 2025.
Enforced at the national level
Each EU member state monitors compliance and sets its own penalties, which can include fines, orders to fix the product, and in serious EAA cases withdrawal of a product or service from the market.
What EN 301 549 is and why it exists
Before EN 301 549, every EU country could interpret "accessible technology" its own way, which made life hard for anyone selling or operating across borders. The European Commission asked the European standards bodies to produce one common specification, and EN 301 549 was the result. It has been revised several times since its first release in 2014; the widely used version 3.2.1 (published in 2021) aligns its web requirements with WCAG 2.1 Level AA, and further updates are in progress to support the European Accessibility Act and newer WCAG versions.
The standard is organized around functional performance statements (what a user must be able to accomplish — for example, use the product without vision, without hearing, or with limited dexterity) and detailed technical requirements organized by technology type: web, non-web software, documents, hardware, and support services. For a typical website operator, the web chapter is the one that matters most.
Who must comply
Two major EU laws point to EN 301 549 as their technical standard, and together they define who is on the hook.
First, the Web Accessibility Directive (2016) requires the websites and mobile apps of public-sector bodies across the EU — government agencies, municipalities, public universities, and similar organizations — to conform to the standard and to publish an accessibility statement.
Second, the European Accessibility Act extends accessibility obligations to the private sector. Its requirements have applied since June 28, 2025 and cover a broad range of consumer-facing products and services, including e-commerce, banking services, e-books, transport booking and ticketing, telecommunications, and audiovisual media services. There is a limited exemption for microenterprises providing services (fewer than 10 employees and under EUR 2 million in annual turnover), but most established businesses selling to EU consumers are in scope — including companies based outside the EU that serve the EU market.
Core requirements for websites and web apps
For web content, EN 301 549 essentially adopts WCAG 2.1 Level AA. That means the requirements will feel familiar if you have done accessibility work before. In practical terms, your website needs to satisfy criteria such as:
- Text alternatives for images and other non-text content, so screen readers can describe them
- Captions for video and transcripts or alternatives for audio content
- Full keyboard operability — every interactive element usable without a mouse
- Sufficient color contrast between text and its background, and no reliance on color alone to convey meaning
- Clear focus indicators, logical heading structure, and meaningful link text
- Forms with programmatically associated labels, helpful error messages, and accessible validation
- Content that reflows and remains usable when zoomed to 200 percent or viewed on small screens
- Compatibility with assistive technologies through correct semantic markup and ARIA where needed
Beyond WCAG: what the standard adds
EN 301 549 goes further than WCAG in a few areas that are easy to overlook. Downloadable documents such as PDFs are explicitly covered, so an inaccessible brochure or invoice can put you out of conformance even if the site around it is fine. The standard also covers non-web software (including mobile apps, with some criteria adapted for native contexts), requirements for two-way communication services such as real-time text, and expectations for support services — meaning your help desk and product documentation should be able to serve users with disabilities and describe the product's accessibility features.
Public-sector bodies additionally must publish an accessibility statement describing conformance status, known gaps, and a feedback mechanism users can use to report barriers. Even where a statement is not legally required, it is fast becoming an expected good practice for commercial sites in the EU.
Enforcement and penalties
EN 301 549 itself is a standard, not a law, so enforcement flows through the legislation that references it. Under the Web Accessibility Directive, each member state runs a monitoring body that periodically audits public-sector sites and apps and reports results to the European Commission. Under the European Accessibility Act, national market-surveillance authorities can investigate complaints, require corrective action, impose fines, and in serious cases restrict or withdraw non-conforming products and services from the market.
Exact penalty levels vary by country because each member state sets its own sanctions, but the direction of travel is clear: since the EAA deadline passed in mid-2025, private-sector digital accessibility in the EU has shifted from a nice-to-have to an enforceable obligation, and consumers and disability organizations can lodge complaints with national authorities.
Practical steps toward compliance
Getting to conformance is a process, not a single fix. A realistic roadmap for most website operators looks like this:
- Determine your scope: which laws apply to you (Web Accessibility Directive, EAA, or both) and which digital properties and documents are covered
- Audit against WCAG 2.1 AA using a combination of automated scanning and manual testing with keyboards and screen readers
- Prioritize fixes by user impact — blocked checkout flows and inaccessible forms before cosmetic issues
- Fix content at the source: templates, components, and the design system, so new pages inherit accessibility by default
- Cover your documents: remediate high-traffic PDFs or replace them with accessible HTML
- Publish an accessibility statement and provide a working feedback channel for users who hit barriers
- Build accessibility into your workflow with developer training, design reviews, and automated checks in CI, then re-audit periodically
How EN 301 549 relates to WCAG
Think of WCAG as the ingredient and EN 301 549 as the recipe the EU has adopted. WCAG is a global, technology-focused guideline for web content published by the W3C; EN 301 549 wraps WCAG 2.1 AA in a legal-conformance framework and extends it to software, documents, hardware, and support services. If your website genuinely meets WCAG 2.1 AA, you have satisfied the core web requirements of EN 301 549 — but remember the extras, especially downloadable documents, mobile apps, and the accessibility statement.
Because the standard is periodically updated to track newer WCAG versions, the safest long-term strategy is to treat WCAG 2.2 AA as your working target. Tools can help you get there faster: an accessibility solution like AccessWiser can surface issues, add usability improvements, and support your remediation work, though no automated tool on its own can guarantee legal compliance — sustained conformance always requires fixing issues in your underlying code and content.
Frequently asked questions
Is EN 301 549 legally binding?
The standard itself is voluntary, but it becomes effectively mandatory when legislation references it. EU public-sector bodies must meet it under the Web Accessibility Directive, and conforming to it is the recognized way for private businesses to demonstrate compliance with the European Accessibility Act's digital requirements.
My company is based outside the EU. Does this apply to me?
It can. The European Accessibility Act applies to products and services offered to consumers in the EU regardless of where the provider is established. If you sell to EU customers — for example through an e-commerce site — the EAA's accessibility requirements, measured against EN 301 549, are likely to apply.
If my site meets WCAG 2.1 AA, am I done?
You have covered the core web requirements, which is most of the work for a typical website. But EN 301 549 also covers downloadable documents, mobile apps, and support services, and public-sector bodies must publish an accessibility statement. Check those areas before declaring conformance.
What is the difference between EN 301 549 and the European Accessibility Act?
The EAA is the law: it says which products and services must be accessible and who enforces that. EN 301 549 is the technical standard that defines what accessible means in testable terms. The EAA sets the obligation; EN 301 549 tells your engineers what to build.
Can an accessibility widget make my site EN 301 549 compliant?
No single tool can guarantee compliance. Widgets and automated tools can improve usability, catch many issues, and accelerate remediation, but conformance ultimately depends on your site's underlying code, content, and documents meeting the standard's requirements. Treat tools as part of a broader accessibility program, not a substitute for one.
This article is provided for general information about accessibility regulations and standards. It is not legal advice — consult a qualified professional about your specific compliance obligations.