How to Add Captions to Video for Accessibility (ADA & WCAG Guide)
Video captions are not optional — they are a legal and ethical requirement for accessible content. Over 430 million people worldwide have disabling hearing loss, and millions more watch video without sound. This guide covers the legal requirements, caption types, and practical steps to make your videos accessible.
Why video captions matter for accessibility
Captions provide text alternatives for audio content, making videos accessible to people who are deaf or hard of hearing. But accessibility extends far beyond hearing disabilities.
People in noisy environments (airports, gyms, open offices) rely on captions to follow along. Non-native speakers use captions to catch words they might miss from audio alone. People with attention or processing differences find that reading along with audio improves comprehension. And anyone who watches video on mute — which is the majority of social media users — depends on captions.
Accessible captions are not just subtitles of dialogue. They should also describe meaningful sounds: [door slams], [phone rings], [upbeat music playing], [crowd applause]. These non-speech audio cues carry information that deaf viewers need to fully understand the content.
ADA and WCAG requirements for video captions
In the United States, the Americans with Disabilities Act (ADA) requires that public-facing digital content be accessible to people with disabilities. While the ADA does not explicitly mention video captions, courts have consistently ruled that websites and digital services must be accessible, and uncaptioned video violates this standard.
The Web Content Accessibility Guidelines (WCAG) are more specific. WCAG 2.1 Level A requires captions for all prerecorded audio content in synchronized media (Success Criterion 1.2.2). Level AA requires captions for live audio content (Success Criterion 1.2.4). Level AAA adds sign language interpretation (Success Criterion 1.2.6).
Section 508 of the Rehabilitation Act requires federal agencies to make electronic content accessible, which includes captioning video content. The 21st Century Communications and Video Accessibility Act (CVAA) requires captions on video content distributed on the internet that previously aired on television.
The bottom line: if your organization publishes video content on a public website or app, you almost certainly have a legal obligation to provide captions. Enforcement has increased significantly in recent years, with lawsuits targeting universities, government agencies, and private businesses.
Types of captions: open vs closed
Closed captions are stored as a separate text track alongside the video. Viewers can turn them on or off, adjust the font size and color, and choose between languages. On the web, closed captions are typically delivered as WebVTT (.vtt) or SRT (.srt) files. YouTube, Vimeo, and most video platforms support closed caption uploads.
Open captions (also called burned-in or hardcoded captions) are permanently embedded in the video frames. Every viewer sees them and they cannot be turned off. Open captions guarantee that captions are visible regardless of the platform or player — they work on social media, in presentations, and on any device.
For maximum accessibility, closed captions are preferred because viewers can customize the appearance (larger text, high-contrast colors) to suit their needs. However, open captions are better for social media platforms that do not reliably display closed captions, or when you want to guarantee that every viewer sees the text.
The ideal approach for web accessibility is to provide both: closed captions as a WebVTT track for customization, and well-designed open captions as a default for social media distribution.
How to add accessible captions with ClipUtils
ClipUtils makes captioning simple with an AI-powered subtitle generator that runs entirely in your browser.
1. Go to the ClipUtils Subtitle Generator at cliputils.com/tools/subtitle-generator 2. Drop your video file onto the page — it is processed locally, never uploaded 3. Click 'Generate Subtitles' — the Whisper AI model transcribes your audio 4. Review and edit the generated captions for accuracy. Pay special attention to proper nouns, technical terms, and homophones. Add non-speech sound descriptions in brackets where relevant 5. Download the subtitle file as SRT or VTT for closed captions 6. Optionally burn the captions into the video for open captions — choose a readable font (Arial or Impact), high-contrast colors (white text on dark background), and appropriate positioning
For WCAG compliance, make sure your captions meet these quality standards: 99% or higher accuracy for prerecorded content, proper synchronization with audio (captions should appear within 1 second of the spoken word), identification of speakers when multiple people are talking, and descriptions of relevant non-speech audio.
Caption quality best practices
Accuracy is paramount. Auto-generated captions from tools like Whisper or YouTube's auto-captions are a starting point, not a finished product. Always review and correct the output. Misspelled words, incorrect homophones (their/there/they're), and garbled proper nouns make captions less useful and can even change the meaning of what was said.
Line length should be limited to about 32-42 characters per line, with no more than two lines on screen at once. This keeps the text readable without covering too much of the video.
Timing matters. Each caption should appear slightly before or exactly when the word is spoken and disappear shortly after. Captions that lag behind or jump ahead are disorienting. Most AI transcription tools, including ClipUtils, handle timing automatically, but review fast-paced sections.
Contrast and readability are essential. Use a high-contrast color combination — white text on a semi-transparent dark background is the most universally readable. Avoid decorative or thin fonts. For burned-in captions, test on both desktop and mobile screens to ensure the text is large enough.
Frequently asked questions
Are video captions legally required for my website?
In most cases, yes. If your website is public-facing and serves users in the United States, ADA requirements apply. WCAG 2.1 Level A explicitly requires captions for prerecorded video with audio. Government agencies, educational institutions, and large businesses face the highest enforcement risk, but lawsuits have targeted organizations of all sizes.
What is the difference between captions and subtitles?
Subtitles translate dialogue into another language and assume the viewer can hear the audio. Captions transcribe all audio content — dialogue, sound effects, music descriptions — for viewers who cannot hear. For accessibility purposes, captions are what you need.
Are auto-generated captions sufficient for ADA compliance?
Generally no. Auto-generated captions typically achieve 80-95% accuracy, but ADA compliance effectively requires near-perfect accuracy (99%+). Use auto-generated captions as a starting point, then manually review and correct errors before publishing.
Do I need captions for background music in my video?
Yes. WCAG guidelines require that significant audio content be captioned. If music sets the mood or conveys meaning, describe it in brackets: [upbeat electronic music], [somber piano]. If the music is purely incidental, a brief note like [background music] is sufficient.
Related tools: Auto Subtitle Generator
Related articles: Burned-In Subtitles vs Soft Subtitles · SRT vs VTT: What's the Difference?