Agent Compliance

European Accessibility Act: UX Compliance Checklist 2025+

By the UXreviewer.io team4 min read

The European Accessibility Act (Directive (EU) 2019/882) applies from 28 June 2025 and requires many consumer products and services sold in the EU, including e-commerce, banking services, e-books, electronic communications and parts of passenger transport, to be accessible to people with disabilities. For websites and apps, compliance is usually assessed against EN 301 549, which incorporates the WCAG 2.1 level AA success criteria.

This article is a practical UX checklist: scope, exemptions, the requirements that most often fail, documentation and testing. National implementations differ in details and enforcement, so check the rules in each country where you sell. This is not legal advice.

Who is covered by the European Accessibility Act?

The Act covers specific products and services rather than all websites. For digital teams the most relevant are e-commerce services, consumer banking services, electronic communications services, e-books and their software, access to audiovisual media services, and websites, apps and ticketing for certain passenger transport services. It also applies to businesses outside the EU that offer these services to EU consumers.

Microenterprises providing services, meaning fewer than 10 employees and an annual turnover or balance sheet total not exceeding EUR 2 million, are exempt from the service requirements. There are transitional provisions, for example for service contracts concluded before June 2025, and a disproportionate burden exception that must be assessed and documented. Do not assume an exemption applies without checking it carefully.

Which accessibility requirements fail most often?

In UX reviews of shops and service apps, the same issues recur. They are usually cheap to fix once found:

Also check native mobile apps, not only the website. Apps that are part of a covered service fall under the same requirements, and platform components such as custom tab bars or gesture-only interactions frequently fail screen reader and switch control tests.

  • Insufficient colour contrast for text, icons, placeholder text and focus indicators.
  • Form fields without programmatic labels, unclear error messages or errors shown only in colour.
  • Custom components such as dropdowns, date pickers and modals that cannot be operated by keyboard or screen reader.
  • Missing or meaningless alternative text for product images and icon buttons.
  • Checkout steps with time limits, CAPTCHAs or authentication that rely on memory or puzzles.
  • Cookie banners and chat widgets that trap keyboard focus or hide content.
  • Layouts that break when text is enlarged or the screen is narrow.

What about chatbots and AI assistants?

If a chatbot or AI agent is part of a covered service, for example a shop's support assistant or a banking app's helper, it must be accessible too. Streaming responses must be announced sensibly to screen readers, the input must be labelled and keyboard operable, and conversation history must be navigable.

AI transparency notices under the EU AI Act must also meet accessibility requirements, so the two regimes meet in the same chat window. Our article on WCAG 2.2 for AI products covers chat-specific patterns in detail.

Want an expert opinion on your product?

Talk to a UX expert or AI Code Engineer — 30 minutes, free, no obligation.

Book a call for free

What documentation do you need?

Service providers must provide information on how the service meets the accessibility requirements, commonly published as an accessibility statement, and keep it available for as long as the service is offered. A good statement describes the service, the standard applied, known limitations with planned fixes, and a way to report barriers.

Internally, keep audit reports, test results, remediation tickets and any disproportionate burden assessment. Market surveillance authorities can request information, and consumer organisations may act on complaints, depending on national law.

Make the feedback channel itself accessible and monitored. A reporting form that fails keyboard navigation, or an inbox nobody reads, undermines the statement and tends to turn frustrated users into formal complaints.

European Accessibility Act UX checklist

Automated scanners catch only part of the problems. Combine them with manual expert review and, where possible, testing with disabled users. Our article on AI tools for accessibility testing explains where automation helps and where it misleads.

  1. Confirm whether your services fall under the Act in each EU market and document the reasoning.
  2. Audit key journeys against WCAG 2.1 AA via EN 301 549, and consider the newer WCAG 2.2 criteria as well.
  3. Fix blockers in critical flows first: navigation, search, product pages, cart, checkout, login and account.
  4. Test with keyboard only, a screen reader on desktop and mobile, 200 percent zoom and reduced motion settings.
  5. Check third-party components: payment, cookie consent, chat, maps and video players.
  6. Publish an accessibility statement with a working feedback channel.
  7. Add accessibility checks to design reviews, definition of done and regression testing.

Why is accessibility good business, not just compliance?

Accessible flows are usually clearer flows for everyone: better labels, readable contrast, forgiving forms and predictable navigation reduce errors and abandonment across all users. Accessibility fixes often overlap with conversion improvements found in a website UX audit.

Treat the Act as a forcing function to fix long-standing usability debt. Teams that build accessibility into components and design systems stop paying for the same fixes over and over.

Frequently asked questions

Does the Act apply to B2B software?

The Act focuses on products and services for consumers. Pure B2B services are generally outside its scope, but public procurement rules and customer requirements often demand accessibility anyway.

Is WCAG 2.2 required?

EN 301 549 references WCAG 2.1 AA as of late 2026. WCAG 2.2 adds useful criteria, and future updates to the standard may reference it, so implementing 2.2 is a sensible way to stay ahead.

What happens if we do not comply?

Enforcement and penalties are set by each member state and vary. Consequences can include orders to fix issues, fines and restrictions on offering the service. Check the rules in your markets.

Can UXreviewer.io audit our accessibility?

Our UX audits include accessibility findings in key journeys with commented screenshots and concrete fixes, delivered within 10 business days. See pricing or book a free call.

Book a call for free

From UX audits and Agentic UX reviews to AI development, agentic coding workshops and publishing your AI-built app on the App Store and Google Play — we help you ship. 24/7 call support in English and German.

Related insights