Recorded meetings and silent clips need a transcript or description so deaf and blind residents get the same information as everyone else.
Some content has no second channel. A council meeting posted as an MP3 gives a deaf resident nothing. A silent screen recording of how to use a ticket kiosk gives a blind resident nothing. WCAG 1.2.1 (Level A) covers exactly these two cases: prerecorded audio-only and prerecorded video-only content.
Recordings that combine sound and picture are not handled here; they fall under 1.2.2, 1.2.3 and 1.2.5. Live audio and live video are outside this criterion too.
Local governments publish a lot of audio: board meetings, emergency alerts, voicemail-style recorded messages, oral history collections in libraries. They also publish silent clips, such as a looping demonstration of how to scan a card at a turnstile. These are often uploaded as bare files with only a title, and the minutes are a separate PDF that may or may not match.
A transcript posted next to the recording does the job and also helps everyone who wants to search, skim or read in a noisy place. For entities working toward the deadlines in the Title II web rule, the most common gap is simply that nobody owned the transcript step when the file was uploaded.
The recording and its alternative should sit together so a user does not need to search for the second one.
<h2>Board of Supervisors, March 12</h2>
<audio controls src="/audio/bos-2026-03-12.mp3"></audio><h2>Board of Supervisors, March 12</h2>
<audio controls src="/audio/bos-2026-03-12.mp3"></audio>
<p>
<a href="/audio/bos-2026-03-12-transcript.html">
Read the transcript of the March 12 meeting
</a>
</p>A silent video needs the information carried in words (or in a narration track). Tie the description to the video so it is announced with it.
<video controls muted src="/video/kiosk-tap-card.mp4"></video><video controls muted
src="/video/kiosk-tap-card.mp4"
aria-describedby="kiosk-desc"></video>
<div id="kiosk-desc">
<p>A rider holds a fare card flat against the round
reader on the right side of the kiosk. The screen
changes from "Tap card" to "Balance: $12.40".</p>
</div>A transcript is more than the spoken words. Speakers and meaningful sounds belong in it.
we will now open the hearing on the
parking proposal ... all in favor[Gavel]
CHAIR HOLT: We will now open the hearing on the
parking proposal.
[Chairs scraping, murmuring]
CHAIR HOLT: All in favor?
[Four voices: "Aye"]The rule does not depend on the platform: an app that plays a recorded message or a silent tutorial needs the same transcript or description. It is delivered as screen content, such as a "Transcript" button that opens a text view, so no platform-specific API snippet is needed here.
Automated tools can detect an audio or video element; they cannot tell whether a transcript is complete.