Video accessibility under ADA Title II requires that all government video content, including YouTube uploads and live streams, meet WCAG 2.1 AA standards for captions, audio description, and usability.
In nearly every ADA accessibility audit we conduct for government agencies, the same conversation happens when we get to video content.
"We have a YouTube channel. Do we need to worry about that?"
The honest answer is yes — and for most agencies, the current state of their video content creates more ADA exposure than they realize.
The follow-up question is always some version of: "We have hundreds of videos going back years. Are we really expected to fix all of them?"
The honest answer to that one is more nuanced. You are expected to have a plan, a going-forward standard, and a documented remediation program. The specific scope of what you need to fix depends on the content, when it was published, and how central it is to your agency's public service delivery.
This guide covers everything a government agency needs to know about video accessibility under ADA Title II — what the law actually requires, what "accessible video" means technically, how to evaluate your existing video backlog, how to build a going-forward standard, and what the most common failures look like and how to fix them.
What the Law Requires
ADA Title II requires that government agencies provide equal access to their programs, services, and activities — including digital content and communications. Video content published by a public agency as part of its public communications, service delivery, or program delivery falls within this obligation.
The DOJ's 2024 final rule establishing WCAG 2.1 AA as the technical standard for digital accessibility addresses video specifically through the WCAG success criteria that govern time-based media. The relevant criteria are:
1.2.1 Audio-only and Video-only (Prerecorded) — Level A Pre-recorded audio-only content requires a text transcript. Pre-recorded video-only content (video with no audio track) requires either a text alternative or an audio track.
1.2.2 Captions (Prerecorded) — Level A All pre-recorded video content that contains audio must have synchronized captions.
1.2.3 Audio Description or Media Alternative (Prerecorded) — Level A Pre-recorded video must have either an audio description or a text alternative that provides equivalent information for content conveyed visually but not through audio.
1.2.4 Captions (Live) — Level AA Live video that contains audio — live-streamed council meetings, live press briefings, live emergency communications — must have real-time captions.
1.2.5 Audio Description (Prerecorded) — Level AA Pre-recorded video must have audio description for all content conveyed visually that is not conveyed through the existing audio.
These five criteria together define what accessible video means under WCAG 2.1 AA. Captions for pre-recorded video is Level A — the most fundamental requirement. Audio description for pre-recorded video where it is needed is Level AA. Live captions for live video is Level AA.
All of these apply to government video content. Including your YouTube channel.
Government Video Accessibility Checklist
- Human-reviewed captions (not auto-generated)
- Accurate synchronization with audio
- Speaker identification when needed
- Non-speech audio described
- Audio description for visual content
- Real-time captions for live streams
- Accessible video descriptions (text summaries)
- Caption files uploaded (not default auto captions)
Caption Requirements for Government Videos (WCAG 2.1 AA)
Captions are the most universally understood video accessibility requirement and the most universally misunderstood in terms of what "captions" actually means for compliance purposes.
Why YouTube Auto Captions Do Not Meet ADA Requirements
This is the most important thing to understand about YouTube video accessibility. YouTube's automatic captions — the captions that appear when a video is uploaded and YouTube's speech recognition processes the audio — do not meet WCAG 2.1 AA requirements for most government video content.
Auto-generated captions achieve approximately 80 percent accuracy under good audio conditions. Under poor audio conditions — a council chamber with room echo, a field interview with wind noise, a recorded phone call with compression artifacts, a speaker with an accent that YouTube's speech recognition is not trained for — accuracy drops significantly below that.
80 percent accuracy means one in five words may be incorrect. For a council member making a motion on a budget item, for a health official communicating COVID guidance, for a public works director explaining a service disruption, one in five words incorrect is not acceptable. The captions are not communicating the same information the audio is communicating. They are communicating an approximation that may be misleading.
WCAG does not specify an exact accuracy percentage for captions. The requirement is that captions be "equivalent" to the audio — that they convey the same information. Auto-generated captions that produce meaningful errors in substantive government communications are not equivalent. A caption that reads "the council approves the meditation" when the audio says "the council approves the motion" is not equivalent. It is a false statement.
The caption quality standard for government video content is human-reviewed captions with an accuracy rate that would be expected of a professional court reporter — typically cited at 99 percent or better for substantive spoken content.
Captions vs Transcripts (What ADA Actually Requires)
Captions are synchronized — they appear at the correct time relative to the audio, allowing a viewer to read the captions in sync with watching the video. Transcripts are text documents of the spoken content, not synchronized with the video.
Both are required in different contexts under WCAG. Captions are required for all pre-recorded video with audio (1.2.2). Transcripts may satisfy 1.2.3 as the text alternative option for Level A compliance, but captions are required for Level AA (1.2.5 context and 1.2.4 for live content).
A transcript is not a substitute for captions. A viewer who is deaf or hard of hearing watching a video needs captions — not a separate document they would have to read while trying to follow the visual content of the video. A transcript is an additional useful resource, not a replacement for synchronized captions.
Caption Formatting Requirements
Captions must not only be accurate — they must be readable. Common caption formatting failures that degrade usability even when the text is accurate:
Line length. Captions that display more than two lines at a time, or lines that extend beyond the readable width of the video frame, require more reading time than the audio allows. The standard for readable captions is a maximum of two lines, displayed for sufficient time to read at a comfortable pace.
Speaker identification. When multiple speakers are present — a panel discussion, a council meeting with multiple council members speaking, a press conference with questions from reporters — captions should identify who is speaking. This is particularly important for government meetings where understanding who is making a motion or who is asking a question is substantively significant.
Sound effects and non-speech audio. Captions must include descriptions of significant non-speech audio — [applause], [phone ringing], [alarm sounds] — that conveys information relevant to the video content. A council meeting recording that captions only the spoken content but does not indicate [gavel] or [vote taken] is missing context that affects comprehension.
Caption placement. Default bottom-center caption placement works for most content. When significant visual content appears at the bottom of the frame — lower-third graphics, charts, on-screen text — captions should be repositioned to avoid obscuring that content.
Audio Description Requirements for Government Videos
Captions serve viewers who are deaf or hard of hearing. Audio description serves viewers who are blind or have low vision — it provides spoken narration of visual content that is not conveyed through the existing audio track.
Audio description is required for pre-recorded video under WCAG 1.2.5 (Level AA) when the video contains visual content that is not conveyed through the audio. If a video shows a speaker presenting a chart that is never described in the audio, a person who is blind receives no information about the chart. If a training video shows a step-by-step physical process that the narrator references without describing — "now do this" while demonstrating on screen — a blind viewer cannot follow the instruction.
Many government agencies have not thought seriously about audio description because captions are the more commonly discussed requirement. Here is a framework for determining which of your videos require audio description.
Videos that typically require audio description:
- Tutorial or how-to videos where the process is shown visually but not fully described in the narration
- Presentation recordings where the presenter refers to slides without reading their content aloud
- Field videos where what is happening is shown without verbal description — a public works crew making repairs, a controlled burn in progress, an environmental monitoring process
- Map or data visualization videos where geographic or statistical content is displayed without being narrated
- Event recordings where visual elements of the event — signage, crowd size, environmental context — are relevant to understanding what happened
Videos that typically do not require audio description:
- Talking head videos where a speaker is simply talking to camera with no additional visual content conveying information
- Videos with full audio narration that completely describes all visual content — if the narrator says "this bar chart shows that permit applications increased by 23 percent from 2023 to 2024" while the chart is on screen, the audio description is already provided
- Interview recordings where the visual content is simply the person speaking
The practical test is: if a blind person listened to only the audio of this video, would they receive all of the information the video conveys? If yes, audio description is not needed. If no — if there is visual information that the audio does not communicate — audio description is needed.
How to Add Audio Description to Existing Videos
Audio description can be added to existing videos in two ways:
Extended audio description: A second version of the video with additional narration inserted during natural pauses in the audio. This is the standard approach for videos with sufficient pauses in the existing audio.
Text-based alternative: A text document that provides equivalent information for all visual content not conveyed in the audio. This is an acceptable Level A alternative (1.2.3) and may be more practical for agencies with large video backlogs when the full audio description process is not immediately feasible.
For newly produced videos, the most efficient approach is to script and record audio description as part of production — writing narration that fully describes all visual content — rather than adding it post-production.
Live Video: Council Meetings, Press Briefings, and Public Events
Live-streamed government video — council meetings, board hearings, press briefings, public safety announcements, emergency communications — carries the WCAG 1.2.4 Level AA requirement for real-time captions.
Auto-generated live captions from YouTube or Zoom are subject to the same accuracy limitations as auto-generated captions for pre-recorded content — approximately 80 percent under good conditions, significantly lower under poor conditions.
For formal government proceedings — council meetings, board hearings, public hearings, and other meetings where the content of the proceedings is a public record — CART (Communication Access Realtime Translation) captioning is the appropriate standard. CART captioners are trained stenographers who produce real-time captions at approximately 99 percent accuracy. A CART provider joins the live stream as a panelist or through a separate integration and types captions directly into the caption display.
For less formal government live video — field updates, behind-the-scenes content, social media live video — auto-generated captions with a post-broadcast correction process may be an acceptable interim approach while a full CART integration is implemented.
What to Do With Live Meeting Archives
When a live-streamed council meeting or public hearing is posted as an archive recording, it transitions from live content to pre-recorded content — and the pre-recorded caption and audio description requirements apply. Auto-generated captions that were acceptable as live stream output need to be reviewed and corrected before the archived recording is published.
Most agencies post archived meeting recordings to YouTube with the auto-generated captions unchanged. This is a compliance failure. The archived recording is now pre-recorded content subject to 1.2.2, which requires accurate synchronized captions.
The archive caption review process should be built into the meeting publication workflow — not treated as an optional post-processing step.
The Backlog Question: How to Handle Years of Existing Video Content
This is the question that creates the most anxiety in audit conversations. An agency has five years of YouTube content — hundreds of videos — and wants to know whether they have to remediate all of it.
The answer depends on a principle that runs through the entire ADA compliance framework: risk-based prioritization. Not everything needs to be done at once. Everything needs to be on a documented plan.
How to Triage Your Video Library
Evaluate your existing video library using these classification criteria:
Tier 1 — Remediate Immediately:
Videos that are directly connected to public service delivery and currently in active use. A how-to video for completing a permit application. A tutorial for the online payment portal. An explanatory video about a current regulation or requirement. A water safety or public health guidance video currently linked from the agency website. These videos are part of current service delivery. Their inaccessibility creates current barriers.
Videos connected to time-sensitive regulatory or legal requirements. A public hearing recording from a contested land use matter. A board meeting recording where significant votes occurred. A public notice video. These have legal significance beyond general public interest.
Any video that has received an accessibility complaint or that an accessibility report has flagged as creating a specific barrier for an identified user.
Tier 2 — Remediate Within 6 to 12 Months:
Videos from the past two to three years that receive significant ongoing traffic. Public awareness campaigns still being promoted. Informational videos still linked from agency web pages. Training videos still in use for staff or community education.
Council meeting recordings and board meeting archives from the past 12 to 18 months that are referenced in ongoing public processes.
Tier 3 — Remediate on a Rolling Schedule:
Older informational content that is no longer actively promoted but remains publicly accessible. Council meeting archives older than 18 months. Event recordings and ceremonial content. Press releases and communications that addressed time-limited issues now resolved.
Tier 4 — Consider Removing or Restricting:
Content so old or so low-traffic that remediation cost clearly exceeds accessibility benefit. Content that has been superseded by newer versions of the same information. Content that is no longer relevant or accurate.
Removing a video from public access is a legitimate compliance option for content that is not essential and not worth remediating. An agency that removes low-value, inaccessible content and documents the removal decision is managing its compliance posture more effectively than one that leaves a vast inaccessible archive online with no remediation plan.
How to Document the Backlog Plan
The documentation of your video remediation plan is as important as the plan itself. The compliance record for video accessibility should include:
A complete inventory of your video library with URLs, titles, publication dates, and current view counts.
A classification of each video by remediation tier with the reasoning documented.
A remediation schedule with target completion dates for each tier.
A log of completed remediations — each video remediated, the date caption review was completed, and the date audio description was added where required.
An ongoing monitoring notation — a schedule for reviewing the accessibility of newly published videos before they go live.
This documentation is what turns a reactive remediation effort into a proactive compliance program. The difference matters in an enforcement context.
The Going-Forward Standard: New Videos Published After Today
The backlog conversation is about catching up. The going-forward standard is about stopping the problem from getting worse while you do.
From this point forward, every video your agency publishes should meet these requirements before it goes live:
Human-reviewed captions. For every video with a spoken audio track, upload a reviewed caption file — not rely on YouTube auto-captions. The review process does not need to be performed by a professional captioner for all content. A staff member can review and correct auto-generated captions for most videos. The investment is time, not necessarily money.
Audio description where needed. For every video that contains visual content not fully conveyed by the audio track, add audio description or a text alternative before publishing.
Accessible video description on YouTube. Every YouTube video should have a description that provides the key information conveyed in the video in text form. This is not a substitute for captions — it is a supplementary resource that also serves SEO purposes.
Caption files uploaded, not just auto-generated. YouTube allows creators to upload SRT or VTT caption files. Uploading a reviewed caption file replaces YouTube's auto-generated captions with accurate captions. For each video, the caption upload step should be part of the standard publication checklist.
How to Add and Manage Captions on YouTube
For agencies managing captions on YouTube, here is the practical workflow.
Adding Reviewed Captions to Existing Videos
- Go to YouTube Studio.
- Select the video you want to caption.
- Click "Subtitles" in the left sidebar.
- Click "Add" next to the language.
- Select "Upload file" and upload your reviewed SRT or VTT caption file.
To obtain the auto-generated captions as a starting point for review:
- In YouTube Studio, go to Subtitles for the video.
- Under "Published" captions, click the three dots next to "English (automatic)."
- Select "Download" and choose SRT format.
- Open the SRT file in a text editor or caption editing software.
- Review and correct errors — name misspellings, technical terms, proper nouns, and any phrase that is incorrectly transcribed.
- Upload the corrected file back to YouTube as a new subtitle track.
- Set the reviewed captions as the published track.
Caption Editing Tools
YouTube's built-in caption editor: YouTube Studio includes a caption editor that allows you to edit caption text and timing in-browser. This works well for simple corrections but can be slow for full caption reviews.
Rev.com: A professional captioning service that can produce reviewed captions from auto-generated starting points at per-minute pricing. Appropriate for high-priority content or high-volume workflows.
Otter.ai: An AI transcription tool that produces text transcripts that can be converted to caption format. More accurate than YouTube's auto-generation for some content types. Requires review before use.
Aegisub: A free, open-source caption editor with professional timing and formatting controls. Has a steeper learning curve than YouTube's built-in editor but provides more control for complex caption formatting.
MacCaption / CaptionMaker: Professional desktop captioning software used by broadcast and media companies. Appropriate for agencies with significant ongoing video production.
The Accessible YouTube Channel: Beyond Captions
Captions and audio description address the content accessibility of individual videos. Several additional elements affect the accessibility of a YouTube channel as a whole.
Video Titles and Descriptions
YouTube video titles and descriptions are indexed text content that affects both accessibility and discoverability. Accessible video titles:
Describe the content of the video specifically — "Springfield City Council Regular Meeting — March 15, 2026" rather than "Council Meeting 3/15."
Avoid title-casing that makes text harder to read for users with dyslexia — "Springfield City Council Regular Meeting" not "SPRINGFIELD CITY COUNCIL REGULAR MEETING."
Video descriptions should include key information conveyed in the video in text form. For a council meeting video, the description should include the agenda items discussed and any significant votes taken. For a tutorial video, the description should include the steps demonstrated. This text serves users who cannot access the video content and serves the agency's search discoverability simultaneously.
Playlist Organization
YouTube playlists organize related video content for easier navigation. Accessible playlist organization:
Uses descriptive playlist names — "City Council Meetings 2026" rather than "Meetings."
Organizes videos consistently — council meetings in chronological order, service tutorial videos grouped by service type.
Provides a description for each playlist explaining what the playlist contains.
Thumbnails
Video thumbnails are images. If thumbnails contain text — "Emergency Notice," "Water Quality Update," "How to Apply" — that text is embedded in an image and is not accessible to screen reader users browsing YouTube. YouTube does not currently support alt text on thumbnails. The compensating approach is to ensure the video title conveys the same information the thumbnail text conveys.
A Note on Embedded Videos on Agency Websites
When a government agency embeds a YouTube video on its own website, the accessibility obligations extend to how the video is embedded.
The video player must be keyboard accessible — play, pause, volume, captions toggle must all be operable without a mouse. YouTube's standard embed player generally meets this requirement, but custom video players or custom embed implementations may not.
The captions that work in YouTube must also work in the embedded player. If you have uploaded reviewed caption files to YouTube, those captions should be available in the embedded player. Verify this — not all embed configurations pass caption functionality through correctly.
If a video is embedded without captions available in the player, the agency website must provide an accessible text alternative — either a link to the captioned YouTube version or a transcript of the video content adjacent to the embedded player.
Building the Video Accessibility Program
Video accessibility is not a one-time remediation project — it is an operational program that runs alongside your video production and publication workflow. The governance structure for video accessibility should include:
A going-forward publication checklist that confirms captions have been reviewed, audio description has been added where needed, and the video description has been written before any video goes live.
A named owner responsible for the video accessibility checklist — typically the staff member who manages the YouTube channel.
A remediation queue for the backlog — the tiered inventory with target completion dates and assigned ownership.
Monthly monitoring — a brief review of recently published videos to confirm the going-forward standard is being followed and that no videos have been published without completing the checklist.
Documentation of every remediation action — each video remediated, the date of completion, and what was done — in the agency's central remediation log.
The video accessibility program does not need to be large or expensive. It needs to be consistent, documented, and improving over time.
Related:
FAQ: YouTube and Video Accessibility for Government Agencies
Are YouTube videos published by a government agency required to be accessible under ADA Title II? Yes. Video content published by a public agency as part of its public communications, service delivery, or program delivery falls within the ADA Title II obligation. WCAG 2.1 AA — the technical standard established by the DOJ's 2024 final rule — includes specific success criteria for video accessibility: accurate synchronized captions for pre-recorded video with audio (1.2.2), audio description for visual content not conveyed through the audio track (1.2.5), and real-time captions for live video (1.2.4). YouTube channels operated by government agencies are within the scope of these requirements.
Are YouTube's auto-generated captions sufficient to meet ADA Title II requirements? No. YouTube's auto-generated captions achieve approximately 80 percent accuracy under good conditions — meaning one in five words may be incorrect. WCAG 2.1 AA requires captions that are equivalent to the audio content. Auto-generated captions that produce meaningful errors in government communications — incorrect votes, incorrect dates, incorrect names, incorrect instructions — are not equivalent. Government agencies must upload human-reviewed caption files that achieve a high level of accuracy, not rely on YouTube's automatic speech recognition output.
What is audio description and which government videos require it? Audio description is spoken narration added to a video that describes visual content not conveyed through the existing audio — charts, maps, on-screen text, physical processes, environmental context. It is required under WCAG 1.2.5 (Level AA) for pre-recorded video where significant information is conveyed visually but not described in the audio track. Government videos that typically require audio description include tutorial videos where processes are shown but not fully narrated, presentation recordings where slides are displayed but not read aloud, field videos where what is happening is shown without verbal description, and data visualization videos where charts or maps are displayed without being narrated.
Does a government agency need to caption all of its existing YouTube videos? The obligation is to have a documented, risk-based remediation plan — not necessarily to caption all existing videos simultaneously. A tiered approach is appropriate: Tier 1 (videos directly connected to current service delivery or legal significance) should be addressed immediately; Tier 2 (videos from the past two to three years with ongoing traffic) should be addressed within 6 to 12 months; Tier 3 (older content with lower traffic) should be addressed on a rolling schedule; Tier 4 (superseded or negligible-value content) should be considered for removal. The critical requirement is that the plan is documented, the tiers are defensible, and remediation is actually progressing on the stated schedule.
What does accessible live video require for government agencies? Live-streamed government video — council meetings, board hearings, press briefings, emergency communications — requires real-time captions under WCAG 1.2.4 (Level AA). For formal public proceedings where the content is a legal record, CART (Communication Access Realtime Translation) captioning is the appropriate standard — professional real-time stenography achieving approximately 99 percent accuracy. Auto-generated live captions from YouTube or Zoom are insufficient for formal government proceedings. When archived recordings of live streams are published as permanent video content, they must have reviewed, accurate captions — the auto-generated captions from the live stream must be corrected before publication.
What is the most efficient process for a government agency to caption its YouTube backlog? The most efficient backlog captioning process starts with prioritizing by tier — highest-traffic, highest-impact videos first. For each video: download the auto-generated SRT caption file from YouTube Studio, open it in a caption editing tool or text editor, review and correct errors (focusing on proper nouns, technical terms, procedural information, and any phrase that is meaningfully incorrect), upload the corrected caption file to YouTube as a new subtitle track, and set the reviewed file as the published track. For agencies with large backlogs, professional captioning services like Rev.com can process videos at per-minute pricing, which may be more cost-effective than staff time for high-volume remediation.