Does your webshop meet the requirements of the European Accessibility Act?
The deadline passed June 28, 2025. Webshops across the EU must now meet EN 301 549 (the harmonised standard built on WCAG 2.1 AA) — and the first court cases have already been filed. Get a free check in under a minute.
We open your homepage in an ordinary browser and run up to 17 automated checks based on WCAG 2.1 AA – including colour contrast, visible keyboard focus and mobile reflow. No install, no commitment.
Are you even covered?
The EAA covers webshops selling to consumers in the EU — but microenterprises providing services are exempt (Article 4(5)). A great many smaller shops are therefore outside the law entirely. Find out in ten seconds, before spending money on anything.
Tick the boxes above to see your status.
Indicative only, not legal advice. Both of the first two conditions must be true at the same time for the exemption to apply, and it covers services only. Source: Directive (EU) 2019/882, Article 4(5).
Webshops
The entire buying flow — search, product page, cart and payment — must be accessible, e.g. to customers using a screen reader, keyboard only, or strong magnification. If they cannot complete a purchase, the shop does not meet the law.
Enforcement has started
In France, disability organisations sent formal notices (mises en demeure) to four major grocery chains in mid-2025 — not over their physical stores, but over the chains' webshops, which did not meet the requirements. Court proceedings were filed in November 2025. These are the same requirements our scan tests your shop against. In Denmark, Erhvervsstyrelsen supervises — typically via spot checks or consumer complaints.
Information required
Your shop must prepare and publish accessible information on how it meets the requirements — Article 13 and Annex V of the directive, implemented as section 35 and Annex 4 of the Danish Act — and reference it in e.g. your terms and conditions. We generate that document for you – try a free template.
Sources: Directive (EU) 2019/882 (EUR-Lex) · Danish Act no. 801 of 7 June 2022 (retsinformation.dk) · Agency for Digital Government guidance (digst.dk)
EN 301 549 is being updated: version 4.1.1, built on WCAG 2.2 AA, is expected to be cited in the Official Journal during autumn 2026. Until then v3.2.1 (WCAG 2.1 AA) remains the harmonised standard in force — and that is what we test against.
What you get
Professional accessibility tools cost thousands per month and are written for developers. We translate the rules into plain language.
Free scan
Up to 17 automated checks of your front page – contrast, keyboard focus, alt text and mobile reflow. See the result instantly – and what needs a manual review.
Full report
- Your Annex V document – what the law requires, written and ready to publish.
- Scan of up to 25 pages – the whole purchase flow, not just the front page.
- Prioritized fix list – every finding with its location and a concrete fix.
Checkout and the terms of sale are in Danish. Billing is in Danish kroner (DKK); your bank may apply a currency conversion.
Ongoing documentation
We review your shop every month and rewrite your Annex V document with a current date. The first report is included and arrives immediately.
Checkout and the terms of sale are in Danish. Billing is in Danish kroner (DKK); your bank may apply a currency conversion.
How to use the report
The report arrives by email. The Annex V document goes straight onto your site. The fix list you can work from yourself, or pass to your developer.
Why not just an overlay?
Some tools promise to make your shop accessible with a single script — a so-called "overlay" that sits on top of the page. It doesn't hold up: most accessibility problems live in the code itself and can't be fixed from the outside. In the US, the FTC fined an overlay vendor $1 million for claiming exactly that — that its tool could make websites compliant.
That's why EAACheck doesn't sell an overlay — and why we never claim that any automated tool can make your site "compliant". We find the problems that automated testing can detect, show exactly where they are – and tell you what needs a manual review. The lasting fix happens in the code — once, by you or your developer.