EAA compliance checklist for websites and apps (2026)
Hephaestus Technology7 min read

A European Accessibility Act checklist for a website or app has three parts: confirm you are in scope and not exempt, make the service meet WCAG-based accessibility requirements, and publish and maintain information showing how it complies. The 15 items below follow that order, so you can copy them into a ticket tracker and work through them with your designers, developers and content team.
Key takeaways
- Start with scope: the European Accessibility Act covers listed consumer services such as e-commerce, banking and e-books, and microenterprises providing services are exempt.
- Use WCAG 2.2 Level AA as your target: it satisfies the current EN 301 549 baseline (WCAG 2.1) and the new V4.1.1 standard.
- Automated scanners are only a first pass; keyboard, screen reader and zoom testing by a person are essential.
- You must publish information on how your service meets the requirements, typically an accessibility statement, and keep it current.
- Build accessibility into every release, because a single update can break compliance.
Why use a European Accessibility Act checklist at all?
A checklist turns a broad legal duty into tasks a team can assign and verify. Directive (EU) 2019/882 has applied since 28 June 2025 and describes outcomes (services must be perceivable, operable, understandable and robust) rather than technical steps. In Ireland it is enforced under S.I. No. 636 of 2023, where offences can carry a fine of up to EUR 60,000 or imprisonment on indictment. If you need the background first, read our explainer on what the European Accessibility Act requires of digital products.
This checklist is a practical aid, not legal advice. For borderline scope questions or exemption claims, speak to a solicitor or accessibility specialist.
Part 1: Are you in scope?
You are in scope if you provide a listed service to consumers in the EU, or place a listed product on the EU market, and no exemption applies.
1. Map your services against Article 2. List every consumer-facing channel: website, iOS app, Android app, checkout, account area, customer support chat. The directive defines e-commerce services as services provided at a distance, through websites and mobile device-based services, at the individual request of a consumer with a view to concluding a consumer contract. Pure B2B services are generally outside the services list.
2. Check the microenterprise exemption. Microenterprises providing services are exempt if they have fewer than 10 employees and annual turnover or balance sheet total of EUR 2 million or less (Articles 3(23) and 4(5) of the directive). Record the figures you relied on. Product manufacturers do not get this exemption.
3. Identify your regulator. In Ireland the National Disability Authority lists the CCPC for e-commerce, e-books and products, ComReg for electronic communications, Coimisiún na Meán for audiovisual media access, the Irish Aviation Authority and National Transport Authority for transport, and the Central Bank for consumer banking. Selling into other Member States means other national authorities too.
4. Note any transitional rules. Products a service provider lawfully used before 28 June 2025 can continue until 28 June 2030, and existing self-service terminals up to 20 years (CCPC). Content such as pre-recorded video published before 28 June 2025 and unchanged archives is excluded.
Part 2: Does your website or app meet the requirements?
Your service meets the requirements in practice when it conforms to the European standard EN 301 549, which builds on WCAG.
5. Set WCAG 2.2 AA as the target. The National Disability Authority reports that EN 301 549 V4.1.1, published on 2 September 2026, references WCAG 2.2 Level AA and is expected to be cited in the Official Journal on 16 December 2026; until then V3.2.1 (WCAG 2.1) applies. The W3C confirms that content conforming to WCAG 2.2 also conforms to 2.1, so one target covers both.
6. Run an automated scan. Use a browser extension or CI tool on every template and key journey. It quickly finds missing alt text, contrast failures and unlabelled fields, but it cannot judge whether alt text is meaningful or a flow makes sense.
7. Test manually with a keyboard. Tab through sign-up, search, product pages, cart, checkout and account settings. Every control must be reachable, the focus indicator visible, and nothing should trap focus.
8. Test with screen readers and zoom. Use NVDA or JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android. Check text resizing to 200 percent and reflow on a narrow screen.
9. Fix forms and checkout first. Labels, clear error messages, no unexplained time limits and accessible authentication are where users most often get stuck, and checkout is the core of an e-commerce service.
10. Fix media and content. Add captions and transcripts to video and audio, write meaningful alt text, use real headings and plain language. Make sure PDFs and e-books you supply are accessible too.
11. Check third-party components. Payment widgets, cookie banners, chatbots, maps and embedded booking tools are part of your service. Ask vendors for their conformance report and test them yourself.
Part 3: Can you show that you comply?
You can show compliance when the required information is published, decisions are documented and there is a route for users to report problems.
12. Publish an accessibility statement. Annex V requires service providers to include information on how the service meets the accessibility requirements in their general terms and conditions or an equivalent document. A clear statement page, linked from the footer and app settings, should cover the standard you target, known gaps with fix dates and contact details.
13. Document any disproportionate burden claim. Article 14 allows this only after an assessment against Annex VI criteria. Service providers must renew it when the service changes and at least every five years. Keep the assessment on file.
14. Provide a feedback and complaints route. Give users a way to report barriers and get an alternative, such as an email address or phone line, and track responses. The CCPC expects providers that find non-compliance to correct it and inform the relevant authority.
15. Make it part of every release. Add accessibility acceptance criteria to user stories, accessible components to your design system, automated checks to CI and a manual check before major launches. Train designers, developers and content editors once a year.
How long does EAA compliance work take?
There is no official benchmark, so plan from your own audit. A small site built on a modern, accessible component library may need days of fixes; a large app with custom widgets, legacy code and inaccessible third-party tools may need several sprints. The audit in items 5 to 11 gives you the real number. If you are planning a launch, fold the checks into your product launch checklist for B2B software or consumer equivalent so they are not left to the last week.
What mistakes should you avoid?
The most common mistakes are treating accessibility as a plugin or a one-off project.
- Overlay widgets. A toolbar script does not change the underlying code and does not by itself make the service accessible.
- Scanner-only audits. Passing an automated tool is not the same as conforming to WCAG 2.2 AA.
- Statements that overclaim. Saying "fully compliant" when known issues exist is worse than an honest statement with a fix plan.
- Ignoring native apps. The directive covers mobile device-based services, not only websites.
Frequently asked questions
Does every item on this checklist apply to my business?
Items 1 to 4 apply to everyone, because they decide whether the EAA covers you. If you are a service microenterprise, the remaining items are good practice rather than a legal duty under the EAA. If you are in scope, all 15 apply.
Do I need an external accessibility audit?
The EAA does not require an external audit. Many teams commission one for the first baseline, because experienced testers using assistive technology find issues internal teams miss, then run internal checks for each release.
What should an accessibility statement contain?
At minimum: which standard you target (for example WCAG 2.2 AA), how the service meets it, any known non-conforming parts and when they will be fixed, and how users can report problems or get an alternative format. Keep the date of the last review visible.
Is WCAG 2.1 AA still enough in 2026?
Under EN 301 549 V3.2.1, which remains in force until V4.1.1 is cited in the Official Journal, WCAG 2.1 is the reference. V4.1.1 moves to WCAG 2.2 AA, so targeting 2.2 now avoids a second round of work.
How often should we re-test?
Run automated checks on every build and manual keyboard and screen reader checks before major releases. A full re-audit once a year, or after a redesign, is a sensible rhythm.
Want help turning this checklist into a scoped plan for your website or app? Book a free 30-minute call.
Cover photo by Nimit Kansagra on Pexels.