The European Accessibility Act (EAA): A Guide for Software Teams

The European Accessibility Act (EAA) is no longer a future proposal. It is a directive (Directive 2019/882) that EU member states have translated into national law. The enforcement date is 28 June 2025. After that date, specific digital products and services sold to consumers in the EU must be accessible to people with disabilities.

Unlike older accessibility mandates that mostly governed public-sector websites, the EAA targets the private sector. If you sell an e-book, a smartphone, a streaming service, or run an e-commerce storefront for European consumers, you are on the list. The geographic location of your headquarters does not matter. The location of your customer does.

What is actually covered?

The EAA is not a blanket rule for the entire internet. It names specific categories of hardware, software, and services that are deemed essential for participation in society. If your business model relies on European consumer revenue, check this list.

E-commerce. This is the net that catches most software shops. If you sell products or services online to consumers in the EU, the entire digital storefront — from product search to the final checkout button — must be accessible. The physical product being sold does not have to be in scope, but the digital transaction process does.

Consumer hardware and operating systems. Smartphones, tablets, laptops, and the operating systems that run them. Self-service terminals like ATMs, ticketing machines, and check-in kiosks are also expressly covered.

Digital services. E-books and dedicated reading software. Banking and financial services provided to consumers. Audiovisual media services (streaming platforms). Electronic communications services (messaging apps, telecom services). Transport service tickets and information.

The directive targets B2C (business-to-consumer) transactions. B2B software is generally outside the direct scope of the EAA, though procurement rules often demand accessibility anyway.

The microenterprise exception

The EAA contains a specific carve-out for microenterprises that provide services. A microenterprise is defined as a business that employs fewer than 10 people and has an annual turnover or balance sheet total not exceeding EUR 2 million.

If a company meets this definition and provides covered services (like an e-commerce site), it is exempt from the EAA obligations to avoid disproportionate burden. However, microenterprises that manufacture covered products (hardware) must still comply, though they face lighter administrative reporting requirements. Size is a shield only for the smallest service providers, and that shield vanishes the moment the company scales.

The technical standard: EN 301 549

The EAA is a political directive. It demands accessibility but does not write the code. The technical specification that bridges the law to the engineering team is EN 301 549.

For web content, EN 301 549 Chapter 9 historically points directly to WCAG 2.1 Level AA. The upcoming v4 of the standard aligns closer to WCAG 2.2 AA. The European Commission publishes references in the Official Journal to declare which version of the standard confers a “presumption of conformity” with the law.

The practical engineering translation is straightforward: build your web applications to WCAG 2.2 AA. It is backwards compatible with 2.1, it meets the EN 301 549 requirements for web, and it stops arguments about which minor version the law currently cites. If you build a native mobile app, the standard maps the same principles to platform-specific APIs.

CE marking and market surveillance

Digital products (hardware and operating systems) covered by the EAA must carry the CE mark, declaring conformity with the accessibility requirements, just as they do for electrical safety. Services do not carry a CE mark, but service providers must explain how their service meets the requirements in their general terms and conditions or a dedicated accessibility statement.

Enforcement is not handled by a single European police force. Each member state designates a market surveillance authority. These authorities have the power to demand compliance data, order a product withdrawn from the market, and issue financial penalties. Furthermore, consumer protection bodies and disability advocacy groups have the explicit right to take legal action against non-compliant companies under national law.

Do not expect the authorities to audit every website on June 29. Expect competitors to use compliance as a weapon in procurement, and expect advocacy groups to target high-profile consumer platforms that ignore the deadline.

The engineering action plan

A PDF accessibility statement drafted by legal is not compliance. The EAA requires the actual digital interface to work. The remediation path is the same as any other WCAG effort.

First, audit the critical paths. If you run e-commerce, the product search, the cart, and the checkout flow are the immediate liabilities. Test them with a keyboard. Test them with a screen reader. Automated scanners only catch a fraction of the failures that block a user from spending money.

Second, fix the design system. Remediating a site page by page is a waste of budget. Fix the contrast, the focus states, and the form labels in your component library. When the components are accessible, the templates they build inherit that accessibility.

Third, publish a factual statement. State what works, what does not, and the timeline for fixing the known issues. The EAA requires transparency. Claiming perfect compliance on a broken site is worse than admitting a defect and providing a contact method.

The June 2025 deadline is fixed. The European market is too large to ignore, and the requirements are too complex to fix in a two-week sprint. Treat the EAA as a standard engineering requirement, not a sudden emergency, and it becomes manageable.