What Is Closed Captioning? Definition, Legal Requirements, and Practical Guide (2026)
Closed captioning is on-screen text that reproduces a video's spoken dialogue, speaker labels, and non-speech audio cues (music, laughter, [door slam]) — delivered as a viewer-toggleable track so it can be turned on or off, unlike open captions which are permanently burned into the video image.
By VexaScribe Editorial · Verified
Closed captions are on-screen text of a video's dialogue, speaker labels, and non-speech audio cues, delivered as a viewer-toggleable sidecar file (SRT, WebVTT, TTML, SCC). In the US, captions are required by ADA, Section 508, CVAA, FCC rules, and the DOJ Title II Final Rule (April 2024). In the EU, the European Accessibility Act has required captions on covered private-sector digital services since June 28, 2025.
Closed Captioning Definition — Plain and Technical
Closed captioning is time-synchronized on-screen text that reproduces a video's spoken dialogue, speaker identifications, and non-speech audio cues, delivered as a track the viewer can turn on or off. It is the accessibility-oriented equivalent of subtitles and is the default way Deaf and hard-of-hearing viewers experience video.
Technically, a closed-caption track is a stream of time-coded text cues in one of several standard formats (SRT, WebVTT, TTML/DFXP, SCC). The cues carry three categories of information: dialogue (what each person says), speaker identification (who is speaking, especially off-screen or when multiple speakers are audible), and non-speech audio cues (music, laughter, applause, sound effects such as [door slam] or [phone rings]). The video player renders the cue text as an overlay synchronized to playback time.
The word “closed” refers to the viewer's ability to toggle the caption stream on or off. On US broadcast television this toggle was standardized by the Television Decoder Circuitry Act (Public Law 101-431, 1990), which required all televisions 13 inches or larger sold in the United States after July 1993 to include a built-in caption decoder chip that reads captions encoded on Line 21 (the CEA-608 standard) or in the digital transport stream (CEA-708). The same lineage is why every streaming device, smart TV, and set-top box natively supports caption rendering today.
On the web, closed captions are delivered as a separate file that a media player reads and overlays — a “sidecar” caption track. Open captions, by contrast, are burned directly into the video pixels and cannot be turned off.
Closed Captions vs Subtitles vs SDH
These three terms are routinely conflated on streaming platforms. The distinctions matter for accessibility compliance because different laws expect different tracks.
| Track type | Dialogue | Sound cues | Language | Toggle-able | Primary purpose |
|---|---|---|---|---|---|
| Closed captions (CC) | ✓ | ✓ | ✓ (source language) | ✓ | Accessibility for Deaf/HoH viewers |
| Subtitles (translated) | ✓ | ✗ (usually omitted) | ✗ (different language) | ✓ | Translation for viewers who don't speak the source language |
| SDH (Subtitles for the Deaf and Hard-of-Hearing) | ✓ | ✓ | ✓ (source language) | ✓ | CC content delivered via the subtitle track (streaming standard) |
Source: WCAG 2.1 definitions; W3C Media Accessibility User Requirements.
On Netflix, Apple TV+, Prime Video, and Disney+, an “English SDH” track behaves like closed captions but is delivered through the subtitle stream. For accessibility compliance both CC and SDH are treated equivalently.
How Closed Captions Work — Broadcast and Web
Broadcast TV (CEA-608 / CEA-708). On US analog television, closed captions were encoded in Line 21 of the vertical blanking interval per the CEA-608 standard, decoded by the TV's built-in caption chip. Digital ATSC television uses the successor CEA-708 standard, which supports multiple caption tracks, richer styling, and up to 8 language streams. Broadcast captioning workflows produce SCC files that carry the raw CEA-608 byte pairs.
Web video (sidecar files). HTML5 video and modern streaming players read a separate caption file — most commonly SRT or WebVTT — and render the text as an overlay synchronized to the video timeline. Netflix and enterprise workflows use TTML (in the IMSC 1.2 profile) for stricter styling and multi-language delivery. YouTube accepts SRT, VTT, SBV, SCC, TTML, and DFXP.
Embedded vs sidecar. Captions can be muxed into container formats (MP4, MOV, MKV) as a text track alongside video and audio streams, or shipped as a separate file. Sidecar files are easier to update and localize; embedded tracks are easier to distribute in a single asset. Both remain toggleable at the player.
Live captions. For live-streamed video, captions are generated in real time by a human stenographer (CART), by automatic speech recognition (Google, Microsoft, Otter, Zoom), or by a hybrid pipeline. Live captions are transmitted over WebSocket, SRT protocol, or an in-band caption channel. Industry norm for compliance-grade live captions is under 5 seconds of end-to-end latency.
For a deeper look at the two most common web formats, see what is an SRT file and what is a VTT file.
When Are Closed Captions Legally Required in the US?
Six overlapping frameworks drive US captioning obligations. This is the consolidated summary compliance coordinators actually need — each with its primary source below.
| Framework | Who it covers | Caption trigger | Standard | Dates |
|---|---|---|---|---|
| ADA Title II | State and local governments | Public web content and mobile apps | WCAG 2.1 Level AA (per DOJ Final Rule, 89 FR 31320) | By Apr 24, 2026 (pop. 50,000+) or Apr 24, 2027 (smaller) |
| ADA Title III | Places of public accommodation (private businesses) | Public-facing websites and mobile apps | WCAG 2.1 AA (de facto, via case law) | In force since 1990; web application via settled case law |
| Section 508 (Rehabilitation Act) | US federal agencies and federally funded ICT | All electronic and information technology | Revised 508 Standards (WCAG 2.0 AA baseline) | Revised 2018; in force |
| CVAA (Public Law 111-260) | IP-delivered video previously aired on US broadcast TV | Prerecorded, live, and near-live IP video | FCC captioning quality rules | 2010 (phase-in 2012–2016) |
| FCC captioning rules | US broadcast TV and covered IP video programming | Programming previously aired with captions on TV | Accuracy, synchronicity, completeness, placement | In force; last consolidated update 47 CFR §79.1 et seq. |
| State-level (Unruh, NY HRL) | California / New York businesses | Web accessibility | WCAG 2.1 AA (de facto) | Ongoing private enforcement (Unruh: $4,000/violation minimum) |
ADA Title II — State and Local Governments (DOJ Final Rule, April 2024)
The Department of Justice published its final rule on the accessibility of web information and services of state and local governments in the Federal Register on April 24, 2024 (89 FR 31320). The rule adopts WCAG 2.1 Level AA as the technical standard for public web content and mobile apps. Under WCAG 2.1 Level AA, both SC 1.2.2 (prerecorded captions) and SC 1.2.4 (live captions) are required.
Compliance dates are staggered by jurisdiction size: April 24, 2026 for large local governments (populations of 50,000 or more) and state government entities, and April 24, 2027 for small local governments (populations under 50,000) and special-purpose districts.
Primary source: Federal Register 89 FR 31320 · ada.gov/resources/web-guidance
ADA Title III — Private Businesses (Places of Public Accommodation)
ADA Title III (42 U.S.C. §12181 et seq.) prohibits discrimination in places of public accommodation. Since NAD v. Netflix (D. Mass. 2012, 869 F. Supp. 2d 196), courts have consistently applied Title III to web-only services and to the web presence of physical businesses (Robles v. Domino's, 9th Cir. 2019). The DOJ has not fixed a specific technical standard by regulation for Title III, but WCAG 2.1 Level AA is the de facto standard cited in enforcement and private lawsuits.
Primary source: ada.gov/topics/title-iii · DOJ web accessibility guidance
Section 508 — Federal Agencies
Section 508 of the Rehabilitation Act (29 U.S.C. §794d), as revised in the 2018 ICT Refresh, requires federal agencies to make their electronic and information technology accessible. The Revised 508 Standards incorporate WCAG 2.0 Level AA by reference and apply to procurement, development, and maintenance of ICT. Captions are required for all prerecorded and live synchronized media produced or funded by federal agencies.
Primary source: section508.gov · US Access Board ICT Standards
CVAA — 21st Century Communications and Video Accessibility Act
The CVAA (Public Law 111-260, October 2010) extended captioning requirements to IP-delivered video that was previously aired on US broadcast television. The FCC implemented CVAA captioning obligations in a phased schedule from 2012 through 2016, with distinct rules for prerecorded, live, near-live, edited-for-IP, and video clip categories.
Primary source: fcc.gov/consumers/guides/twenty-first-century-communications-video-accessibility-act-cvaa
FCC Captioning Rules — Broadcast Television
The FCC captioning rules for television (47 CFR §79.1 et seq.) require broadcasters, cable operators, and satellite TV providers to caption almost all English- and Spanish-language programming. The rules also set four quality standards: accuracy (verbatim within the limits of the medium), synchronicity, completeness, and placement. These quality standards are the most widely cited benchmark for editorial review of any caption file, even outside the FCC's direct jurisdiction.
Primary source: fcc.gov/consumers/guides/captioning-television-and-video
State-Level — California, New York
California's Unruh Civil Rights Act (Civil Code §51 et seq., with recent amendments including AB 1836) sets a $4,000 per-violation minimum in private civil actions and has been the vehicle for a large share of state-level web-accessibility captioning lawsuits. New York's Human Rights Law (§290 et seq.) plus the New York City Human Rights Law generate a similar volume of private enforcement in the Southern and Eastern Districts of New York. Both statute frameworks apply WCAG 2.1 AA as the de facto conformance target through case law.
EAA 2025 — European Accessibility Act (In Force Since June 28, 2025)
The European Accessibility Act (Directive (EU) 2019/882) has been in force across all EU Member States since June 28, 2025. It requires accessibility — including captions on audiovisual content and video communication — for a defined list of private-sector products and services placed on the EU market. Covered categories include e-commerce, consumer banking services, e-books and dedicated software, audiovisual media services (including their electronic programme guides), passenger transport services, ATMs and payment terminals, and smartphones and their operating systems.
Transition window. Products and services already on the market before June 28, 2025 have until June 28, 2030 under the Directive's transitional provisions. Some service contracts concluded before June 28, 2025 may run to their natural end no later than June 28, 2030.
Technical standard. The harmonized standard EN 301 549 is the primary conformance path for the EAA and incorporates WCAG success criteria for captions on prerecorded and live synchronized media. Enforcement is by Member State market-surveillance authorities and includes penalties, product withdrawal, and end-user complaint mechanisms.
Primary source: EUR-Lex Directive 2019/882 · European Commission — EAA
How to Caption to Be WCAG-Compliant
WCAG 2.1 SC 1.2.2 (Level A) requires captions for prerecorded synchronized media. SC 1.2.4 (Level AA) requires captions for live synchronized media. Both are cited by the DOJ Title II Final Rule, Section 508, and the EU EAA (via EN 301 549). Here is what a compliant caption file actually looks like at the format level.
A WCAG-compliant caption file must include:
- All spoken dialogue — verbatim within the limits of the reading-speed budget (typically 15–20 characters per second, ~160–180 wpm).
- Speaker identification when speakers are off-screen, when multiple speakers are audible, or when the visual context does not make the speaker obvious.
- Non-speech audio cues that are significant for comprehension: music, laughter, applause, sound effects (
[door slams],[phone rings]), ambient sound relevant to plot or meaning. - Time synchronization with the audio — each cue appears while its corresponding audio is playing.
- Adequate accuracy — SC 1.2.2 and 1.2.4 do not set a numeric threshold, but courts and DOJ guidance treat quality (not just presence) as the operative test. The FCC 47 CFR §79.1(j) quality standards (accuracy, synchronicity, completeness, placement) are the widely used editorial benchmark.
- Readable presentation — 4.5:1 minimum contrast per WCAG 2.1 SC 1.4.3, no more than 2 lines per cue (Netflix/BBC style guides), positioned so it does not obscure critical on-screen information.
Auto-generated captions rarely clear this bar on their own. OpenAI's Whisper Large-v3 achieves roughly 4.2% word error rate on the English FLEURS benchmark (arXiv:2212.04356, Table 5) on clean speech; consumer auto-caption systems (YouTube, Zoom, Teams) reach 85–92% accuracy on clean English but drop to 60–75% on accented English, technical vocabulary, or noisy audio. A human editorial pass is the difference between a caption file and a compliant caption file.
Primary sources: WCAG 2.1 SC 1.2.2 · SC 1.2.4 · Whisper Large-v3 paper (arXiv:2212.04356).
Do I Need to Caption My Videos? A Decision Tree
A practical walk-through of the question compliance officers get asked most often. Start at the top and stop at the first “yes.”
- 1
Are you a US federal agency, or is the video produced under a federal grant or contract?
Yes → Section 508 (revised 2018) requires captions on prerecorded and live synchronized media.
- 2
Are you a US state or local government entity?
Yes → DOJ Title II Final Rule (89 FR 31320) requires WCAG 2.1 AA (including SC 1.2.2 and 1.2.4) by April 24, 2026 (pop. 50,000+) or April 24, 2027 (smaller jurisdictions).
- 3
Is your video being broadcast on US TV, or was it previously broadcast on TV and is now delivered over IP?
Yes → FCC captioning rules (47 CFR §79.1) and CVAA (Public Law 111-260) apply.
- 4
Do you operate a place of public accommodation in the US (retail, hospitality, healthcare, professional services, education, most consumer-facing businesses) with a public-facing website or app?
Yes → ADA Title III risk. WCAG 2.1 AA is the de facto standard; captions on public video are strongly indicated.
- 5
Do you sell products or services in the EU that fall within EAA scope (e-commerce, banking, e-books, audiovisual media, passenger transport, smartphones, ATMs)?
Yes → EAA (Directive 2019/882) in force since June 28, 2025 requires captions on audiovisual content per EN 301 549.
- 6
Are you a California or New York business with public video content?
Yes → State civil-rights statutes (Unruh, NY HRL) create private-lawsuit exposure with WCAG 2.1 AA as the de facto benchmark.
- 7
None of the above — you have no legal caption obligation.
You still probably want captions: sound-off consumption is the majority behavior on social feeds, captions extend reach, they make content indexable for search, and they benefit non-native speakers and viewers in noisy environments. See the next section.
When You Don't Need Captions but Should Add Them Anyway
Even outside a regulatory obligation, three practical reasons make captions the default choice for published video.
Sound-off consumption is the norm on social feeds. Widely cited industry estimates put the share of social-feed video watched with sound off at around 85% (Digiday reporting on Verizon Media, 2019; treat as a widely-cited estimate, not a peer-reviewed figure). Regardless of the precise number, autoplay-muted is the default state of TikTok, Instagram Reels, YouTube Shorts, Facebook, and LinkedIn feeds — captions are the only way to convey dialogue without a viewer action.
SEO and content indexing. Search engines, LLM crawlers, and platform recommender systems index caption tracks. A captioned video is a substantively larger surface for topical retrieval than an uncaptioned one. YouTube's search and recommendation systems have used caption text since the mid-2010s.
Non-native speakers and noisy environments. Captions materially improve comprehension for viewers watching in a second language and for anyone in a shared or noisy environment where audio is impractical.
How to Turn Closed Captions On or Off
The universal shortcut on almost every platform: look for a rectangle with the letters CC or a speech-bubble icon in the player controls.
Netflix
Per video: During playback, click/tap the screen → speech-bubble icon (or “Subtitles”) → choose a language or “Off.”
Profile default: Netflix.com → Manage Profiles → pick a profile → Subtitle appearance → set language, style, and background opacity.
YouTube
Per video: Click the CC button on the player, or press c on desktop to toggle.
Account default: Settings → Playback and performance → Captions → “Always show captions.” Style options let you set font, size, background, and edge type.
Roku
Per video: Press the star (*) button on the remote during playback → Closed Captioning → Off / On / On Replay / Instant Replay.
System default: Home → Settings → Accessibility → Captions mode.
Smart TVs (Samsung / LG / Sony / TCL)
Most remotes have a dedicated CC or Subtitle button. If not: Settings → Accessibility → Captions/Subtitles → set on/off, style, size. Older sets: Menu → Sound/Display → Closed Captioning. On cable/satellite boxes, the box setting overrides the TV — use the box remote's CC button in that case.
Zoom, Microsoft Teams, Google Meet
Zoom: during meeting, click More → Captions → Show captions. Teams: More → Language and speech → Turn on live captions. Google Meet: click the CC button at the bottom of the meeting window. All three use automatic speech recognition with per-user visibility toggles; captions are generated live.
Closed Caption File Formats
Five file formats cover almost every 2026 web, streaming, and broadcast workflow. Choice of format depends on delivery destination and styling needs.
| Format | Extension | MIME type | Best for | Styling |
|---|---|---|---|---|
| SubRip (SRT) | .srt | application/x-subrip | Max compatibility, YouTube, social, most video editors | Minimal (bold/italic) |
| WebVTT | .vtt | text/vtt | HTML5 <video> element, browser-native rendering | CSS + positioning cues |
| TTML / DFXP | .ttml, .dfxp | application/ttml+xml | Netflix (IMSC 1.2 profile), broadcast, enterprise | Full XML styling |
| SCC (Scenarist) | .scc | text/plain | US broadcast TV workflows | EIA-608 codes (broadcast native) |
| SBV | .sbv | text/plain | YouTube legacy uploads | None |
Sources: W3C WebVTT, W3C TTML2, YouTube caption formats, Netflix TTSGuide (IMSC 1.2 profile).
For a format-level deep-dive, see what is an SRT file. To generate a caption file from an existing video, see the video-to-SRT tool.
SDH Subtitles — What They Are and When to Use Them
SDH (Subtitles for the Deaf and Hard-of-Hearing) is content that behaves like closed captions but is delivered through a subtitle track. It includes speaker labels and non-speech audio cues but uses subtitle file formats (SRT, WebVTT, TTML) rather than the CEA-608/708 broadcast caption stream. It emerged as streaming platforms consolidated their internal delivery pipelines on TTML/IMSC and needed a same-language track that included accessibility metadata without going through broadcast caption infrastructure.
Use SDH when: you are shipping video to a streaming platform (Netflix, Prime, Apple TV+, Disney+) that expects TTML/IMSC delivery; you want a single format that works across web, mobile, and TV apps; you are producing multilingual content and want a same-language accessibility track alongside translated subtitle tracks.
Compliance treatment. For ADA, WCAG, Section 508, and EAA compliance purposes, SDH and CC are treated equivalently: both satisfy the “captions for synchronized media” requirement as long as the content includes speaker IDs and non-speech audio cues.
Need a caption file for a video you already have?
Generate captions with VexaScribe · SRT export · Video to SRT
Frequently Asked Questions
What does CC stand for?
CC stands for closed captioning (or closed captions). The "closed" part refers to the viewer's ability to toggle the caption track on or off — as distinct from open captions, which are permanently burned into the video image. The CC button on a remote, media player, or web video control turns the caption stream on and off.
What is the difference between closed captions and subtitles?
Closed captions assume the viewer cannot hear the audio, so they include speaker labels ("NARRATOR:") and non-speech audio cues ([door slams], [music playing]) in addition to dialogue. Subtitles assume the viewer can hear but doesn't understand the language, so they translate dialogue but typically omit sound effects and speaker IDs. On US streaming platforms the two terms are frequently conflated and delivered under the labels "CC" and "SDH" (Subtitles for the Deaf and Hard-of-Hearing).
Are closed captions required by law?
It depends on who you are and what you publish. In the US: broadcast TV must be captioned under FCC rules; federal agencies must caption under Section 508 (revised 2018); state and local governments must conform to WCAG 2.1 Level AA under the DOJ Title II Final Rule (89 FR 31320, published April 24, 2024), with deadlines of April 24, 2026 for jurisdictions of 50,000+ and April 24, 2027 for smaller ones; private businesses face ADA Title III claims where WCAG 2.1 AA is the de facto standard. In the EU, the European Accessibility Act (Directive 2019/882) has been in force since June 28, 2025 for private-sector digital services.
Does the ADA require captions on YouTube videos?
If you are a place of public accommodation under ADA Title III (most private businesses with a customer-facing web presence), then yes — courts have consistently applied Title III to web video, and WCAG 2.1 Level AA is the de facto conformance standard invoked in web-accessibility settlements. If you are a state or local government, YouTube videos linked or embedded from your official site are covered by the DOJ Title II Final Rule (April 2024). Purely personal YouTube videos are not covered.
What is the difference between open and closed captions?
Closed captions are stored as a separate track (SRT/VTT/TTML/SCC) that the video player overlays on the video, and the viewer can turn them on or off. Open captions are burned directly into the video pixels — they are always visible and cannot be disabled. Open captions are common on TikTok, Reels, and Shorts (where sound-off autoplay is the norm) and in accessibility-first productions where you want to guarantee captions display regardless of player support. Closed captions are the standard for TV, streaming platforms, and web video.
How do I turn on closed captions on Netflix?
During playback, click or tap the screen to reveal controls, click the speech-bubble icon (or select "Subtitles"), and choose a language. On a TV app, press up or menu on the remote during playback, navigate to Subtitles/Audio, and pick a language. To set the default for the whole profile: sign in on Netflix.com → Manage Profiles → pick a profile → Subtitle appearance → choose language, font, and background style.
How do I turn off closed captions?
On most video players and TVs: press the CC button on the remote, or open the player's subtitle menu and choose "Off." Netflix: click the speech-bubble icon during playback → Off. YouTube: click the CC button on the player, or press the "c" key on desktop. Roku: press the star (*) button during playback → Closed Captioning → Off. Smart TVs (Samsung/LG/Sony/TCL): press the CC or Subtitle button, or open Settings → Accessibility → Captions and toggle off. On cable/satellite boxes, use the box remote's CC button rather than the TV remote — the box setting overrides the TV.
What file format do closed captions use?
The four dominant formats: SRT (SubRip, .srt) — the most widely supported format, accepted by YouTube, most video editors, and social platforms. WebVTT (.vtt) — HTML5-native, supports CSS styling and positioning. TTML/DFXP (.ttml, .dfxp) — XML-based, used by Netflix (IMSC 1.2 profile), broadcast, and enterprise workflows. SCC (Scenarist Closed Captions, .scc) — carries EIA-608 codes for US broadcast television. SRT and VTT cover most day-to-day web workflows.
What is SDH?
SDH stands for Subtitles for the Deaf and Hard-of-Hearing. It is a hybrid: the content of closed captions (speaker labels and non-speech audio cues) packaged as a subtitle track. On Netflix, Apple TV+, Prime Video, and Disney+, an "English SDH" track behaves like closed captions but is delivered through the subtitle stream. Traditional closed captions used EIA-608/CEA-708 broadcast standards; SDH uses subtitle file formats (SRT, VTT, DFXP). For accessibility compliance both are treated equivalently.
Are auto-generated captions ADA compliant?
Generally no — not on their own. WCAG 2.1 SC 1.2.2 requires captions that accurately reproduce dialogue and sufficient non-speech audio information. YouTube, Zoom, Teams, and Meet auto-captions typically achieve 85–92% accuracy on clean single-speaker English and drop to 60–75% on accented English, technical vocabulary, or noisy audio. Both DOJ guidance and settled ADA case law increasingly interpret compliance as requiring adequate quality, not merely the presence of a caption track. Auto-captions are a starting point; a human editorial pass is what makes a caption file defensibly compliant.
What is WCAG 2.1 SC 1.2.2?
WCAG 2.1 Success Criterion 1.2.2 (Level A) requires that captions be provided for all prerecorded audio content in synchronized media — in plain terms, any recorded video that has audio must carry a caption track. It is the operative rule for prerecorded web video. Its companion SC 1.2.4 (Level AA) applies the same requirement to live synchronized media (webinars, live streams). The full text is at w3.org/TR/WCAG21/#captions-prerecorded. WCAG 2.1 is the technical baseline adopted by the DOJ Title II Final Rule.
Does the European Accessibility Act require captions?
Yes. The European Accessibility Act (Directive (EU) 2019/882) has been in force since June 28, 2025 and requires accessibility — including captions on audiovisual content and video communication — for private-sector digital services sold in the EU. Covered categories include e-commerce, consumer banking, e-books, ticketing, ATMs, smartphones, and audiovisual media services. Existing service contracts have a transition window through June 28, 2030. The Directive references the harmonized standard EN 301 549, which incorporates WCAG success criteria for captions.