Last updated: November 15, 2026
Quick answer: The European Accessibility Act (EAA) requires many websites, apps and digital services sold to consumers in the EU to be accessible to people with disabilities. It has applied since June 28, 2025. In practice, a covered website or app should meet WCAG 2.1 Level AA through the European standard EN 301 549, publish accessibility information, and fix barriers across key journeys such as sign-up, search, checkout and payment.
This guide explains who the EAA covers, what it asks of websites and apps, how enforcement works in 2026 and 2027, and a practical plan to get compliant. It is general information, not legal advice, and national rules differ, so check with a lawyer in the countries where you trade.
The EAA is Directive (EU) 2019/882. It sets common accessibility requirements for a list of products and services across all EU member states, replacing a patchwork of national rules. Each member state turned it into national law, so enforcement and penalties are set country by country.
The EAA applies to businesses that provide covered services to consumers in the EU, or place covered products on the EU market. That includes companies based outside the EU, such as US or UK businesses selling to EU consumers.
Covered services include:
Covered products include computers and operating systems, smartphones, e-readers, self-service terminals such as ATMs, ticket machines and check-in kiosks, and consumer TV equipment.
Microenterprises that provide services are exempt. A microenterprise has fewer than 10 employees and an annual turnover or balance sheet total of no more than €2 million. Microenterprises that make products are not exempt from the product rules, though they have lighter obligations.
A business can claim that a requirement would be a disproportionate burden or would fundamentally change its service. This must be assessed and documented, and regulators can review it. It is not a general opt-out.
The EAA itself describes functional requirements: services must be perceivable, operable, understandable and robust. The practical benchmark is EN 301 549, the harmonised European standard. Its current version, V3.2.1, incorporates WCAG 2.1 Level AA for web and mobile content. A new version that moves to WCAG 2.2 has been in preparation, so it makes sense to design to WCAG 2.2 AA now.
In practice, that means:
Service providers must make information available on how their service meets the accessibility requirements, typically in an accessibility statement linked from the site or included in terms and conditions. It should describe the service, explain how it meets the requirements and give a way to report problems.
Most websites and apps are expected to comply now. The transition periods mainly cover existing equipment and contracts, not ongoing digital services.
Each member state names market surveillance authorities that can investigate complaints, order fixes and impose penalties. Penalties are set nationally and vary widely. Reports from the first year of enforcement suggest authorities focused on notices and remediation first, with more formal action expected as casework builds.
List which services you offer to EU consumers and check them against the covered categories and the microenterprise exemption.
Commission a manual and automated audit against WCAG 2.1 or 2.2 Level AA, focusing on sign-up, search, product pages, checkout, payment and account management. Our list of accessibility audit companies can help.
Prioritize blockers that stop people completing tasks. Fix the code and design rather than relying on overlay widgets, then retest.
Write and publish your accessibility statement, with a contact route for users to report barriers.
Add accessibility checks to design reviews, your design system and release testing so new features stay compliant. See our list of design system agencies.
We checked official pages, help center documentation and current published terms, then compared them with independent sources where details differ. Policies, prices and programs change, so confirm the specifics with the provider before you act. Read our full method on the How We Research And Rank page.
Yes, if they provide covered services to consumers in the EU, such as an online store that sells to EU customers.
The EAA points to EN 301 549, which currently incorporates WCAG 2.1 Level AA for web and mobile content.
Service providers with fewer than 10 employees and annual turnover or balance sheet total of no more than €2 million are exempt.
Overlays do not fix the underlying code and are not a reliable route to compliance. An audit and real fixes are needed.
If you sell to consumers in the EU, assume the EAA applies unless you qualify as a microenterprise. Audit your key journeys against WCAG 2.1 or 2.2 Level AA, fix the barriers, publish accessibility information and keep accessibility in your design and release process.
For more rankings and guides, visit our UX/UI & Product Design hub.