Accessible Videos – Captions, Audio Description and WCAG Requirements
Accessible videos are video content that can be used by all people – regardless of hearing or vision ability. The key components are captions for deaf and hard-of-hearing users, audio description for blind and visually impaired people, and transcripts as a complete text alternative. An accessible video player that is keyboard-operable completes the picture.
Videos are among the content types where accessibility is most frequently overlooked – despite clear WCAG requirements. Missing captions, absent audio description and auto-playing sound are typical errors that exclude people with disabilities from content. The good news: creating accessible content is achievable with the right tools and practical examples.
For digital offerings covered by the European Accessibility Act (EAA), corresponding accessibility requirements apply. The WCAG serve as the international standard – with concrete criteria for accessible videos at Level A and AA.
Accessible Videos at a Glance
- Captions: For deaf and hard-of-hearing people – WCAG 1.2.2 (AA) for pre-recorded videos
- Audio description: For blind and visually impaired people – WCAG 1.2.5 (AA) for pre-recorded videos
- Transcript: Complete text alternative – especially important for audio-only content (WCAG 1.2.1 A)
- Accessible player: Controls operable via keyboard, sufficient contrast
- No autoplay with sound: Automatically playing audio must be stoppable (WCAG 1.4.2 A)
Captions: What They Are and How to Create Them
Captions display spoken content as text – synchronised with the video. They help not only deaf and hard-of-hearing people but also users in noisy environments, language learners and people watching videos without sound. There are two types: closed captions (toggleable) and open captions (burned into the video).
- Manual creation: Highest quality – timestamps and text set by hand (e.g. in SRT format)
- Auto-generation: YouTube, AI tools or Whisper (open source) – always check for accuracy
- Professional services: Captioning services deliver reviewed, standards-compliant captions
- Quality check: Auto-generated captions must be proofread before publication
Audio Description: Making Visual Content Audible
Audio description is an additional audio track that verbally describes visual content – for blind and visually impaired people. It explains what is happening on screen: actions, facial expressions, scene changes, on-screen text or graphics. Audio description is embedded in natural pauses in the existing audio and adds to it without replacing it.
A practical example: a product video shows a user navigating through an app. Without audio description, blind users only hear background music. With audio description, a narrator explains: "The user opens the menu in the top right and selects Settings." Only then does the content become fully accessible.
Transcripts: Text Alternatives for Audio and Video Content
A transcript is a complete written version of audio or video content. Unlike captions, it is not displayed synchronously but provided as a separate text document. Transcripts help deaf people, deafblind users who rely on Braille output, and people who prefer to read content rather than watch it.
- For audio-only content (podcasts): Transcript is mandatory at WCAG Level A (1.2.1)
- For videos: Transcript recommended – complements captions and audio description
- Content: All spoken content, relevant sounds and visual information
- Placement: Directly below the video or as a linked document
Accessible Video Player: What Matters
Even perfect captions and audio description are of little use if the video player itself is not accessible. An accessible player must be fully keyboard-operable – play, pause, volume, captions on/off, full screen – and all controls must have adequate descriptions for screen readers.
- Keyboard operable: All functions reachable via Tab and arrow keys
- ARIA labels: Buttons have accessible descriptions for screen readers
- Sufficient contrast: Controls meet WCAG 1.4.11 (3:1 for UI components)
- Accessible players: Ableplayer, Plyr with configuration, Video.js with plugins
SiteCockpit Solution
easyMonitoring: Identify Video Barriers on Your Website
easyMonitoring helps you identify relevant barriers in video content on your website – including missing text alternatives, problematic autoplay configurations and inaccessible player elements. This gives you a structured overview of which video content does not yet meet WCAG requirements.
Discover easyMonitoring →Frequently Asked Questions about Accessible Videos
Are auto-generated captions sufficient for WCAG compliance?
Not automatically. Auto-generated captions frequently contain errors with proper names, technical terms or fast speech. WCAG 1.2.2 requires accurate captions. Auto-generated captions must be reviewed and corrected before publication.
Is autoplay permitted on websites?
Autoplay without sound is generally permitted under WCAG but must be pauseable (WCAG 2.2.2). Autoplay with sound is problematic: audio playing automatically for more than 3 seconds must be stoppable or limited to 3 seconds (WCAG 1.4.2). Auto-playing sound is particularly disruptive for screen reader users.
Do I need both captions and audio description?
For full accessibility, yes. Captions help deaf and hard-of-hearing people – but they do not replace audio description for blind people. Audio description conveys visual content that the audio track does not communicate. Together, both make a video accessible to all user groups.
What format should captions be in?
The most common format is SRT (SubRip Text) – supported by all major video platforms and players. For web videos, WebVTT is recommended as it is natively supported in the HTML5 video element. Both formats contain timestamps and the corresponding caption text.
Check Your Website's Video Content for Accessibility
With easyMonitoring, you can identify which video content on your website does not yet meet WCAG requirements – and get concrete guidance on accessible implementation.
Try for free