WCAG video accessibility requirements: A complete reference map

Introduction

If you manage video content for a government agency, you probably have a folder somewhere labeled "compliance" that you open with a sense of dread. Maybe you've seen "WCAG 2.1 Level AA" mentioned in a memo, or someone forwarded you a legal opinion about ADA Title II requirements. You know accessibility matters, but translating abstract guidelines into actual steps for your Tuesday morning council meeting feels overwhelming.

This guide is your translation tool. It maps all 26 Web Content Accessibility Guidelines (WCAG) 2.1 success criteria that apply to government video content—from recorded meetings to training videos to public announcements. Each requirement includes what it means in plain language, how it applies to the videos you actually produce, and practical examples from government contexts.

Think of this as your compliance roadmap. Whether you're planning new video projects or auditing existing content, you'll know exactly which requirements apply to your situation and what you need to do about them.

Legal and standards context

The Americans with Disabilities Act Title II regulations require state and local government entities to ensure their digital content is accessible. The technical standard referenced in these regulations is WCAG 2.1 Level AA. The compliance deadline is April 26, 2027 for most public entities.

WCAG 2.1 organizes accessibility requirements into three conformance levels:

Level A represents minimum accessibility. These are foundational requirements—if you don't meet them, you're creating significant barriers for people with disabilities. For video, this includes basics like captions on recorded content and keyboard-accessible player controls.

Level AA is the standard most government agencies must meet. It builds on Level A with additional requirements like real-time captions for live meetings and audio descriptions for recorded videos. This is your compliance baseline.

Level AAA represents enhanced accessibility. These requirements—like sign language interpretation and extended audio descriptions—aren't typically mandated by law, but they significantly improve access for specific user groups. Some agencies choose Level AAA standards for high-priority content.

It's important to understand that meeting these requirements isn't a one-time checklist exercise. Accessibility is ongoing—new content gets added, staff changes, platforms update. The goal is building these standards into your regular workflow so accessibility becomes part of how you work, not an extra burden.

How to use this reference guide

This guide organizes WCAG criteria into five practical categories based on what they address:

Time-based media alternatives ensure audio and visual information reaches everyone. This includes captions for people who are deaf or hard of hearing, audio descriptions for people who are blind or have low vision, and transcripts for people who need written references.

Visual presentation covers how your video appears on screen—contrast requirements for captions and text overlays, font sizing, and visual design standards that ensure readability for people with low vision or color blindness.

Player controls and keyboard access ensure everyone can operate your video player, whether they use a mouse, keyboard, voice control, or other assistive technology. This includes requirements for play/pause buttons, volume controls, and caption toggles.

Safety and motion protect viewers from content that could trigger seizures or vestibular disorders. This covers restrictions on flashing content and requirements for controlling animations.

Technical implementation ensures your video player is properly coded so screen readers and other assistive technologies can interact with it. This includes semantic markup and ARIA labels.

Start by identifying which conformance level you need to meet. For most government agencies subject to ADA Title II, that's Level AA. Then review which requirements apply to your specific video types:

A typical government meeting recording needs synchronized captions (criteria 1.2.2 and 1.2.4)
If speakers reference visual materials like slides or documents, you need audio description (criterion 1.2.5)
If you embed video on your website, you need keyboard-accessible controls (criteria 2.1.1 and 2.1.2)
If you display captions on screen, they need sufficient contrast (criterion 1.4.3)

The reference document provides the complete list with government-specific examples for each requirement.

Real-world application

Let's walk through how this works with a common scenario: your monthly city council meeting.

Your meeting involves multiple speakers, a projected agenda on screen, occasional PowerPoint presentations, and public comment periods. Here's what WCAG requires:

For the live meeting stream, you need real-time captions (criterion 1.2.4). These captions must show who's speaking and what they're saying. If the mayor references a budget chart on the screen, that's visual information that needs audio description or verbal explanation (criterion 1.2.5).

For the archived meeting recording, you need synchronized captions (criterion 1.2.2) and audio description if visual materials were presented (criterion 1.2.5). You might also provide a full transcript for searchability and public records requests (criterion 1.2.8, Level AAA).

For the video player where people watch the archived meeting, you need keyboard-accessible controls (criterion 2.1.1), visible focus indicators (criterion 2.4.7), and proper ARIA labels on buttons (criterion 4.1.2). If captions appear on screen, they need 4.5:1 contrast ratio against the background (criterion 1.4.3).

If your website auto-plays the meeting video, you need an immediate pause button (criterion 2.2.2). If your video player offers caption customization, users need to be able to resize caption text (criterion 1.4.4).

That's 10 different WCAG criteria applying to a single monthly meeting—but once you understand the pattern, it becomes routine. You're not doing 10 separate tasks; you're executing an integrated workflow where accessibility is built in.

Here's another scenario: a training video for new employees about your permitting process. This video includes screen recordings of your online permit system, a narrator explaining each step, and on-screen text callouts.

Required: Synchronized captions showing the narration (criterion 1.2.2). Audio description explaining what's happening in the screen recordings—"The cursor moves to the 'Submit' button in the lower right corner" (criterion 1.2.5). Keyboard-accessible video player (criterion 2.1.1). Proper contrast for any on-screen text (criterion 1.4.3).

Recommended: A full transcript people can reference while watching or search later (criterion 1.2.8). Caption customization options so viewers can adjust text size (criterion 1.4.4).

The reference guide helps you identify which requirements apply to your specific content types and plan accordingly.

MediaScribe integration

MediaScribe supports several of these WCAG requirements through its workflow tools, but it's important to understand what MediaScribe handles and what requires organizational policy and human judgment.

MediaScribe helps directly with:

Caption creation and editing (supporting criteria 1.2.2 and 1.2.4): MediaScribe Live provides real-time captioning for meetings with editing capabilities. The system generates initial captions that your team can review and correct.
Caption formatting and display (supporting criterion 1.4.3): MediaScribe uses black text on white backgrounds for caption displays, meeting contrast requirements.
Content organization (supporting archival and retrieval): MediaScribe's Files section organizes meeting recordings with associated caption files for easy access.
Multiple output formats (supporting various distribution needs): MediaScribe exports captions in standard formats (WebVTT, SRT) compatible with different video players.

MediaScribe does not:

Determine which videos need audio description—that requires human review based on content
Guarantee caption accuracy without human review—AI-generated captions need correction
Control how video players are embedded on your website—that's a web development task
Replace organizational accessibility policies—MediaScribe is a tool that supports your workflow

The key distinction: MediaScribe reduces the manual effort required to operationalize accessibility, but your organization remains responsible for policy decisions, quality review, and ensuring complete compliance.

Summary

WCAG 2.1 Level AA is the technical standard for ADA Title II compliance, with 26 success criteria applying to video content
Requirements are organized into three conformance levels: Level A (minimum), Level AA (standard), and Level AAA (enhanced)
Five key areas affect video: time-based media alternatives, visual presentation, player controls, safety considerations, and technical implementation
Government meeting recordings typically require captions, audio description for visual elements, keyboard-accessible players, and proper contrast
Different video types (live meetings, archived recordings, training videos) trigger different combinations of requirements
The reference document provides government-specific examples for each criterion to help you identify what applies to your content
MediaScribe supports compliance workflows through captioning tools and content organization, but organizations remain responsible for policy, review, and complete implementation

What's next

Download the complete WCAG criteria reference document to keep as a planning and audit tool. Use it when scoping new video projects to identify requirements upfront, and when reviewing existing content to spot gaps. The checklist format helps you work systematically through each requirement rather than feeling overwhelmed by the full scope of accessibility obligations.

Remember: accessibility isn't about perfection from day one. It's about building sustainable practices that serve your entire community. Start with your most-viewed content, apply these standards consistently, and expand your accessibility practices over time.