When a meeting needs audio description — and when the dais already said it

ADA Title II meeting videoYouTube auto-captionsAudio descriptionClerk checklist

What 1.2.5 is actually asking for

W3C’s Understanding document for 1.2.5 describes audio description of important visuals in prerecorded video. In clerk language: if the picture carries information the soundtrack does not, that information needs a spoken description — timed into pauses, or offered as a description track the player can turn on.

W3C is also explicit that extra narration is not needed if the soundtrack already carries the important visual information. Applying that note to a dais is a facts-and-counsel question, not a slogan.

Two meeting patterns fall on opposite sides of that line.

Talking-head dais: the vote was spoken

A typical stretch of a city council or school board meeting is faces at microphones.

• The chair recognizes a member.
• The member reads a motion into the record.
• Someone seconds.
• Discussion happens at the mics.
• The clerk calls the roll, or the chair announces the result.

For those stretches, the important information is usually already in the audio. Who moved, what they moved, how the vote landed — a resident who cannot see the dais can still follow it if the captions and the soundtrack are accurate. Extra description of every nod, every nameplate, and every shift in the chair is not what 1.2.5 is for.

That is not a pass for the whole file. It is a description of the talking-head stretches. The same recording often cuts from that dais to a shared screen. The second half is a different criterion problem.

Screen-share: budgets, maps, slides, GIS

The 1.2.5 gap in most government video is the other half of the same meeting.

Someone shares a screen. A budget workbook fills the frame. A zoning map. A staff slide deck. A GIS layer. A chart of enrollment, overtime, or fund balance. The speaker says “as you can see on the slide,” “the red parcels,” “line 14,” or “this column versus last year,” and then the board votes on what was on that screen.

A resident who cannot see the screen cannot follow that vote. The soundtrack named a color, a line number, or a gesture. It did not describe the visual that carried the decision.

That is the 1.2.5 work:

• Budgets and spreadsheets — which fund, which line, which year-over-year change is highlighted.
• Maps and GIS — what is shaded, what boundary is on the table, which parcels the overlay covers.
• Slide decks — the heading, the figure, the recommendation on the slide, not only the staff member talking past it.
• Charts and dashboards — the comparison the speaker is pointing at.
• Exhibits held up to a camera — a site plan, a petition, a photo of a sidewalk, a board-packet page that never gets read aloud.

If the only accessible version of that material is “you had to be looking at the screen,” the posted recording does not carry the meeting for someone who was not.

A clerk’s video checklist puts 1.2.5 on the posted-file row, next to captions, so a screen-share meeting does not ship with a talking-head pass and an undescribed budget.

Posted recording vs. livestream

1.2.5 is a prerecorded criterion. It applies to the file you post, not to the livestream as it happens.

Three jobs get collapsed in the same conversation:

Auto-captions do none of the description work, and they do not satisfy 1.2.2 either. YouTube auto-captions are not WCAG 1.2.2 captions.

Section508.gov’s synchronized-media page covers player-side controls: the person watching has to be able to reach captions and audio description. A description file that exists in a clerk’s folder but is not available in the player is not a 1.2.5 program.

You can keep YouTube or your current player as the host. The description still has to be available on the posted recording.

How Aware Lens handles audio description

Aware Lens, from AwareNow, Inc., generates audio description for the posted recording, with emphasis on the on-screen materials that speech does not cover — slides, exhibits, maps, roll-call graphics, shared budgets. It is not a second voice narrating every nod on the dais.

You import a YouTube link, a Zoom recording, or an MP4. Description comes back with the reviewed captions, a searchable transcript, and a plain-language summary for clerk review. Residents use the Aware portal for the full record; you can keep publishing the video to the channel you already use. Export captions, transcripts, and audio description anytime. An Accessibility Conformance Report (VPAT) is available on request.

Start with a meeting that has a screen-share. That is the file where 1.2.5 is visible.

Book a 20-minute demo. We will import one of those recordings and show the description track against the slides that were actually on screen.

The rest of Title II for meeting video — dates, 1.2.2, archives — is on ADA Title II meeting video.

Sources

• W3C Understanding 1.2.5 (WCAG 2.1)
• W3C Understanding 1.2.2 (WCAG 2.1)
• W3C Understanding 1.2.4 (WCAG 2.1)
• Section508.gov synchronized media
• ADA.gov Title II web-rule fact sheet

Product explanation, not legal advice.F.R. Part 35 and current ADA.gov materials before they go live.