Found me on Upwork? If you found me through Upwork and want to work together, please contact me through Upwork. Messages from Upwork clients sent outside Upwork will not be answered.
Step-by-step guide🎬 Captioning & Subtitles

ADA, CVAA, and Section 508: when is video captioning legally required?

CVAA covers broadcast-to-internet reposts; Section 508 covers federal ICT (WCAG 1.2.2/1.2.4); ADA Title III covers movie theaters. Deliverable for each.

Dao Huy (Lucas)8 min read8 steps
ADA, CVAA, and Section 508: when is video captioning legally required?

💡 Three US laws govern video captioning compliance. CVAA (FCC-enforced) requires TV distributors to caption internet reposts of content that previously aired captioned on TV; original web-only video is not covered. Section 508 requires federal agencies to meet WCAG 1.2.2 (prerecorded, Level A) and 1.2.4 (live, Level AA) for all ICT video. ADA Title III requires movie theaters to show captioned digital films when available. For broadcast, deliver SCC; for federal web, deliver WebVTT or TTML/IMSC.

Key takeaways

  • CVAA/FCC Part 79: covers internet video only if the same content previously aired captioned on US TV. Original internet-only content (YouTube Originals, Netflix Originals, TikTok) is not covered.
  • Section 508 (Revised, January 2018): prerecorded federal video requires WCAG 1.2.2 (Level A); live federal video requires WCAG 1.2.4 (Level AA). Deliver WebVTT or SRT via HTML5 <track kind="captions">.
  • ADA Title III: movie theaters must provide closed movie captioning (CMC) when screening a digital film distributed with that feature. No obligation if the distributor never added CMC to the DCP.
  • Broadcast TV delivery: seconv input.srt ScenaristClosedCaptionsDropFrame --fps:29.97 --output-folder:out --overwrite for SCC (CEA-608, semicolon-separated drop-frame timecodes). CEA-608 is Latin-only. Vietnamese, Chinese, and CJK text must go as separate subtitle tracks.
  • Courts have extended ADA Title III to websites. WCAG 1.2.2 and 1.2.4 at Level AA are the standard expected by most ADA digital-accessibility consent decrees.

What do the ADA, CVAA, and Section 508 each cover for video captions?

Three distinct US laws govern video captioning requirements. Each has a different enforcement agency, a different definition of who must comply, and a different threshold for covered content. Understanding which law applies is the first step before choosing a deliverable format.

The CVAA (21st Century Communications and Video Accessibility Act, 2010) gave the FCC authority to require captions on internet-distributed video. The rule is narrow: if programming aired on US television with captions, it must carry those captions when the same distributor posts it online. Full-length programming phased in by January 2012. Video clips of previously aired content phased in between January 2016 and July 2017 depending on clip type. Original content that never aired on TV is not covered.

Section 508 (Rehabilitation Act Revised Standards, effective January 2018) governs ICT accessibility for federal agencies and their procurement. It incorporates WCAG 2.0 at Level A and Level AA by reference. For video, the operative criteria are WCAG 1.2.2 (prerecorded synchronized media, Level A) and WCAG 1.2.4 (live synchronized media, Level AA). No specific caption file format is mandated; the player must support captions and give users control.

ADA Title III covers public accommodations. The DOJ's 2016 rule specifically requires movie theaters to provide closed movie captioning when screening a digital film distributed with that feature. For website video content, ADA Title III's reach has been shaped by litigation: courts have consistently found that WCAG 2.1 Level AA compliance satisfies the effective-communication standard for digital accessibility.

Law-by-law comparison: who is covered and what do I deliver?

This is the table I return to at the start of every new project to confirm which requirement applies:

LawWho must complyContent coveredCaption requirementTypical deliverable
FCC Part 79 / CVAA - broadcast TVTV broadcasters, cable operators, satellite providersAll pre-recorded and live programming aired on US TVClosed captions required; 4 quality benchmarks: accuracy, synchronicity, completeness, placement (47 CFR § 79.1(j)(2))SCC (.scc, CEA-608) for broadcast; SMPTE-TT ST 2052-1 (.xml) for 708-class delivery
FCC Part 79 / CVAA - internet videoSame distributors posting online; third parties for full-length contentInternet versions of content that previously aired captioned on US TV; clips phased in 2016-2017Same quality benchmarks; original web-only content is not coveredSCC, SRT, WebVTT, or TTML/IMSC - format not mandated, must display correctly
Section 508 (2018) - prerecordedFederal agencies; contractors supplying ICT to federal agenciesPre-recorded video with audio on federal websites, intranets, and appsWCAG 1.2.2 Level A: captions for all pre-recorded synchronized mediaWebVTT or SRT via HTML5 <track kind="captions">
Section 508 (2018) - liveFederal agenciesLive video with audio (webinars, congressional streams, agency broadcasts)WCAG 1.2.4 Level AA: live captions requiredLive WebVTT/SRT feed or CART service
ADA Title III - movie theaters (DOJ rule, 2016)Movie theater operators (public accommodations)Digital films distributed with closed movie captioning availableMust provide CMC when screening a captioned digital film; no obligation if distributor never added CMCCMC data in DCP or via device-based track (Sony DCCS, CaptiView)

Which format do I actually produce for each scenario?

Once I know which law applies, the format choice follows from the delivery channel. For broadcast TV and CVAA internet delivery where the client expects a broadcast-compatible file, I produce SCC or SMPTE-TT with SeConv. Here are the two commands I use in US broadcast and streaming work:

# SCC for broadcast delivery (CEA-608, 29.97 drop-frame timecodes)
seconv input.srt ScenaristClosedCaptionsDropFrame --fps:29.97 --output-folder:out --overwrite

# SMPTE-TT ST 2052-1 for 708-class streaming delivery
seconv input.srt SMPTE-TT2052 --output-folder:out --overwrite
  • ScenaristClosedCaptionsDropFrame: produces a .scc file with semicolon-separated drop-frame timecodes (00;00;01;00). CEA-608 is Latin-only - other languages must be separate subtitle tracks.
  • SMPTE-TT2052: produces a TTML/XML file. Unicode, so it handles any language. Deliver a second SMPTE-TT with xml:lang="vi" for a Vietnamese subtitle track.
  • --fps:29.97: sets the frame rate written into the SCC timecodes. Required for broadcast; not needed for SMPTE-TT (which uses millisecond timestamps).

For Section 508 (federal web), I produce WebVTT from SRT with SeConv's WebVTT format name, then attach it via the HTML5 <track> element. No FPS flag needed:

seconv input.srt WebVTT --output-folder:out --overwrite

For ADA theater compliance, the captioning data is embedded in the DCP during the digital mastering workflow. It cannot be added after the DCP is complete. The standard for cinema subtitle data is SMPTE ST 428-7 subtitle XML - this needs DCP authoring tools, not a standalone caption converter.

What video content falls outside all three laws?

Original internet-only video does not fall under any of these three laws directly. A YouTube channel, TikTok account, independent streaming series, or e-commerce site's product videos are not covered by the CVAA, Section 508, or the ADA movie-theater rule.

  • YouTube Originals and Netflix Originals - commissioned exclusively for online platforms, never broadcast on TV with captions
  • Internal company training videos not shared publicly
  • Personal video communications and private calls
  • Video on a privately owned website, unless it provides services to a federal agency (which triggers Section 508 for that work product)

That said, the landscape is shifting. The DOJ's 2024 final rule under ADA Title II requires state and local government websites to meet WCAG 2.1 Level AA, which includes 1.2.2 (prerecorded captions) and 1.2.4 (live captions). And under Title III, courts have repeatedly found that inaccessible business websites violate the ADA's effective-communication standard. For any commercial platform with a broad public audience, WCAG 1.2.2-compliant captions are now a standard risk-mitigation practice.

What can I do myself, and when does a compliant deliverable need a specialist?

Section 508 compliance for federal web video is entirely self-service: produce a clean SRT in Subtitle Edit, run seconv input.srt WebVTT --output-folder:out --overwrite, and attach the .vtt file via <track kind="captions" srclang="en" src="captions.vtt" default>. That satisfies WCAG 1.2.2. No specialized broadcast knowledge needed.

For CVAA broadcast delivery, the bar is higher. SCC requires correct drop-frame timecode. A source file at 23.976 or non-drop needs a frame-rate conversion step first. The four FCC quality benchmarks also require a QC pass: accuracy, sync, completeness, and placement. For SCC files, I always run a caption-inspector decode to verify the byte-level encoding and PAC row assignments before submitting to a broadcaster.

ADA theater compliance is a production-chain issue. Closed movie captioning is authored as part of the DCP package at the digital mastering stage. If a deliverable requires CMC and it is not in the production spec from the beginning, adding it later means rebuilding the DCP.

For US broadcast or streaming delivery where FCC quality benchmarks apply, my caption QC service covers the full benchmark review: accuracy check, sync and completeness verification, caption-inspector decode for SCC files, and delivery-ready format conversion.

FAQ

Does the CVAA require captions on Netflix Originals or YouTube Originals?

No. The CVAA covers content that previously aired captioned on US TV and is then redistributed online by the same distributor. Content commissioned and published exclusively for an online platform - Netflix Originals, YouTube Originals, Hulu exclusive series - was never broadcast on TV and falls outside the CVAA's scope. These platforms add captions under their own policies and contractual requirements.

Does Section 508 apply to a contractor building a website for a federal agency?

Yes, in most cases. The Revised 508 Standards apply to ICT that is "procured, developed, maintained, or used" by federal agencies. A contractor building a web application for a federal client must deliver a Section 508-conformant product under the Federal Acquisition Regulation (FAR). The contractor's own marketing site is not covered - only the deliverable provided to the federal agency.

Can auto-captions alone satisfy WCAG 1.2.2 for Section 508 compliance?

No. WCAG 1.2.2 requires accurate captions that include non-speech audio information. Auto-captions from YouTube or Whisper can generate a first draft, but they regularly miss proper nouns, produce no speaker identification or sound-effect notation, and can have timing gaps. Section508.gov guidance notes that auto-captioning alone is insufficient. After a human correction pass, export to WebVTT with SeConv and attach it via the HTML5 <track> element.

What is the ADA movie theater rule, and does it require captions on all films?

The DOJ's rule, effective December 20, 2016, requires movie theater operators to provide closed movie captioning when showing a digital film that was distributed with that feature. It does not require theaters to add CMC to films that were never distributed with it. The rule covers digital projection (DCP). If a studio does not include CMC data in the DCP, the theater has no obligation to add it after the fact.

How does the DOJ's 2024 ADA Title II web rule affect video captions on government sites?

The DOJ's 2024 final rule under Title II requires state and local government websites and apps to conform to WCAG 2.1 Level AA. This includes Success Criterion 1.2.2 (captions for prerecorded synchronized media) and 1.2.4 (live captions). Title II covers state and local governments; private businesses remain under Title III, which does not yet have a parallel web-specific rule.

Official Sources

Dao Huy (Lucas)
Dao Huy (Lucas)
Graduate, University of Foreign Language Studies, University of Da Nang. Signs a certificate of accuracy on every certified translation (USCIS, IRCC).

Written by Dao Huy (Lucas), Vietnamese translator and localization specialist (English, Chinese and French into Vietnamese). See translation services →

Get QuoteWhatsApp