WCAG Video Requirements for Streaming and Video Platforms

WCAG video requirements come down to three things: captions, audio description or a text alternative, and a player you can run from the keyboard. Five success criteria in Guideline 1.2 cover the media at Level A and AA, and each one asks something of you and your platform.

TL;DR:

• Five WCAG criteria apply to typical video at Level A and AA: 1.2.1 (audio-only and video-only), 1.2.2 (prerecorded captions), 1.2.3 (audio description or media alternative), 1.2.4 (live captions) and 1.2.5 (prerecorded audio description).
• WCAG 2.2 kept all five unchanged, and US rules for public bodies still point to WCAG 2.1 Level AA.
• Auto-generated captions only pass once a person has checked them, because captions must carry meaningful sounds as well as speech.
• The player counts too: play, pause, volume, the caption toggle and seeking must all work from the keyboard (2.1.1).
• AIOZ Stream stores your caption files as .vtt transcripts, one per language. Its docs describe no audio description track type and no live captioning, so plan those two separately.

Updated Oct 19, 2026: new title, a criteria diagram and a platform checklist. We added sourced 2026 DOJ and HHS deadlines, rechecked the AIOZ Stream section against the current docs and added References.

What does WCAG require for video?

You will see "WCAG compliance for video" used loosely, but the standard is specific. The video rules sit under Guideline 1.2 (Time-based Media), and at Level A and AA five of them apply to normal on-demand or live video:

• 1.2.1 Audio-only and Video-only (Prerecorded), Level A. Content with only sound or only pictures needs a text alternative.
• 1.2.2 Captions (Prerecorded), Level A. Recorded video with sound needs captions.
• 1.2.3 Audio Description or Media Alternative (Prerecorded), Level A. Recorded video needs audio description or a full text alternative.
• 1.2.4 Captions (Live), Level AA. Live video with sound needs captions during the broadcast.
• 1.2.5 Audio Description (Prerecorded), Level AA. Recorded video needs audio description, and a transcript no longer counts as a substitute.

The gap between 1.2.3 and 1.2.5 trips up many teams. At Level A, you can meet 1.2.3 with a full text alternative that describes what happens on screen, while at Level AA, 1.2.5 asks for the audio description itself. Most public sites and the US public-sector rules target Level AA, so in practice you need both captions and audio description.

W3C notes one useful exception: if the soundtrack already conveys everything important in the picture, you need no extra audio description. A talking-head interview where the speaker names every chart they show may already pass, while a product demo with silent screen recordings will not.

WCAG 2.2, published in 2023, added new criteria elsewhere but left 1.2.1 to 1.2.5 as they were. Level AAA adds four more media criteria (sign language, extended audio description, a full media alternative and live audio-only alternatives), but few laws require AAA, so this guide stops at AA.

Do auto-generated captions meet WCAG?

Not on their own, because criterion 1.2.2 asks for captions of all meaningful audio, and that includes sounds that matter to the story. A doorbell, applause or a phone ringing all belong in the caption file when they change what a viewer understands.

Speech-to-text tools handle clean dialogue well, but they still miss product names and jargon, and they mispunctuate in ways that change meaning. They also skip sound cues, because they only listen for speech, so a file that passes a "captions exist" check can fail a real audit.

The fix is cheap: run the auto captions, then have a person edit them before you publish. Add speaker names where two people talk, and add sound cues in brackets. If you want the format details, our guide to SDH versus closed captions covers what goes into the file.

What should a WCAG-compliant video platform provide?

The media criteria cover the content, while your platform and player decide whether viewers can reach it. When you evaluate a video platform for WCAG, check these points:

• Caption tracks per language. You should be able to upload your own edited caption file and pick a default track.
• A caption toggle in the player. Viewers must be able to turn captions on and off, and the text must stay readable against the video.
• Keyboard control. Criterion 2.1.1 (Keyboard, Level A) says play, pause, volume, captions and seeking must all work without a mouse. Criterion 2.1.2 says focus must never get stuck inside the player.
• Visible focus. Criterion 2.4.7 (Level AA) asks that you can see which control has keyboard focus.
• No surprise audio. Criterion 1.4.2 (Level A) says audio that plays on its own for more than 3 seconds needs a way to pause it or turn it down.
• A home for audio description. You need either a second audio track or a way to publish a described version of the video.
• Live captions, if you stream live and target Level AA.

Keyboard support depends on how the player and its embed are built, so test it yourself. Tab to the player, then start, pause and seek using only Enter, Space and the arrow keys. If you get stuck at any step, so will your viewers, and the W3C page on Understanding 2.1.1 Keyboard lists which interactions count.

The legal deadlines moved in 2026

The US public-sector timeline changed this year: on April 20, 2026, the Department of Justice published an interim final rule that pushed its ADA Title II dates back by one year. Public entities serving 50,000 people or more now have until April 26, 2027, and smaller entities and special district governments have until April 26, 2028.

The Department of Health and Human Services followed in May 2026 for Section 504. Recipients of HHS funding with 15 or more employees now have until May 11, 2027, and those with fewer than 15 employees have until May 10, 2028.

Neither rule changed the technical bar, since both still require WCAG 2.1 Level AA, which includes all five video criteria above. Section508.gov's guidance on synchronized media lists the same baseline for federal video.

Private businesses got no extension, because neither rule covers them, and ADA Title III lawsuits over inaccessible websites and video continue on their own timeline. If you run a private company, read the 2026 news as a public-sector change and keep your own plan on schedule.

How AIOZ Stream handles it

We checked AIOZ Stream against each criterion using the current docs and SDK. Caption files go through the Media Transcript API, where you upload your own .vtt file per language with a BCP 47 code such as en or fr-CA. Each video holds at most one transcript per language, and you mark one as the default the player loads. This is the request from the Media Transcript docs:

curl --location --request POST 'https://api.aiozstream.network/api/media/media_id/transcripts/en' \
  --header 'stream-public-key: your_public_key_here' \
  --header 'stream-secret-key: your_secret_key_here' \
  --form 'file=@"/path/to/your/transcript.vtt"'

The documented response returns the track's url, language, status, description and is_default. The Go SDK (v3.0.4) exposes the same tracks as captions with one extra field, is_generated. Because you upload the file yourself, an edited caption file covers 1.2.2, and the same text can serve as the text alternative for 1.2.1 and the Level A option in 1.2.3. The player settings also let you set a caption color, which helps you keep captions readable over your video.

What the docs don't cover yet:

• No audio description track type. For 1.2.5, publish a described version of the video as its own media item and link to it from the original.
• No live captioning in the live streaming docs. For 1.2.4, plan a captioning workflow outside AIOZ Stream before you go live.
• No statement on keyboard support in the player. Run the keyboard test above on your own embed.

We ran the same check for DRM on AIOZ Stream. For the full upload and default-track workflow across languages, see our multi-language captions guide. Next step: open the Media Transcript API docs and upload your first caption file.

FAQ

Does WCAG require captions for every video?
Captions apply to recorded and live video with sound (1.2.2 and 1.2.4). Audio-only or video-only content falls under 1.2.1, which asks for a text alternative instead.

Is a transcript enough to meet WCAG on its own?
For audio-only or video-only content, yes. For normal video, a transcript does not replace captions; it meets 1.2.3 at Level A, but Level AA (1.2.5) needs audio description.

Can AIOZ Stream generate WCAG-compliant captions automatically?
The documented API stores the caption files you upload, and whether a file meets WCAG depends on its accuracy and on a human review, so edit auto captions before you upload them.

Does AIOZ Stream support audio description tracks?
Not as a track type, so publish a described version of the video as a separate media item instead.

What is the difference between WCAG Level A and Level AA for video?
Level A covers prerecorded captions (1.2.2) and audio description or a text alternative (1.2.3). Level AA adds live captions (1.2.4) and requires the audio description itself (1.2.5), which is why most organizations target AA.

Did the 2026 ADA deadline changes apply to my business?
Only if you are a public entity under Title II or an HHS-funded organization under Section 504, because private businesses got no extension.

Related Reading

• Multi-language captions and transcripts on AIOZ Stream
• What Does SDH Mean in Subtitles? SDH vs Closed Captions
• Media Chapter vs Media Transcript API: The Real Differences
• Video SEO: How to Get Video Content Indexed by Google
• AIOZ Stream Video Player: Features and Customization Guide
• How to Embed the AIOZ Stream Player on Your Website

References

• W3C: Web Content Accessibility Guidelines (WCAG) 2.2: the text and levels of criteria 1.2.1 to 1.2.5, 1.4.2, 2.1.1, 2.1.2 and 2.4.7
• W3C: Understanding 1.2.5 Audio Description (Prerecorded): when no extra description is needed
• W3C WAI: Making Audio and Video Media Accessible: captions, description and player requirements
• Section508.gov: Synchronized Media: the federal baseline for video
• Duane Morris: DOJ Extends ADA Title II Digital Accessibility Deadlines by One Year: the April 20, 2026 interim final rule and new dates
• Federal Register: HHS Extension of Section 504 Compliance Dates: the May 2026 extension to 2027 and 2028
• AIOZ Stream Docs: Media Transcript: the upload request, response fields and one-per-language limit
• AIOZ Stream Docs: Player setup and customization: the caption color setting