Skip to content
Book a call
UI Design

The European Accessibility Act: what product teams should know

The EAA applies to many digital products sold in the EU. What designers and developers should check first, and when to ask a lawyer.

MD Rakib Shekh6 min read
Cover illustration for the article "The European Accessibility Act: what product teams should know"

The European Accessibility Act, or EAA, has been in the news among product teams since it began to apply in June 2025. Many founders outside Europe hear about it late and wonder if it concerns them.

This is a plain explanation for designers, developers and founders. It is not legal advice. Whether the act applies to your product, and what you must do, depends on facts we do not know, so a lawyer who knows EU law should confirm anything that matters.

What the act is

The EAA is Directive (EU) 2019/882. It sets accessibility requirements for a list of products and services, so that people with disabilities can use them. The directive was adopted in 2019. EU member states had to turn it into national law, and the rules started to apply on 28 June 2025.

It is a directive, so each country has its own national law that applies it. The details, such as who enforces it and what the penalties are, differ from country to country. That is one reason to check the rules in the markets where you sell.

The goal is practical. A blind person should be able to use a banking app with a screen reader. A person with limited hand movement should be able to complete a checkout. A deaf person should be able to use customer support. Accessibility becomes a product requirement, not a nice extra.

Who it may cover

The act does not cover every website. It names product and service categories. Among the services, the ones most relevant to software teams include:

  • E-commerce services, such as online shops and marketplaces that sell to consumers
  • Consumer banking services
  • Electronic communications services, such as messaging and calling
  • E-books and dedicated e-reading software
  • Passenger transport services, including the websites, apps, ticketing and information
  • Services giving access to audiovisual media

It also covers some hardware, such as self-service terminals and e-readers.

A few things to know about scope:

  • It is about services offered to consumers in the EU. A pure B2B tool may fall outside it, though your customers may still ask for accessibility in their contracts. If you are not sure whether a product is "consumer-facing", ask a lawyer.
  • Microenterprises that provide services are generally exempt from the service requirements. The directive defines a microenterprise as fewer than 10 people and a turnover or balance sheet total of not more than 2 million euros. Check the definition and how your country applies it.
  • The act can apply to companies outside the EU if they sell the covered products or services in the EU.
  • There are exceptions, for example where meeting the requirements would fundamentally change the service or put a disproportionate burden on the business. These are narrow, and you would need to document the case.

If you are a SaaS company selling to businesses, you may be outside the main scope, but your enterprise customers may be inside it and may pass the requirement down to you. Read your contracts and security questionnaires.

How it relates to WCAG

The act itself sets high-level goals. It does not list screen-by-screen rules. The technical detail comes from standards.

For web content and apps, the key standard is the European standard EN 301 549. For web content, it points to the Web Content Accessibility Guidelines (WCAG) at level AA. The current version of EN 301 549 refers to WCAG 2.1 AA. WCAG 2.2, which became a W3C Recommendation in October 2023, adds more success criteria on top of 2.1. You can read it at w3.org/TR/WCAG22.

In practice, many teams aim for WCAG 2.2 AA. It includes everything in 2.1 AA and is where the standards are heading. But the exact standard that counts as meeting the law in your market is a legal question. Ask your adviser which version to target and how your country treats it.

WCAG is organized around four ideas. Content must be perceivable, operable, understandable and compatible with other tools:

  • Perceivable, so users can see or hear it, for example through text alternatives and enough contrast
  • Operable, so users can use it with a keyboard or other input, with enough time and no traps
  • Understandable, with clear labels, predictable behavior and helpful errors
  • Compatible with assistive technology such as screen readers, because the code is clean and well structured

What to check first

You do not need to fix everything on day one. Start with the parts users go through to buy, sign up or get help, since those are the most likely to matter.

  1. List your key flows. Sign-up, log-in, search, checkout, account settings, support. These come first.
  2. Try the keyboard. Put your mouse away. Can you complete each flow with Tab, Enter, Space and the arrow keys? Is the focus always visible? Can you get out of every menu and dialog?
  3. Check contrast and text size. Body text needs enough contrast against its background, and the page should still work when text is enlarged.
  4. Check forms. Every field has a visible label. Errors are explained in text, not just by color. Required fields are marked.
  5. Check images and icons. Meaningful images have text alternatives. Icon-only buttons have names.
  6. Try a screen reader. VoiceOver on Mac and iOS, NVDA on Windows, TalkBack on Android. Spend an hour on your main flow. It teaches more than any report.
  7. Check video and audio. Captions for video, and transcripts where they help.
  8. Run an automated scan as a first pass. Tools like axe or Lighthouse catch only part of the problems, so do not treat a clean scan as a pass.

Fix by pattern. If your button component has a weak focus style, fixing the component fixes every screen. This is why accessibility belongs in the design system from the start.

A UX audit can include these checks on your key flows, with a ranked list of what to fix first. We are not a legal firm, and we do not certify compliance. What we can do is find usability and accessibility problems in your product and help you fix them.

Accessibility statements and documentation

Service providers covered by the act must also provide information about how their service meets the accessibility requirements. In practice, many teams publish an accessibility statement. It usually says:

  • Which standard you aim to meet and how well you meet it today
  • Known gaps, and your plans to fix them
  • How users can report a problem or ask for help, with a real contact
  • The date of your last review

Keep your own records too: what you tested, what you found, what you fixed and when. If a regulator asks, a clear paper trail helps. Which documents are required, and in what form, depends on the country. Ask your lawyer rather than copying another company's statement.

Be honest in the statement. An accurate "we meet most of this and are working on the rest" is better than a claim of full compliance that a quick test would disprove.

Next steps

  1. Ask a lawyer whether and how the EAA applies to your product and markets.
  2. Pick a target, such as WCAG 2.2 AA, with their advice.
  3. Test your top flows with a keyboard and a screen reader.
  4. Fix the biggest issues at the component level.
  5. Add accessibility checks to your design and release process.
  6. Publish an honest statement and keep records.

If you would like help finding the problems in your key flows, see how we work with SaaS teams or ask for a free design review of one page at /contact. Again, nothing here is legal advice. For legal questions, talk to a qualified adviser.

Want a second pair of eyes on your product?

Send your site or app and get a free design review from Rakib. No sales call, no cost.