Video Accessibility Guidance

Videos can be made accessible if content providers:

  • utilize accessibility best practices when creating videos
  • properly insert videos into websites
  • provide captions or a transcript

W3C Worldwide Consortium (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1), Level AA for audio and video included within websites are the basis for universal accessibility standards. The same principles can be applied to audio and video utilized and distributed for instructional purposes as well (e.g., audio and video avaiable via Canvas). 

  • WCAG 2.0 Guidelines for Audio and Video

    • If you use audio files on your web page or Canvas page, a text transcript or other text-based material should be provided.

  • WCAG 2.0 Guideline 1.2.1

    • "An alternative for time-based media is provided that presents equivalent information for pre-recorded audio-only content." Note: Captions also benefit non-native speakers, users with audio disabled or viewers watching a video with poor quality audio.

  • WCAG 2.0 Guideline 1.2.2

    • "Captions are provided for all pre-recorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such." Video files should be embedded or displayed in a player that can be accessed by a screen reader via keyboard commands. Accessible players include QuickTime, RealPlayer, iTunes, Vimeo, Panopto, JW Player and YouTube.

  • WCAG 2.0 Guideline 2.1

    • "Make all functionality available from a keyboard." Videos that include visual information critical to comprehension should include a description of events or images for visually impaired audiences. For example, a screencast of a software product should name the buttons and commands being used, not just say "click here."

  • WCAG 2.0 Guideline 1.2.3

    • An alternative for time-based media or audio description of the pre-recorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. A lengthy piece of audio or video should not be played by default when entering a page. Instead, the user should be able to click the play button to start the file. This provision prevents audio from interfering with the screen reading technology.

Best practices for video accessiblity for course materials include: 
  • Using captioned video files.
  • Keeping captioning auto-play off.
  • Showing captions in courses, trainings, and large or public meetings.
  • Including transcripts with prerecorded video.
  • Checking captions and transcripts for completeness and accuracy, including technical terms, spelling, punctuation, and grammar.

AU's Office of Accessibility 

AU's Office of Audit, Compliane & Privacy

AU's eAccessibility Academy

What is Zoom? 

Zoom is a video conferencing platform that integrates Canvas and Outlook, allowing users to host video meetings for up to 300 participants and schedule meetings right in the calendar. More information related to Zoom eligibility, requirements, and meeting security can be found in the Zoom: Overview article.  

What about Captions in Zoom? 

There are two things to know about captions in Zoom:

  1. Your Zoom video must have been recorded to cloud (not to local computer) and be stored on Auburn's Zoom server before you can edit captions in Zoom.
  2. Captions for a Zoom cloud recording are auto-generated and sourced from the Zoom meeting transcript.  This transcript can be accessed and edited to meet accessibility standards and shared to viewers.

The Zoom support website has has information about Using Audio Transcription for Cloud Recordings. The section of How to View or Edit an Audio Transcript has specific information for editing transcripts from a Zoom cloud recording. 

How long can I use a Zoom recording?

A Zoom recording will be automatically deleted after 180 days and permanently deleted after 210 days.  For longer retention, it is recommended you upload your Zoom videos into Panopto and edit the auto-generated captions created in Panopto.

 

 

 

 

What is Panopto? 

Panopto is a versatile video platform at Auburn University. It can be used for video hosting, screencasting, and classroom recordings. The Panopto: Overview article provides more information for integrating Panopto with Canvas.

What about Captions in Panopto? 

All Panopto recordings created at Auburn University have machine-generated captions added by default. These captions are automatically created using speech recognition and may contain errors. Accurate captions are required to meet digital accessibility standards under federal law and Auburn University policy. 

Panopto: Editing Captions provides directions to manually review and correct captions in Panopto. 

How long can I use a Panopto recording?

Unlike Zoom recordings, Panoto recordings are not automatically deleted. 

Read the Automatic Zoom to Panopto in a Canvas Course article for directions to enable Zoom and Panopto in your Canvas course(s).

Refer to the Auburn University eAccessibility Academy's Selecting Good Video and Audio Files.  

Audio Accessibility Guidance

Audio-only media  can be made accessible if content providers: 

  • utilize accessibility best practices when creating audio-only media (e.g., podcasts)
  • provide written transcripts 

W3C Worldwide Consortium (W3C) Web Content Accessibility Guidelines 2.1 (WCAG 2.1), Level AA for audio and video included within websites are the basis for universal accessibility standards. The same principles can be applied to audio and video utilized and distributed for instructional purposes as well (e.g., audio and video avaiable via Canvas). 

  • WCAG 2.0 Guidelines for Audio and Video

    • If you use audio files on your web page or Canvas page, a text transcript or other text-based material should be provided.

  • WCAG 2.0 Guideline 1.2.1

    • "An alternative for time-based media is provided that presents equivalent information for pre-recorded audio-only content." Note: Captions also benefit non-native speakers, users with audio disabled or viewers watching a video with poor quality audio.

  • WCAG 2.0 Guideline 1.2.2

    • "Captions are provided for all pre-recorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such." Video files should be embedded or displayed in a player that can be accessed by a screen reader via keyboard commands. Accessible players include QuickTime, RealPlayer, iTunes, Vimeo, Panopto, JW Player and YouTube.

  • WCAG 2.0 Guideline 2.1

    • "Make all functionality available from a keyboard." Videos that include visual information critical to comprehension should include a description of events or images for visually impaired audiences. For example, a screencast of a software product should name the buttons and commands being used, not just say "click here."

  • WCAG 2.0 Guideline 1.2.3

    • An alternative for time-based media or audio description of the pre-recorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. A lengthy piece of audio or video should not be played by default when entering a page. Instead, the user should be able to click the play button to start the file. This provision prevents audio from interfering with the screen reading technology.

AU's eAccessibility Academy

Key requirements for audio accessibility include:

  • Transcripts: Podcasts require full text transcripts that include speaker identification and non-speech sounds important to the context.
  • Audio Control: Any audio that plays automatically for mre than 3 seconds must have a mechanism to pause, stop, or mute it.
  • Clear Audio: Ensure speech is clear and background noise is minimized or removable.
  • Media Player Accessibility: Use players that allow keyboard navigation or playback controls (pay, pause, volume)

Best practices for digitally accessible audio-only course materials include:  
  • Providing transcripts that exactly match the spoken audio.
  • Placing transcripts immediately before or after the audio player for easy access.
  • Offering sign language interpretation for crucial multimedia content.
  • Designing with accessibility in mind to avoid retrofitting or digital remediation of the audio content.