EAA video accessibility — audit, backlog and compliance requirements
Most organisations don't have a single video to fix. They have a backlog. Under EN 301 549, video content in scope of the EAA requires captions, audio description, and transcripts. Here is what that means in practice and where to start.
What the EAA requires for video content
The EAA requires digital products and services to meet EN 301 549, the harmonised European technical standard. For video content, EN 301 549 maps to WCAG 2.1 Level AA, which sets four specific requirements for pre-recorded video:
Captions for pre-recorded audio content
Accurate, synchronised captions covering spoken dialogue, relevant sound effects, and non-speech audio cues. Captions go beyond subtitles: they include everything a deaf or hard-of-hearing user needs to understand what is happening in the audio track, not just what is being said.
Audio description for pre-recorded video
Narration describing visual information that is not conveyed in the existing audio. A product demo that shows a user clicking through a flow, a tutorial that relies on screen visuals, a training video where the presenter points to something on a slide: all of these require audio description for blind or visually impaired users to follow the content.
Transcript or text alternative
A text version of the audio content, including spoken words and relevant non-speech audio. Transcripts serve users who cannot or prefer not to watch video at all, and also serve search engines and assistive technologies that read text.
Accessible video player
The player itself must be keyboard-navigable and compatible with assistive technologies. A video with perfect captions published in a player that cannot be operated without a mouse fails the requirement. The player controls, caption toggle, and playback functions must all be reachable and operable without a mouse.
Why this matters beyond the EAA
Video accessibility is not only a compliance question. Independent of what any regulation requires, in whichever market you operate, inaccessible video content is closing the door on real viewers who want to watch it.
Audio description is the clearest example. Imagine a blind shopper close to buying a product from your site. The product page has a thirty-second video showing how it works, with background music but no narration explaining what is happening on screen. Sighted shoppers watch and immediately understand the size, the texture, how it fits together. The blind shopper hears music and nothing else. They cannot tell if this product actually does what they need. They close the tab and buy the same kind of product from a competitor whose listing includes a description they can actually use.
Captions serve a similarly broad audience for different reasons. They are the only way a deaf or hard-of-hearing viewer can access the audio track at all. They also serve the much larger group of viewers who watch video with the sound off, whether by preference, by platform default, or because sound is not an option in the environment they are in. Captioned video reaches viewers that uncaptioned video does not, for reasons that have nothing to do with any regulation.
Transcripts extend the same content to viewers who prefer reading to watching, and to the search engines that determine whether your video is found at all.
None of this depends on EAA applicability. An organisation with no EU consumer exposure whatsoever still has viewers who cannot access unlabelled, uncaptioned, undescribed video content, for the same reasons an EU-exposed organisation does. The compliance requirement and the audience-reach argument point in the same direction, whether or not the law is the reason you are reading this.
Why video is a common gap even in otherwise-compliant products
Video is often produced outside the core development and design workflow. It is created by marketing teams, filmed by external agencies, or pulled from product recordings. Unlike a button label or a form field, it does not go through a standard development review before publication. By the time a video is live on your site, it has typically passed through several teams, none of whom had accessibility in their checklist.
The result is that organisations which have made significant progress on their core product accessibility frequently have an entirely separate video accessibility problem sitting unaddressed on the same domain. A checkout flow that is keyboard-navigable, properly labelled, and screen-reader-friendly can exist on the same website as a product demo with no captions, no audio description, and a player that traps keyboard focus.
This is not negligence. It is a structural gap in how video content is typically commissioned, reviewed, and published. The fix requires bringing video into the same accessibility governance process as the rest of the product.
The backlog problem: where to start
Most organisations that have been publishing video content for any significant time are not dealing with one new video to make accessible. They are dealing with a library: product demos, onboarding videos, tutorial series, marketing explainers, recorded webinars, support content. The question is not "is this video accessible." It is "where do we even start."
The answer is prioritisation, not paralysis. A structured approach works as follows:
- Highest-traffic video first. Start with the videos that appear on your most-visited pages. These reach the most users, generate the most revenue-relevant journeys, and represent the highest enforcement exposure.
- Journey-critical video second. Any video embedded in a core user journey, such as onboarding flows, checkout processes, account setup, or support escalation paths, carries higher risk than a background marketing video on a homepage. A user who cannot access an onboarding video may not be able to use the product at all.
- Legally prominent content third. Terms and conditions videos, safety information, product documentation: content where the information itself has legal or contractual significance.
- Long tail last. Archive content, seasonal campaigns, older tutorial series: address these after the high-priority content is resolved. A documented, in-progress remediation plan for the long tail is a defensible compliance position. An entirely unaddressed backlog is not.
A documented, in-progress backlog is a defensible compliance position. An unaddressed one is not. The difference is not how many videos are captioned: it is whether there is a documented process for addressing them and evidence that it is active.
Which videos are actually in scope
The EAA's scope for video content is specific and worth understanding precisely before building a remediation plan:
| Content type | Status | Note |
|---|---|---|
| Video published after 28 June 2025 | In scope | Must comply. No exemption. |
| Pre-2025 video, unmodified since 28 June 2025 | Exempt | Exempt as pre-existing content under the EAA. No requirement to remediate unless the content is updated. |
| Pre-2025 video, modified or republished after 28 June 2025 | In scope | The update triggers the compliance requirement. Any version published or updated after the deadline must comply. |
| Pre-2025 video on audiovisual media services (streaming, broadcasting) | Transitional | Article 32 grants audiovisual media services until 2030 for pre-2025 backlog content. This applies to streaming platforms and broadcasters, not to general e-commerce or product websites. |
The practical implication: for most organisations in scope of the EAA through e-commerce, FinTech, SaaS, travel, or telecoms, the backlog is everything published since 28 June 2025, plus any pre-2025 video that has been updated or republished since that date. If your team regularly refreshes or republishes older video content, that content is in scope the moment it is touched.
The first step is knowing what you have. Most organisations have not counted their in-scope video content. That count is the starting point for any prioritisation exercise, and most teams have not done it yet. The number is usually larger than expected.
Tools and solutions for EAA video compliance
Several categories of tool support video accessibility compliance. The right choice depends on the volume of content, the languages required, and whether new production or backlog remediation is the priority.
Automated captioning. AI-generated captions (from tools such as Descript, Otter.ai, or platform-native tools on YouTube or Vimeo) provide a starting point but require human review. Accuracy varies significantly by accent, technical vocabulary, and audio quality. Automated captions that have not been reviewed should not be published as the compliance solution: errors in captions can be worse than no captions for users relying on them.
Human captioning services. Professional captioning services (such as 3Play Media, Rev, or Verbit) produce higher-accuracy output, particularly for technical content, multiple speakers, and non-native English. For high-priority content, human-reviewed captions are the appropriate standard.
Audio description services. Audio description requires scripting and often re-recording, which makes it more resource-intensive than captioning. For large backlogs, prioritise audio description for videos where visual information is essential to understanding the content. Background videos, animations without substantive visual information, and videos that are fully described in surrounding text may have a lower priority.
Accessible video players. If your current video player is not keyboard-navigable or does not support caption toggling, player replacement is a prerequisite. Plyr, Video.js, and native HTML5 players with appropriate controls are common accessible alternatives. Test any player with keyboard-only navigation and with a screen reader before publishing.
For organisations with large backlogs, a phased approach is more realistic than attempting full compliance simultaneously. A documented phased plan is a valid compliance position; complete non-compliance with no plan in place is not.
How video compliance fits into the broader audit
The EAA compliance audit guide covers the general methodology for auditing your digital product against EAA requirements across all four compliance requirements: technical conformance, accessibility statement, governance, and documentary evidence. Video is one component of technical conformance, not a separate compliance track.
For the video-specific questions (how to audit existing video content, how to generate a captioning checklist for your library, how to test an accessible player), this page provides the video-specific guidance. For the broader audit question across your full product, the audit guide covers the complete methodology.
Find out where your video content stands
Our free initial assessment covers your current compliance position, including whether video content is likely creating exposure for your organisation, and what a proportionate next step looks like.
Book your free assessment today