Dansk →
The EU Accessibility Act is in force

Is your webshop legal under the EAA?

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 a real 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.

Check your status

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)

What do you get?

Enterprise tools cost thousands per month and are written for engineers. We translate the rules into plain language.

Free scan

We test in a real browser – not just the code. Up to 17 automated homepage checks: alt text, colour contrast, keyboard focus, forms, mobile reflow and more. See the result instantly, and we tell you honestly what to check yourself.

Full report (coming soon)

  • Your Annex V information document – the accessibility information the law requires your shop to publish. Written and ready to publish on your site. Most shops don't know they need it – and it's hard to write yourself.
  • Scan of up to 25 pages – homepage, categories, product pages and the full checkout flow, not just the front page. 25 well-chosen pages are enough to catch the problem types: webshops are template-built, so a finding on one product page usually applies to all of them.
  • Prioritized fix list in plain language – every finding with location, severity and a concrete fix, ready to hand to your developer.

See a sample report

€149one-time

Monitoring (coming soon)

Monthly re-scans with alerts when new automated findings appear.

€29per month

No consultants

No meetings, no legal jargon, no hourly billing. A report you can act on — or hand straight 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 can be found automatically, show exactly where they are – and tell you honestly what needs a human check. The fix happens for real: in the code, once, by you or your developer.