If your website features videos or other prerecorded media that include audio, WCAG 1.2.2 applies to you.
In this WCAG Fix It guide, we’re breaking down a core accessibility requirement: providing captions for prerecorded multimedia content.
It sounds simple, just text on the screen, but it has an enormous impact on accessibility and usability. Fixing it ensures your videos are truly accessible to everyone who visits your site.
What Is WCAG 1.2.2?
WCAG 1.2.2 – Captions (Prerecorded) requires that captions are provided for all prerecorded audio content in synchronized media, except when the media is a clearly labelled text alternative.
In plain English, if your video has spoken words, narration, sound effects, or other non-visual audio, you must include captions that cover it all.
This is a Level A requirement, meaning it’s a fundamental accessibility barrier if missed.
What Are Captions?
Captions are a text alternative for audio content that appears on screen and in sync with the media.
They include:
- Spoken dialogue
- Sound effects that convey meaning
- Speaker identity (e.g., “Narrator:” or “John:”)
- Other auditory cues essential to understanding the content
Unlike simple subtitles (which may only show dialogue or translate language), captions must communicate all relevant audio information needed to comprehend what’s being said or heard.
The Human Impact of Missing Captions
Consider someone who is:
- Deaf or hard of hearing
- Watching in a noise-sensitive environment
- In a public place without sound
- Learning in a second language
- Using captions to reinforce comprehension
Without captions, all spoken content and often critical audio cues are inaccessible.
No captions means users miss dialogue and sound cues (like alarms, laughter, transitions). In some instances, they can even lose context entirely, highlighting the importance of providing accessible captions.
Common WCAG 1.2.2 Failures
Here’s what we typically see when scanning sites:
- Videos without captions
- Auto-generated captions left unedited
- Captions that are out of sync
- Captions that omit sound effect descriptions
- Embedded videos without caption support
All of these fall short of WCAG 1.2.2.
How to Fix Captions (Prerecorded)
Identify What Needs Captions
Any video with audio needs captions, including:
- Instructional tutorials
- Interviews
- Product demonstrations
- Testimonials
- Explainer videos
- Screencasts with narration
There are some exceptions to the rule where captions are not required, including when the media is visual or has no essential audio information.
Create Accurate Captions
Captions must include:
- All speech
- Speaker identification
- Relevant non-speech sounds (e.g., phone ringing, applause, music cues)
Captions should:
- Be synchronized with the media
- Be easy to read
- Stay on screen long enough for comprehension
Mistakes to avoid:
- Using simple subtitles that ignore sound effects
- Auto-generated captions without review
- Captions that lag or lead the video
Good captions are accurate, complete, and well-timed.
Add Captions to Videos
The methods used for adding captions may vary depending on how your video is delivered:
Hosted on Your Website
Use HTML <track> elements:
<video controls>
<source src=”video.mp4″ type=”video/mp4″>
<track kind=”captions” src=”video-captions.vtt” srclang=”en” label=”English captions”>
</video>
Closed captions allow users to turn them on and off.
Embedded Videos
Platforms like YouTube, Vimeo, and other players support captions:
- Upload caption files (e.g., .vtt or .srt)
- Enable captions in the video settings
- Ensure captions are fully edited and synchronized
Automatically generated captions may be a starting point, but they must always be reviewed for accuracy.
How to Test WCAG 1.2.2
After adding captions, you can test for WCAG 1.2.2 compliance by following these simple steps:
- Re-run your accessibility scan
- Play the video with captions on
- Confirm:
- Dialogue appears as text
- Sound effects are included
- Timing matches the audio
If everything is captured correctly and synchronised, you’ve fixed it.
Why WCAG 1.2.2 Matters Beyond Compliance
Providing captions isn’t just important for accessibility compliance. It provides several other benefits, including:
- Makes videos accessible to people who can’t hear sound
- Improves usability in sound-off environments
- Supports language learners and cognitive comprehension
- Helps with SEO when caption text is indexable
- Reduces exclusion and legal risk
WCAG 1.2.2 Quick Fix Checklist
If you’re starting to prioritize accessibility through WCAG 1.2.2 fixes, make sure you follow our checklist:
- All prerecorded videos with audio have captions
- Captions include speech and relevant sound effects
- Captions are synchronized with the media
- Caption text is accurate and readable
- Embedded videos support captions
- Issues re-tested after update
WCAG 1.2.2 Captions FAQs
Looking for a quick recap? Here are answers to some of the most frequently asked questions on this topic:
WCAG 1.2.2 requires captions for all prerecorded audio content in synchronized media to make videos accessible to people who are deaf or hard of hearing.
Not exactly. Subtitles may only include dialogue, while captions must include dialogue, speaker information, and relevant non-speech sounds.
Autogenerated captions are a useful starting point, but to meet WCAG 1.2.2 they should be reviewed and corrected for accuracy.
If the video has no essential audio information, captions are not required. But you should still clearly label such media.