European Accessibility Act checklist: scope, score and action plan
This checklist tells you whether Directive (EU) 2019/882 is likely to apply to your website or app, using its product and service lists and the microenterprise test of fewer than 10 people and EUR 2 million. It then scores a WCAG 2.1 AA self-assessment mapped to EN 301 549 and writes a ranked action plan. It is a checklist with sources, not legal advice.
Updated
Is the EAA likely to apply to you?
In scope
Article 2(2)(f), e-commerce services. Applies to services provided after 28 June 2025.
- Pass · In a listed product or service categoryArticle 2(2)(f), e-commerce services.
- Pass · Offered to consumers in the EUConsumers in the Union, or offers made to them.
- Pass · Above the microenterprise limitsArticle 3(23): fewer than 10 persons, and turnover or balance sheet total not above €2 million. You entered 25 people, €3.5m turnover and €2.8m balance sheet total.
Action plan
EAA self-assessment (a checklist with sources, not legal advice)
Scope: In scope. Article 2(2)(f), e-commerce services. Applies to services provided after 28 June 2025.
Score: 9% of weighted items done (3 of 24).
FIX FIRST
- [ ] Everything can be used with a keyboard alone (links, menus, forms, checkout) and focus never gets trapped
Maps to: WCAG 2.1 2.1.1 (A), 2.1.2 (A); EN 301 549 9.2.1.1, 9.2.1.2.
Do: Tab through every flow with no mouse. Replace click handlers on divs with buttons and links, and add a way out of any modal.
- [ ] Every control has an accessible name, role and state (custom widgets use the right ARIA)
Maps to: WCAG 2.1 4.1.2 (A); EN 301 549 9.4.1.2.
Do: Use native elements first. For custom widgets, give each an aria-label or visible label and expose open, selected and checked states.
- [ ] Every form field has a visible label that is linked to it
Maps to: WCAG 2.1 1.3.1 (A), 3.3.2 (A); EN 301 549 9.1.3.1, 9.3.3.2.
Do: Pair each input with a label (for/id on the web, a labelled TextField in apps). Placeholders alone don't count.
- [ ] Form errors are shown in text, say which field, and suggest a fix
Maps to: WCAG 2.1 3.3.1 (A), 3.3.3 (AA); EN 301 549 9.3.3.1, 9.3.3.3.
Do: Write the error next to the field, tie it to the input, and move focus to the first error on submit.
- [ ] Images that carry meaning have text alternatives, and decorative ones are hidden from screen readers
Maps to: WCAG 2.1 1.1.1 (A); EN 301 549 9.1.1.1.
Do: Add alt text to product, logo and icon-button images; use empty alt for decoration. Check CAPTCHA has a non-visual option.
- [ ] The whole purchase path works with keyboard and screen reader: sign-in, security checks (CAPTCHA, one-time codes) and payment
Maps to: WCAG 2.1 Annex I Section IV(g)(ii)-(iii); for banking IV(e)(i); EN 301 549 same SCs as above, applied to the flow.
Do: Run a real purchase end to end with a screen reader. Make sure your payment provider's embedded form is reachable and labelled, and that OTP fields allow paste and autofill.
NEXT
- [ ] Buttons, input borders, icons and focus indicators have 3:1 contrast against their background
Maps to: WCAG 2.1 1.4.11 (AA), new in WCAG 2.1; EN 301 549 9.1.4.11.
Do: Darken pale input borders and icon-only buttons. This is the most commonly missed 2.1 criterion.
- [ ] A visible outline shows which element has keyboard focus
Maps to: WCAG 2.1 2.4.7 (AA); EN 301 549 9.2.4.7.
Do: Remove outline: none rules or replace them with a clear :focus-visible style.
- [ ] Text enlarges to 200% and the page reflows at 320 CSS px wide with no sideways scrolling
Maps to: WCAG 2.1 1.4.4 (AA), 1.4.10 (AA); EN 301 549 9.1.4.4, 9.1.4.10.
Do: Use relative units and responsive layouts; test at 400% zoom on a desktop browser. Tables and code blocks may scroll, nothing else should.
- [ ] Status messages (item added, saved, error) are announced without moving focus
Maps to: WCAG 2.1 4.1.3 (AA), new in WCAG 2.1; EN 301 549 9.4.1.3.
Do: Put cart updates and toasts in a live region (role=status or aria-live).
- [ ] Time limits and moving content (session time-outs, carousels) can be extended, paused or turned off
Maps to: WCAG 2.1 2.2.1 (A), 2.2.2 (A); EN 301 549 9.2.2.1, 9.2.2.2.
Do: Warn before a checkout session expires and let the user extend it. Add a pause button to auto-rotating banners.
- [ ] You publish how your service meets the accessibility requirements, in an accessible form, and a way to report problems
Maps to: WCAG 2.1 Article 13(2), Annex V; EN 301 549 no SC; an information duty.
Do: Publish an accessibility page in plain text, with contact details. Article 13(2) says the information must be available to the public and be accessible itself.
- [ ] You have tested with a screen reader and a keyboard, not only an automated scanner
Maps to: WCAG 2.1 Good practice. Scanners find only part of the issues.; EN 301 549 n/a.
Do: Book a short manual audit with NVDA or VoiceOver on your top three flows, then fix what it finds.
THEN
- [ ] Product and service pages carry accessibility information where you have it
Maps to: WCAG 2.1 Annex I Section IV(g)(i); EN 301 549 no SC; a content duty.
Do: Add an accessibility line to listings (for example, which products have accessible manuals) wherever you or the supplier know it.
- [ ] Help desk, chat and phone support can answer accessibility questions and are themselves accessible
Maps to: WCAG 2.1 Annex I Section III(d); EN 301 549 clause 12 (support services).
Do: Make sure the chat widget is keyboard operable, and that there is an email or phone route for people who can't use chat.
- [ ] Works in both portrait and landscape unless one is essential
Maps to: WCAG 2.1 1.3.4 (AA), new in WCAG 2.1; EN 301 549 9.1.3.4.
Do: Remove any orientation lock in the manifest, viewport or app settings.
- [ ] Personal-data fields (name, email, address, card) declare their purpose with autocomplete
Maps to: WCAG 2.1 1.3.5 (AA), new in WCAG 2.1; EN 301 549 9.1.3.5.
Do: Add autocomplete tokens such as given-name, email and cc-number to checkout and sign-up fields.
- [ ] Content that appears on hover or focus (tooltips, menus) can be dismissed, hovered and stays until dismissed
Maps to: WCAG 2.1 1.4.13 (AA), new in WCAG 2.1; EN 301 549 9.1.4.13.
Do: Let Escape close tooltips and keep them open while the pointer is over them.
- [ ] Nothing breaks when users override text spacing (line height 1.5, paragraph spacing 2, letter 0.12, word 0.16 times the font size)
Maps to: WCAG 2.1 1.4.12 (AA), new in WCAG 2.1; EN 301 549 9.1.4.12.
Do: Avoid fixed heights on text containers; test with a text-spacing bookmarklet or user stylesheet.
- [ ] Navigation and repeated components keep the same order on every page
Maps to: WCAG 2.1 3.2.3 (AA); EN 301 549 9.3.2.3.
Do: Render the header, footer and filter bars from shared components so order can't drift.
- [ ] A skip link or landmarks let users bypass repeated navigation
Maps to: WCAG 2.1 2.4.1 (A); EN 301 549 9.2.4.1.
Do: Add a visible-on-focus Skip to content link and use header, nav, main and footer landmarks.
- Scope reasoning
- Your service falls in a listed category and you are above the microenterprise limits, so the Annex I requirements apply to your website and app.
- Self-assessment score
- 9%3 of 24 applicable items; each item is weighted 3, 2 or 1 by how much it blocks use.
- Application date
- 28 June 2025Article 31(2): Member States apply the measures from this date.
| When | What | WCAG 2.1 / EAA reference | EN 301 549 |
|---|---|---|---|
| Fix first | Everything can be used with a keyboard alone (links, menus, forms, checkout) and focus never gets trapped | 2.1.1 (A), 2.1.2 (A) | 9.2.1.1, 9.2.1.2 |
| Fix first | Every control has an accessible name, role and state (custom widgets use the right ARIA) | 4.1.2 (A) | 9.4.1.2 |
| Fix first | Every form field has a visible label that is linked to it | 1.3.1 (A), 3.3.2 (A) | 9.1.3.1, 9.3.3.2 |
| Fix first | Form errors are shown in text, say which field, and suggest a fix | 3.3.1 (A), 3.3.3 (AA) | 9.3.3.1, 9.3.3.3 |
| Fix first | Images that carry meaning have text alternatives, and decorative ones are hidden from screen readers | 1.1.1 (A) | 9.1.1.1 |
| Fix first | The whole purchase path works with keyboard and screen reader: sign-in, security checks (CAPTCHA, one-time codes) and payment | Annex I Section IV(g)(ii)-(iii); for banking IV(e)(i) | same SCs as above, applied to the flow |
| Next | Buttons, input borders, icons and focus indicators have 3:1 contrast against their background | 1.4.11 (AA), new in WCAG 2.1 | 9.1.4.11 |
| Next | A visible outline shows which element has keyboard focus | 2.4.7 (AA) | 9.2.4.7 |
| Next | Text enlarges to 200% and the page reflows at 320 CSS px wide with no sideways scrolling | 1.4.4 (AA), 1.4.10 (AA) | 9.1.4.4, 9.1.4.10 |
| Next | Status messages (item added, saved, error) are announced without moving focus | 4.1.3 (AA), new in WCAG 2.1 | 9.4.1.3 |
| Next | Time limits and moving content (session time-outs, carousels) can be extended, paused or turned off | 2.2.1 (A), 2.2.2 (A) | 9.2.2.1, 9.2.2.2 |
| Next | You publish how your service meets the accessibility requirements, in an accessible form, and a way to report problems | Article 13(2), Annex V | no SC; an information duty |
| Next | You have tested with a screen reader and a keyboard, not only an automated scanner | Good practice. Scanners find only part of the issues. | n/a |
| Then | Product and service pages carry accessibility information where you have it | Annex I Section IV(g)(i) | no SC; a content duty |
| Then | Help desk, chat and phone support can answer accessibility questions and are themselves accessible | Annex I Section III(d) | clause 12 (support services) |
| Then | Works in both portrait and landscape unless one is essential | 1.3.4 (AA), new in WCAG 2.1 | 9.1.3.4 |
| Then | Personal-data fields (name, email, address, card) declare their purpose with autocomplete | 1.3.5 (AA), new in WCAG 2.1 | 9.1.3.5 |
| Then | Content that appears on hover or focus (tooltips, menus) can be dismissed, hovered and stays until dismissed | 1.4.13 (AA), new in WCAG 2.1 | 9.1.4.13 |
| Then | Nothing breaks when users override text spacing (line height 1.5, paragraph spacing 2, letter 0.12, word 0.16 times the font size) | 1.4.12 (AA), new in WCAG 2.1 | 9.1.4.12 |
| Then | Navigation and repeated components keep the same order on every page | 3.2.3 (AA) | 9.3.2.3 |
| Then | A skip link or landmarks let users bypass repeated navigation | 2.4.1 (A) | 9.2.4.1 |
- This is a checklist with sources, not legal advice. The Directive is applied through each Member State's own law, so enforcement, penalties and the authority you answer to differ by country. Ask a lawyer in the countries you sell in.
- Dates: Member States had to adopt the laws by 28 June 2022 and apply them from 28 June 2025 (Article 31). Service contracts agreed before 28 June 2025 may continue unchanged until they expire, but no longer than five years from that date (Article 32).
- Article 14 lets an operator rely on fundamental alteration or disproportionate burden for a specific requirement. It needs a documented assessment against Annex VI, the authorities must be told, and the Directive's recitals say it should be renewed at least every five years. Don't treat it as a blanket excuse.
- Article 2(4) leaves out some content: pre-recorded media and office files published before 28 June 2025, online maps whose essential information is accessible, third-party content you don't fund or control, and archives not updated after that date.
- Standards: the Directive's Annex I states requirements, not a standard. EN 301 549 V3.2.1 is ETSI's harmonised standard: its web clause 9 says WCAG 2.1 Level AA conformance equals meeting clauses 9.1 to 9.4, and its clause 11 covers apps. Under Article 15, conformity with a harmonised standard whose reference has been published in the Official Journal gives a presumption of conformity. I could not confirm which EN 301 549 version the Commission has listed for this Directive, so check the Official Journal before you cite it.
How does this checklist decide scope and score?
Scope follows Directive (EU) 2019/882 Article 2. Services in scope are electronic communications, access to audiovisual media, passenger transport websites and apps and ticketing, consumer banking, e-books and dedicated software, and e-commerce services, when provided to consumers after 28 June 2025. Products in scope include consumer computers and operating systems, payment terminals, ATMs, ticketing and check-in machines, interactive self-service information terminals, consumer terminal equipment for electronic communications or audiovisual media, and e-readers. 'E-commerce services' means services provided at a distance through websites and apps at a consumer's individual request with a view to concluding a consumer contract.
The microenterprise exemption is Article 4(5): microenterprises providing services are exempt from the service accessibility requirements. Article 3(23) defines a microenterprise as an enterprise that employs fewer than 10 persons and has an annual turnover not exceeding EUR 2 million or an annual balance sheet total not exceeding EUR 2 million. It applies to services, not to products, and the Directive says the status must genuinely meet Recommendation 2003/361/EC so that groups can't split up to qualify.
The score is a weighted share of the items you tick: each item has a weight of 3 (blocks use), 2 (serious) or 1 (important), and items that don't apply to your channel or offering are left out. WCAG 2.1 Level AA is the working benchmark because EN 301 549 clause 9 treats it as equivalent to its web requirements, and clause 11 applies the same ideas to apps. The score tells you where to start; it is not a compliance rating.
score = (sum of weights of ticked items) / (sum of weights of applicable items) × 100 microenterprise (services only) = staff < 10 AND (turnover ≤ €2m OR balance sheet ≤ €2m)
What does a WCAG 2.1 AA item mean in EN 301 549 and the Directive?
| Area | Item | WCAG 2.1 / Directive | EN 301 549 | Weight |
|---|---|---|---|---|
| Operable | Everything can be used with a keyboard alone (links, menus, forms, checkout) and focus never gets trapped | 2.1.1 (A), 2.1.2 (A) | 9.2.1.1, 9.2.1.2 | 3 |
| Robust | Every control has an accessible name, role and state (custom widgets use the right ARIA) | 4.1.2 (A) | 9.4.1.2 | 3 |
| Forms | Every form field has a visible label that is linked to it | 1.3.1 (A), 3.3.2 (A) | 9.1.3.1, 9.3.3.2 | 3 |
| Forms | Form errors are shown in text, say which field, and suggest a fix | 3.3.1 (A), 3.3.3 (AA) | 9.3.3.1, 9.3.3.3 | 3 |
| Perceivable | Images that carry meaning have text alternatives, and decorative ones are hidden from screen readers | 1.1.1 (A) | 9.1.1.1 | 3 |
| EAA-specific | The whole purchase path works with keyboard and screen reader: sign-in, security checks (CAPTCHA, one-time codes) and payment | Annex I Section IV(g)(ii)-(iii); for banking IV(e)(i) | same SCs as above, applied to the flow | 3 |
| Mobile app | TalkBack and VoiceOver can reach and operate every screen of the app | EN 301 549 clause 11 (software), Annex I Section III(c) | 11.x | 3 |
| Perceivable | Text contrast is at least 4.5:1 (3:1 for large text) | 1.4.3 (AA) | 9.1.4.3 | 2 |
| Perceivable | Buttons, input borders, icons and focus indicators have 3:1 contrast against their background | 1.4.11 (AA), new in WCAG 2.1 | 9.1.4.11 | 2 |
| Operable | A visible outline shows which element has keyboard focus | 2.4.7 (AA) | 9.2.4.7 | 2 |
| Perceivable | Text enlarges to 200% and the page reflows at 320 CSS px wide with no sideways scrolling | 1.4.4 (AA), 1.4.10 (AA) | 9.1.4.4, 9.1.4.10 | 2 |
| Mobile app | The app respects the system's larger text and display size settings without clipping | 1.4.4 applied to software (EN 301 549 clause 11) | 11.x | 2 |
| Robust | Status messages (item added, saved, error) are announced without moving focus | 4.1.3 (AA), new in WCAG 2.1 | 9.4.1.3 | 2 |
| Operable | Time limits and moving content (session time-outs, carousels) can be extended, paused or turned off | 2.2.1 (A), 2.2.2 (A) | 9.2.2.1, 9.2.2.2 | 2 |
| Perceivable | Pre-recorded video has captions and audio description or a text alternative | 1.2.2 (A), 1.2.5 (AA) | 9.1.2.2, 9.1.2.5 | 2 |
| EAA-specific | Product and service pages carry accessibility information where you have it | Annex I Section IV(g)(i) | no SC; a content duty | 1 |
| EAA-specific | You publish how your service meets the accessibility requirements, in an accessible form, and a way to report problems | Article 13(2), Annex V | no SC; an information duty | 2 |
| EAA-specific | Help desk, chat and phone support can answer accessibility questions and are themselves accessible | Annex I Section III(d) | clause 12 (support services) | 1 |
| Perceivable | Works in both portrait and landscape unless one is essential | 1.3.4 (AA), new in WCAG 2.1 | 9.1.3.4 | 1 |
| Forms | Personal-data fields (name, email, address, card) declare their purpose with autocomplete | 1.3.5 (AA), new in WCAG 2.1 | 9.1.3.5 | 1 |
| Perceivable | Content that appears on hover or focus (tooltips, menus) can be dismissed, hovered and stays until dismissed | 1.4.13 (AA), new in WCAG 2.1 | 9.1.4.13 | 1 |
| Perceivable | Nothing breaks when users override text spacing (line height 1.5, paragraph spacing 2, letter 0.12, word 0.16 times the font size) | 1.4.12 (AA), new in WCAG 2.1 | 9.1.4.12 | 1 |
| Understandable | Navigation and repeated components keep the same order on every page | 3.2.3 (AA) | 9.3.2.3 | 1 |
| Operable | Each page has a descriptive title and a sensible heading order starting with one h1 | 2.4.2 (A), 1.3.1 (A), 2.4.6 (AA) | 9.2.4.2, 9.1.3.1, 9.2.4.6 | 1 |
| Operable | A skip link or landmarks let users bypass repeated navigation | 2.4.1 (A) | 9.2.4.1 | 1 |
| Understandable | The page language is set (lang attribute) and changes in language are marked | 3.1.1 (A), 3.1.2 (AA) | 9.3.1.1, 9.3.1.2 | 1 |
| Practice | You have tested with a screen reader and a keyboard, not only an automated scanner | Good practice. Scanners find only part of the issues. | n/a | 2 |
How to use the EAA checklist
- 1Check scopeChoose what you provide, who uses it in the EU, where it is delivered, and your headcount, turnover and balance sheet total. Read the scope result and the exemption reasoning.
- 2Tick what you have verifiedTick only items you have tested, not items you assume. Leave video off unless you publish it.
- 3Read the action planWork through Fix first, then Next, then Then. Each line names the WCAG criterion and EN 301 549 clause to cite in your own tickets.
- 4Verify and recordRe-test the top flows with a keyboard and a screen reader, publish your accessibility information, and keep the plan with dates. Take legal questions to a lawyer.
Frequently asked questions
When did the European Accessibility Act start to apply?
Does the microenterprise exemption apply to my online shop?
Does the Act apply if I am outside the EU?
Is WCAG 2.1 AA enough for the European Accessibility Act?
What counts as an e-commerce service under the Directive?
Do I need to publish an accessibility statement?
Sources
- EUR-Lex: Directive (EU) 2019/882 on the accessibility requirements for products and services (Articles 2, 3, 4, 13, 14, 15, 31, 32; Annex I). Text read from an archived copy of the EUR-Lex HTML (checked 11 Nov 2026)
- European Commission: European Accessibility Act (checked 11 Nov 2026)
- ETSI EN 301 549 V3.2.1 (2021-03): Accessibility requirements for ICT products and services (clauses 9, 11, 12) (checked 11 Nov 2026)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.1 (checked 11 Nov 2026)
- Commission Implementing Decision (EU) 2021/1339 (EN 301 549 V3.2.1 for the Web Accessibility Directive, not the EAA) (checked 11 Nov 2026)
Need a custom dev tool for your team?
We build internal tools, dashboards, APIs, and SaaS platforms. If you can describe it, we can ship it.
Built by CountryDevs · No signup · No ads · We count visits, never what you enter