If your WordPress site includes video content — product demos, tutorials, testimonials, or explainer videos — there’s a good chance you’re unintentionally excluding a significant portion of your audience. Videos without captions, transcripts, or audio descriptions fail users who are deaf, hard of hearing, blind, or have cognitive disabilities. And increasingly, they also expose site owners to legal liability under the ADA and WCAG guidelines.
The accessibility requirements for video aren’t complicated, but they’re widely misunderstood and frequently skipped. This guide breaks down what WCAG requires, why it matters, and how to implement accessible video on your WordPress site.
Why Video Accessibility Is Both a Legal and Practical Issue
According to the World Health Organization, approximately 1.5 billion people worldwide have some degree of hearing loss. In the United States alone, about 15% of adults report trouble hearing. For this group, a video without captions is essentially inaccessible — the same as publishing a page with no text, only images.
Blind and low-vision users face a different barrier: when important information is conveyed visually through on-screen text, demonstrations, or visual cues, they miss it entirely if no audio description is provided alongside the existing audio track.
From a legal standpoint, videos without captions have been the subject of ADA Title III lawsuits — including against universities, retailers, and media companies. WCAG 2.1, the technical standard referenced in most ADA web accessibility lawsuits and in the European Accessibility Act, includes specific requirements for video content under Guideline 1.2: Time-based Media. For businesses that are serious about compliance, those requirements aren’t optional.
Beyond legal risk, accessible video content benefits a much wider audience than you might expect: non-native English speakers, people watching in noisy environments, users on mobile with sound off, and search engines that index captions and transcripts.
The Three Core Requirements: Captions, Transcripts, and Audio Descriptions
Captions
Captions are synchronized text that appears on-screen during video playback, covering all spoken dialogue and relevant non-speech audio (like “[applause]” or “[phone ringing]”). WCAG 1.2.2 requires captions for all pre-recorded video content with audio at Level A — meaning this is a baseline requirement, not an advanced one.
There are two types:
- Closed captions — can be toggled on or off by the viewer. This is the preferred format because users have control over the experience.
- Open captions — permanently embedded in the video and always visible. Simpler to implement but less flexible for users who don’t need them.
One critical point: auto-generated captions from YouTube or Vimeo are not sufficient on their own. These tools have improved significantly, but they still produce errors — especially with technical terms, proper nouns, and accented speech. Auto-captions should be treated as a draft that requires human review and correction before you can rely on them for compliance purposes.
Transcripts
A transcript is a complete text version of everything spoken and any relevant non-speech audio in the video. While full transcripts aren’t required by WCAG at Level AA for standard video content, they are required at Level A for audio-only content, and they’re a best practice for all video on your site.
Transcripts serve users who can’t or don’t want to watch the video in full — including screen reader users, people who prefer to read and skim, and users with cognitive disabilities who benefit from processing information at their own pace. They also get indexed by search engines, giving your video content an SEO boost that embedded video alone doesn’t provide.
Place transcripts directly below or near the video on the same page — not hidden behind a dropdown or linked to a separate URL. Accessibility is about removing friction, not adding it.
Audio Descriptions
Audio descriptions are additional narration added to a video to describe visual information that isn’t conveyed in the existing dialogue or audio. If someone is demonstrating a process on screen, pointing to a chart, or showing text appearing as an animation, blind users miss that information entirely unless it’s described out loud.
WCAG 1.2.5 requires audio descriptions for pre-recorded video with audio at Level AA — the compliance level referenced in most ADA litigation and in the European Accessibility Act. This is the requirement that catches most WordPress site owners off guard. If your product demo video walks through a visual interface without narrating what’s on screen, it very likely fails this criterion.
How to Add Accessible Video to Your WordPress Site
The right approach depends on how you’re hosting and embedding video:
- YouTube: Add captions in YouTube Studio under “Subtitles.” You can upload a .vtt or .srt file, or use auto-generated captions as a starting point — but always review them before publishing. When embedding via the WordPress block editor, the YouTube block preserves the embedded player’s caption controls.
- Vimeo: Vimeo Pro and above lets you upload caption files directly in the video settings panel. As with YouTube, auto-generated captions need human review before you can treat them as compliant.
- Self-hosted video: Use the HTML5
<video>element with a<track>tag pointing to a .vtt caption file. The native WordPress Video block supports this. Store your .vtt files in your media library and reference them in the block settings.
For transcripts, add a paragraph block directly below your video embed with the full transcript text. Label it with an H3 heading like “Video Transcript” so screen reader users know it’s there and can navigate to it without hunting.
Common Video Accessibility Mistakes on WordPress Sites
These are the errors that show up most often when auditing WordPress sites with video content:
- Publishing auto-generated captions without review — errors in auto-captions can make content confusing or misleading for deaf users, and they don’t satisfy WCAG requirements as-is.
- Embedding third-party videos without verifying their accessibility — if a vendor provides an embed code, don’t assume their captions are accurate, complete, or properly synced.
- Forgetting audio descriptions for visual demonstrations — especially common in software tutorials, product demos, and e-learning content where most of the important information is visual.
- Hiding transcripts behind a dropdown or on a separate page — this adds unnecessary friction and defeats the purpose of making content accessible.
- Using autoplay with sound enabled — this is a direct WCAG 1.4.2 failure and is disruptive to screen reader users whose software gets drowned out by unexpected audio. If autoplay is necessary, start the video muted.
What WCAG 2.1 Actually Requires for Video
Here’s a straightforward reference for Guideline 1.2 requirements at Levels A and AA:
- 1.2.1 (Level A): Audio-only or video-only content must have a text or audio alternative.
- 1.2.2 (Level A): Pre-recorded video with audio must have synchronized captions.
- 1.2.3 (Level A): Pre-recorded video with audio must have an audio description or a full media alternative.
- 1.2.4 (Level AA): Live audio content — webinars, live streams — must have real-time captions.
- 1.2.5 (Level AA): Pre-recorded video with audio must have audio descriptions for visual content not conveyed in the audio track.
Most WordPress sites with video content fail at minimum 1.2.2 and 1.2.5. Both are referenced in ADA litigation and the European Accessibility Act’s technical standard. If your site has even one uncaptioned video, you have a provable accessibility barrier under current law.
Take Action
Video accessibility failures are real code-level issues — missing caption tracks, autoplay violations, absent transcript markup — and they won’t be caught by basic automated scanners that only check visible page elements. LEWCA’s WCAG scanner identifies these problems at the code level on your actual WordPress pages, giving you a concrete list of what needs fixing rather than a vague compliance score. Download LEWCA free to scan your site today, or explore LEWCA Pro for AI-powered code fixes and scheduled scanning that keeps your site compliant as you publish new video content over time.