Content · Web Development · HTML

HTML Accessible Audio-Only Content and Transcripts

Accessible Audio-Only Content and Transcripts: Try moving through the elements with a keyboard. The labels and relationships matter even when no extra styling has been added. Includes a practical HTML example and an explanation.

1 views Published Oct 19, 2026 Updated Oct 19, 2026 Admin

Good accessibility usually starts with clear words and the right HTML elements, not a large amount of extra code.

What You Need to Know


People who cannot hear an audio recording need the information in written form. Place a transcript near the player and include meaningful speaker changes or sound descriptions when they matter.

Try the Example


Take a look at the example. We’ll explain the important lines right below it.

<audio controls preload="metadata">
    <source src="media/interview.mp3" type="audio/mpeg">
    Your browser cannot play this audio recording.
</audio>
<h2>Transcript</h2>
<p>Speaker: Welcome to our interview.</p>

Let’s Read the Code


  • <audio>: The audio element creates a native sound player when controls are present.
  • <source>: A source points to a media file or image choice with a type or other condition.
  • controls: Controls asks the browser to provide its native audio or video player controls.
  • preload: Preload hints how much media to fetch before playback.

Read the named elements and attributes together. They explain how the browser connects this feature to the rest of the page.

What Happens in the Browser?


Try this with Tab and Shift+Tab. If you can, inspect the accessibility tree too; appearance alone does not tell the whole story.

Try a different way of reading. Read only the headings and labels, or navigate through links without looking at the rest of the page. If the page still makes sense, the underlying HTML is probably doing an important part of its job.

Your Turn


Replace the media filename with your own local recording and check playback, controls, and fallback content.

Common Beginner Mistakes


  • Expecting the page to run scripted behavior when the required JavaScript is missing.
  • ARIA changes what assistive technology is told; it does not automatically add keyboard controls, visual styling, or JavaScript behavior.

Key Takeaways


  • People who cannot hear an audio recording need the information in written form.
  • <audio>: The audio element creates a native sound player when controls are present.
  • A meaningful HTML element is usually a stronger starting point than adding an ARIA role to a generic div. Also check what happens using only the keyboard.
Share this resourceSend this page to someone who may find it useful.