Yes — if you sell to EU consumers through e-commerce, booking, banking, or digital media, the European Accessibility Act (enforceable since 28 June 2025) almost certainly covers you, with WCAG 2.1 AA as the practical target. Micro-enterprises under 10 employees and €2M turnover are exempt. This guide covers scope, real enforcement numbers, and a remediation sequence.
Serving EU customers? Our accessibility compliance service includes an EAA readiness audit, remediation roadmap, and handover documentation your legal team can review.
Which websites does the European Accessibility Act actually cover?
The EAA doesn't cover every website. It covers specific products and services placed on the EU market, and for most web businesses the trigger is selling to EU consumers through an in-scope service. The big ones:
- E-commerce and retail websites — online shops are the primary digital target
- Banking and payment services — account dashboards, payment flows
- Transport booking — airlines, rail, ride services, travel booking flows
- Telecom and subscription services — account management, plan purchase
- E-books and digital media — readers, storefronts, libraries
- Audiovisual media services — streaming, on-demand video
The key legal test isn't where your company is registered — it's whether you offer the service to EU consumers. A Dubai-based store shipping to Germany falls in scope the same way a Frankfurt store does. The exemption is narrow: micro-enterprises with fewer than 10 employees AND under €2 million in annual turnover are excluded (Velstar, 2026). Everyone else must comply.
For comparison with the American framework your US-facing sites already navigate, see our web accessibility compliance guide — digital-accessibility lawsuits in the US topped 5,000 in 2025 (DigitalApplied, 2026), and the EU is building enforcement on top of that same pressure curve. European-specific readiness is covered separately in our European website accessibility readiness guide.
What standard should you build against: WCAG 2.1 AA
The EAA's technical requirements are defined through the harmonised European standard EN 301 549, which in practice maps to WCAG 2.1 AA success criteria for web content. Targeting WCAG 2.1 AA is the defensible engineering choice: it's the version with the deepest tooling, the most audited criteria, and the clearest mapping to the EAA's functional requirements.
That means concrete, testable targets for every template:
- Keyboard operability — every action completes with a keyboard alone; no traps, no unreachable controls
- Visible focus order — the focus indicator stays visible and follows a logical order after every action
- Form labels and error handling — every field has a visible programmatic label; errors are described in text and locatable
- Alt text — informative images carry text meaning; decorative images are hidden from assistive tech
- Color contrast — text meets the approved ratio, and color is never the only carrier of meaning
- Screen-reader task completion — a critical task (checkout, booking) can be completed using a named screen reader + browser combination
A worked example: dark-grey body text at #595959 on white measures roughly 7:1 in a standard contrast checker and passes AA, while #999999 on white drops to about 2.8:1 and fails. Record the exact foreground, background, measured ratio, tool, and component state — "tested with a screen reader" is not evidence; a record naming the OS, assistive technology, browser, device, tester, and date is.
Automated scans catch roughly a third of real issues; manual keyboard and screen-reader journeys catch the rest. When we scope accessibility work, we treat it the way we treat SEO-friendly web development: baked into the build and verified at launch, not bolted on afterwards. Our Core Web Vitals launch checklist applies the same evidence discipline to performance — named environment, named date.
What does enforcement look like so far? Real numbers, not hype
Enforcement is active, but it's uneven — and the actual record differs from the fear-marketing version. A review of 15 months of EAA enforcement across all 27 member states (Peculiar Systems, October 2026) found only four monetary fines on public record, all in Czechia, totalling about €580 — each citing a missing accessibility paragraph in shop terms and conditions (EIN Presswire). That is not a reason for complacency; it's the standard EU enforcement pattern — regulators move from notice to remediation order before fines, and 2026–2027 is when formal sanctions are expected to ramp up.
What has happened so far:
- Netherlands — in March 2026, the Dutch consumer authority ACM tried to shop at about a hundred of the Netherlands' largest webshops, telecom, and energy sites using assistive technology. At 61% of them, it could not finish the order (Peculiar Systems review).
- France — on 4 June 2026, the Tribunal judiciaire de Caen ordered Carrefour France to make its e-commerce site and app fully accessible within six months, with a daily penalty accruing after the deadline (DigitalApplied, 2026). France's maximum fines reach €75,000 per violation, with daily penalties up to €3,000 capped at €300,000.
- Germany — private warning letters from law firms began landing shortly after the law took effect, using competition-law dynamics; the maximum fine is €100,000 per violation (Level Access).
- Spain and Sweden — the heaviest ceilings: €600,000 in Spain and roughly €900,000 (SEK 10 million) in Sweden. The Netherlands caps at €90,000, Austria at €80,000 per violation, Italy at €40,000 plus up to 5% of turnover (Level Access).
As one agency-focused analysis put it, the grace period is over but "fines are already flying" is a myth — enforcement is at the notice-and-inspection stage, which is precisely when remediation is cheapest (Instarenewal, 2026). Businesses that ignore repeated warnings absorb the heaviest penalties, not first-time offenders. Because penalties accrue per violation and can multiply across templates, documenting what was tested matters as much as the fixes — our accessibility EAA compliance service produces exactly that evidence package. If you're weighing scope and budget, talk to our team before the next inspection cycle starts.
The business case: 90 million customers, not just compliance
The commercial argument lands harder than the legal one. Roughly 24% of EU adults over 16 have some form of disability — about 90 million people — and 87% of them used the internet in the past year (Velstar, 2026). An inaccessible store turns them away before they reach a product page, and their friends, carers, and family members actively choose accessible brands — so the addressable market is considerably larger than the 90 million figure.
The work also pays for itself twice over. Meeting WCAG 2.1 AA routinely surfaces UX improvements that benefit every visitor: cleaner navigation, faster load times, simpler checkout flows. Our lead-gen website development framework shows how those same improvements lift conversion rates — and for businesses that also need to win in AI search, our AEO vs SEO guide explains why machine-readable, well-structured pages get cited more. If you're planning the work, consulting with our web development team at the scoping stage keeps accessibility and conversion in the same conversation.
Your remediation sequence: what to do first
Don't open with a site-wide scanner or a promise of full compliance. Scanners create findings without a settled scope, and promises turn incomplete evidence into a legal conclusion. Work the sequence below instead.
1. Determine coverage. For every customer-facing service, document the entity facts, service functions, customer types, transaction steps, EU markets served, and any exemption claim with the exact legal provision attached. Send the evidence to qualified counsel — a web agency can attest to what it built and tested; it cannot certify your legal compliance.
2. Pick the target and lock it in writing. Name the standard, version, level (WCAG 2.1 AA), templates, components, journeys, test environments, and evidence format in the statement of work before anyone touches code. Our guide to fixed-price vs retainer vs time-and-materials shows how to structure that statement of work so acceptance criteria are auditable.
3. Test one revenue-critical journey end to end. Pick checkout or booking and run it keyboard-only plus with a named screen reader and browser, using a fictional itinerary — never customer data. Record expected result, actual result, severity, owner, and retest state at every step. A component checklist can't show whether a visitor can finish a commercial task; a journey test can.
4. Remediate at the component level. Apply the correction to the shared component rather than one page, so the fix propagates. Rerun the affected journey after each fix and check you haven't created a new barrier elsewhere.
5. Request a conformance statement at handover. Ask for criterion-by-criterion results with evidence references — assessment scope, target standard, environments, methods, results, limitations with owners and target dates, and named approvers. The VPAT/ACR format is the widely used template. This is technical evidence, not a legal certificate — keep the two attestations in separate documents. Our website handover ownership checklist shows what a complete handover package must include beyond accessibility evidence.
6. Schedule recurring audits. Accessibility degrades with every deploy. Treat it as a tracked, recurring asset — a technical SEO audit cadence is the right model — not a project you mark "done."
Frequently asked questions
Does the European Accessibility Act apply to my website?
It applies to in-scope products and services offered to EU consumers — most notably e-commerce, banking, transport booking, telecom, and digital media — regardless of where your company is based. Micro-enterprises (fewer than 10 employees and under €2M turnover) are exempt. Confirm your position with qualified counsel using your actual entity, service, and market facts.
Is WCAG 2.1 AA the standard the Act requires?
The EAA's technical requirements flow through the harmonised standard EN 301 549, which maps to WCAG 2.1 AA criteria for web content. Targeting WCAG 2.1 AA is the defensible engineering choice, but confirm the exact target with your qualified reviewer for your market.
Does passing an automated scan prove compliance?
No. Automated tools catch roughly a third of real issues and can't judge journey-level barriers like an unannounced checkout error. Keep the scan as one test record alongside manual keyboard and screen-reader journeys, scope decisions, environments, limitations, and retest results.
What fines have actually been issued?
As of late 2026, only four monetary fines appear on public records EU-wide — all in Czechia, totalling about €580 — per a review of all 27 member states. But enforcement machinery is active everywhere: inspections (Dutch ACM), court orders with daily penalties (Carrefour, France), and private warning letters (Germany). Regulators escalate from notice to fine; ignoring warnings is what draws the heavy penalties.
What should my web agency deliver at handover?
An accessibility conformance statement: assessment scope, target standard, test environments, methods, criterion-level results, evidence references, known limitations with owners and dates, and named approvers. Ask the agency to attest to its technical work — the standard it targeted, what it tested, and the results — without issuing a legal opinion.
How long does remediation take?
It depends on the site's starting point and template count, but a bounded first pass — one revenue-critical journey plus shared components — typically runs weeks, not months. Third-party widgets you can't change are the usual wild card; those go into the supplier register with interim measures and a commercial decision. An EAA readiness audit scopes that work before you commit to remediation, and our accessibility compliance service carries it through to documented handover.
Is this legal advice?
No. This guide describes the operational method for scoping and testing accessibility work. Applicability, exemptions, and compliance wording require qualified counsel in your market. Our accessibility compliance service documents what we built and tested; your legal team decides what it means.
The bottom line
The EAA is enforceable, enforcement is moving from notices to sanctions, and the work pays for itself in a wider customer base plus better UX for everyone. Start with one revenue-critical journey, lock the target in the statement of work, and treat accessibility as a recurring asset. Start an EAA readiness audit or read our European accessibility readiness guide for the preparation checklist.
