European Accessibility Act 2025: Complete Guide
Everything you need to know about the EAA — what it requires, who it affects, deadlines, penalties, and step-by-step compliance guidance for website owners.
What Is the European Accessibility Act?
The European Accessibility Act (EAA), formally known as Directive (EU) 2019/882, is a landmark piece of legislation that harmonizes accessibility requirements across all 27 EU member states. It was adopted by the European Parliament in April 2019 and became enforceable on June 28, 2025.
The EAA establishes common accessibility requirements for a wide range of products and services, including websites, mobile applications, e-commerce platforms, banking services, and transportation ticketing systems. Its primary goal is to improve the functioning of the internal market for accessible products and services by removing barriers created by divergent national rules.
Who Does the EAA Affect?
The EAA applies to both public and private sector organizations that sell products or provide services within the European Union. This includes:
- E-commerce websites — Any online store selling products or services to EU consumers
- Banking and financial services — Online banking, payment terminals, ATMs
- Telecommunications — Phone services, messaging apps, customer support portals
- Transportation — Ticketing websites, booking platforms, self-service terminals
- Media services — E-books, audiovisual media platforms
- Computing hardware and software — Operating systems, consumer hardware
Notably, the EAA applies regardless of where the company is headquartered. If your website serves EU customers, you are subject to EAA requirements. This means US-based, UK-based, and other international companies must comply when their services reach the EU market.
Microenterprise Exemption
The EAA includes a limited exemption for microenterprises — businesses with fewer than 10 employees and an annual turnover or balance sheet total not exceeding 2 million euros. However, this exemption only applies to services, not products. If a microenterprise manufactures products covered by the EAA, they must still comply.
Even exempt microenterprises are encouraged to voluntarily meet accessibility standards. The exemption may also be narrowed by individual member states in their national transposition of the directive.
Technical Requirements: WCAG 2.1 Level AA
The EAA references the harmonized European standard EN 301 549, which in turn maps to WCAG 2.1 Level AA as the minimum compliance standard for web content. This means your website must satisfy the four POUR principles:
- Perceivable — Content must be presentable to users in ways they can perceive. This includes text alternatives for images, captions for video, sufficient color contrast, and content that can be presented in different ways without losing meaning.
- Operable — Interface components must be operable by all users. All functionality must be available via keyboard, users must have enough time to read content, and navigation must be predictable.
- Understandable — Information and operation of the user interface must be understandable. Text must be readable, pages must operate in predictable ways, and users must receive help to avoid and correct mistakes.
- Robust — Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies. This means valid, semantic HTML and proper ARIA usage.
Key Deadlines
Understanding the EAA timeline is critical for planning your compliance efforts:
- April 2019 — EAA adopted by the European Parliament
- June 28, 2022 — Deadline for EU member states to transpose the directive into national law
- June 28, 2025 — Enforcement begins. All covered products and services must be accessible
- June 28, 2030 — Transition period ends for services that were already under contract before June 2025
Penalties for Non-Compliance
The EAA requires each member state to establish penalties that are “effective, proportionate, and dissuasive.” While the directive does not specify exact fine amounts, individual countries have set their own enforcement mechanisms:
- Germany — The Barrierefreiheitsstarkungsgesetz (BFSG) allows fines up to 100,000 euros
- France — Fines up to 50,000 euros per infringement
- Netherlands — Market surveillance authorities can impose administrative fines and order product withdrawal
- Italy — AGID can impose sanctions and order corrective measures
Beyond fines, non-compliant businesses face potential market restrictions, mandatory corrective actions, and reputational damage. In some member states, consumers can file complaints directly with market surveillance authorities.
How to Comply: Step-by-Step
Achieving EAA compliance requires a systematic approach. Here is a practical roadmap:
- Audit your current website — Use an automated scanner like FixMyWeb to identify existing WCAG 2.1 AA violations. Automated tools typically catch 30-50% of issues.
- Conduct manual testing — Test with keyboard navigation, screen readers (NVDA, JAWS, VoiceOver), and zoom at 200%. Check logical reading order and focus management.
- Prioritize critical issues — Fix critical and serious issues first: missing alt text, broken keyboard navigation, poor contrast, and missing form labels.
- Train your team — Developers, designers, and content creators should understand basic accessibility principles. WCAG is not a one-time fix but an ongoing practice.
- Integrate accessibility into your workflow — Include accessibility checks in design reviews, code reviews, and QA testing. Use tools like FixMyWeb's API to automate scanning in your CI/CD pipeline.
- Publish an accessibility statement — Document your conformance level, known limitations, and contact information for accessibility feedback.
- Monitor continuously — Accessibility is not a one-time project. New content, features, and third-party integrations can introduce new barriers. Schedule regular scans.
EAA vs Other Accessibility Laws
The EAA exists alongside other accessibility regulations worldwide:
- ADA Title II (United States) — Requires government websites to meet WCAG 2.1 AA by April 2026. ADA Title III has been applied to private business websites through litigation.
- Section 508 (United States) — Applies to federal agencies and their contractors.
- Accessibility for Ontarians with Disabilities Act (Canada) — Requires accessible websites for Ontario organizations.
- Equality Act 2010 (United Kingdom) — While the UK is no longer in the EU, similar accessibility requirements apply under domestic law.
The EAA is notable for its breadth — it covers both public and private sectors, applies to physical products and digital services, and harmonizes requirements across 27 countries simultaneously.
Common Mistakes to Avoid
- Relying solely on overlays — Accessibility overlay widgets do not make websites WCAG compliant. They can interfere with assistive technologies and have been the target of lawsuits.
- Treating accessibility as a one-time project — Every new page, feature, or content update can introduce accessibility barriers. Continuous monitoring is essential.
- Ignoring mobile accessibility — The EAA explicitly covers mobile applications. Touch targets, zoom support, and screen reader compatibility on mobile are required.
- Forgetting third-party content — Embedded widgets, chat tools, payment forms, and social media feeds must also be accessible. You are responsible for ensuring third-party components on your site meet standards.
Start Your Compliance Journey Today
With the EAA already in force, the time to act is now. Over 80 million people in the EU have some form of disability, and accessible design benefits everyone — including users on mobile devices, older adults, and people with temporary impairments.
Start by running a free accessibility scan on your website. Our scanner checks 11+ WCAG criteria and provides actionable fix recommendations with code snippets for every issue found.
Is Your Website EAA Compliant?
Scan your website now and get a detailed WCAG 2.1 AA audit report in seconds.
Free Accessibility Scan