Since 28 June 2025, accessibility stopped being a "nice to have" in Europe and became the law. The European Accessibility Act (EAA) now requires a huge range of consumer-facing digital products and services to be usable by people with disabilities—and the enforcement powers are real. In Germany, the first warning letters landed within weeks of the deadline; in Ireland, serious breaches can carry criminal liability.
But there's a catch most "comply or get fined €3 million" headlines miss: the EAA does not apply to everyone or every website. Whether you need to act—and how urgently—depends on what your product does, who you sell to, and how big you are. This guide cuts through the panic-marketing: who is actually in scope, what the law requires in plain terms, a practical checklist, and what it costs to get compliant.
This is a practical guide, not legal advice. The EAA is an EU directive transposed into 27 different national laws. For a binding answer on your specific obligations, confirm with a qualified lawyer in your market.
Short on time? If you already know you need help, get matched with vetted European agencies that build to WCAG 2.1 AA, or browse the directory.
Quick Reference: Are You In Scope?
| Question | If yes… |
|---|---|
| Do you sell products or services to consumers in the EU? | Likely in scope—keep reading. |
| Is your offering B2B-only, internal, or not aimed at consumers? | Generally out of scope. |
| Are you a microenterprise (<10 staff and ≤€2M turnover) offering a service? | Exempt from the service obligations (products are different—see below). |
| Is your site a pure brochure/marketing site with no covered service? | Often not directly covered—but read the nuance below. |
| Are you outside the EU but selling into the EU market? | In scope. Location doesn't exempt you. |
The EAA is Directive (EU) 2019/882. "In scope" means you must meet the technical standard below; deadlines and penalties are set by each member state.
What the EAA Actually Requires
The law doesn't invent a new design rulebook. For websites and apps, compliance means meeting the harmonised European standard EN 301 549, which for digital content maps directly to WCAG 2.1 Level AA—the same Web Content Accessibility Guidelines the rest of the world already uses.
In practice, WCAG 2.1 AA means things like:
- Perceivable: sufficient colour contrast, text alternatives for images, captions for video, content that reflows on mobile without horizontal scrolling.
- Operable: everything works by keyboard alone, no keyboard traps, visible focus states, no content that flashes dangerously.
- Understandable: clear labels and instructions, predictable navigation, helpful error messages on forms.
- Robust: clean, semantic markup that works with screen readers (NVDA, VoiceOver, JAWS) and assistive tech.
On top of the technical standard, in-scope services must also publish an accessibility statement explaining how the service meets the requirements and how users can report problems.
💡 The good news for anyone building new
If you hire a competent UX/UI agency in 2026, WCAG 2.1 AA should already be part of the deliverable—not a premium add-on. Accessibility built in from day one typically adds only a modest amount to a project. The expensive path is retrofitting a finished, inaccessible product later.
Who Is In Scope (and Who Isn't)
This is where most of the confusion lives. The EAA targets specific consumer-facing services, not "every website on the internet."
Services that are covered
The directive names a defined list of consumer services, including:
- E-commerce (any site where a consumer can conclude a contract or buy online)
- Banking and consumer financial services
- Telecommunications services
- Transport services—ticketing, check-in, real-time travel information
- Audiovisual media access services (e.g. streaming platform interfaces)
- E-books and dedicated reading software
If your website is one of these or contains one (for example, a marketing site with a checkout, a booking flow, or a customer login that performs a covered service), the covered functionality must be accessible.
What is generally not directly covered
- Pure B2B services and internal tools not offered to consumers.
- Purely informational marketing/brochure sites that don't offer a covered service—no shop, no booking, no account. (Accessibility is still strongly advisable here for SEO, reach, and reputation—but the EAA obligation hinges on offering a covered service.)
- Microenterprises providing services—businesses with fewer than 10 employees and annual turnover or balance-sheet total of €2 million or less are exempt from the service requirements. Note: this exemption is for services. If a microenterprise manufactures or sells covered products, the product rules can still apply.
- Archived content not updated after 28 June 2025, and pre-recorded media published before that date.
⚠️ Don't over-rely on the exemptions
Two traps: (1) "We're B2B" is fuzzy—if any part of your site lets a consumer buy, book, or sign up, that part is likely in scope. (2) The microenterprise exemption is narrow and you must meet both the headcount and the financial test. Growing past either threshold ends the exemption. When the stakes are legal, get the determination in writing from a lawyer, not from a blog.
Deadlines: It's Not All June 2025
- 28 June 2025: The headline date. All new products placed on the market and services provided from this date must comply.
- Transition to 28 June 2030: Member states may allow service providers to continue using certain service contracts agreed before June 2025, and self-service terminals already in use, until the end of their economic life or up to this date.
- No grandfathering for new work. Anything you launch or substantially update now is expected to be compliant today.
The direction of travel is one-way: the window only narrows from here.
Penalties: Set Nationally, and Already Being Used
The EAA itself doesn't fix a single EU-wide fine. Each member state sets its own penalties through national transposition, so the real risk depends on where you operate. Examples reported after the deadline:
- Germany (BFSG): fines reported up to €100,000 per violation. More immediately, opportunistic law firms began sending private warning letters (Abmahnungen) to e-commerce operators within weeks—using competition law, not the accessibility act directly. For many German online shops, the lawyer's letter is a bigger near-term risk than the regulator.
- Ireland: the only confirmed member state where serious breaches can carry criminal liability—reported up to €60,000 and/or up to 18 months' imprisonment after a notice to comply.
- Across the EU: regulators can investigate complaints, order remediation, and ultimately have non-compliant products or services withdrawn from the market.
💡 The under-priced risk isn't the fine
As of early 2026, headline regulator fines have been rare. The realistic costs are the legal warning letters, the emergency remediation under deadline pressure (always more expensive than doing it right), the lost customers who simply can't use your product, and the reputational hit. Roughly one in four people in the EU lives with some form of disability—inaccessibility is also a revenue leak.
The Practical Compliance Checklist
A pragmatic path for a team that wants to get this right without panicking:
- Determine scope. Decide—ideally with legal input—whether your service is covered, and whether any exemption genuinely applies to you.
- Run an accessibility audit. Combine automated scanning (axe, WAVE, Lighthouse) with manual testing, including keyboard-only navigation and a real screen reader. Automated tools catch only a fraction of WCAG issues on their own.
- Triage by severity. Fix the blockers first: things that make a task impossible (unlabelled form fields, keyboard traps, checkout steps that can't be completed without a mouse).
- Remediate against WCAG 2.1 AA. Contrast, alt text, focus order, semantic headings, error handling, captions.
- Publish an accessibility statement. State your conformance, known limitations, and a contact route for problems.
- Bake it into your process. Add accessibility acceptance criteria to your design and development workflow so new features don't reintroduce regressions. Put "WCAG 2.1 AA" explicitly in your design brief.
- Re-test periodically. Accessibility is a state you maintain, not a box you tick once.
✅ Green flags you're on track: keyboard-only users can complete every core task; your audit combined automated and manual testing; accessibility is in your definition of done; you have a published statement and a fix log.
🚩 Red flags: you "ran a scanner and it said 98%" (automated alone is not compliance); an overlay widget is your entire strategy (overlays don't make a site conformant and have themselves attracted legal complaints); or nobody can say whether you're even in scope.
What It Costs to Get Compliant
There's no single number—it scales with your site's size and how far from the standard you currently are. Rough European ranges:
| Engagement | Typical cost | What you get |
|---|---|---|
| Automated scan + quick review | €0–€2,000 | A first signal of where you stand (incomplete on its own) |
| Professional accessibility audit | €3,000–€15,000+ | Manual + automated testing, prioritised issue report, WCAG mapping |
| Remediation (design + dev) | Highly variable | Fixing the issues; cost depends on volume and severity |
| Accessibility built into a new build | +~5–15% of project | Compliance from day one—far cheaper than retrofitting |
An accessibility audit is closely related to a general UX audit—many European agencies offer both, and the two often surface overlapping issues. For a scoped estimate, use the UX cost calculator.
💡 Why "built in" wins
Retrofitting accessibility into a finished product means re-opening design decisions, re-testing flows, and often re-doing components. Specifying WCAG 2.1 AA in the brief before design starts folds it into work you're paying for anyway. If you're building new in 2026, this is the single highest-leverage decision in this guide.
FAQ: Frequently Asked Questions
1. What is the European Accessibility Act (EAA)? The EAA (Directive (EU) 2019/882) is an EU law requiring a defined set of consumer-facing digital products and services—e-commerce, banking, telecoms, transport, e-books and more—to be accessible to people with disabilities. For websites and apps it means meeting EN 301 549, which maps to WCAG 2.1 Level AA. Enforcement powers took effect on 28 June 2025.
2. Does the EAA apply to my website? It depends on what your site does. If it offers a covered consumer service (a shop, a booking flow, banking, telecoms, e-books), that functionality is in scope. Pure B2B services, internal tools, and purely informational marketing sites with no covered service are generally not directly covered. Microenterprises (<10 employees and ≤€2M turnover) are exempt from the service requirements. Confirm your specific case with a lawyer.
3. What standard do I have to meet? EN 301 549, the harmonised European standard, which for web and app content corresponds to WCAG 2.1 Level AA. In practice: sufficient colour contrast, full keyboard operability, text alternatives, captions, semantic markup that works with screen readers, and clear, accessible forms.
4. What are the penalties for non-compliance? There's no single EU-wide fine—each member state sets its own. Germany's law allows fines reported up to €100,000 per violation (and has triggered private legal warning letters); Ireland can impose up to €60,000 and/or imprisonment for serious breaches. Regulators can also order remediation or market withdrawal.
5. Is an accessibility overlay widget enough to comply? No. Overlay or "accessibility widget" tools do not make a site WCAG-conformant, can interfere with users' own assistive technology, and have themselves been the subject of legal complaints. Real compliance comes from fixing the underlying code and design, verified by manual testing.
6. How much does it cost to make my site compliant? A professional accessibility audit typically runs €3,000–€15,000+; remediation cost depends on how many issues you have and how severe they are. Building accessibility into a new project from the brief stage usually adds only around 5–15%—far cheaper than retrofitting a finished, inaccessible product.
Ready to Get Compliant?
Short on time? Get matched with 3 vetted agencies that build to WCAG 2.1 AA, estimate a project with the UX cost calculator, or browse the directory.
For the official text and guidance, see the European Commission's EAA page and the full directive on EUR-Lex.
Related Guides: