Video Accessibility: Captions, Transcripts & WCAG Compliance (2026)

The ADA Title II compliance deadline for state and local government websites is April 24, 2026 — weeks away. If your site has video content without captions, you're not just losing viewers. You're potentially facing legal action in a landscape where digital accessibility lawsuits hit 4,187 in 2024 and are tracking 37% higher in 2025 (UsableNet, 2024).

But here's the thing most compliance guides won't tell you: making your videos accessible isn't just about avoiding lawsuits. It's a practical business decision. 80% of people who use captions aren't hearing impaired — they're watching in noisy environments, in quiet offices, or in their non-native language (Verizon Media & Publicis Media, 2019). Accessible video is better video for everyone.

Why Video Accessibility Matters (Beyond Legal Compliance)

Most guides frame video accessibility as a legal requirement you need to check off. That's true — but it's also incomplete. The business case is strong enough to justify the work even without the legal risk.

Reach. Over 70% of Americans now watch content with subtitles or captions enabled (Kapwing, 2024). That includes people in noisy commuter environments, non-native English speakers, and anyone who just prefers reading along. If your video doesn't have captions, you're excluding the majority of viewers — not a minority.

Engagement. Viewers are 80% more likely to watch a video to completion when closed captions are available (3Play Media). Facebook's internal research found captions increased video views by 12% (Lemonlight). For product videos, training content, or explainer videos on your website, that's a measurable impact on conversion and retention.

SEO. Search engines can't watch your video, but they can index your captions and transcripts. Adding a text transcript to your video page gives Google crawlable content that matches search queries. This is particularly valuable for online course videos and training content where long-tail search traffic matters.

Legal risk. The enforcement landscape is real and growing. 4,187 digital accessibility lawsuits were filed in 2024, and 2025 is pacing 37% higher. The DOJ's April 2024 final rule establishes WCAG 2.1 Level AA as the standard for ADA Title II compliance, with the first deadline hitting April 24, 2026 for public entities serving populations over 50,000 (DOJ, 2024).

Closed Captions vs. Subtitles: The Difference That Matters for Compliance

These terms are often used interchangeably, but they mean different things — and the distinction matters for WCAG compliance.

The bottom line: If you have subtitles on your video but no proper closed captions, you're not WCAG compliant. Captions must include all meaningful audio — dialogue, speaker identification, sound effects, and music cues — not just a translation of the spoken words.

WCAG Video Requirements Explained

WCAG (Web Content Accessibility Guidelines) is the technical standard that defines what "accessible" means for web content. Here's what it requires for video, broken down by conformance level:

Most organizations target Level AA — that's what the DOJ requires for ADA Title II and what courts reference in ADA Title III cases. Level AAA is aspirational but rarely required by law.

The most commonly misunderstood requirement is SC 1.2.5 (audio descriptions at Level AA). At Level A, you can provide a full text transcript as an alternative. But at Level AA, a transcript alone isn't enough — you must provide actual audio descriptions that narrate visual content for blind users. This catches many organizations off guard because they assume their transcript covers everything.

How to Make Your Videos Accessible

Here's the practical implementation, step by step:

1. Add Closed Captions

Captions are the highest-impact accessibility feature. Here's the workflow:

Generate a first draft. Use an auto-captioning service (YouTube, Rev, Otter.ai, or Descript) to create an initial caption file. Auto-generated captions have improved significantly, but they're still not compliant on their own — the FCC standard requires 99% accuracy, and auto-captions typically hit 85-95%.

Edit for accuracy. Review every line. Fix proper nouns, technical terms, and homophones. Add speaker identification ([James:], [Customer:]) and non-dialogue audio ([background music], [applause], [door closes]).

Save as WebVTT (.vtt) or SRT (.srt). These are the two standard caption formats supported by virtually all video players. VTT is the web-native format and supports more styling options. For a detailed walkthrough, see our guide on how to create a VTT caption file.

Upload to your video platform. How you attach captions depends on your hosting setup. Most dedicated video hosting platforms accept VTT/SRT uploads through their dashboard. If you're self-hosting with an HTML5 video player, you add a <track> element pointing to your VTT file.

2. Provide Transcripts

A transcript is a text version of all audio and visual content in your video. Unlike captions (which are time-synchronized), transcripts are a standalone document — typically placed below the video on the same page.

For Level A compliance, a transcript can serve as your "media alternative" (SC 1.2.3). At Level AA, you still need audio descriptions in addition to any transcript.

Transcripts also serve a practical SEO function: they give search engines full-text content to index on your video page, which is particularly valuable for embedded video content that would otherwise be invisible to crawlers.

3. Add Audio Descriptions (When Required)

Audio descriptions are a narrated track that describes important visual content — actions, scene changes, on-screen text, charts — during natural pauses in dialogue. They're designed for blind and visually impaired users.

When are they required?

• Level A: You can provide a text transcript instead (SC 1.2.3)
• Level AA: Audio descriptions are required — a transcript alone doesn't satisfy SC 1.2.5
• Practical exemption: If all visual information is already conveyed through the audio track (e.g., a talking-head video where the speaker describes everything), no additional audio description is needed

For most corporate and marketing videos, the practical approach is to script your videos with accessibility in mind. If the narrator verbally describes what's on screen ("As you can see in the chart, costs dropped 40% in Q3"), you've effectively built audio description into the original content.

4. Ensure Player Accessibility

This is the requirement most guides skip — and where many organizations fail compliance audits. WCAG 2.1 Level AA requires:

• Keyboard navigation: Play, pause, volume, seek, captions toggle, and fullscreen must all be operable with keyboard only (no mouse required)
• ARIA labels: Every player control must have proper ARIA attributes so screen readers can announce what each button does
• Focus indicators: When tabbing through controls, users must see a visible focus indicator showing which control is active
• No keyboard traps: Users must be able to tab into and out of the video player without getting stuck

Why Your Video Hosting Choice Affects Compliance

Here's something the W3C documentation and compliance guides don't address: your video hosting platform is part of your accessibility stack.

If you embed a YouTube video on your site, YouTube's embedded player becomes part of your page. And YouTube's embedded iframe has known accessibility limitations:

• Keyboard navigation in the embedded player can be inconsistent — tabbing through controls doesn't always follow a logical order
• Caption controls in embedded mode behave differently than on youtube.com — users may not be able to toggle captions reliably
• Auto-generated captions on YouTube are enabled by default but rarely meet the 99% accuracy standard required for compliance
• You don't control the player — YouTube can change their player's accessibility features at any time, and you inherit those changes on your site

This doesn't mean YouTube embeds are inherently non-compliant. But it means you're outsourcing a critical compliance component to a platform you don't control. For organizations serious about accessibility — particularly those subject to ADA Title II — using a dedicated video platform where you control the player, caption tracks, and delivery gives you more predictable compliance.

Common Video Accessibility Mistakes

These are the failures that come up most often in compliance audits:

Relying on auto-generated captions without review. YouTube and other platforms generate captions automatically, but they regularly miss proper nouns, technical terms, and speaker changes. Auto-captions also don't include sound effects or music cues. They're a starting point, not a finished product.

Providing subtitles instead of captions. If your caption file only contains translated dialogue — no speaker identification, no sound effects, no music cues — it doesn't satisfy WCAG SC 1.2.2. This is the most common "we thought we were compliant" failure.

Assuming a transcript replaces audio descriptions at Level AA. At Level A, yes. At Level AA (the standard courts and the DOJ reference), you need actual audio descriptions for videos where visual content isn't described in the dialogue. A transcript on the page isn't sufficient.

Ignoring the video player itself. You can have perfect captions and transcripts, but if your video player can't be operated by keyboard alone, you fail SC 2.1.1. This is particularly common with custom-built players and some embedded third-party players.

Not captioning background music and sound effects. If a dramatic music swell signals a mood change, or a notification sound indicates an action, that audio carries meaning. Captions should note it: [suspenseful music], [notification chime], [audience laughter].

Publishing live video without real-time captions. Level AA (SC 1.2.4) requires live captions for live video with audio. If you're live streaming events, webinars, or presentations, you need a real-time captioning service or a qualified CART provider.

Video Accessibility Checklist

Use this to audit your existing video content or plan new videos:

The Legal Landscape: ADA, Section 508, and What Applies to You

The regulatory framework can be confusing. Here's a quick orientation:

ADA Title II applies to state and local government entities. The DOJ's April 2024 final rule requires WCAG 2.1 Level AA compliance for web content. Deadline: April 24, 2026 for entities serving populations over 50,000; April 26, 2027 for smaller entities.

ADA Title III applies to private businesses ("places of public accommodation"). There's no explicit federal deadline, but courts have increasingly ruled that websites are covered, and WCAG 2.1 AA is the standard courts reference. If you're a business with a website that includes video, you're in scope — and 4,187 lawsuits in 2024 show enforcement is active.

Section 508 applies to federal agencies and their contractors. It directly references WCAG 2.0 Level AA (with ongoing alignment to 2.1). If you sell to the federal government or produce content for federal agencies, your videos must comply.

All three frameworks converge on the same practical standard: WCAG 2.1 Level AA. If you meet that, you're covered for virtually all U.S. regulatory contexts.