Making Product Videos Accessible: Captions, Transcripts, and Audio Description
Product-demo clips, unboxing footage, size-guide walkthroughs, and looping hero videos are now a routine part of e-commerce product pages — dropped in through a native <video> tag, a YouTube or Vimeo embed, or a reviews platform’s UGC widget. Video gets built and reviewed the same way images used to be: for how it looks, not for whether the information in it reaches everyone who can’t see it, can’t hear it, or can’t do both.
Quick answer: WCAG 2.1 AA governs video through four success criteria that e-commerce product videos routinely trip: SC 1.2.2 Captions (Prerecorded) (Level A) requires synchronized captions for any video with a soundtrack; SC 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) requires a text alternative for silent, narration-free videos that convey information; SC 1.2.5 Audio Description (Prerecorded) (Level AA) requires narrated description of visual content the existing audio doesn’t already cover; and SC 1.4.2 Audio Control (Level A) requires a way to pause or mute any video whose audio autoplays for more than three seconds.
This article covers technical accessibility practice, not legal advice — it explains what WCAG 2.1 AA requires for video and audio content and how to meet it, not whether a specific implementation carries legal risk.
The video types a typical product page mixes together
Not every video on a PDP has the same accessibility obligations, because they don’t all carry the same kind of information:
- Narrated demo or size-guide videos — a voice explaining features, measurements, or how to use the product. These carry a soundtrack, so captions apply.
- Silent, looping hero or feature videos — a product rotating, fabric moving, a close-up with no dialogue. No soundtrack to caption, but they can still fail if they show something a blind visitor can’t otherwise learn from the page.
- UGC or unboxing videos embedded from a reviews platform — the same criteria apply to embedded third-party video as to anything hosted natively; the source doesn’t change the requirement.
Captions cover anyone who can’t hear the soundtrack
SC 1.2.2 requires synchronized captions for prerecorded video that has an audio track — not just spoken words, but meaningful non-speech sound too (a snap-closure click, a motor whirring). The one real exception: if a video is “an alternative to text and is clearly labeled as such,” and duplicates content already on the page as text, captions aren’t required. A narrated size-guide video that says things the page’s size chart doesn’t already say in text needs captions; it isn’t covered just because a size chart exists elsewhere on the page.
Captions are most commonly delivered as a WebVTT file, referenced from a native <video> element with a <track> tag:
<video controls>
<source src="tripod-setup-demo.mp4" type="video/mp4">
<track kind="captions" srclang="en" label="English" src="tripod-setup-demo.en.vtt" default>
</video>WEBVTT
00:00:00.000 --> 00:00:03.500
Unfold both tripod legs until they click into place.
00:00:03.500 --> 00:00:07.000
[metallic click] Then twist the center column to lock the height.Most video hosts (YouTube, Vimeo) and native HTML5 video both support uploading a WebVTT or SRT caption file directly. Auto-generated captions from a hosting platform are a starting point, not a finished product — W3C’s own guidance on captioning notes it’s “more art than science” deciding which non-speech sounds to include, and automatic speech recognition routinely mishears product names, model numbers, and technical terms that a generic language model wasn’t trained on. Review and correct auto-captions before publishing rather than trusting them as-is.
Silent videos aren’t automatically exempt (SC 1.2.1)
A looping hero video with no soundtrack has nothing to caption, but that doesn’t mean it’s automatically accessible. SC 1.2.1 requires prerecorded video-only content to have a text alternative — or an added audio track — when it conveys information not already available elsewhere on the page.
The distinction that matters in practice: a 360°-spin product video that shows the same product from angles a static image gallery already covers doesn’t need a separate alternative, since the information is duplicated elsewhere. A silent video demonstrating an assembly sequence — “unfold, then twist, then lock” — with no equivalent text on the page does need one, because a blind visitor has no other way to learn those steps. A short line of alt text on the video’s container, or a text list of the same steps shown in the clip, satisfies this without re-shooting anything.
Audio description covers what the soundtrack leaves out (SC 1.2.5)
SC 1.2.5, a Level AA requirement, applies when a video’s existing soundtrack doesn’t describe everything a sighted viewer would understand from watching it — an on-screen measurement overlay, a size comparison shown visually rather than said aloud, a demonstration step performed silently while background music plays. The fix isn’t always a separate audio track: if the visual information gets folded into the narration script itself (“here you can see the strap adjusts to three lengths — small, medium, and large”), no additional audio description is needed, because the primary audio already conveys it. A separate, timed audio-description track — inserted into natural pauses in the existing audio — is the fallback when a video can’t be re-narrated.
Don’t forget audio that autoplays (SC 1.4.2)
Most hero and background product videos autoplay muted by default, which sidesteps this criterion entirely. But SC 1.4.2, Level A, requires a pause/stop control or independent volume control for any video whose audio autoplays for more than three seconds. If a hero video, a flash-sale banner, or an embedded player is set to autoplay with sound on, add a visible, keyboard-operable mute or pause control — competing with screen-reader speech output is disorienting for anyone using one, not just a rare edge case.
Transcripts are the flexible option
A full text transcript alongside a video — not a substitute for captions on videos with dialogue, but a useful companion — serves people who prefer reading, gives search engines crawlable text a video file alone doesn’t provide, and gives an AI answer engine quotable, structured text to pull from when summarizing what the video covers. W3C WAI’s transcribing guidance treats a transcript as a distinct deliverable from captions, not an automatic byproduct of having them.
FAQ
Do auto-generated captions from YouTube or Vimeo satisfy SC 1.2.2? Only once reviewed and corrected. Uncorrected automatic captions routinely misrecognize product names and technical terms, and WCAG requires captions to accurately represent the audio content, not merely attempt to.
Does a silent, looping hero video ever need nothing at all? Yes — if it’s purely decorative or duplicates information already available as text or images elsewhere on the page, SC 1.2.1 doesn’t require an additional alternative.
Do these rules change for video embedded from a third-party platform? No. The success criteria apply to the content a visitor experiences on your page regardless of where the video file is hosted — a YouTube or Vimeo embed still needs captions uploaded and, where applicable, a text alternative or audio description.
Video is one more thing a manual review checks that a scan usually can’t
Automated scanners can flag a <video> element with no <track> tag, but they can’t judge whether captions are accurate, whether a silent video conveys unique information, or whether an audio-description script actually covers what’s on screen — all judgment calls that need a person watching the video, not just crawling the markup around it. A full Quietramp audit includes that manual review across your whole site. See a real sample report, or check pricing — $890 one-time, $99/month for ongoing re-checks after fixes ship.
This is educational content about technical accessibility standards, not legal advice. Meeting WCAG 2.1 AA does not guarantee legal compliance with the ADA or any other law, and nothing here should be read as a compliance guarantee. Consult qualified counsel for legal risk questions.
This article was drafted with AI assistance and reviewed by a person for accuracy before publication.