The European Accessibility Act (EAA) has applied since 28 June 2025. It requires many products and services sold to consumers in the EU, including online shops, banking, e-books, ticketing and transport services, to be accessible to people with disabilities.
More than a year in, enforcement is building country by country, and many businesses still aren't sure whether it applies to them. Here's a practical guide. It's not legal advice; check national guidance for the countries you sell to.
Who the EAA covers
Services covered (most relevant to websites)
- E-commerce services: online shops and marketplaces selling to consumers.
- Consumer banking services.
- E-books and dedicated reading software.
- Passenger transport services (websites, apps, ticketing, real-time travel information).
- Electronic communications services.
- Access to audiovisual media services.
Products covered
Computers, smartphones, ticket and check-in machines, ATMs, e-readers and similar.
Who must comply
| Business | Covered? |
|---|---|
| EU business selling online to consumers | Yes, unless a microenterprise |
| UK or US business selling online to EU consumers | Yes, unless a microenterprise |
| Microenterprise (<10 staff and ≤€2m turnover or balance sheet) providing services | Exempt from service requirements |
| B2B-only services | Generally not, as the EAA focuses on consumers |
Even if you're exempt, accessibility is still good business: roughly one in five people has a disability, and accessible sites tend to be easier for everyone to use.
What "accessible" means for a website
In practice, websites are assessed against EN 301 549, which incorporates WCAG 2.1 level AA. WCAG is built on four principles:
| Principle | Meaning | Examples |
|---|---|---|
| Perceivable | People can see or hear the content | Alt text, captions, colour contrast |
| Operable | People can use it with different inputs | Keyboard navigation, no traps, enough time |
| Understandable | Content and controls are clear | Labels, error messages, consistent navigation |
| Robust | Works with assistive technology | Valid code, proper roles, screen reader support |
Aiming for WCAG 2.2 AA covers 2.1 and adds useful criteria such as focus visibility, target sizes and accessible authentication. Our WCAG 2.2 checklist goes through each one.
Other EAA obligations
- Accessibility information: service providers must explain how their service meets the requirements, typically through an accessibility statement.
- Accessible support: customer support should be reachable in accessible ways.
- Ongoing compliance: changes to your site must keep it accessible.
- Disproportionate burden: businesses can claim an exemption if a requirement would impose a disproportionate burden, but must assess and document it, and it's interpreted narrowly.
The most common failures on shop websites
- Low colour contrast on text, buttons and prices. Check with our free colour contrast checker.
- Missing or useless alt text on product images.
- Forms without labels, especially search, newsletter and checkout fields. Read form design best practices.
- Keyboard traps in pop-ups, cookie banners and mega menus.
- Invisible focus so keyboard users can't see where they are.
- Custom dropdowns and size selectors that screen readers can't use.
- Error messages that only use colour or don't explain the fix.
- Videos without captions.
- Checkout steps with timeouts and no way to extend.
- CAPTCHAs without accessible alternatives.
A compliance checklist
- Decide whether you're covered: do you sell to EU consumers, and are you above the microenterprise thresholds?
- Audit your site against WCAG 2.2 AA with automated tools and manual testing (keyboard only, screen reader, zoom to 200%).
- Prioritise the purchase journey: home, search, category, product, basket, checkout, account, contact.
- Fix your design system (colours, buttons, form components) so fixes carry across the site. See how to build a design system.
- Check third-party tools: reviews widgets, chat, payment pages, cookie banners.
- Publish an accessibility statement explaining your conformance, known issues and how to get help.
- Train your team: content editors need to write alt text and structure pages properly.
- Test regularly, especially after redesigns and new features.
Do accessibility overlays help?
Overlay widgets that promise one-line compliance generally don't make a site compliant on their own, and some interfere with assistive technology. Fix the underlying code instead.
Accessibility also helps SEO and AI agents
Clear headings, alt text, labels and semantic HTML help search engines understand your pages, and AI agents rely heavily on the accessibility tree to use websites. Read WebMCP explained and the AI agent-ready website checklist.
The short version
The European Accessibility Act has applied since 28 June 2025 to e-commerce and other consumer services sold in the EU, including by UK and US businesses, with microenterprises exempt from service requirements. Aim for WCAG 2.2 AA, prioritise the purchase journey, fix your design system and third-party tools, publish an accessibility statement and keep testing.
Need an accessibility audit or fixes? Our UI/UX design team and web development team can help.




