Making Videos ADA-Compliant: Captions, Transcripts, and Checklists

Every video you publish without captions locks out a real part of your audience — and, if your videos belong to a business, a school, or any organization that serves the public, it can also put you on the wrong side of the law. US courts have interpreted the Americans with Disabilities Act (ADA) to cover websites and the video on them, and lawsuits over inaccessible video keep climbing. Most are not aimed at giants; small businesses, course creators, and local organizations get demand letters too.

The good news is that making a video ADA-compliant is far simpler than most creators fear. It comes down to three things: accurate captions for everything spoken, a text alternative for everything shown and heard, and a player that people can actually operate. This guide walks through each one, in order, with a pre-publish checklist you can reuse for every video.

What the ADA actually requires from video

The ADA itself does not contain a checklist for video. Courts and regulators instead point to the Web Content Accessibility Guidelines (WCAG), the technical standard the US Department of Justice has repeatedly endorsed. For video, WCAG 2.1 Level AA — the level most settlements and regulations reference — boils down to a handful of concrete requirements.

• Captions for prerecorded video (1.2.2). Every video with audio needs synchronized captions that cover all speech plus important non-speech sounds like [music] or [applause]. Auto-generated captions only count if you review and correct them.
• Audio description or a transcript (1.2.3 / 1.2.5). For prerecorded video, a text transcript can satisfy the Level A requirement; Level AA asks for audio description of important visual information, or a transcript that covers it.
• Keyboard access and no traps (2.1.1 / 2.1.2). Play, pause, volume, and the caption toggle must all work from a keyboard, and a keyboard user must never get stuck inside the player.
• No flashing that can trigger seizures (2.3.1). Content must not flash more than three times per second.
• Contrast and focus (1.4.3 / 2.4.7). Any text in the player interface and any burned-in captions need enough contrast, and focused controls must be visible.

Two honest caveats: WCAG is a standard, not a statute — a court or settlement decides what "compliant" means, so meeting Level AA in full is the safest position. And this article is practical guidance, not legal advice; if you have received a demand letter, talk to a lawyer who handles digital accessibility.

Step 1: Add accurate captions to every video

Captions are the single highest-impact accessibility fix, and they are also the one most creators get half-right. YouTube and social platforms generate captions automatically, but raw auto captions are not ADA-grade: they mishear names, drop words in noisy audio, and garble anything outside plain, clear English. A caption track full of errors is not a good-faith effort.

1. Generate a transcript. Run your video or audio through a transcription tool. Captionbench's free browser tool transcribes locally on your device and exports a timestamped SRT, VTT, or TXT file — nothing is uploaded, which also keeps sensitive recordings private.
2. Review and correct the text. Read the whole transcript once. Fix proper names, brand terms, numbers, and technical vocabulary. Check the timing: each caption should stay on screen for 1–7 seconds, hold one or two short lines, and never rush past at reading speeds above roughly 20 characters per second.
3. Add non-speech information. Real captions include the sounds that matter to the story — [door slams], [crowd cheers], [soft music]. Identify speakers when more than one person talks, for example "SARAH: Let's start with the budget."
4. Upload the file as a sidecar track. On YouTube, that means uploading your .srt in YouTube Studio under Subtitles. On your own site, use a <track> element with kind="captions" inside the <video> tag so the captions are a real, toggleable track rather than text burned into the picture.
5. Test with the sound off. Watch the whole video muted. If you can follow the story, the jokes, and the instructions from captions alone, the track is doing its job.

Prefer toggleable captions over burned-in (open) captions for anything longer than a short-form clip. A sidecar SRT can be translated, searched, and restyled by the viewer's own settings; text baked into the video pixels can do none of that. Burned-in captions still suit Shorts and Reels, where the platform controls the player — but on your own site or YouTube, the toggleable track is the accessible choice.

Step 2: Publish a transcript and describe the visuals

Captions help people who cannot hear. A transcript helps everyone else who cannot watch: blind viewers using a screen reader, people on slow connections, and anyone who wants to search, quote, or skim your content. WCAG treats a full transcript as the Level A alternative to audio description, making it the cheapest way to cover the visual side of accessibility.

• Publish the transcript on the same page as the video. A collapsible section under the player works well. Do not hide it behind a download link that forces people to open a separate file.
• Write it as a complete record, not a summary. Include all spoken words in order, speaker labels, and descriptions of important visual information in brackets — what is on screen during a silent demo, what a chart shows, what text appears in a slide. If the video alone carries meaning, the transcript must carry it too.
• Reuse the same file. The corrected transcript you made for your SRT is already 90% of a transcript. Export it as plain text, add the visual descriptions, and you have both deliverables from one review pass.
• Consider audio description for high-stakes video. If the video relies heavily on visuals — a product demo, a training walkthrough, a documentary — a separate audio-description track, where a narrator describes key visuals during natural pauses, is the Level AA gold standard. It costs more, so prioritize your most-watched and most essential videos first.

Transcripts also help SEO: search engines can index a transcript on the page, but they cannot watch your video. Pages with full transcripts often rank for the exact phrases spoken in the video — accessibility work that pays for itself.

Step 3: Fix the player and the page around the video

Perfect captions inside an unusable player still fail the test. Most video accessibility complaints are not about captions at all — they are about a custom player a keyboard cannot operate, a caption button a screen reader cannot find, or a video that blasts audio the moment the page loads.

1. Use a native or well-tested player. The browser's built-in <video> element and established players like YouTube's embed already handle keyboard focus, caption toggles, and screen-reader labels. Custom players built from divs usually fail at least one of these — if you must customize, test with a keyboard and a screen reader before shipping.
2. Make every control keyboard-reachable. Tab to the player and confirm you can play, pause, seek, change volume, and toggle captions without touching the mouse. A visible focus outline on each control is not optional decoration; it is how keyboard users see where they are.
3. Never autoplay with sound. Autoplay is a WCAG failure when it plays audio for more than three seconds without a stop control, and it is miserable for screen-reader users, whose audio gets drowned out. If you autoplay at all, mute it by default.
4. Label the video itself. Give the player an accessible name that says what the video is, and add a short description or a link to the transcript right next to it. "Watch the video" tells a screen-reader user nothing.
5. Check contrast and flashing. Burned-in caption text and player controls need at least 4.5:1 contrast against their background, and the video must not flash more than three times per second. Most editing tools have a photosensitive-epilepsy check — run it on any video with strobe effects, rapid cuts, or flashing graphics.

The ADA video checklist (use before every publish)

Run through this list before a video goes live. Ten minutes of checks here prevents the kind of complaint that costs weeks.

• Captions uploaded as a real track (SRT or VTT), reviewed and corrected — not raw auto captions.
• Captions cover all speech, identify speakers, and note important sounds like [music] and [applause].
• Full transcript published on the same page, including descriptions of key visuals.
• Audio description added, or planned, for videos where visuals carry the meaning.
• Player controls all work from a keyboard, with a visible focus indicator.
• Caption toggle is labeled and reachable.
• Video does not autoplay with sound; no flashing above three times per second.
• Video has an accessible name and a link to its transcript nearby.
• Captions and player text meet 4.5:1 contrast.
• Final check: watch the whole video muted, then listen to it with eyes closed. Both versions should make sense.

Key takeaways

• ADA compliance for video means WCAG 2.1 Level AA in practice: accurate captions, a transcript or audio description, and a keyboard-operable player.
• Raw auto captions are not enough — review and correct every transcript before it reaches viewers.
• A full transcript on the same page covers the visual side of accessibility and helps your SEO at the same time.
• Run the ten-point checklist before every publish; it takes minutes and prevents most complaints.

Ready to caption your next video properly? Generate free timed captions with Captionbench right in your browser — no account, no uploads, SRT/VTT/TXT export included.