EN 301 549 Compliance
EN 301 549 is the European accessibility standard the EAA points to — and for the web, its Chapter 9 is WCAG 2.1 AA. Here is what the standard requires, and how to check your site against it in about a minute.
Check my website free3 free scans per day · No credit card · Results in 60 seconds
What is EN 301 549?
EN 301 549 — full title "Accessibility requirements for ICT products and services" — is the European harmonised standard that defines what it means for technology to be accessible. It is maintained by the three European Standards Organisations (ETSI, CEN, and CENELEC) and originated from an EU standardisation request tied to public procurement, so it has been the reference for accessible ICT buying in Europe for years.
What makes it matter now is that EU accessibility law points to it. The European Accessibility Act and the public-sector Web Accessibility Directive both use EN 301 549 as the technical benchmark: meet the standard and you get a presumption of conformity with the law. For a website, the standard resolves to one thing you can actually test — WCAG 2.1 Level AA.
Which version of EN 301 549 is current?
The version that matters today is EN 301 549 V3.2.1, published in March 2021 — the one that incorporates WCAG 2.1 Level AA and that EU accessibility law currently relies on. The standard has been revised repeatedly as WCAG and the underlying EU directives evolved, and further work aligning it with WCAG 2.2 is under way — but V3.2.1 is the version harmonised for the European Accessibility Act right now.
| Version | Year | What changed |
|---|---|---|
| V1.1.1 | 2014 | The first EN version, produced under EU Mandate M/376 to make ICT procurement accessible. Built on WCAG 2.0 and aligned with the US Section 508 refresh. |
| V2.1.2 | 2018 | Revised to support the public-sector Web Accessibility Directive (EU 2016/2102) — the version public bodies used for their websites and apps. |
| V3.2.1Current | 2021 | The current harmonised version. Chapter 9 adopts WCAG 2.1 Level AA, and this is the version the European Accessibility Act relies on for a presumption of conformity. |
Always confirm the latest published revision on the ETSI portal; V3.2.1 is the version currently referenced by EU law.
Law, standard, web rules: how EN 301 549 fits
EN 301 549 sits in the middle of a chain. The law names the standard; the standard names the web rules. Follow it down and it lands on WCAG 2.1 AA.
The law
European Accessibility Act
Directive (EU) 2019/882 sets the accessibility obligation for covered products and services. It does not spell out the technical rules — it points to a harmonised standard.
The standard
EN 301 549
The harmonised European standard for ICT accessibility. Meeting it gives a "presumption of conformity" with the EAA — and it is the standard EU public procurement has referenced for years.
The web rules
WCAG 2.1 Level AA
EN 301 549 Chapter 9 adopts the W3C's WCAG 2.1 A and AA success criteria wholesale for web content. So for a website, EN 301 549 conformance is WCAG 2.1 AA conformance.
What EN 301 549 covers
The standard is broader than websites — it is organised into clauses for different kinds of technology. These are the ones that decide whether a digital product passes.
Chapter 9
Web
Incorporates WCAG 2.1 Level A and AA by reference. This is the chapter that governs websites and web apps — the bulk of what most businesses need.
Chapter 10
Non-web documents
PDFs, Word, and other downloadable documents. Maps the same WCAG criteria onto document content — relevant if you publish reports, invoices, or e-books.
Chapter 11
Software
Non-web software, including mobile apps. Applies WCAG criteria plus software-specific requirements such as platform accessibility-service support.
Chapter 12
Documentation & support
Product documentation and support services (help desks, chat) must themselves be accessible and describe the product's accessibility features.
Chapters 4–5
Functional & generic
Functional-performance statements (use without vision, hearing, speech, etc.) and generic requirements that apply across every kind of ICT.
Chapters 6–7
Voice & video
Requirements for ICT with two-way voice communication and for video capabilities — captions, audio description, and caption/CV controls where relevant.
For most businesses the deciding chapter is Chapter 9 (Web) — and because it adopts WCAG 2.1 AA, a WCAG scan is the practical way to measure it.
EN 301 549 web checklist (Chapter 9 / WCAG 2.1 AA)
The web slice of the standard, in plain language. These are the WCAG 2.1 AA requirements a website has to meet — grouped the way WCAG groups them.
Perceivable
- Text alternatives for images, icons, and controls
- Captions for pre-recorded video; audio description where needed
- Content works without relying on colour alone
- Text contrast of at least 4.5:1 (3:1 for large text)
- Content reflows and stays readable when zoomed to 200%
Operable
- Everything reachable and usable by keyboard alone
- No keyboard traps; a visible focus indicator
- Enough time to read and use content
- Skip-to-content and clear, consistent navigation
- Descriptive page titles, headings, and link text
Understandable
- Page language set programmatically
- Predictable, consistent behaviour and navigation
- Form fields have labels and clear instructions
- Errors are identified in text and easy to correct
Robust
- Valid, well-structured HTML
- Name, role, and value exposed for custom components
- Status messages announced to assistive technology
This is the machine-and-manual checklist condensed. For the criteria in full, with copy-paste code, see the WCAG 2.1 AA developer guide.
From clause to fix: a worked example
A checklist tells you what to meet; this shows what a failure actually looks like in code, which EN 301 549 clause it breaks, and the one-line fix. EN 301 549 numbers its web clauses to mirror WCAG — clause 9.4.1.2 is simply WCAG success criterion 4.1.2 — so a WCAG failure is an EN 301 549 failure by the same number.
An icon-only button with no accessible name
EN 301 549 §9.4.1.2 · WCAG 2.1 SC 4.1.2 Name, Role, Value (A) · SC 1.1.1 Non-text Content (A)
A search button that shows only a magnifying-glass icon. A screen reader announces "button" with no name, so the user has no idea what it does — and it fails both the non-text-content and name/role/value criteria EN 301 549 references.
<button class="search">
<svg viewBox="0 0 20 20"><path d="M12.9 14.32a8..."/></svg>
</button><button class="search" aria-label="Search">
<svg viewBox="0 0 20 20" aria-hidden="true"><path d="M12.9 14.32a8..."/></svg>
</button>A form field with no label
EN 301 549 §9.3.3.2 · WCAG 2.1 SC 3.3.2 Labels or Instructions (A) · SC 1.3.1 Info and Relationships (A)
A placeholder is not a label — it disappears on focus and is not reliably read by assistive technology. Without a programmatic label, a screen-reader user reaches the field not knowing what to type.
<input type="email" name="email"
placeholder="Email address"><label for="email">Email address</label>
<input type="email" id="email" name="email">A scan finds these across your whole site at once — every failing element, the criterion it breaks, and the fix — instead of hunting them by hand.
The most common EN 301 549 failures
Across real-world audits, a small set of issues accounts for most failures. These are the ones worth checking first — each maps to a specific EN 301 549 web clause and the WCAG criterion behind it.
| Common failure | Clause | Who it blocks |
|---|---|---|
| Images and icons with no text alternative | §9.1.1.1 · SC 1.1.1 | Blind and low-vision users on a screen reader hear nothing meaningful. |
| Text contrast below 4.5:1 | §9.1.4.3 · SC 1.4.3 | Low-vision users, and anyone on a bright screen, cannot read the text. |
| Form fields without programmatic labels | §9.3.3.2 · SC 3.3.2 | Screen-reader users reach a field not knowing what to enter. |
| Content not reachable or usable by keyboard | §9.2.1.1 · SC 2.1.1 | Keyboard and switch users — and many screen-reader users — get stuck. |
| No visible focus indicator | §9.2.4.7 · SC 2.4.7 | Keyboard users lose track of where they are on the page. |
| Skipped or missing heading structure | §9.1.3.1 · SC 1.3.1 | Screen-reader users lose the outline they navigate by. |
| Vague link text such as "click here" | §9.2.4.4 · SC 2.4.4 | Users scanning links out of context cannot tell them apart. |
| Custom widgets missing name, role, or value | §9.4.1.2 · SC 4.1.2 | Assistive technology cannot announce or operate the control. |
Who needs to meet EN 301 549?
Businesses under the EAA
Any company offering a covered product or service to EU consumers meets the EAA by conforming to EN 301 549 — for a website, that means WCAG 2.1 AA.
Public-sector suppliers
EU public bodies must meet EN 301 549 under the Web Accessibility Directive, and reference it in procurement — so vendors selling to the public sector are held to it too.
Developers & procurement
Teams evaluating or building ICT use EN 301 549 as the acceptance criteria. For the web portion, the fastest read is a WCAG 2.1 AA scan.
EN 301 549 and the VPAT / Accessibility Conformance Report
If you sell software or digital services to enterprises or the public sector, you will eventually be asked for a VPAT — a Voluntary Product Accessibility Template. It is a standard document, maintained by the Information Technology Industry Council, in which a vendor reports how a product measures up against accessibility standards. The EU edition of the VPAT reports specifically against EN 301 549 (the INT edition covers EN 301 549, Section 508, and WCAG together).
A completed VPAT is called an Accessibility Conformance Report (ACR). For each requirement it records one of Supports, Partially Supports, or Does Not Support, with remarks. Buyers use it to compare vendors and to satisfy their own procurement and accessibility obligations — it is increasingly a condition of the sale, not a nicety.
A VPAT is a self-disclosure, not a certification — its value rests entirely on the evidence behind it. That is where a scan helps: WCAGsafe gives you per-criterion WCAG 2.1 AA results — pass, fail, and needs-review for each success criterion — which map directly onto the Chapter 9 rows of an EN 301 549 VPAT, plus a dated audit record you can keep on file as the supporting documentation.
EN 301 549 vs WCAG — what's the difference?
They are related but not interchangeable. WCAG is a set of guidelines for web content, written by the W3C. EN 301 549 is a European standard for all ICT — hardware, software, documents, voice, video, support — and for the web part, it simply adopts WCAG 2.1 AA rather than reinventing it.
So for a website the two line up exactly: pass WCAG 2.1 AA and you have met Chapter 9 of EN 301 549. The difference only appears once you go beyond web content — a mobile app, a downloadable PDF, or a support line each bring in EN 301 549 clauses that plain WCAG does not cover. If your product is a website, WCAG 2.1 AA is the whole job; if it is a broader ICT product, WCAG is the biggest single piece of it.
EN 301 549 vs Section 508 and the Web Accessibility Directive
EN 301 549 does not stand alone — it is the technical standard several accessibility regimes point to, and it lines up with the US Section 508 through their shared reliance on WCAG. Here is how the pieces fit together.
| Framework | Region | Who it covers | Standard used |
|---|---|---|---|
| EN 301 549 | EU | The standard itself — accessibility of all ICT | Adopts WCAG 2.1 AA for web (Chapter 9) |
| Web Accessibility Directive | EU | Public-sector bodies' websites and apps | Requires EN 301 549 |
| European Accessibility Act | EU | Private-sector products and services | Requires EN 301 549 |
| Section 508 | US | US federal agencies and their suppliers | WCAG 2.0 AA — harmonised with EN 301 549 |
The practical upshot: EN 301 549 is the common thread across EU public- and private-sector accessibility law, and because it and Section 508 both build on WCAG, a single WCAG 2.1 AA (or 2.2 AA) pass puts you in a strong position across the EU and the US at once. See the Section 508 compliance guide for the US side in detail.
How to check your site against EN 301 549
Enter your URL
Paste any public page. No install, no browser extension, no code added to your site.
Scan to WCAG 2.1 AA
Our engine runs axe-core plus enhanced checks across the WCAG 2.1 A and AA criteria Chapter 9 of EN 301 549 requires.
Plain-English report
Every issue explained simply, with the exact element, your score, and how to fix it — plus what still needs a manual check.
An automated scan reliably catches the machine-testable criteria — the bulk of real-world barriers — but not every WCAG criterion can be judged by a machine. WCAGsafe tells you plainly where a human check is still needed rather than pretending it found everything.
EN 301 549 FAQs
What is EN 301 549?
EN 301 549 — full title "Accessibility requirements for ICT products and services" — is the European harmonised standard that defines how information and communication technology must be accessible to people with disabilities. It is published by the European Standards Organisations (ETSI, CEN, CENELEC) and is the technical benchmark that EU accessibility law, including the European Accessibility Act, points to.
Is EN 301 549 the same as WCAG?
No, but they overlap heavily for the web. EN 301 549 is broader — it covers hardware, software, documents, voice and video, and support services, not just websites. For web content specifically, its Chapter 9 adopts the W3C's WCAG 2.1 Level A and AA success criteria by reference. So conforming a website to WCAG 2.1 AA is how you meet the web portion of EN 301 549, but EN 301 549 also includes requirements WCAG does not.
Does meeting WCAG 2.1 AA mean my website is EN 301 549 compliant?
For the web portion, yes. EN 301 549 Chapter 9 is WCAG 2.1 AA, so a website that conforms to WCAG 2.1 AA meets the web accessibility requirements of the standard. If your product also includes downloadable documents (Chapter 10), software or a mobile app (Chapter 11), or support services (Chapter 12), those parts have their own requirements to check as well.
Which version of EN 301 549 is current?
The version referenced across EU accessibility law is EN 301 549 V3.2.1, published in March 2021, which is the version that incorporates WCAG 2.1 Level AA for web content. The standard is periodically revised as WCAG evolves; check the ETSI portal for the latest published version, but V3.2.1 is the one currently harmonised for the EAA.
Is EN 301 549 mandatory?
EN 301 549 is a voluntary standard, but meeting it is the practical route to legal compliance. Under the European Accessibility Act it gives a presumption of conformity — meaning if you meet the standard, you are presumed to meet the law. It is also mandated for public-sector websites and apps under the Web Accessibility Directive and referenced in EU public procurement. So while the standard itself is not a law, the laws that require accessibility point to it.
What is the difference between EN 301 549 and the European Accessibility Act?
The European Accessibility Act (EAA) is the law — it says covered products and services must be accessible. EN 301 549 is the standard — it says, in technical detail, what "accessible" means. The EAA points to EN 301 549 as the way to satisfy the obligation, and EN 301 549 points to WCAG 2.1 AA for the web. Law, standard, web rules: three layers, one testable target.
What is a VPAT for EN 301 549?
A VPAT (Voluntary Product Accessibility Template) is a standard document in which a vendor reports how a product conforms to accessibility standards. The EU edition of the VPAT reports specifically against EN 301 549, and the INT edition covers EN 301 549, Section 508, and WCAG together. A completed VPAT is called an Accessibility Conformance Report (ACR), and it records Supports, Partially Supports, or Does Not Support for each requirement. It is a self-disclosure, not a certification — its value depends on the testing evidence behind it, such as per-criterion WCAG 2.1 AA scan results.
Is EN 301 549 the same as Section 508?
No, but they are closely aligned. Section 508 is the US law covering federal agencies' ICT; EN 301 549 is the European standard. Both were deliberately harmonised and both rely on WCAG for web content — Section 508 references WCAG 2.0 AA and EN 301 549 references WCAG 2.1 AA. Because they share that WCAG foundation, conforming a website to WCAG 2.1 AA (or 2.2 AA) puts you in a strong position against both at once, even though the legal frameworks and full clause sets differ.
How do I test my website against EN 301 549?
Because the web portion of EN 301 549 is WCAG 2.1 AA, you test a website by scanning it against the WCAG 2.1 A and AA success criteria. Paste your URL into WCAGsafe and it runs the machine-testable criteria across your pages, lists each failure in plain English with the exact element and a fix, and gives you a score. Automated scanning covers the bulk of real-world barriers; some criteria still need a human check, which the report flags.
Sources
- ETSI — EN 301 549 "Accessibility requirements for ICT products and services" (V3.2.1, 2021-03; Chapter 9 incorporates WCAG 2.1 AA for web). etsi.org
- W3C Web Accessibility Initiative — Web Content Accessibility Guidelines (WCAG) 2.1. w3.org/WAI
- EUR-Lex — Directive (EU) 2019/882 (European Accessibility Act), which relies on harmonised standards such as EN 301 549 for a presumption of conformity. eur-lex.europa.eu
- European Commission — Web Accessibility Directive (EU) 2016/2102 and the mandate behind EN 301 549. ec.europa.eu
Last reviewed July 2026. This page is general information, not legal advice.
Keep exploring
Check your EN 301 549 compliance now
Free to start, results in about a minute. Test your site against the web portion of EN 301 549 — WCAG 2.1 AA — and see exactly how to fix what fails.
Start free accessibility check