Resources

WCAG Fix It: 1.2.2 Captions (Prerecorded)

 

Table of Contents


Free Audit

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 screenm 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
  • Users miss sound cues (like alarms, laughter, transitions)
  • Users lose context entirely

Having no caption is a barrier to comprehension and equal access.

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.

This includes:

  • Instructional tutorials
  • Interviews
  • Product demonstrations
  • Testimonials
  • Explainer videos
  • Screencasts with narration

If the media is only visual or has no essential audio information, captions are not required — but document it clearly.

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

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:

  • 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:

  • 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

  • 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 Frequently Asked Questions

What is WCAG 1.2.2 Captions (Prerecorded)?

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.

Are subtitles the same as captions?

Not exactly. Subtitles may only include dialogue, while captions must include dialogue, speaker information, and relevant non-speech sounds.

Do autogenerated captions count?

Autogenerated captions are a useful starting point, but to meet WCAG 1.2.2 they should be reviewed and corrected for accuracy.

What if my video has no audio?

If the video has no essential audio information, captions are not required. But you should still clearly label such media.

Related Content

WCAG Fix It: 4.1.2 Name, Role, Value

If your website has buttons, forms, menus, dropdowns, or interactive components, WCAG 4.1.2 applies to you. In this WCAG Fix It guide, we’re breaking down one of the most technical-sounding, yet critically important accessibility requirements: ensuring that interactive elements have a proper, programmatically defined name, role, and value. It sounds developer-heavy burut at its core,

Read more: WCAG Fix It: 4.1.2 Name, Role, Value

WCAG Fix It: 3.3.2 Labels or Instructions

If your website has forms, contact forms, checkout forms, booking forms, login forms, WCAG 3.3.2 applies to you. In this WCAG Fix It guide, we’re breaking down one of the most common and preventable accessibility failures: missing labels or unclear instructions. When users don’t know what information is expected in a field, forms become frustrating,

Read more: WCAG Fix It: 3.3.2 Labels or Instructions

WCAG Fix It: 3.1.1 Language of Page

If your website has text and they all do, WCAG 3.1.1 – Language of Page applies to you. In this WCAG Fix It guide, we’re breaking down a technical requirement that has a huge impact on accessibility: ensuring the primary language of your web page can be programmatically determined. It’s one line of code, but

Read more: WCAG Fix It: 3.1.1 Language of Page