Audio Accessibility

Audio recordings are a flexible way to share content, capture live discussions, or provide supplemental learning materials. But to ensure everyone can access the information, audio must be accompanied by accessible formats like transcripts and meaningful descriptions.

Whether you’re recording a podcast, uploading lecture audio, or creating a multimedia resource, this guide outlines key practices to support inclusive access.

Why Accessible Audio Matters

Creating accessible audio helps ensure that everyone, including people with hearing, cognitive, or processing disabilities, can engage fully with your content. Providing alternatives to sound also supports:

  • Deaf and hard-of-hearing users
  • Multilingual audiences and English language learners
  • Students who prefer to read or search the content
  • Anyone accessing content in a noisy or quiet environment

Core Accessibility Features for Audio

A transcript is a written record of all spoken content in an audio recording. It should accurately capture what was said, including filler words, pauses, and speaker changes. For recordings with multiple speakers, identify who is speaking by name or role to help readers follow the conversation. Non-speech sounds that add meaning — like [laughter], [music playing], or [applause] — should be included in brackets.

Transcripts are essential for accessibility, but they also benefit anyone who prefers to read, skim, or search the content. They support notetaking, comprehension, and translation, and they allow users to engage with audio content at their own pace.

At UMBC, transcripts should be provided for all standalone audio materials shared with students or the campus community. Tools like Microsoft Word and Otter.ai can help generate a starting draft, but manual review and editing are critical to ensure accuracy and clarity.

When applicable:

Audio description is typically used for video content, but it can be relevant for audio files when important information is conveyed visually and not explained aloud. For example, if your podcast or audio clip says “look at the image on the homepage,” but doesn’t describe it, you’ll need to include that information in a transcript or a linked document with a text description.

In most cases, audio-only content doesn’t need a separate audio description. However, if the recording is part of a multimedia learning experience — such as a narrated slideshow, gallery walk, or interactive audio tour — make sure that all visual elements are described in a way that blind or low-vision users can understand.

If you’re not sure whether audio description is needed, consider the question: “Would someone who can’t see the visuals miss key information?” If the answer is yes, then a description or alternative format should be provided.

 

Tools, Tips, and Support: Audio Tools

UMBC-supported and commonly used tools include:

  • Panopto or YuJa (for lecture recording and captioning)
  • Audacity, Adobe Audition, or GarageBand (for audio editing)
  • Otter.ai, Microsoft Word, or Google Docs Voice Typing (for generating and editing transcripts)

Resources & Support