The European Accessibility Act (Directive (EU) 2019/882) is EU law that requires a defined set of digital products and services to be accessible to people with disabilities, with obligations applying from 28 June 2025. It harmonises accessibility rules across member states so that e-commerce, banking, e-books, ticketing, transport and consumer devices meet a common baseline built on web standards rather than a patchwork of national laws.
What is the European Accessibility Act?
The European Accessibility Act (EAA) is Directive (EU) 2019/882, adopted in 2019 and transposed into national law across the EU. It sets common accessibility requirements for specific products and services so that a company selling into multiple member states meets one harmonised standard instead of negotiating twenty-seven separate rulebooks. The directive covers both physical products and digital services, and its digital requirements are what most product and design teams need to plan for.
The headline date is 28 June 2025: from that point, in-scope products placed on the market and services provided to consumers must meet the Act's requirements. Existing service contracts and self-service terminals carry longer transition windows in some member states, but the direction is settled. Accessibility has moved from a design preference to a legal baseline for a large slice of the digital economy.
Which products and services are in scope?
The EAA targets consumer-facing products and services where exclusion causes real harm. If your business touches any of the categories below and sells to EU consumers, assume you are in scope until a lawyer tells you otherwise.
- E-commerce — consumer online shops, checkout flows and the services behind them.
- Banking and payments — consumer banking services, payment terminals and related interfaces.
- E-books — digital publications and the software used to read them.
- Ticketing and transport — websites, apps and self-service machines for air, bus, rail and waterborne transport.
- Telecoms — electronic communications services and their consumer interfaces.
- Consumer devices — computers, smartphones, e-readers, ATMs, ticketing and check-in machines.
There is a meaningful carve-out. Micro-enterprises — broadly, fewer than ten staff and under a defined annual turnover threshold — that provide services are exempt from the bulk of the obligations, though micro-enterprises manufacturing products are not automatically off the hook. Exemption is not an excuse to ship an inaccessible product; it is a narrow legal relief for the smallest operators.
How does EN 301 549 and WCAG 2.1 AA fit in?
The EAA sets outcomes, not pixels. To show you have met those outcomes, you follow the harmonised European standard EN 301 549, which is the reference for ICT accessibility across the EU. For web content, EN 301 549 points to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. In practice, meeting WCAG 2.1 AA across your websites and apps is the single most useful thing a product team can do to demonstrate conformance.
WCAG organises requirements under four principles, usually shortened to POUR: content must be perceivable, operable, understandable and robust. Those four words are the backbone of any credible interface design process, because the same qualities that help a screen-reader user also help everyone else move through a product faster.
Does the EAA apply to UK companies after Brexit?
The EAA is EU law and was not retained in UK domestic law. UK-only businesses instead answer to the Equality Act 2010, which requires reasonable adjustments and effectively expects accessible digital services, and public bodies must meet the Public Sector Bodies Accessibility Regulations (PSBAR), also built on WCAG. So the UK has its own accessibility duties, distinct from the EAA.
The important nuance for anyone running a business from London: if you sell in-scope products or services to consumers in the EU, the EAA still bites regardless of where you are incorporated. A UK fintech, publisher or retailer with EU customers has to meet the same bar as a Berlin or Tallinn competitor. Building to WCAG 2.1 AA once satisfies the UK duty and the EU requirement together, which is why we treat it as the baseline for every client, from a Baltic scale-up to a London fintech.
The practical design and build checklist
Accessibility is not a plugin you bolt on at the end. Most failures are decided in the design file and the component library, long before code review. Work through these areas as you design and build.
Perceivable
- Meet WCAG contrast ratios — at least 4.5:1 for normal text and 3:1 for large text and meaningful UI components.
- Never use colour alone to carry meaning; pair it with text, icons or patterns.
- Provide text alternatives for images and captions or transcripts for audio and video.
Operable
- Make every interaction reachable and usable by keyboard alone, in a logical order.
- Show a clear, visible focus state on every interactive element — no invisible outlines.
- Respect reduced-motion preferences and avoid content that flashes or auto-plays disruptively.
- Size touch targets generously so they work for imprecise input.
Understandable
- Label every form field, and tie error messages to the field they describe.
- Write plain, specific error and instruction text; explain how to fix a problem, not just that one exists.
- Keep navigation and component behaviour consistent across the product.
Robust
- Use semantic HTML and correct ARIA so assistive technology can interpret the interface.
- Name, role and state must be exposed for custom components in your design system.
Governance and testing that actually holds up
Conformance is a moving target because your product ships every week. Treat accessibility as a standing process, not a one-off audit. Assign clear ownership, bake acceptance criteria into your definition of done, and keep an accessibility statement that reflects reality rather than aspiration. The EAA also expects you to be able to describe how your service meets the requirements, so documentation is part of the deliverable.
Testing works best in three layers, because each catches what the others miss:
- Automated tools (such as axe or Lighthouse) catch roughly a third of issues — contrast, missing labels, structural errors — and belong in your CI pipeline.
- Manual review catches keyboard traps, focus order, reading order and logic that automation cannot judge.
- Assistive-technology testing with real screen readers (VoiceOver, NVDA) and, ideally, disabled users confirms the experience actually works.
The business upside of getting this right
Framing the EAA purely as legal risk undersells it. A meaningful share of the population lives with a disability, and accessible products open your market to customers competitors are quietly excluding at checkout. The engineering discipline behind accessibility — semantic markup, clear structure, keyboard support — also improves performance and SEO, because search engines parse the same signals assistive technology relies on.
There is a commercial calm to it too. Accessible-by-default products reduce legal exposure across both UK and EU regimes, cut the cost of retrofitting, and tend to convert better because they are simply easier to use. For teams operating between London and Tallinn, building to WCAG 2.1 AA is the pragmatic way to satisfy every regulator you answer to and every customer you want to keep. If you are weighing where accessibility sits in your roadmap, talk to us about folding it into your product design from the first sprint rather than the last.
Frequently asked questions
When does the European Accessibility Act take effect?
The Act's obligations apply from 28 June 2025. From that date, in-scope products placed on the EU market and services provided to consumers must meet its accessibility requirements. Some existing service contracts and self-service terminals have longer transition periods under national law, but the core deadline is fixed and already in force.
Does the EAA apply to UK businesses?
The EAA is EU law and does not apply to UK-only businesses, which follow the Equality Act 2010 and, for public bodies, PSBAR. However, any UK company selling in-scope products or services to EU consumers must comply with the EAA regardless of where it is based. Building to WCAG 2.1 AA satisfies both regimes at once.
What standard proves EAA compliance?
The harmonised European standard EN 301 549 is the reference for ICT accessibility under the EAA. For web content it points to WCAG 2.1 at Level AA. Meeting WCAG 2.1 AA across your websites and apps is the most practical way to demonstrate conformance for digital products and services.
Which businesses are exempt from the EAA?
Micro-enterprises providing services — broadly those with fewer than ten employees and turnover below a defined threshold — are exempt from most obligations. Micro-enterprises that manufacture products are not automatically exempt. Exemption is a narrow legal relief, not a reason to ship inaccessible products, and thresholds should be confirmed with legal counsel.
How do we test for accessibility compliance?
Use three layers. Automated tools like axe or Lighthouse catch around a third of issues and belong in CI. Manual review catches keyboard traps, focus order and reading logic. Assistive-technology testing with real screen readers such as VoiceOver and NVDA, ideally with disabled users, confirms the experience works in practice.