European Accessibility Act: The Complete Guide (2026)
User Interfaces
August 4, 2026•4 min read
I hope you enjoy reading this post. If you want us to do your frontend development or design, click here.
Author: Alex Vasylenko | Founder of The Frontend Company
The European Accessibility Act (EAA) is an EU law that requires most digital products and services sold in the EU — websites, apps, e-commerce, banking, e-books — to be accessible to people with disabilities. It has been enforceable since June 28, 2025. If your company sells digital services to EU customers, even from outside the EU, the EAA almost certainly applies to you, and member states are now actively enforcing it with fines that reach six figures.
This guide covers who must comply, what the law actually requires in technical terms, the real deadlines that remain, and a practical path to compliance that holds up to scrutiny — not an overlay widget.
What is the European Accessibility Act?
The EAA is EU Directive 2019/882, adopted in 2019 and transposed into the national law of every EU member state. Unlike earlier EU accessibility rules that applied mainly to public-sector bodies, the EAA targets the private sector: it sets accessibility requirements for products and services placed on the EU market, regardless of where the company behind them is based.
The directive does not invent its own technical standard. In practice, conformity is assessed against EN 301 549, the European standard for ICT accessibility, which for websites and apps maps directly to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. If your product meets WCAG 2.1 AA and you can document it, you are on solid ground for the EAA’s digital requirements.
Who has to comply
The EAA applies to manufacturers, importers, distributors, and service providers that offer covered products or services to consumers in the EU. Three points catch companies off guard:
- Non-EU companies are covered. The law follows the market, not the headquarters. A US or UK SaaS selling to EU consumers falls under the EAA the same way it falls under GDPR.
- B2C is the trigger, but the line is blurry. The EAA covers services provided to consumers. Pure B2B tools sit outside the strict scope, but products with mixed audiences — marketplaces, booking tools, fintech apps, self-service platforms — are typically in scope in practice.
- The microenterprise exemption is narrow. Service providers with fewer than 10 employees and under EUR 2 million annual turnover are exempt for services. The exemption does not cover products, and it disappears the moment you cross either threshold.
What products and services are covered
The EAA’s scope list is broad. For digital businesses, the categories that matter most:
Covered category | Typical examples |
|---|---|
E-commerce services | Online stores, marketplaces, checkout flows |
Consumer banking services | Online banking, payment apps, statements |
Electronic communications | Messaging services, VoIP apps |
Audiovisual media access | Streaming platform interfaces, EPGs |
E-books and readers | Reading apps, e-book files, DRM |
Transport services | Ticketing sites and apps, check-in kiosks |
Hardware and terminals | ATMs, payment terminals, self-service kiosks, smartphones |
If your product touches any of these categories for EU consumers, the accessibility of your web and app interfaces is now a legal requirement, not a nice-to-have.
The deadlines that actually matter in 2026
- June 28, 2025 — passed. New products and services placed on the market must comply. This deadline is behind us: anything you ship today must already meet the requirements.
- June 28, 2030. The transition window closes for service contracts concluded before June 2025 and for certain self-service terminals already in use. This is the absolute backstop, not a safe harbor for new work.
- Ongoing — member-state enforcement. Each country enforces through its own market surveillance authorities, complaint mechanisms, and penalties. Enforcement began in mid-2025 and is ramping through 2026.
Penalties: what non-compliance costs
Penalties are set nationally, so they vary across the EU, but the pattern is consistent: meaningful fines plus the power to order products and services off the market. Germany’s implementation (the BFSG) allows fines up to EUR 100,000 for violations. Ireland’s act provides for fines up to EUR 60,000 and, for some offences, criminal liability. Other member states sit in similar ranges, and authorities can also compel remediation with deadlines.
The direct fine is rarely the biggest cost. Losing an enterprise deal because procurement asked for an accessibility conformance report you do not have, or being forced to rework a product under a regulator’s deadline, costs far more than fixing accessibility on your own schedule.
Transform your UI for peak performance!
🔹
Unlock seamless, high-performance frontend solutions tailored to your business.
🔹
Get an interface that outshines competitors and delights your users.
The pressure is global, not just European
The EAA did not appear in a vacuum. In the United States, plaintiffs filed 3,117 website accessibility lawsuits in federal court in 2025 — a 27% increase over 2024, according to Seyfarth Shaw’s ADA Title III tracker. Add state-court filings and the total passes 5,000, with tens of thousands of pre-suit demand letters on top. The majority of targets are not tech giants: most defendants are companies under $25 million in revenue, and e-commerce sites take roughly seven in ten of the hits.
For a company selling on both sides of the Atlantic, the practical conclusion is simple: one accessible codebase satisfies both regimes, because both resolve to WCAG conformance.
Why accessibility overlays will not save you
A one-line JavaScript widget that promises instant compliance is tempting — and it does not work. The US Federal Trade Commission ordered overlay vendor accessiBe to pay $1 million in January 2025 for misrepresenting that its AI-powered tool could make websites WCAG-compliant. Courts have repeatedly allowed lawsuits to proceed against sites running overlays, and a large share of recent US filings were generated by scanners that read the underlying source code — which an overlay never changes.
The reason is structural: WCAG failures live in the markup, the component logic, the focus order, the media, and the content itself. According to WebAIM’s annual analysis of the top one million homepages, roughly 95% have detectable WCAG failures — and those are only the machine-detectable ones. Real conformance means fixing the code.
What compliance looks like in practice
A defensible EAA program has five parts:
- Audit against WCAG 2.1 AA / EN 301 549. Combine automated scanning with manual testing — keyboard navigation, screen readers, contrast, forms, error handling. Automation alone finds only a fraction of the criteria.
- Remediate in the code. Fix components, templates, and content: semantic structure, labels, focus management, alt text, captions. This is frontend engineering work, and it is where most of the effort goes.
- Publish an accessibility statement. The EAA expects you to declare how your service meets the requirements, note known exceptions, and give users a feedback channel.
- Document conformance. Keep the audit trail: what was tested, when, by what method, what was fixed. This documentation is what you show a regulator, an enterprise buyer, or a court.
- Monitor continuously. Products change every sprint; accessibility regresses silently. Build checks into CI and re-audit on a schedule, so compliance is a state you maintain, not a project you finish.
Teams that already work in modern frontend stacks have an advantage here: most EAA findings in React, Angular, and Next.js codebases trace back to a manageable set of component-level patterns. Fixing the design system often fixes hundreds of pages at once — the same leverage that makes UI modernization projects pay off.
Get an EAA readiness review of your product
We audit your UI against WCAG 2.1 AA, fix the code — not the symptoms — and leave you with documentation that stands up to procurement and regulators. Book a call to scope it.
FAQ
Alex Vasylenko is the founder of The Frontend Company, DBC and several other successful startups. A dynamic tech entrepreneur, he began his career as a frontend developer at Deloitte and Scandinavia's largest banking company. In 2023, Alex was honored as one of 'Top 10 Emerging Entrepreneurs' by USA Today.
Follow the expert:
RATE
Rate this article please
This will help us provide more useful information.
727 ratings, average 4.89 out of 5
LEARN MORE
