Tutorials Accessibility

The European Accessibility Act: What Media Producers Have to Do

By Infinite Creation · Intermediate · ~14 min

The Short Version

The European Accessibility Act is Directive 2019/882. It sets accessibility requirements for a list of products and services sold in the European Union, and unlike earlier accessibility law it reaches private companies rather than only public bodies. For anyone who publishes video, runs a podcast with a paid tier, sells a course, or ships an app, the relevant parts are e-commerce, e-books and access services for audiovisual media. The obligations began to apply on 28 June 2025. This page sets out who it covers, what standard compliance is measured against, and what the work actually consists of.

Before You Start

Somewhere you sell to, or serve, people in the European Union. Where you are based does not decide this
A list of what you publish: video, audio, e-books, courses, an app, a shop
Access to whatever publishes it, since most of the work happens in a player or a template
A way to test with a keyboard and a screen reader. Every operating system includes one
An honest estimate of your headcount and turnover, because one exemption depends on it

Walkthrough

Work out whether it reaches you

The Act covers a defined list, and the entries that matter to media are e-commerce, e-books and access services for audiovisual media, meaning captions, subtitles, audio description and sign language interpretation. Selling into the EU is what triggers it, not being established there, so a producer outside Europe with European customers is inside its scope. There is an exemption for microenterprises providing services, defined as fewer than ten people and turnover or balance sheet under two million euro. That exemption covers services and not products, and it is worth reading carefully rather than assuming.

Know which standard you will be measured against

The Act states requirements in outcome terms and does not name a technical specification. In practice conformity is assessed against the harmonised European standard EN 301 549, which for anything on the web adopts the Web Content Accessibility Guidelines at level AA. WCAG 2.2 became a W3C Recommendation in December 2024. If you already hold a WCAG 2.2 AA baseline and can show how you test it, most of the web-facing argument is already made.

Caption everything, and caption it properly

Automatic captions are a draft. The Act is concerned with whether a person can actually use the service, and captions that mangle names, run three lines deep or lag the audio fail that test regardless of their word accuracy. Fix the errors, set reading rate and line length so they can be read at speed, and identify speakers where more than one person talks.

Add audio description where the content needs it

Audio description is narration of what is happening on screen for viewers who cannot see it. Not everything needs it: a talking head saying what it is doing needs very little. Anything that shows rather than says, which includes most tutorials with an on-screen demonstration, needs it or needs to be re-narrated so the spoken track carries the information on its own.

Make the player operable, not only the media

An accessible file inside an inaccessible player is not an accessible service. Every control must be reachable and operable from a keyboard, focus must be visible, controls must have names a screen reader can announce, and nothing may depend on a mouse hover. This is where most embedded players fail, and it is worth testing the one you use before assuming.

Remember that the shop counts

E-commerce is named in the Act in its own right. The checkout, the account flow, the pricing table and the emails that follow a purchase are all part of the service. A perfectly captioned course sold through a checkout that cannot be completed with a keyboard is still a non-compliant service.

Publish an accessibility statement that is true

A statement should say what the service does, what it does not yet do, how somebody reports a problem, and when it was last reviewed. Resist the template that claims full conformance. A statement naming two known gaps and a contact address is more credible, more useful, and easier to defend than one claiming perfection.

Keep the evidence

Compliance is a claim you may have to support. Keep the test results, the date, the tool or person that produced them, and what was fixed. An automated checker finds perhaps a third of real problems, so record the manual keyboard and screen reader passes as well. Evidence gathered as you go costs nothing. Evidence reconstructed afterwards costs weeks.

Watch Out For

Test with a keyboard first. It takes ten minutes, needs nothing installed, and finds the failures that matter most in a player.
An automated contrast or caption checker is a filter, not a verdict. It cannot tell you whether a caption makes sense.
Where a third-party player or checkout is the weak point, the obligation is still yours. Ask the vendor for their conformance report before you need it.
Do the accessibility statement early. Writing it forces you to find out what is actually true.

Knowledge Base

What You'll Learn

The Act is short on technical detail by design, so most practical questions resolve to the same three places: what is covered, which standard applies, and what evidence you kept.

Why the Act names outcomes instead of a specification

Reading Directive 2019/882 for a checklist is frustrating, because it does not contain one. It states requirements in terms of what a person must be able to do, and leaves the technical detail to harmonised standards. That is deliberate, and it has one useful consequence and one uncomfortable one. The useful consequence is that the law does not go out of date every time a specification is revised. The uncomfortable one is that meeting the letter of a standard is not automatically the same as meeting the Act, because the test the Act sets is whether somebody can actually use your service. In practice, conformity is assessed against EN 301 549, which adopts the Web Content Accessibility Guidelines at level AA for anything on the web. Holding a WCAG 2.2 AA baseline is therefore most of the argument, and being able to show how you test it is the rest.

Why an automated pass is not the evidence you need

Automated checkers are useful and they are not sufficient. They find contrast failures, missing labels and broken structure, and they are silent on everything that requires judgment. No tool can tell you whether a caption makes sense, whether an audio description conveys what the shot conveys, or whether a keyboard user can get through a checkout without knowing the layout in advance. Industry estimates put the automatically detectable share of real problems at around a third, which is why the evidence worth keeping is a record of the manual passes: who ran the keyboard test, on what date, with what result, and what was fixed. That record costs nothing while you are doing the work and is effectively impossible to reconstruct once somebody has asked for it.

Where This Fits

The Act names the standard, and Publishing Accessible Video turns the conformance levels into a publishing checklist you work through before release.

FAQ

Q: Does the European Accessibility Act apply to me if I am not in the EU?
A: It can. What triggers the Act is placing covered products on the EU market or providing covered services to people in the EU, not where the business is established. A producer selling a course to customers in Europe is inside its scope.

Q: Are automatic captions enough?
A: No. The test is whether somebody can use the service, and automatic captions typically fail on names, technical terms, punctuation and speaker changes. Treat the machine output as a first draft and correct it.

Q: What standard do I actually have to meet?
A: The Act states outcomes rather than naming a specification. In practice conformity is assessed against EN 301 549, which for web content adopts WCAG at level AA. WCAG 2.2 reached Recommendation status in December 2024.

Q: Is there an exemption for very small businesses?
A: There is one for microenterprises providing services, meaning fewer than ten people and turnover or balance sheet under two million euro. It applies to services and not to products, so read it against what you actually do.

Vocabulary

European Accessibility Act Directive 2019/882, which sets accessibility requirements for a defined list of products and services sold in the European Union. Its obligations reach private companies rather than only public bodies, and they began to apply on 28 June 2025.

EN 301 549 The harmonised European standard for accessibility requirements in information and communication technology. It is the specification conformity is assessed against in practice, and for web content it adopts the Web Content Accessibility Guidelines at level AA.

Access service The umbrella term for captions, subtitles, audio description and sign language interpretation provided alongside audiovisual media. The Act treats these as part of the service rather than as optional additions to it.

Microenterprise Fewer than ten people, with annual turnover or a balance sheet total not above two million euro. Microenterprises providing services are exempt from the Act's requirements. The exemption does not extend to products.

Accessibility statement A published description of how accessible a service is, what is known not to work, how to report a problem, and when it was last checked. It is more useful and more defensible when it names real gaps than when it claims full conformance.

Sources

The directive and the accessibility standard were read directly. One date could not be, and this page says which. Checked 26 August 2026.

European Commission, European Accessibility Act. The Commission's own page for the Act. It gives the directive number as 2019/882, the title as a directive on the accessibility requirements for products and services, and the covered list including audiovisual media access, e-books and e-commerce. It also records that member states had to transpose it into national law by June 2022.
W3C, Web Content Accessibility Guidelines (WCAG) 2.2. Published as a W3C Recommendation on 12 December 2024. This is the specification EN 301 549 adopts for web content, so it is what a conformance argument rests on in practice.

The application date of 28 June 2025 is not cited above because it could not be read from an official source. The consolidated text on EUR-Lex returned nothing to an automated request on 26 August 2026, and the ETSI copy of EN 301 549 refused access. The date is consistent across legal and industry accounts, and it is stated here on that basis rather than on a document this page has read. Anyone relying on it for a compliance decision should confirm it against Article 31 of the directive itself.