The 2025 TestParty Guide to WCAG 1.2.2 – Captions (Prerecorded) (Level A)

Why did the video player go to therapy? Because it had trouble expressing itself to deaf users—turns out it just needed captions to communicate better!

WCAG 1.2.2 requires captions for all prerecorded video content with audio. This Level A criterion ensures that people who are deaf or hard of hearing can access the same information as hearing users. Without captions, you're excluding millions of users and risking legal action under the ADA, Section 508, and similar laws worldwide.

Table of Contents

• What WCAG 1.2.2 Requires
• Why This Matters
• Quick Implementation Guide
• Common Mistakes to Avoid
• How to Test for WCAG 1.2.2
• How TestParty Helps
• FAQs

What WCAG 1.2.2 Requires

WCAG 1.2.2 mandates that all prerecorded audio content in synchronized media (video with sound) must include captions. Captions are text alternatives that display dialogue, identify speakers, and describe important sound effects.

Key requirements:

• All dialogue must be captioned, including off-screen speech
• Speaker identification when multiple people speak or the speaker isn't visible
• Sound effects that are important to understanding the content (door slams, phone rings, ominous music)
• Synchronization with the audio—captions must appear at the right time
• Accuracy—captions should match spoken content without significant omissions

Important exceptions:

• Media that is itself a text alternative (e.g., a video showing someone reading an article aloud) doesn't need captions if it's clearly labeled as an alternative
• Live content is covered by a different criterion (1.2.4)
• Audio-only content (podcasts without video) is covered by 1.2.1

What's affected:

• Marketing and product videos
• Training and educational content
• Webinars and recorded presentations
• Social media video embeds
• Video backgrounds with meaningful audio
• Tutorial and demo videos

Why This Matters

Over 37 million American adults report some degree of hearing loss. Captions aren't just for people who are deaf—they help users in noisy environments, non-native speakers, people with auditory processing disorders, and anyone who prefers to read along.

From a legal perspective, WCAG 1.2.2 is a Level A requirement—the baseline for accessibility compliance. The ADA requires public accommodations and state/local governments to provide equal access to digital content. Section 508 mandates captions for federal agencies. EN 301 549 and the European Accessibility Act include identical requirements for EU organizations. High-profile lawsuits against universities, retailers, and streaming services have resulted in settlements requiring comprehensive captioning.

The business case is straightforward: captioned videos have higher engagement, better SEO (search engines index caption files), and reach a broader audience. Studies show that 80% of people who use captions aren't deaf or hard of hearing—they're multitasking, watching without sound, or learning a new language.

Quick Implementation Guide

1. Generate accurate captions

Use professional captioning services for important content. Automated speech recognition (ASR) from YouTube, Rev, or Otter.ai can work for drafts, but always review and correct errors—especially for technical terms, names, and accents.

2. Choose open or closed captions

• Closed captions can be toggled on/off by users (most common, more flexible)
• Open captions are burned into the video and always visible (use when the player doesn't support closed captions)

3. Use WebVTT or SRT format

WebVTT is the web standard for HTML5 video. Here's a basic example:

<video controls>
  <source src="product-demo.mp4" type="video/mp4">
  <track kind="captions" src="product-demo.vtt" srclang="en" label="English" default>
  Your browser does not support the video tag.
</video>

And the corresponding product-demo.vtt file:

WEBVTT

00:00:00.000 --> 00:00:03.500
Welcome to our product demo.

00:00:03.500 --> 00:00:07.000
[upbeat music plays]

00:00:07.000 --> 00:00:11.200
First, let's look at the dashboard interface.

4. Include speaker identification and sound effects

When multiple people speak, prefix captions with names or roles. Describe sound effects in brackets: [door slams], [phone vibrates], [applause].

5. Ensure synchronization

Captions should appear within 0.5 seconds of the audio. Break long sentences into multiple caption frames so users have time to read.

Key techniques: G93 (open captions), G87 (closed captions)

Common Mistakes to Avoid

Missing important sound effects

Captions that only include dialogue fail when sound effects convey meaning. If a character hears a noise off-screen and reacts, caption it: [glass breaking in distance].

Auto-generated captions without review

YouTube's auto-captions are a starting point, not a solution. They frequently misinterpret words, miss punctuation, and fail on accents or technical vocabulary. Always review and edit.

Omitting speaker identification

When two or more people are speaking—especially in interviews or panel discussions—users need to know who's talking. Use >> SPEAKER NAME: or similar conventions.

Providing video without captions when it adds new information

If your page has text content and a video that expands on that content with additional details, the video needs captions. You can't claim the video is redundant if it's not.

How to Test for WCAG 1.2.2

Automated checks:

• Scan for <video> and <audio> elements without associated <track> elements
• Detect embedded YouTube, Vimeo, or third-party players without caption options enabled
• Flag videos without caption files in common formats (VTT, SRT)

Manual review required:

• Watch the video with captions on to verify accuracy and synchronization
• Check that all dialogue is captioned, including off-screen speech
• Verify sound effects that are important to understanding are described
• Confirm speaker identification when multiple people speak
• Test caption controls to ensure users can toggle captions on/off (for closed captions)

Testing checklist:

• [ ] Every prerecorded video with audio has captions available
• [ ] Captions include all dialogue, speaker IDs, and relevant sound effects
• [ ] Captions are synchronized within 0.5 seconds of audio
• [ ] Caption files are properly linked using <track> or player-specific methods
• [ ] Videos that are text alternatives are clearly labeled as such

How TestParty Helps

TestParty automates the detection of missing captions and integrates caption compliance into your development workflow, ensuring that every video meets WCAG 1.2.2 before it reaches production.

What TestParty detects:

TestParty's automated scanning analyzes your site's DOM and source code to identify:

• <video> and <audio> elements lacking <track kind="captions"> child elements
• Embedded third-party video players (YouTube, Vimeo, Wistia, etc.) without caption tracks enabled or available
• Videos with caption tracks that aren't set to a valid language (srclang attribute missing or incorrect)
• Missing default attribute on caption tracks, which can prevent captions from displaying automatically for users who need them
• Video content added dynamically via JavaScript that bypasses caption requirements

TestParty flags these issues at the page and component level, providing line-specific annotations in your codebase so developers know exactly where captions are missing.

How TestParty suggests fixes:

For videos hosted directly on your site, TestParty generates code-level remediation suggestions:

• Auto-generated `<track>` elements with proper kind, srclang, and label attributes, ready to insert into your video markup
• Guidance on caption file formats (WebVTT vs. SRT) and where to place them in your project structure
• Integration recommendations for third-party video platforms—TestParty detects your player (YouTube, Vimeo, etc.) and provides platform-specific instructions for enabling captions via embed parameters or API settings

For sites with hundreds of videos, TestParty can analyze video libraries in bulk and generate a prioritized remediation list based on page traffic, user impact, and legal risk.

TestParty also integrates with AI-powered transcription services. When you upload a video without captions, TestParty can route the audio to a transcription API, generate a draft WebVTT file, and flag it for human review. This automation-plus-review workflow dramatically reduces the time required to caption large video libraries.

Developer workflow integration:

TestParty catches missing captions before they go live:

• CI/CD gates block pull requests that introduce new videos without caption tracks, preventing regressions
• Pull request annotations highlight missing <track> elements with suggested fixes directly in GitHub, GitLab, or Bitbucket
• Pre-commit hooks warn developers when video files are added to the repository without corresponding caption files

For content management systems and headless CMS platforms, TestParty integrates at the template and component level. If your video component doesn't enforce caption uploads, TestParty flags the template itself and suggests schema changes to require caption files before publishing.

Ongoing monitoring:

Accessibility isn't a one-time fix. TestParty continuously monitors your site for caption compliance:

• Regression detection: If a developer removes a caption track or a CMS update breaks caption rendering, TestParty alerts your team within hours
• New content scanning: As new videos are published, TestParty automatically checks for captions and adds violations to your dashboard
• Compliance reporting: Generate audit-ready reports showing caption coverage across your entire video library, with timestamps and remediation status for legal and procurement teams

TestParty's dashboard tracks caption compliance over time, showing trends and highlighting pages with the highest risk. For ecommerce sites with product videos, TestParty can prioritize high-traffic product pages to maximize impact.

Because TestParty works at the code and template level—not as a cosmetic overlay—caption fixes are durable and survive CMS updates, theme changes, and content migrations.

Some TestParty features described in this article are currently under development. Visit TestParty.ai to learn more about our current capabilities and roadmap, or book a demo at TestParty.ai/book-a-demo to see TestParty in action.

Disclaimer: Some of this article was generated with Large Language Models (LLMs) and Artificial Intelligence (AI). There may be some errors and we advise you to consult with human professionals for detailed questions.

FAQs About WCAG 1.2.2

What is WCAG 1.2.2 in plain language?

WCAG 1.2.2 requires that all prerecorded videos with audio must have captions. Captions are text that displays what's being said and describes important sounds, so people who are deaf or hard of hearing can understand the content. This is a Level A requirement—the most basic level of accessibility compliance.

Is WCAG 1.2.2 required for ADA compliance?

Yes. The ADA requires that public accommodations (businesses, nonprofits, state and local governments) provide equal access to digital content. Courts have consistently ruled that videos without captions violate the ADA when they prevent people with hearing disabilities from accessing information or services. Federal agencies must also comply under Section 508.

Do YouTube's auto-generated captions meet WCAG 1.2.2?

Not reliably. Auto-generated captions are a helpful starting point, but they often contain errors—especially with technical terms, names, accents, and background noise. WCAG 1.2.2 requires accurate captions. You must review and correct auto-generated captions before they meet compliance standards.

What's the difference between captions and subtitles?

Captions include both dialogue and sound effects, designed for people who can't hear the audio. Subtitles typically only include dialogue and assume the viewer can hear sound effects and music. For WCAG compliance, you need captions, not just subtitles.

Do I need captions if my video has no dialogue?

If the video has meaningful audio—music that sets a mood, sound effects that convey information, or ambient sounds important to understanding—then yes, you should caption those sounds. If the video is purely visual with no meaningful audio (e.g., a silent product showcase with text overlays), captions aren't required under 1.2.2.

Can I use open captions instead of closed captions?

Yes. WCAG 1.2.2 accepts both open captions (burned into the video, always visible) and closed captions (can be toggled on/off). Closed captions are generally preferred because they give users control, but open captions are compliant and useful when your video player doesn't support caption tracks.

How do I add captions to third-party embedded videos?

For YouTube, upload a caption file (SRT or VTT) through YouTube Studio, or edit the auto-generated captions. For Vimeo, upload captions in your video settings. Most platforms support caption uploads—check their documentation. When embedding, ensure captions are enabled by default or easily accessible to users.