Videos

Why this matters

Video has become central to education and communication at UGA. From lecture recordings to training videos to institutional communications, video reaches diverse audiences. However, video presents unique accessibility challenges: it combines visual and auditory information, making it inaccessible by default to individuals who are deaf, hard of hearing, or blind. Without captions and audio description, video content excludes students and employees with sensory disabilities and limits access for those in noisy environments, those learning in a second language, or those using devices without sound. Accessible video is not a “nice-to-have” – it is essential to equitable access and compliance with federal law. By building accessibility into video from the start, you create content that serves more learners, improves learning outcomes for everyone, and demonstrate institutional commitment to inclusion. This resource provides an overview of video accessibility; for detailed guidance on specific components, see the related resources.

WCAG 2.1 requirements for accessible video

What WCAG 1.2 requires for video

The WCAG 2.1 standard includes several requirements under “Time-based Media” (WCAG 1.2) that apply to video and audio content. Here is what is required for Level AA compliance, which is UGA’s target:

Level A requirements (minimum)

• WCAG 1.2.1: Audio-Only and Video-Only (Prerecorded) – For audio-only content, provide a transcript or text description. For video-only content (no audio), provide a transcript or audio description.
• WCAG 1.2.2: Captions (Prerecorded) – All prerecorded video with audio must include captions.

Level AA requirements (UGA standard)

• WCAG 1.2.3: Audio Description or Media Alternative (Prerecorded) – For prerecorded video, provide either audio description or a detailed descriptive transcript.
• WCAG 1.2.4: Captions (Live) – All live video broadcasts must include real-time captions.
• WCAG 1.2.5: Audio Description (Prerecorded) – Provide audio description for prerecorded video content.

Meeting these requirements

To create WCAG 2.1 Level AA compliant video:

• Captions: Add synchronized captions to all prerecorded and live video content.
• Transcripts: Provide complete, searchable transcripts of all video content.
• Audio Description: Add audio description for visual information essential to understanding the content.
• Accessible player: Use a media player that supports captions and audio description controls and is keyboard accessible.

Video accessibility components

1. Captions

Captions provide synchronized text of all audio content, including dialogue, sound effects, and music cues. Captions are essential for viewers who are deaf or hard of hearing and beneficial for anyone in a sound-off environment.

Key requirements:

• Include all spoken dialogue verbatim
• Describe relevant sounds: [door slams], [music begins]
• Synchronize captions precisely with audio
• Use clear, readable formatting
• Maintain accuracy; automated captions must be reviewed and corrected

For detailed guidance, see guidance on creating captions and best practices for live captions.

2. Transcripts

Transcripts are complete text representations of video content, including dialogue, descriptions of visual information, and speaker identification. Transcripts provide text-based access for individuals who are deaf or hard of hearing, support searching and review, and serve as study aids.

Key requirements:

• Include all dialogue with speaker identification
• Describe relevant sounds and visual information essential to understanding
• Organize logically with headings and timestamps when helpful
• Provide in accessible, searchable format (HTML, text, or Word)
• Make transcripts easily accessible from the video page

For detailed guidance, see guidance on creating and formatting transcripts.

3. Audio Description

Audio description is spoken narration that conveys visual information in the video, describing actions, expressions, scene details, on-screen text, and visual demonstrations. Audio description is essential for viewers who are blind or have low vision.

Key requirements:

• Describe visual information essential to understanding the content
• Present descriptions during natural pauses in dialogue
• Be objective and factual; avoid editorial comments
• Synchronize precisely with the video
• Use clear, professional narration

For detailed guidance, see how to create audio descriptions for video.

4. Accessible Media Player

The player used to display video must be fully accessible:

• Caption controls: Users must be able to enable/disable captions with a visible, labeled button
• Audio description controls: If multiple audio tracks are available (including one with audio description), users must be able to select them
• Keyboard accessibility: All player controls must be operable via keyboard (play, pause, volume, seeking, captions, etc.)
• Screen reader compatibility: Player controls must be properly labeled so screen readers can identify their function
• Pause on focus: Auto-playing video should pause if keyboard focus moves to the player or nearby controls

See “Accessible Media Players” section below for specific recommendations.

Captions and transcripts: The foundation of video accessibility

Captions and transcripts are the most fundamental accessibility features for video. Every video should include both:

Captions provide:

• Real-time access while viewing the video
• Essential information for viewers who are deaf or hard of hearing
• Access for viewers in sound-off environments
• Support for language learners

Transcripts provide:

• Text-based alternative for complete video content
• Searchable reference for key terms and concepts
• Option for review and study at viewer’s own pace
• Alternative for viewers with different learning styles
• Archive and preservation of video content as text

For maximum accessibility, provide both captions (for real-time viewing) and transcripts (for review and searching).

Audio description: Making visual information accessible

Video is inherently visual, but not all viewers can see. Audio description ensures that visual information is conveyed through sound, making video accessible to individuals who are blind or have low vision.

When audio description is essential:

• Educational videos demonstrating procedures or processes (lab techniques, software tutorials)
• Videos with important on-screen text, graphics, or data visualizations
• Narrative or dramatic content relying on facial expressions or visual details
• Videos where visual information conveys essential meaning

Audio description can be omitted if:

• All essential visual information is described in dialogue or narration
• A comprehensive descriptive transcript is provided that covers all visual information
• The video is purely abstract or decorative with no informational intent

When in doubt, provide audio description – it benefits many viewers beyond those with disabilities.

Choosing accessible media players

UGA video platforms

Kaltura (Media Portal)

UGA’s primary video platform. Kaltura’s player supports captions, audio description, and is keyboard accessible. Features:

• Built-in caption support (upload or auto-generate)
• Audio description support through multiple audio tracks
• Keyboard-accessible controls
• Screen reader compatible (with some configuration)

Configuration: Enable caption display in Kaltura settings and upload caption files with your video.

YouTube

If hosting on YouTube:

• Native caption support with caption editor
• Auto-generate captions (but review for accuracy)
• Keyboard accessible player
• Transcript generation and display
• Multiple audio track support

Configuration: Upload caption files (.srt or .vtt) or use YouTube’s caption editor to add captions manually.

Third-party accessible media players

HTML5 video element with accessible controls

If building custom video implementation, use native HTML5 video with track elements for captions. Pair with accessible JavaScript controls or use an accessible third-party player library.

JW Player

A widely-used commercial player with strong accessibility features:

• Full keyboard navigation
• Caption support and controls
• Audio description support
• Screen reader friendly

Accessible Video Player by accessible-video.com or similar

Open-source accessible players available through GitHub and other repositories designed specifically for WCAG compliance.

What to look for in a media player

When selecting a player, ensure:

• Caption controls are visible and clearly labeled
• All controls (play, pause, volume, seeking, captions) are keyboard accessible
• Controls have proper ARIA labels for screen readers
• Audio description or multi-track audio is supported
• Player does not auto-play with sound (or pauses on user focus)
• Player interface is tested for screen reader compatibility

Embedding video for accessibility

HTML5 video element approach

When embedding video in HTML, use the semantic video element with track elements for captions:

<video controls width=”640″ height=”360″>
<source src=”video.mp4″ type=”video/mp4″>
<track kind=”captions” src=”captions.vtt” srclang=”en” label=”English”>
<track kind=”descriptions” src=”descriptions.vtt” srclang=”en” label=”English Audio Description”>
Your browser does not support the video element.
</video>

This approach ensures:

• Native browser support for captions
• Keyboard accessibility (if browser player is used)
• Alternative text if video cannot play
• Proper semantic structure

Platform-specific embedding

If using Kaltura or YouTube, use their standard embed codes, which include their accessible players. These are generally more accessible than custom implementations.

Providing context and alternatives

When embedding video, also provide:

• A descriptive heading or title for the video
• A brief description of video content above the player
• A link to the transcript below the player
• Alternative text or captions if the video cannot be displayed

Example HTML structure

<h3>Introduction to Photosynthesis</h3>
<p>This 10-minute video explains the process of photosynthesis in plant cells, including the light reactions and Calvin cycle.</p>

[Video player here]

<p><a href=”#transcript”>View full transcript</a></p>

Flashing and flickering content

WCAG requirement

WCAG 2.3: Seizures and Physical Reactions – Content must not flash or flicker more than 3 times per second. Content that violates this can trigger seizures in individuals with photosensitive epilepsy, causing physical harm.

What counts as flashing?

Problematic flashing includes:

• Any element that changes color or brightness more than 3 times per second
• Entire screen flashing (backgrounds, overlays)
• Strobing effects in animations
• Rapidly blinking elements

What is safe?

Safe patterns include:

• Smooth animations and transitions (not abrupt flashing)
• Color or brightness changes slower than 3 times per second
• Single flashes not exceeding brief moments

Video content guidance

If your video contains flashing or strobing effects (e.g., lightning, club lighting, emergency strobe):

• Warn viewers before the video that it contains flashing
• Provide a means to skip problematic content if possible
• Avoid rapid flashing entirely if possible
• Never use flashing as a design element; reserve for intentional visual effects with appropriate warnings

Creating accessible video: Start to finish

Before recording

• Plan for accessibility: Design video with accessibility in mind from the start.
• Ensure good audio quality: Clear audio is essential for accurate captions. Use a quality microphone and minimize background noise.
• Consider visual clarity: Use sufficient contrast, avoid small text on screen, and ensure visuals are clear for viewers with low vision.
• Script if possible: A script helps captioners, and allows you to review and plan content.

During recording

• Speak clearly and at moderate pace: This improves caption and audio description accuracy.
• Identify speakers: Introduce yourself and any guests by name.
• Describe visuals aloud: Verbally reference what is on screen, especially important visuals or text.
• Avoid rapidly changing visuals or flashing.
• Use good lighting: Proper lighting improves visual clarity for viewers with low vision.

After recording (Post-production)

• Create captions: Add or generate captions and review for accuracy.
• Create transcripts: Produce detailed transcripts with speaker identification and descriptions of visual content.
• Add audio description: Record and mix audio description for visual information.
• Review and test: View the video with captions and audio description enabled to verify accessibility.
• Make transcripts findable: Provide prominent links to transcripts on the page with the video.

Publishing

• Use an accessible media player: Choose a platform or player that supports captions and audio description.
• Enable caption display by default: Make captions visible on page load (though users should be able to disable them).
• Provide context: Include a descriptive title and brief description of video content.
• Link to transcripts: Make transcripts easily accessible from the video page.
• Test with assistive technology: Test the video page with screen readers and keyboard navigation to ensure full accessibility.

Common mistakes to avoid

• Uploading video without captions: Captions are not optional. Every video with audio must be captioned.
• Using auto-generated captions without review: Automated captions contain errors. Always review and correct before publishing.
• Providing captions only, without transcripts: Transcripts offer different benefits and serve different user needs. Provide both.
• Assuming audio description is not needed: If visual information is essential, audio description is needed. When in doubt, provide it.
• Using inaccessible media players: Some players lack keyboard accessibility or caption support. Choose platforms that support full accessibility features.
• Auto-playing video with sound: This startles users and is inaccessible. Use silent auto-play only, and always allow users to control playback.
• Hiding transcripts in collapsed sections: Make transcripts prominently visible and easily accessible.
• Providing transcripts only as images or locked PDFs: Transcripts must be in searchable text format to be truly accessible.
• Including flashing content without warning: If video contains strobing or flashing effects, provide clear warnings before the video.
• Overlooking supplementary videos: Captions are needed for lecture recordings, demonstration videos, and all content, not just main lectures.
• Not testing accessibility with actual users: Test video accessibility with individuals using assistive technology to identify issues you may have missed.

Related DASH resources

• Detailed guidance on creating and adding captions to recorded video and audio
• Best practices for real-time captions on live events and meetings
• Comprehensive guide to creating audio description for video
• How to create, format, and provide accessible transcripts
• Accessibility guidance for virtual teaching and synchronous events

Getting help

UGA’s Digital Accessibility Services Hub (DASH) is here to support you. Whether you need guidance on making existing videos accessible, planning accessibility during video production, choosing accessible platforms, captioning videos, creating audio description, producing transcripts, or training on video accessibility best practices, we are ready to help.

• Visit dash.uga.edu for resources, guides, and tools.
• Contact DASH for consultations on video accessibility, access to transcription and audio description services, technical assistance, or training for your team.

Accessibility is a shared responsibility. Accessible video ensures that all members of the UGA community can fully engage with educational content and institutional communications.