What Is the European Accessibility Act?
The European Accessibility Act (EAA), formally Directive (EU) 2019/882, is landmark EU legislation requiring that a broad range of digital products and services meet specific accessibility standards. Unlike previous accessibility rules that focused primarily on public sector websites, the EAA extends accessibility obligations to private companies across several key sectors.
The goal is straightforward: ensure that people with disabilities — estimated at more than 87 million across the EU — can access the same digital products and services as everyone else, on equal terms.
The directive was adopted in April 2019. EU member states were required to transpose it into national law by June 2022, and enforcement began on 28 June 2025. For most businesses, that deadline has already passed.
Who Does the EAA Affect?
The EAA applies to companies that manufacture or distribute products, or provide services, in EU markets. It is not limited to EU-registered businesses: any organisation serving EU customers falls within scope if it crosses the micro-enterprise threshold (fewer than 10 employees and less than €2 million annual turnover are exempt).
The sectors explicitly covered include:
- E-commerce — online shops and marketplaces selling goods or services to consumers
- Banking and financial services — consumer banking, payment terminals, ATMs, digital banking apps
- Transport — passenger transport services (air, rail, bus, urban transport), including ticket booking and real-time information
- Telecommunications — telephone services, messaging apps, and related consumer equipment
- Audiovisual media services — streaming platforms, on-demand video services
- Operating systems and hardware — computers, smartphones, e-readers, and their software environments
- E-books and dedicated reading software
If your business provides any of these services to EU consumers, the EAA almost certainly applies to you.
Key Requirements: What the EAA Actually Demands
The EAA defines accessibility requirements for both products and services. The overarching principle is that they must be perceivable, operable, understandable, and robust — language that maps directly onto the WCAG four-principle framework.
For Products
Products must:
- Provide information about how to use their accessibility features
- Include user interfaces that are operable via multiple input methods (not just a mouse or touchscreen)
- Come with packaging and instructions that are accessible in alternative formats
- Be designed so that assistive technologies (screen readers, switch controls, etc.) can interact with them effectively
For Services
Services must:
- Provide information about how they meet accessibility standards
- Ensure that websites, mobile apps, and other digital touchpoints are accessible
- Use text, video with captions, and audio alternatives where content is published in a single format
- Enable two-way communication (live chat, support interfaces, messaging) in accessible formats
- Not make accessibility a paid add-on — it must be integral to the service
The Standard Behind the Standard
The EAA does not prescribe specific technical criteria in the directive text. Instead, the European Commission mandated that harmonised standards be developed. The result is EN 301 549, a technical standard that incorporates WCAG 2.1 Level AA as the baseline for web and mobile content, with additional criteria for software and hardware.
In practice: if your digital touchpoints meet WCAG 2.1 AA (and ideally WCAG 2.2 AA), you are largely aligned with EAA technical requirements for web content. WCAG 2.2 introduced additional criteria in October 2023, including improvements to focus indicators and mobile accessibility, and is increasingly treated as the de facto target.
The Timeline at a Glance
| Date | Milestone |
|---|---|
| April 2019 | EAA adopted by European Parliament and Council |
| June 2022 | Transposition deadline into national law |
| June 2025 | Enforcement begins — full obligations apply |
| June 2030 | Transition period ends for certain long-term contracts signed before June 2025 |
The 2030 date applies specifically to service contracts already in place before June 2025. However, new contracts and new products/services have had no grace period since June 2025.
Enforcement and Penalties
Enforcement is handled at the member state level, which means the specific penalties and procedures differ across the EU. Each country has designated a market surveillance authority responsible for receiving complaints, conducting investigations, and issuing penalties.
How Enforcement Works
- Market surveillance: National authorities proactively monitor products and services for compliance.
- Complaint mechanisms: Users (or organisations representing users with disabilities) can file complaints with national authorities.
- Corrective orders: Authorities can require companies to take corrective action within a specified timeframe.
- Financial penalties: Non-compliant businesses face fines, which vary by member state.
Penalties by Country (Examples)
Spain: The national transposition (RD 1112/2018 for public sector, extended via the EAA transposition law) connects to the existing LSSICE framework. Infringements related to information society services can trigger fines in the range of €30,001 to €150,000 for serious violations.
Germany: The Barrierefreiheitsstärkungsgesetz (BFSG), Germany's EAA transposition, came into force in June 2025. It empowers the Marktüberwachungsbehörde to issue warnings, withdraw non-compliant products from the market, and levy fines.
France: France's loi pour une République numérique and subsequent EAA transposition provide for fines and mandatory compliance notices issued through DGCCRF (the consumer protection authority).
Across the EU: Fines can also include orders to withdraw products from sale, bans on placing non-compliant products on the market, and mandatory public disclosure of violations.
The financial exposure is real, but the reputational and legal risk of a publicly filed complaint is often the greater concern for consumer-facing brands.
What "Proportionate Burden" Means
The EAA includes a concept of disproportionate burden: if meeting an accessibility requirement would impose costs fundamentally disproportionate to the benefit, a business can claim an exception. However, this is a limited, documented exception — not a general opt-out. The calculation must consider:
- The cost of making the change versus the organisation's size and revenue
- The estimated benefit to users with disabilities
- The frequency of use
Micro-enterprises (fewer than 10 employees and under €2M turnover) are exempt from the service provisions, but not from product obligations.
How to Prepare: A Practical Roadmap
1. Scope Assessment
Identify which of your products and services fall within EAA scope. Not everything you offer may be covered — focus on consumer-facing digital touchpoints first.
2. Gap Analysis Against WCAG 2.1 AA / EN 301 549
Audit your website, mobile app, live chat, chatbot, and any other digital interface against WCAG 2.1 Level AA success criteria. Use automated tools as a starting point, but manual testing with assistive technologies is essential for comprehensive coverage.
3. Prioritise by Risk and User Impact
Not all gaps carry the same risk. Focus first on barriers that prevent core user journeys: completing a purchase, accessing account information, contacting support.
4. Fix Systematically, Document Everything
Accessibility compliance is not a one-time project. Build it into your design system, your QA process, and your vendor contracts. Document your conformance efforts — this documentation is valuable evidence if a complaint is filed.
5. Include Assistive Technology in Your Testing Stack
Screen readers (NVDA, JAWS, VoiceOver), keyboard-only navigation, and browser zoom should be standard parts of your QA process, not afterthoughts.
6. Review Third-Party Components
Your widget library, payment processor UI, chat widget, and any embedded third-party tool must also be accessible. You remain responsible for the full user experience on your platform.
The Business Case Beyond Compliance
Accessible design consistently benefits all users, not just those with disabilities. Captions help users in noisy environments. High contrast benefits users in bright sunlight. Clear focus indicators help power keyboard users. The overlap between accessibility improvements and general UX quality is substantial.
Beyond usability, there is market size. Users with disabilities and their households represent significant purchasing power. Organisations that build accessibility in from the start outcompete those that retrofit it under regulatory pressure.
Where AISWise Fits In
One area where EAA compliance can be complex is conversational interfaces — chatbots and AI assistants embedded on websites and apps. These are increasingly part of customer support, onboarding, and transactional flows, which means they fall squarely within EAA scope.
AISWise builds WCAG-compliant AI chatbots designed for enterprise and regulated environments. Keyboard navigation, screen reader compatibility, focus management, and colour contrast are built into the interface — not bolted on after the fact.
If you are working through your EAA gap analysis and need a support or conversion chatbot that is accessible by design, see how AISWise approaches compliance-first conversational AI.
Summary
The European Accessibility Act is not a future concern — enforcement has been live since June 2025. For any business with digital touchpoints serving EU consumers in e-commerce, banking, transport, telecom, or media, compliance is now a legal obligation.
The technical baseline is WCAG 2.1 AA (EN 301 549). Enforcement is decentralised across member states, with penalties ranging from corrective orders to substantial fines. The most effective path is a structured gap analysis, systematic remediation, and embedding accessibility into your development and procurement processes.
Waiting for a complaint to arrive is the most expensive way to achieve compliance.