Website accessibility compliance in Europe is enforceable law with real penalties, not a guideline you can postpone. The European Accessibility Act became enforceable across all 27 EU member states on 28 June 2025, and the first lawsuits landed in France in November 2025. This guide presents the evidence: failure rates, enforcement actions, fines, and what your site must prove.
Selling into the EU? Book a fixed-price EAA accessibility review — we test your priority journeys, document the findings, and hand you a remediation plan your legal team can rely on.
What evidence shows Europe's accessibility rules have teeth?
The EAA, formally Directive (EU) 2019/882, replaced a patchwork of national rules with one unified set of obligations for private businesses. All 27 member states have transposed it into national law, and enforcement began on 28 June 2025. According to Level Access's EAA compliance overview, the first EAA lawsuits were filed in France in November 2025 (Level Access), with the Netherlands and other member states planning enforcement activity through 2026. Critically, the law reaches companies based outside the EU: if EU consumers can buy from your website, you are in scope regardless of where your company is incorporated.
Enforcement is not theoretical anymore. In March 2026, the Dutch consumer authority ACM tried to complete purchases at roughly 100 of the Netherlands' largest webshops, telecom and energy sites (Autoriteit Consument & Markt ACM) using assistive technology — and could not finish the order at 61% of them, according to an October 2026 review by Peculiar Systems. Sweden's regulators have launched market surveillance cases and received 124 public complaints. Germany's federal accessibility market-surveillance body (MLBF) started operating in September 2025 with a published risk-based strategy. An October 2026 review of all 27 member states found the first four EAA fines, all in Czechia, totalling roughly €580 — each citing a missing accessibility paragraph in shop terms. The Czech example is instructive: regulators read your terms and conditions first, while customers start at your checkout. Both will be inspected.
If your EU-facing site runs on standard marketing pages plus a transactional flow, start with our European Accessibility Act readiness guide for the practical audit sequence. For the broader compliance framework, see our web accessibility compliance guide.
How large are the penalties in each EU country?
Penalties are set nationally, and they vary dramatically — which is why national counsel matters. Reported figures from compliance surveys include:
| Country | Reported maximum / range |
|---|---|
| Germany | Up to €500,000 for serious violations; MLBF cases up to €100,000 (Deque Systems) |
| France | €5,000 to €250,000; reports cite caps up to €375,000 |
| Spain | Up to €600,000 for very serious infractions (iubenda) |
| Netherlands | Up to €900,000 or 1% of annual turnover |
| Sweden | Up to approximately €900,000, with no fixed cap in some readings (Post- och telestyrelsen PTS) |
| Czechia | Up to €400,000 depending on business size |
| Ireland | Up to €60,000 and/or imprisonment |
| Austria | Up to €80,000, levied without a court process |
| Italy | €5,000 to €40,000; up to 5% of turnover for some entities (Clym) |
| Poland | Up to 10% of annual turnover (Interia Biznes) |
Beyond fines, authorities can order a non-compliant service withdrawn from the market, require corrective action under daily penalty, and in some jurisdictions publicly name non-compliant organisations. The Testfort EAA compliance guide catalogues these national penalty ranges in detail. Treat every figure above as a reported range to confirm with qualified counsel in each market — the pattern, not any single number, is the point: fines scale with severity, repeat behaviour, and in some countries, turnover.
Companies budgeting the remediation work should read how much a website costs in 2026 and compare fixed-price web design against open-ended billing before signing anything.
How often do real websites actually fail accessibility checks?
The WebAIM Million 2025 report — which tests the homepages of the top one million websites against WCAG 2 — found that 94.8% contained detectable WCAG 2 A/AA failures, with an average of 51 errors per page (WebAIM Utah State University). That is only a marginal improvement from 95.9% in 2024, and the same six recurring issues have topped the list for years: low-contrast text appeared on 79.1% of pages, 55.5% of images lacked meaningful alternative text, and more than a third of pages had empty links or buttons. Those six issues account for roughly 96% of all detected errors, as DesignRush's analysis of the WebAIM data notes.
Two caveats make the picture worse, not better. First, WebAIM tests homepages; an AudioEye analysis cited by DesignRush found that interior pages — forms, accounts, checkouts — carry about 10% more issues than homepages (AudioEye), and 64% of 2025 web accessibility claims referenced interior pages rather than homepages. Second, automated checkers only catch a fraction of the problem: estimates put automated detection at roughly a quarter to a third of real barriers, because meaning, reading order, focus behaviour and task completion need human testing. A clean automated scan is not evidence of compliance.
As Tim Berners-Lee, inventor of the Web, put it: "The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect." Eurostat data underlines the commercial case too: more than one in four EU residents aged 16 and over report a moderate or severe disability — a large audience that an inaccessible site quietly turns away.
Developers preparing a launch should work through our Core Web Vitals 2026 launch checklist alongside accessibility testing, and multilingual teams should review the multilingual website architecture guide.
What does US litigation evidence teach European sellers?
The United States has the longest track record of digital accessibility litigation, and it previews what European enforcement could look like. UsableNet's 2025 year-end digital accessibility lawsuit report, published in January 2026, counted 4,928 US web accessibility lawsuits filed in 2025. Federal filings alone reached 3,117, up 27% from 2,452 in 2024 (Seyfarth Shaw LLP Launey & Vu, via JD Supra). Roughly 70% of suits targeted e-commerce (UsableNet), and 35.8% of the top-500 e-commerce retailers received at least one accessibility lawsuit in 2025. Geography is concentrated: New York and California state courts combined saw nearly 2,000 filings, and about 46% of federal cases involved repeat defendants — settling once does not end exposure.
Two lessons travel directly to Europe. First, no physical presence is required: US courts allow cases to proceed whenever users in the jurisdiction can access the website — mirroring the EAA's sell-into-the-EU trigger. Second, shortcuts do not work. UsableNet's July 2026 analysis found that roughly 20% of the companies sued already had an accessibility widget or overlay installed (UsableNet), and states plainly that installing one "does not establish that a website is accessible." An overlay is not a compliance strategy; it is, at best, a small supplement to real remediation.
Retailers should also read our e-commerce web development service page and the website redesign SEO migration checklist if a rebuild is on the table.
Which websites does the European Accessibility Act cover?
The EAA covers consumer-facing digital services including e-commerce websites and apps, banking and financial services, transport booking and ticketing, telecom services, e-books and media platforms. The unifying test is whether the website enables EU consumers to use a covered service — informational brochure sites with no transactional function sit lower on the risk scale than shops, booking flows and account portals, though national implementations can extend further.
Two boundaries matter. Microenterprises — fewer than 10 employees and under €2 million in annual turnover (Autoriteit Consument & Markt ACM) — are exempt from the EAA's service obligations in most transpositions, but they still face general consumer expectations and, in the US market, ADA exposure. And non-EU companies are not exempt: a Dubai, London or New York company selling into the EU is covered exactly like an EU company. The Dutch ACM has already sent information requests to companies worldwide, signalling that regulators will not wait for a European legal entity.
If you are unsure where your site falls, our EAA accessibility compliance service overview explains how an applicability assessment works, and web development consulting can scope the technical side before you commit.
What technical target does the evidence point to?
The EAA's harmonised technical standard is EN 301 549 — currently version 3.2.1 as the presumptive standard of conformity — which incorporates WCAG 2.1 Level AA in full. In practical terms, that means every priority journey on your site must be perceivable, operable, understandable and robust: sufficient colour contrast, full keyboard operability with visible focus, meaningful headings and link text, labelled form fields, descriptive alt text, error messages that screen readers announce, and no keyboard traps.
Because WCAG is the common denominator across both European and US expectations, building to WCAG 2.1 AA (and testing against 2.2 where your auditor recommends it) is the defensible technical target. Anything less leaves two exposures open at once: EU regulatory enforcement and US private litigation.
Our SEO-friendly web development builds accessibility into the same QA pass as performance and indexing, and the technical SEO audit surfaces template-level issues an accessibility audit will also flag.
What should you do in the next 30 days?
- Inventory your EU exposure. List every public journey where an EU consumer can buy, book, pay, register or manage an account. Record the operating entity, the markets served, and which third-party components (payment, booking, chat, consent) sit inside each journey.
- Run a baseline audit. Combine automated scanning with keyboard-only and screen-reader testing of your top three journeys. Automated tools find roughly a third of barriers — the manual pass is where the real findings live.
- Fix the shared components first. Navigation, forms, dialogs and templates cause failures across many pages. Correcting one owned component can repair dozens of journeys at once.
- Draft an accessibility statement. Publish what you tested, the standard and version used, known limitations with workarounds, a feedback channel, and a review date. Czechia's first fines were for missing terms paragraphs — the paperwork is inspected too.
- Assign an owner and a review date. Accessibility decays with every release. Name who owns it, and retest after each significant change.
Frequently asked questions
Is the European Accessibility Act already enforceable?
Yes. The EAA became enforceable on 28 June 2025 after all 27 EU member states transposed Directive (EU) 2019/882 into national law. Enforcement activity — lawsuits, market surveillance and information requests — is already underway and expected to expand through 2026.
Does the EAA apply to companies outside the EU?
Yes. The Act applies based on where you sell, not where you are headquartered. A company in the US, UK, UAE or anywhere else that offers covered products or services to EU consumers must comply. Dutch regulators have already sent information requests to companies worldwide.
What fines can an inaccessible website trigger?
Fines are set nationally and range from tens of thousands of euros (Ireland: up to €60,000; Czechia: up to €400,000 (Deque Systems)) to hundreds of thousands (Germany: up to €500,000; France: up to €375,000; Spain: up to €600,000; Netherlands: up to €900,000 or 1% of turnover). Some countries tie fines to a percentage of turnover, so they scale with company size.
What technical standard should our website meet?
EN 301 549 v3.2.1 is the harmonised standard, incorporating WCAG 2.1 Level AA in full. Building and testing to WCAG 2.1 AA is the defensible technical target that satisfies both EU expectations and the benchmark US courts use.
Can an automated accessibility scan prove compliance?
No. Automated checkers detect roughly a quarter to a third of real barriers. They miss meaning, reading order, focus behaviour, error recovery and complete task performance — all of which require keyboard and screen-reader testing by people.
Do accessibility overlay widgets protect against lawsuits?
No. About 20% of US companies sued in the analysed period already had an overlay installed (UsableNet), and researchers state plainly that an overlay does not establish that a website is accessible. Treat overlays as at most a supplement to genuine remediation, never a substitute.
Are small businesses exempt from the EAA?
Microenterprises (fewer than 10 employees and under €2 million annual turnover) are exempt from the EAA's service obligations in most national transpositions. Larger small businesses are not exempt, and no business is exempt from the commercial cost of turning away disabled customers or from US litigation exposure.
Conclusion
The evidence is no longer ambiguous: Europe's accessibility rules are law, enforcement has started, and the failure rate of ordinary websites is near-total — 94.8% of the web's top homepages fail basic WCAG checks (WebAIM Utah State University). The companies that treat accessibility as a documented engineering discipline, tested journey by journey, will experience the EAA as a routine compliance exercise. Everyone else will experience it as a surprise.
Get a fixed-price EAA readiness review — we will test your priority journeys, document what fails and why, and give you a remediation plan your team and your counsel can act on.
