What Is EN 301 549?
EN 301 549 is the European standard for the accessibility of information and communication technology. It is published jointly by the European standards bodies ETSI, CEN and CENELEC, and the current version, 3.2.1, dates from 2021.
The standard covers far more than websites, including software, documents, hardware and two-way voice communication. For web content, Clause 9 reproduces the WCAG 2.1 Level A and AA success criteria, so a web page that meets WCAG 2.1 AA meets the web requirements of EN 301 549. That is why this checker runs the WCAG 2.1 AA rules when you choose EN 301 549.
EN 301 549 is the harmonised standard for the EU Web Accessibility Directive, which covers public sector websites and apps. It is also the reference point for the European Accessibility Act (EAA), which applies to many consumer products and services, including e-commerce, banking, transport and e-books, from June 28, 2025. A new version of the standard is being prepared to support the EAA.
| Published by | ETSI, CEN and CENELEC |
|---|---|
| Current version | 3.2.1 (2021) |
| Web requirements | Clause 9: WCAG 2.1 Level A and AA |
| Used for | EU Web Accessibility Directive and the European Accessibility Act |
| EAA applies from | June 28, 2025 |
Who Needs EN 301 549?
- Public sector bodies in EU member states, for websites and mobile apps under the Web Accessibility Directive.
- Businesses selling covered products and services to consumers in the EU under the European Accessibility Act, such as online shops, banks, transport operators and e-book publishers, including companies based outside the EU.
- Suppliers to public bodies in the EU, where EN 301 549 is used in public procurement.
- Organizations that follow it voluntarily as a comprehensive accessibility benchmark.
What EN 301 549 Covers Beyond a Web Page Scan
The web clause mirrors WCAG, but the full standard asks more. These are the areas teams most often overlook.
Clause 9: Web
The WCAG 2.1 A and AA success criteria for web pages. This is what this checker tests.
Clause 10: Documents
PDFs and office documents offered for download must meet equivalent requirements, including tagging and reading order.
Clause 11: Software
Apps and desktop software, including mobile apps, have their own set of requirements based on WCAG.
Clause 4: Functional performance
Products must be usable without vision, with limited vision, without hearing and with limited manipulation or strength.
Clause 12: Documentation and support
Help documentation and support services must be accessible and describe accessibility features.
Accessibility statement
The Web Accessibility Directive requires public bodies to publish one, and the EAA requires information on how services meet accessibility requirements.
What This EN 301 549 Checker Tests
WCAG 2.1 Level AA has 50 success criteria. This checker runs 62 automated rules, which test 19 of them. The rest need a person to judge, and they are listed here so nothing is missed. Open a principle to see every criterion.
Perceivable 9 of 20 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 1.1.1 Non-text Content | A | Automated (7 rules) |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Manual review |
| 1.2.2 Captions (Prerecorded) | A | Automated (1 rule) |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | Manual review |
| 1.2.4 Captions (Live) | AA | Manual review |
| 1.2.5 Audio Description (Prerecorded) | AA | Manual review |
| 1.3.1 Info and Relationships | A | Automated (9 rules) |
| 1.3.2 Meaningful Sequence | A | Manual review |
| 1.3.3 Sensory Characteristics | A | Manual review |
| 1.3.4 Orientationnew in 2.1 | AA | Manual review |
| 1.3.5 Identify Input Purposenew in 2.1 | AA | Automated (1 rule) |
| 1.4.1 Use of Color | A | Automated (1 rule) |
| 1.4.2 Audio Control | A | Automated (1 rule) |
| 1.4.3 Contrast (Minimum) | AA | Automated (1 rule) |
| 1.4.4 Resize Text | AA | Automated (1 rule) |
| 1.4.5 Images of Text | AA | Manual review |
| 1.4.10 Reflownew in 2.1 | AA | Manual review |
| 1.4.11 Non-text Contrastnew in 2.1 | AA | Manual review |
| 1.4.12 Text Spacingnew in 2.1 | AA | Automated (1 rule) |
| 1.4.13 Content on Hover or Focusnew in 2.1 | AA | Manual review |
Operable 6 of 17 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 2.1.1 Keyboard | A | Automated (3 rules) |
| 2.1.2 No Keyboard Trap | A | Manual review |
| 2.1.4 Character Key Shortcutsnew in 2.1 | A | Manual review |
| 2.2.1 Timing Adjustable | A | Automated (1 rule) |
| 2.2.2 Pause, Stop, Hide | A | Automated (2 rules) |
| 2.3.1 Three Flashes or Below Threshold | A | Manual review |
| 2.4.1 Bypass Blocks | A | Automated (1 rule) |
| 2.4.2 Page Titled | A | Automated (1 rule) |
| 2.4.3 Focus Order | A | Manual review |
| 2.4.4 Link Purpose (In Context) | A | Automated (2 rules) |
| 2.4.5 Multiple Ways | AA | Manual review |
| 2.4.6 Headings and Labels | AA | Manual review |
| 2.4.7 Focus Visible | AA | Manual review |
| 2.5.1 Pointer Gesturesnew in 2.1 | A | Manual review |
| 2.5.2 Pointer Cancellationnew in 2.1 | A | Manual review |
| 2.5.3 Label in Namenew in 2.1 | A | Manual review |
| 2.5.4 Motion Actuationnew in 2.1 | A | Manual review |
Understandable 3 of 10 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 3.1.1 Language of Page | A | Automated (3 rules) |
| 3.1.2 Language of Parts | AA | Automated (1 rule) |
| 3.2.1 On Focus | A | Manual review |
| 3.2.2 On Input | A | Manual review |
| 3.2.3 Consistent Navigation | AA | Manual review |
| 3.2.4 Consistent Identification | AA | Manual review |
| 3.3.1 Error Identification | A | Manual review |
| 3.3.2 Labels or Instructions | A | Automated (1 rule) |
| 3.3.3 Error Suggestion | AA | Manual review |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Manual review |
Robust 1 of 3 automated
| Success criterion | Level | How it is tested |
|---|---|---|
| 4.1.1 Parsing (obsolete in WCAG 2.2) | A | Manual review |
| 4.1.2 Name, Role, Value | A | Automated (28 rules) |
| 4.1.3 Status Messagesnew in 2.1 | AA | Manual review |
What to Check by Hand
Automated rules find the code-level failures. Add these checks to cover what they cannot judge.
- Test key user journeys, such as buying a product or opening an account, with a keyboard and a screen reader.
- Check downloadable PDFs and documents against Clause 10.
- Review your mobile app separately, under Clause 11.
- Zoom to 400 percent and check reflow (WCAG 1.4.10).
- Publish an accessibility statement with a feedback mechanism.
- Keep dated evidence of testing and fixes for regulators and customers.
For a step-by-step routine, see Plan manual testing in our Help Center.
How to Use Your Results
- Fix critical and serious issues first, especially on forms, navigation and checkout. Each issue shows the failing code and how to fix it.
- Filter by criterion to hand one type of issue to the right person, for example contrast to design and labels to development.
- Rescan after each fix to confirm it, then run the manual checks above.
- Monitor the whole site. A free scan checks one page. AccessBell Pro monitors up to 500 URLs per domain against WCAG 2.1 Level AA every day and alerts you to new issues.
Related Guides
EN 301 549 Checker Questions
Is EN 301 549 the same as WCAG 2.1?
For web content, yes: Clause 9 reproduces the WCAG 2.1 Level A and AA success criteria. The full standard also covers documents, software, hardware, functional performance and support, so it is broader than WCAG.
Does the European Accessibility Act apply to companies outside the EU?
Yes, if they sell covered products or services to consumers in the EU. Microenterprises providing services, with fewer than 10 employees and annual turnover or balance sheet of no more than 2 million euros, are exempt from the service requirements.
Will EN 301 549 move to WCAG 2.2?
A new version of EN 301 549 is being prepared to support the European Accessibility Act, and it is expected to reference a newer version of WCAG. Testing against WCAG 2.2 AA now covers WCAG 2.1 AA as well, so you are prepared either way.
Can I claim EN 301 549 conformance from a scan?
An automated scan covers part of Clause 9. A conformance claim also needs manual testing of the web criteria that tools cannot judge, plus any other clauses that apply to your product.
Sources
- ETSI: EN 301 549 V3.2.1 (2021-03) (opens in a new tab)
- EUR-Lex: Directive (EU) 2019/882, the European Accessibility Act (opens in a new tab)
- EUR-Lex: Directive (EU) 2016/2102, the Web Accessibility Directive (opens in a new tab)
This page explains technical standards and is not legal advice. See our disclaimer.