Accessible Captions & WCAG Compliance: Make Your Videos Inclusive

Why Accessible Captions Are a Legal and Moral Imperative

In 2026, video accessibility is not optional. Over 466 million people worldwide have disabling hearing loss, and hundreds of millions more consume video in sound-off environments. Accessible captions ensure your content reaches everyone, regardless of hearing ability, language fluency, or viewing context.

Beyond ethics, accessibility is increasingly a legal requirement. The Americans with Disabilities Act (ADA), the European Accessibility Act (EAA), and Section 508 of the Rehabilitation Act all mandate accessible media in various contexts. WCAG 2.2 (Web Content Accessibility Guidelines) provides the technical standard that courts and regulators reference.

This guide walks you through creating captions that are both accessible and compliant.

Understanding WCAG 2.2 Requirements for Video

WCAG 2.2 addresses video captions under several success criteria:

1.2.2 Captions (Prerecorded) — Level A

All prerecorded audio content in synchronized media must have captions. This is the baseline requirement. If your website has video with audio, it needs captions.

1.2.4 Captions (Live) — Level AA

Real-time captions must be provided for live audio content. This applies to webinars, live streams, and virtual events.

1.2.3 Audio Description — Level A

An alternative for time-based media or audio description is provided for prerecorded video content. This covers visual information that is not conveyed through audio alone.

1.2.5 Audio Description (Prerecorded) — Level AA

Audio description is provided for all prerecorded video content in synchronized media.

Types of Accessible Captions

Standard Closed Captions (CC)

Closed captions transcribe dialogue and can be toggled on or off by the viewer. They are delivered as separate files (SRT, VTT) alongside the video.

SDH (Subtitles for the Deaf and Hard of Hearing)

SDH goes beyond standard subtitles by including:

• Speaker identification: [NARRATOR] or [DR. SMITH]
• Sound effects: [door slams], [phone ringing]
• Music descriptions: [soft piano music], [upbeat rock song plays]
• Emotional tone: [whispering], [sarcastically]
• Off-screen sounds: [footsteps approaching], [thunder rumbles]

Open Captions

Permanently burned into the video. Cannot be turned off. These are required when the delivery platform does not support closed caption tracks (such as some social media auto-plays).

Best Practices for Accessible Captions

1. Accurate Transcription

Captions must accurately represent the spoken content. This includes:

• All spoken dialogue, word for word
• Relevant non-speech sounds
• Speaker identification when multiple people are talking
• Indication of music or silence

Never paraphrase or summarize dialogue in accessibility captions. Accuracy is the top priority.

2. Proper Synchronization

Captions must appear and disappear in sync with the corresponding audio. WCAG does not specify exact timing tolerances, but industry best practices recommend:

• Captions appear within 100ms of the spoken word
• Minimum display time of 1 second
• Maximum display time of 7 seconds
• Minimum gap of 100ms between consecutive captions

Use SubtitleGen to automatically calculate optimal timing distribution for your video duration.

3. Readability

• Maximum 2 lines per caption
• Maximum 42 characters per line (32 for mobile-optimized content)
• Use mixed case (not ALL CAPS except for emphasis)
• Ensure sufficient contrast between text and background
• Use a legible sans-serif font at an adequate size

4. Proper Line Breaking

Break lines at natural linguistic boundaries:

Good:

The quick brown fox
jumps over the lazy dog.

Bad:

The quick brown fox jumps over
the lazy dog.

Break at punctuation, conjunctions, or prepositions when possible.

5. Sound Description Formatting

Use square brackets for non-speech elements:

• [music playing] — General music
• [upbeat electronic music] — Descriptive music
• [door creaks open] — Sound effects
• [silence] — Notable silence
• [speaking in French] — Foreign language indication

6. Speaker Identification

When multiple speakers are present, identify them consistently:

• [Host]: Welcome to the show.
• [Guest]: Thanks for having me.
• [Narrator]: Three months later...

Creating SDH Captions with SubtitleGen

While SubtitleGen excels at generating timed subtitle files from your transcript, you can create SDH-compliant captions by including sound descriptions and speaker labels in your input text.

Step-by-Step SDH Workflow

• Write your transcript with SDH annotations included:

[NARRATOR] Welcome to SubtitleGen.
[upbeat music fades]
[HOST] Today we are building accessible captions.
[sound of keyboard typing]
[HOST] Let me show you how easy it is.

• Paste this annotated transcript into SubtitleGen
• Set your video duration
• Generate and export as SRT or VTT
• Upload to your video platform

The speaker labels and sound descriptions will be included in the generated subtitle segments, making them SDH-compliant.

Testing Caption Accessibility

Manual Testing Checklist

• Watch the entire video with only captions (sound off) — can you follow the content?
• Check timing sync — do captions appear when words are spoken?
• Verify all speakers are identified
• Confirm all significant sounds are described
• Test readability at different screen sizes
• Ensure captions do not obscure important visual content

Automated Testing Tools

• axe DevTools — Checks for caption track presence in HTML5 video
• WAVE — Web accessibility evaluation tool
• Lighthouse — Google's accessibility audit includes media checks

Common Compliance Failures

• Missing captions entirely (the most common failure)
• Auto-generated captions with uncorrected errors
• Missing speaker identification
• No sound effect descriptions
• Poor timing sync
• Captions that obscure important visual content
• Insufficient color contrast

Legal Landscape in 2026

United States

• ADA Title III — Increasingly applied to websites and digital content
• Section 508 — Federal agencies must provide accessible media
• CVAA (21st Century Communications and Video Accessibility Act) — Requires captions on internet video that previously aired on TV
• State laws — Many states have additional accessibility requirements

European Union

• European Accessibility Act (EAA) — Effective June 2025, requires accessible digital products and services
• EN 301 549 — European standard for ICT accessibility, references WCAG

Penalties

Non-compliance can result in:

• Lawsuits (ADA lawsuits against websites have increased 300% since 2020)
• Financial penalties
• Reputational damage
• Loss of government contracts

Caption Formats for Accessibility

For web accessibility, VTT is the recommended format because it integrates natively with the HTML5 element and supports the kind="captions" attribute that screen readers can detect.

For maximum platform compatibility, SRT with manual SDH annotations works everywhere. Generate your timed SRT files with SubtitleGen and upload to any platform.

Frequently Asked Questions

What is the difference between captions and subtitles for accessibility?

Captions include non-speech audio (sound effects, music, speaker IDs) and are designed for deaf or hard-of-hearing viewers. Subtitles only transcribe dialogue and assume the viewer can hear non-speech audio.

Do auto-generated captions meet WCAG requirements?

Generally no. Auto-generated captions typically have 85-95% accuracy, miss sound effects and speaker identification, and contain errors that can change meaning. WCAG requires accurate captions, so you should always review and correct auto-generated text.

Is it enough to just have captions, or do they need to be accurate?

WCAG 1.2.2 requires captions that accurately represent the audio content. Inaccurate captions do not meet the standard, even if they are technically present.

Do I need captions if my video has no dialogue?

If the video has any meaningful audio (music, sound effects, ambient sounds), captions should describe those sounds. If the video is truly silent, captions are not required but a text description of the visual content is recommended.

Can SubtitleGen help with accessibility compliance?

Yes. SubtitleGen generates properly timed and formatted SRT and VTT subtitle files. Include speaker labels and sound descriptions in your transcript text, and SubtitleGen will preserve them in the generated subtitle file.

Conclusion

Accessible captions are essential for reaching the widest possible audience and meeting legal compliance standards. By following WCAG 2.2 guidelines, including SDH elements, and testing thoroughly, you ensure your video content is truly inclusive.

Start creating accessible, properly timed captions today with SubtitleGen. Paste your annotated transcript, generate, and export in SRT or VTT format — free, fast, and compliant.