European Accessibility Act Compliance: What the EAA Requires

What Is the European Accessibility Act?

The EAA is EU legislation that sets common accessibility requirements for a wide range of consumer products and services across all 27 member states. It has two goals: to give people with disabilities in the EU equal access to everyday products and services, and to harmonise accessibility rules so businesses face one consistent standard instead of 27 different national ones. According to the European Commission, an estimated 87 million people in the EU live with some form of disability.

Because it is a directive rather than a regulation, the EAA does not apply directly. Each member state transposed Directive (EU) 2019/882 into national law, and each enforces it through its own authorities and penalty frameworks. Compliance is therefore an EU-wide obligation with country-level variation, which is why a single generic checklist is not enough for a multi-market seller.

What Products and Services Does It Cover?

The Act applies to products and services that are commonly used and historically inaccessible. If your digital storefront or app sits in one of these categories, the covered surface is the whole journey, not just the public homepage.

• Covered products: Computers, smartphones, tablets, e-readers, payment terminals, ATMs, and ticketing and check-in machines.
• Covered services: E-commerce, consumer banking, electronic communications, transport ticketing and information, e-books, and access to audio-visual media services.
• What that means for digital teams: Websites, mobile apps, and the interfaces behind checkout, account, and support flows must be accessible, including the states a URL-only scan never reaches.

The practical consequence is scope creep in the right direction: the login, the cart, the error messages, and the confirmation screen are all in scope, so compliance work has to follow the transaction rather than stop at the landing page.

Who Must Comply With the EAA?

The EAA applies to any business with 10 or more employees or 2 million euros or more in annual turnover that offers covered products or services to EU consumers. Those thresholds come directly from Directive (EU) 2019/882. Crucially, this includes companies based outside the EU: if EU customers can buy from you or use your service, you are in scope regardless of where you are headquartered.

The Directive includes a narrow exemption for microenterprises providing services, meaning fewer than 10 employees and under 2 million euros in turnover. That exemption is limited, applies to services rather than products, and most organisations selling into the EU do not qualify for it. If you are unsure, the safer working assumption is that you are in scope.

Which Standards Define EAA Compliance?

The EAA states what must be achieved but points to technical standards for how. In practice, compliance is measured against EN 301 549, the European standard for ICT accessibility, which references the Web Content Accessibility Guidelines (WCAG 2.1) Level AA as the benchmark for web content. Conforming to EN 301 549 creates a presumption of conformity with the EAA.

The functional requirements rest on the four WCAG principles, known as POUR: content and functionality must be perceivable, operable, understandable, and robust for people with disabilities, including those using assistive technologies such as screen readers. If the distinction between Level A, AA, and AAA is unfamiliar, our breakdown of WCAG conformance levels explains what each tier requires.

EN 301 549 extends beyond the web to cover documents, software, and hardware, and it is moving toward WCAG 2.2, so organisations building for the long term should align with 2.2 AA. Alongside the functional standard, the EAA adds administrative obligations: a published accessibility statement naming the standard you conform to and the authority users can escalate to, and a feedback mechanism for reporting barriers.

How Do You Demonstrate Compliance?

EAA compliance is demonstrated through evidence, not assertion. A defensible approach is a loop, not a one-off audit, and each step produces an artifact you can show a regulator.

• Baseline: Audit against EN 301 549 to establish where you stand today, page by page and flow by flow.
• Prioritise: Fix the barriers that block real user journeys first, registration, checkout, login, search, and support, before cosmetic issues.
• Remediate and re-test: Confirm each fix, then keep testing so the service does not regress as it changes.
• Monitor: Re-scan on a schedule and in CI, because every new template, plugin, or checkout change can reintroduce a barrier.

Because automated tooling catches only part of the WCAG success criteria, compliance requires a combination of automated scanning and manual testing with assistive technologies. TestMu AI supports this through an Axe-core powered Accessibility Testing Suite that spans browser Accessibility DevTools for in-browser WCAG checks, real screen readers such as NVDA, JAWS, VoiceOver, and TalkBack for manual validation, and a keyboard scan for operability. The accessibility automation docs show how to add the same scans to existing Selenium, Playwright, and Cypress suites so checks run on every build.

Note: Baseline your site against WCAG 2.1 AA and keep evidence of active remediation. TestMu AI runs automated and manual accessibility testing in one platform. Try Now!

What Are the Penalties, and Is the EAA Enforced?

The EAA does not set a single EU-wide penalty. Under Article 30 of the Directive, each member state defines its own fines and penalties, which must be effective, proportionate, and dissuasive. Reported maximums vary widely, from fixed amounts in the tens of thousands of euros in some states to turnover-based penalties in others. Fines are rarely the first step: authorities typically begin with notification, investigation, and corrective-action deadlines before penalties apply.

Financial penalties are not the only exposure. Authorities can order product withdrawal, ban non-compliant products from a national market, require audits, and publicly name organisations that fall short. In some jurisdictions, competitors can bring unfair-competition claims over non-compliance, which turns an accessibility gap into a commercial one.

Enforcement is member-state-led and has been uneven across the EU, but the machinery is active. Early enforcement has centred on notices, investigations, market surveillance, and corrective-action deadlines rather than headline fines, with escalation to penalties built into every national framework. Enforcement specifics vary by country and change over time, so verify the current position for your target markets before relying on any single figure.

What Deadlines Remain After June 2025?

Some obligations phase in after the initial date. The Directive's transitional provisions ease the change but do not remove the obligation, so teams that will meet the later deadlines comfortably are building them into their roadmaps now.

• Service contracts: Agreements concluded before 28 June 2025 may continue unchanged until they expire, but no longer than five years from that date.
• 28 June 2030: The transition period for services relying on products already in use ends, after which legacy content must also conform.
• End of economic life: Self-service terminals installed before the deadline may remain in use until the end of their economic life, up to a maximum of 20 years.

The takeaway is that "we have until 2030" is true only for a narrow slice of legacy content. The core obligation for new products and services has been live since 28 June 2025, and a transition window is not a reason to defer the baseline audit.

Turning EAA Compliance Into an Ongoing Process

Start with one concrete step: run a baseline scan of your highest-value journey, the checkout or the signup, against WCAG 2.1 AA, and record the violations with their WCAG references. That single report tells you where the legal exposure actually is, and it becomes the first artifact in your evidence trail.

From there, make testing continuous rather than a one-time project, because every new template, plugin, or checkout change can reintroduce barriers. The organisations best positioned test on every build, validate on real browsers and devices via the TestMu AI Real Device Cloud, and treat accessibility as a quality gate the same way they treat regression testing, an approach we cover in detail for continuous accessibility compliance in CI/CD. Bring that loop into one platform and start free with TestMu AI Accessibility Testing to baseline where you stand today.