- Level
- A
- Since
- WCAG 2.0
1.2.2 Captions (Prerecorded)
A prerecorded video with sound needs captions that carry what is said and the sounds needed to follow it.
/ What it requires
Every prerecorded video with sound needs captions: text synchronised with the picture that carries the spoken words and the sounds needed to follow the content. Real captions identify who is speaking when that is not obvious and note sounds that matter, such as music, an alarm or laughter. They can be closed, switched on in the player, or open, burned into the picture. Captions exist for people who are deaf or hard of hearing, and they are used just as much by people watching without sound.
The words may be lightly condensed so they can be read in time, which is normal practice, but dialogue cannot be dropped and important sounds cannot be left out. The criterion has one exception: a video that only repeats text already on the page, and is clearly labelled as an alternative to that text, does not need captions. If such a video adds information the text does not have, the exception no longer applies. Live video is covered by 1.2.4.
/ How pages fail it
- A product video with a voice-over is embedded on the page with no captions track and no captions in the picture.
- The player offers captions, but they are uncorrected automatic ones that misname the product and skip whole sentences.
- The captions carry the dialogue and leave out the sounds the story depends on, such as the doorbell that starts the next scene.
- Captions run for the first minutes of a training film and stop before the film does.
- A video that is meant to repeat a page of instructions adds new tips of its own, has no captions, and is not labelled as an alternative to the text.
/ How to check it yourself
- Find every video with sound: native video elements, embedded YouTube or Vimeo players, and video hidden in carousels, tabs and dialogs.
- Open the player controls and turn captions on. If there is no captions control and no text burned into the picture, the video fails, unless it is a labelled alternative to text on the page.
- Watch with the sound off, then again with it on. Check that all dialogue is there, that speakers are identified where it is not obvious, and that important sounds are noted.
- Skip to the middle and the end of the video. Captions that start well and stop halfway are a common fault.
- For a native player, inspect the video element in the developer tools, find the track element and open its src address to confirm the caption file actually loads.
/ How to fix it
- Add a track element inside the video element: <track kind="captions" src="film.en.vtt" srclang="en" label="English">, pointing at a WebVTT file.
- Read automatic captions line by line before publishing and correct names, numbers and punctuation.
- Write sound cues in brackets, such as [door slams] or [music stops], and name a speaker who talks off screen.
- On YouTube or Vimeo, upload a corrected caption file in the video's caption settings instead of relying on the automatic track.
- Where a video only repeats text on the page, label it as such and keep anything new out of it, or caption it like any other video.
/ What our scanner checks
Nothing in our scan reports against 1.2.2. Whether a video has captions at all can sometimes be read from the markup, but whether they carry every line of dialogue and the sounds that matter can only be found by playing the video with captions on. Embedded players from YouTube or Vimeo keep their caption tracks on the platform, out of reach of a page scan. Each video is watched in a manual audit.
/ Who fails it, in our own measurements
The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Are YouTube automatic captions enough for WCAG?
Not as they come. Automatic captions are held to the same test as any others: all of the dialogue and all of the important sounds. W3C lists captions that omit dialogue or important sound effects as a failure of 1.2.2. Automatic captions that someone has read and corrected can pass. Unchecked ones pass only if they happen to be complete and accurate, and nobody knows that until a person checks.
What is the difference between captions and subtitles?
Captions carry the dialogue and the sound information a viewer who cannot hear needs: sound effects, music, laughter and who is speaking. Subtitles in the narrow sense translate or transcribe the dialogue only. W3C notes that in some countries captions are called subtitles, so the name does not matter. What counts is whether the sounds are in the text.
Does every video on a website need captions?
Every prerecorded video with sound does, at level A, with one exception: a video that only repeats text already on the page and is clearly labelled as an alternative to it. A video with no audio at all falls under 1.2.1 instead, and live video falls under 1.2.4 Captions (Live), which is level AA.
