Arbitr
Use cases▾
PlatformPricing
Resources▾
Explore
About▾
The company
Book a demo
Home > Regulations > European Accessibility Act (Directive 2019/882)

Directive (EU) 2019/882

The European Accessibility Act

For digital and content teams selling in the EU working out which products and services the European Accessibility Act covers. This page covers what you need to know and ways to avoid running into issues.

What we've seen reported

The European Accessibility Act, Directive (EU) 2019/882, sets common accessibility requirements for listed products and services, including computers, ATMs, e-commerce and consumer banking, with national rules applying from June 28, 2025.1,2

Last updated October 2026 · General information only, not legal advice. Sources.

Who it covers
Manufacturers, importers, distributors and service providers dealing in the products and services it lists, according to its text1
Applies from
June 28, 20251Transposition deadline June 28, 2022; transitional period for some services to June 28, 20301
Region
European Union1

What the rules cover

What the rules ask for

These are the kinds of requirements the European Accessibility Act describes, according to the Directive's text, and who or what each one falls on.1

RequirementWhere it applies
Products placed on the market after June 28, 2025Covered products: computers and operating systems, self-service terminals, phones and other consumer devices, and e-readers.
E-commerce and consumer banking servicesCovered alongside electronic communications, e-books, access to audiovisual media and parts of passenger transport.
Websites and mobile apps that deliver a serviceService providers: made perceivable, operable and understandable, in a consistent way, under Annex I.
Information on how a service meets the requirementsService providers: prepared under Annex V and made public in written and oral formats, including accessible ones.
Product instructions and informationManufacturers: information on use, including instructions and labeling, provided in accessible ways.
Conformity of productsManufacturers: an EU declaration of conformity and the CE marking, after the conformity assessment in Annex IV.
Microenterprises providing servicesExempt from the service accessibility requirements, according to Article 4(5).
Services using products already in useA transitional period to June 28, 2030; self-service terminals may run up to 20 years where member states allow.

Where it goes wrong

Approved once. Then it drifts.

One approved set of product information ends up in many channels, markets and languages. Along the way it gets shortened, translated and reworded, and some versions end up without the warnings or details these rules require.

Approved onceIllustrative example

Heldan Pay accessibility information for the app and online checkout

  • Website · GermanyInformationen zur Barrierefreiheit von App und Checkout "Accessibility information for the app and checkout"
  • App store listing · EUDriftedFeatures listed; accessibility information link removedAccessibility information link missing
  • Help center · FranceInformations sur l'accessibilité du service "Accessibility information for the service"
  • Terms of service · NetherlandsDriftedOlder terms reused; accessibility section droppedAccessibility section missing
  • Campaign · SpainPago accesible con lector de pantalla "Accessible checkout with a screen reader"
  • Social · ItalyInformazioni sull'accessibilità nel link "Accessibility information in the link"

How Arbitr helps

So how do you stay on top of accessibility wording in every market and language you publish in?

Read every version by hand? Or use AI to check what you publish against what you've already approved.

Check everything manually?

  • Too much to check. Too many channels, versions and translations to cover every market.
  • Drift goes unseen. Nothing tells you when a version moves away from the approved product information.
  • Changes mean starting over. When your rules or approved wording change, everything live has to be checked again by hand.

Let Arbitr do it for you

  • Scan what's live. Go through every live version, in every language, against your approved rules, and find every listing, help page and terms document where your approved accessibility wording is missing or out of date.
  • See what needs attention. Get a clear report of anything that might have moved away from what was approved.
  • Check what comes next. Check everything new against what you approved, across every channel, market and language, before it goes live.

Approve once. Apply everywhere.

FAQ

Questions about the European Accessibility Act

For your teams
Where does European Accessibility Act information turn up in our content?

Wherever a covered service describes itself. Article 13 of the European Accessibility Act asks service providers to explain how their services meet the accessibility requirements and make that information public,1 and we usually find it in:

  • accessibility pages and statements
  • terms of service and help centers
  • app store listings
  • checkout and account pages
  • translated versions for each EU market
How can accessibility information stay current after each release?

Give it an owner and a version, like any approved content. The Directive's text describes procedures so that changes to the service, the requirements or the standards are taken into account,1 and old wording tends to survive in app stores and translated help pages. Arbitr checks that wording against what you approved, not design choices such as color contrast or font size. Our content checks page shows how.

Which teams publish what the European Accessibility Act describes?

More than product and engineering. Content, e-commerce, legal, customer service and localization teams all publish what customers read about a service, in every market. A short briefing for each helps. Related rules are on our accessibility hub, including ADA website accessibility for teams also selling in the US.

What should we record for each accessibility information page?

Keep one record per service and market: the approved wording, the service version and standards it refers to, who approved it, and every place and language it's published. When a market surveillance authority asks for information, as Article 13 describes, you can show each version and where it ran.

How it applies to a specific page is a question for your legal adviser. Where that page appears across your markets and languages is a question Arbitr answers.

About the rules
When did the European Accessibility Act start to apply?

Member states were to adopt their national rules by June 28, 2022 and apply them from June 28, 2025, according to Article 31. The Directive itself entered into force on June 27, 2019.1,2

How does the European Accessibility Act treat microenterprises?

According to Article 4(5), microenterprises providing services are exempt from the service accessibility requirements. The Directive describes a microenterprise as one with fewer than 10 employees and annual turnover or balance sheet of no more than EUR 2 million.1

Is the European Accessibility Act the same as the Web Accessibility Directive?

They're separate EU directives. The Web Accessibility Directive, Directive (EU) 2016/2102, covers public sector websites and apps, while the European Accessibility Act covers the products and services it lists, according to its text.1

About Arbitr
What happens when our approved wording changes?

You update the approved version once. Arbitr checks what's already live against it and shows you every version still using the old wording.