Insights
The European Accessibility Act: what your website or online store has to do
Since 28 June 2025 many websites and online shops serving EU consumers must be accessible — including shops run from outside the EU. Here is who is covered, what to fix first, and how to plan the work.
By Jimmy, Product designer · · 9 min read
What is the European Accessibility Act, and does it apply to my website?
The European Accessibility Act is Directive (EU) 2019/882, and member states have had to apply its measures since 28 June 2025. It requires online shops and other covered consumer services offered in the EU to be accessible to people with disabilities, which in practice means meeting EN 301 549, the European standard that incorporates WCAG. Businesses outside the EU can be covered.
Who is covered by the European Accessibility Act?
| Your situation | Covered? | Notes |
|---|---|---|
| Online store selling to consumers in the EU | Yes | Covers the website, the app, the checkout and customer communications |
| Non-EU business selling to EU consumers | Yes, if it offers covered services in the EU | Where the company is registered does not remove the obligation |
| Microenterprise providing services | Exempt from the service requirements | Defined in the Directive as fewer than 10 persons employed and turnover or balance sheet total not above EUR 2 million |
| Microenterprise placing products on the market | Not exempt in the same way | The exemption in Article 4(5) is written for services |
| Business-to-business website only | Generally outside the e-commerce definition | Needs checking case by case |
| Brochure website with no covered service | Not directly covered | Still good practice, and other rules may apply |
A hotel, restaurant or tour operator selling bookings to consumers through an online flow is very likely providing an e-commerce service. Check how your national law treats it rather than assuming the booking engine is someone else's problem.
What does the Act actually cover?
It applies to a defined list of products and services. For websites and apps, the categories that matter are:
- E-commerce: websites and apps through which consumers buy goods or services
- Consumer banking services
- E-books and dedicated reading software
- Electronic communications services
- Access to audiovisual media services
- Passenger transport services by air, bus, rail and water, including their websites, apps and e-tickets
Does it apply to businesses outside the EU?
Yes, if you offer covered services to consumers in the EU. The obligation attaches to the service offered in the EU market, not to where the company is registered. A store run from Lebanon, the UAE or the US that sells to EU shoppers should assume it is in scope until it has confirmed otherwise — and “we did not know it applied to us” has never been a defence anywhere.
Which accessibility standard should you follow?
The Act sets functional requirements: content must be perceivable, operable, understandable and robust. The practical way to demonstrate that is the harmonised European standard EN 301 549, which incorporates WCAG Level AA for web content.
- **Aim for WCAG 2.2 AA.** It is the current W3C Recommendation and it covers the 2.1 AA criteria, so meeting it satisfies the WCAG-related requirements and a little more.
- Remember EN 301 549 goes beyond WCAG, including requirements for documents and support services.
- Do not rely on an accessibility overlay or widget. They do not address the underlying code, design and content problems, and they do not make a site compliant on their own.
What do you need to fix on your website or store?
| Area | What to check | Typical fix |
|---|---|---|
| Keyboard use | Every link, menu, filter and button works without a mouse, with a visible focus indicator | Fix tab order and focus styles, add skip links |
| Text alternatives | Product images, icons and banners carry meaningful alt text | Write descriptive alt text; mark decorative images as decorative |
| Colour and contrast | Contrast ratios met, and colour is never the only signal | Adjust the palette and interaction states |
| Forms and checkout | Clear labels, instructions, error messages and autofill support | Associate labels with fields; explain errors in text |
| Structure | Logical headings, landmarks, page titles, declared page language | Use semantic HTML rather than styled divs |
| Media | Captions for video, text alternatives for audio | Add captions and transcripts |
| Zoom and mobile | Content reflows at high zoom; touch targets are usable | Responsive layouts and adequate target sizes |
| Third-party tools | Payment forms, booking engines, chat, cookie banners | Choose accessible vendors and ask them for their accessibility information |
| Documents and emails | PDFs, invoices, order confirmations | Produce tagged, accessible documents |
| Time limits and motion | Session timeouts, auto-playing carousels | Let users extend or pause |
Start where the money is: homepage, navigation, product pages, cart, checkout and account pages. An inaccessible checkout is both the biggest legal exposure and the most expensive conversion problem you have.
What are the penalties for not complying?
Penalties and enforcement are set by each member state, so they differ by country. Authorities can generally investigate complaints and require corrective action, with national law setting the sanctions. Be sceptical of any article quoting a single EU-wide fine figure — there is no such number. Check the law and the supervising authority in each country where you sell.
How do you comply? A seven-step plan
- Confirm your scope. Which countries do you sell to, and which of your services are covered? Take advice if you are unsure.
- Audit the site. Combine automated scans with manual testing and screen reader checks. Automated tools catch only a fraction of what the standard requires.
- Prioritise by journey. Navigation, product discovery, cart and checkout before anything else.
- Fix root causes. Correct templates, components and the design system, not individual pages, or you will be doing this again next quarter.
- Test with assistive technology. Keyboard only, a screen reader, and zoom, on both desktop and mobile.
- Publish an accessibility statement describing how your service meets the requirements, what the known limitations are, and how to report a problem.
- Make it routine. Add accessibility checks to design, development and content workflows, and re-test after every significant change.
What mistakes do businesses make with accessibility?
- Installing an overlay widget and calling it done. A single script does not fix the underlying problems.
- Testing only the homepage. The failures are almost always in filters, carts and checkout.
- Trusting an automated score. A passing scan does not mean a usable site.
- Ignoring third-party components. The payment form, booking engine and chat widget are part of your service as far as the user is concerned.
- Forgetting documents and emails. Invoices, PDFs and order confirmations count.
- Treating it as a one-off project. Every new page, campaign and feature can introduce new barriers.
- Waiting for a complaint. Fixing this inside a planned redesign costs a fraction of fixing it under deadline.
How do you know what your website needs to become accessible?
The right plan depends on your markets, your platform and how much of the site was built with accessibility in mind in the first place. A small store on a well-built theme may need targeted fixes; an older custom site may be cheaper to rebuild than to patch. A wrong call here shows up late, usually as a second round of work that costs more than the first.
Five questions decide the route:
- Where do you sell, and to whom? This sets which national rules apply.
- What do you sell — products, services, bookings, subscriptions, digital content?
- What platform and theme is the site built on?
- Which third-party tools sit in the journey: payments, booking, chat, consent banners?
- Is a redesign already planned? Building accessibility into a rebuild is far cheaper than retrofitting one.
RedefinedWeb is a Beirut-based team that designs, builds and maintains websites and online stores for clients across the GCC, Europe and the US. We can plan accessibility into a redesign, a new build or ongoing Website Care. Our Website & UX Health Check is a fixed-scope review of performance, UX, SEO and security that gives you a prioritised list — it is not a formal accessibility conformance audit, and if that is what you need we will say so rather than sell you the nearest thing we happen to offer.
What happens on a call:
- We look at your site, platform, markets and the journeys that matter most.
- We recommend a route: targeted fixes, a redesign, or a formal audit by a specialist.
- You receive a written proposal with scope, timeline and cost before anything starts.
Frequently asked questions
- Does the European Accessibility Act apply to non-EU companies?
- Yes, if they offer covered services to consumers in the EU. The requirements follow the service offered in the EU market rather than the location of the company, so a store run from outside the EU that sells to EU shoppers should assume it is in scope.
- Are small businesses exempt from the European Accessibility Act?
- Only microenterprises providing services are exempt from the service requirements. The Directive defines a microenterprise as one employing fewer than 10 persons with an annual turnover or balance sheet total not exceeding EUR 2 million. Microenterprises placing products on the market are not exempt in the same way, and national law can vary.
- Which WCAG level does the European Accessibility Act require?
- The practical benchmark is EN 301 549, the harmonised European standard, which incorporates WCAG Level AA for web content. Many teams target WCAG 2.2 AA because it is current and covers the 2.1 AA criteria.
- Does it apply to B2B websites?
- It is aimed at consumer-facing products and services, so a purely business-to-business site generally falls outside the e-commerce definition. It needs checking case by case, and accessibility remains worth doing regardless.
- Do I need an accessibility statement?
- Publishing one is widely expected, and the Act requires service providers to give information about how their service meets the accessibility requirements. Check what your member state asks for, and always include a way for users to report a problem.
- Can an accessibility overlay make my site compliant?
- Generally no. Overlays and widgets do not fix the underlying code, design and content issues, and they are not sufficient on their own to meet the requirements of the Act or of WCAG.
References and links
Terms in this market change, and some providers don’t publish them. These are the primary sources behind the guide — check the current position yourself before you commit to anything.
- Directive (EU) 2019/882 — the European Accessibility Act, on EUR-Lex
The law itself. Article 31(2) sets the 28 June 2025 application date; Article 4(5) carries the microenterprise services exemption; Article 3 defines a microenterprise.
- W3C — Web Content Accessibility Guidelines (WCAG) 2.2
W3C Recommendation of 12 December 2024. The current version, and the one to build against.
- W3C — Web Content Accessibility Guidelines (WCAG) 2.1
The version EN 301 549 incorporates for web content.
- ETSI — EN 301 549 published versions
The harmonised European standard for ICT accessibility. Check the directory for the current version rather than citing an old one.
Related reading
How much does a website cost in 2026? Prices by type, and what actually drives them
Where accessibility work sits in a build or redesign budget.
Read it →Launch is not the finish line: why a website needs a support plan and somewhere to test
Why accessibility is a routine, not a project — and where to test the fixes.
Read it →
Where this fits on the site: E-commerce and website builds · Payment gateways we integrate · Stores we have built
Next step
Not sure whether the Act applies to you?
Tell us where you sell and what your site does, and we’ll tell you what is likely in scope, what to fix first, and when you need a specialist audit rather than us.