1.2.2 Captions (Prerecorded) – (Level A)
High-Level Description
This criterion requires captions for all pre-recorded audio content in media. Captions are essential for deaf and hard of hearing users to access dialogue, sound effects, speaker identification, and other auditory information.
Captions must be:
- Synchronised with the audio.
- Equivalent in meaning and not just summaries.
- Available whenever pre-recorded video includes spoken content.
Detailed Description
1.2.2 applies to:
- Pre-recorded videos that include speech or other audio.
- All multimedia that combines video and sound, including the below:
- Product demonstrates
- Training content
- Interviews
- Video testimonials
- Screencasts with narration
- Talking-head videos
Requirements:
- Open or closed captions, they can toggled or burned in.
- Include non-speech information such as music, sound effects, speaker tone, laughter, etc.
- Reflect all spoken dialogue word-for-word.
Does Not Apply To:
- Audio-only media
- Live video excluding audio
- Media with no audio
Indicators of Non-Compliance:
- Video has no captions or uses automatic captions only - without human review.
- Captions do not match spoken content – incomplete captions, missing, or out of sync.
- Captions do not include non-verbal sounds – laughter, explosions etc.
- Captions cover only part of the video - intro only.
- Captions are embedded in a way that screen readers cannot access - burned-in captions in a player that doesn’t support them programmatically.
Real World Examples and Scenarios
Scenario | Example |
---|---|
Corporate Training Video A software onboarding video includes narration and sound cues. | Synchronised captions appear onscreen: "Welcome to the dashboard overview. [soft music fades]" |
Interview Clip A customer testimonial video features two speakers. | Captions identify speakers and include pauses and tone: [Rachel]: "I didn't expect it to be that easy." [Tom - laughing]: "Yeah, I was shocked too!" |
Product Showcase A marketing video explains features with voiceover. | Captions ensure deaf viewers understand each feature discussed and hear [background music] and [ding] cues when new features are revealed. |
Disability Impact (Examples)
Disability Group | Barrier Without Compliance | Benefit With Compliance |
---|---|---|
Deaf/Hard of Hearing | Misses all spoken content, cannot follow dialogue | Full comprehension of content through captions. |
Deafblind | Can read captions via braille display | Accesses both speech and non-verbal sound info |
Neurodivergence | May struggle with auditory processing | Captions support clarity and reduce overload |
Cognitive Disabilities | Supports multi-modal learning and focus | Helps users follow structured, visual format |
Supporting Documentation
- WCAG 2.2 Success Criterion 1.2.2 - Captions (Prerecorded)
- W3C Technique G87 - Providing closed captions
Remediation Strategies with Code Examples
1 - Use < track > for captions in HTML5 video
< video controls > < source src="training.mp4" type="video/mp4" > < track src="training-en.vtt" kind="captions" srclang="en" label="English captions" default > < /video >
2 - Ensure captions include:
- All spoken dialogue.
- Non-verbal audio cues - applause, sound effects.
- Speaker identification, especially if offscreen or multiple speakers.
3 - Review auto-captions manually
Never rely solely on auto-generated captions. They must be edited for accuracy, timing, and completeness.
4 - Support multiple languages
Offer captions in multiple languages if your audience is multilingual:
< track src="training-fr.vtt" kind="captions" srclang="fr" label="Français" >