Federal Agencies Audited Their Own Video. The Most Common Failure Was Audio Description.

What You’ll Learn

• The single most common accessibility defect in the federal government’s most-viewed videos, and why it isn’t what you’d guess

• Why that defect points at your player and your publishing workflow, not at your production budget

• What audio description is, in one paragraph, and what it isn’t

• Why federal data doesn’t set your deadline and is still worth ten minutes of your time

• The first thing to check on your own archive

The Defect in Three Words

Somewhere in your archive is a meeting that’s fully captioned, captioned correctly and on time by someone who cared, and it’s still unusable to a resident who can’t see the screen.

The federal government published a one-line explanation of why this year, and it isn’t the reason you’d guess.

When agencies checked their most-viewed public videos for the FY 2025 Governmentwide Section 508 Assessment, one failure came up more than any other. The report gives it three words: Audio Description Controls.

It’s about the controls, not the content. That’s the whole entry too, no chart or case study behind it, no paragraph unpacking what it means.

If you run video for a city, a county, a school district or a library, you probably read those three words and assumed the obvious meaning: they didn’t add audio description. That’s a reasonable guess. It’s also not what the defect says, and the difference is the useful part.

The Defect Is About the Button, Not the Script

Audio Description Controls is a named requirement in the federal Revised 508 Standards, and the text of it is short. Where a system gives a viewer controls for choosing what to play, it has to give them a control for switching on audio description, at the same menu level as the controls for volume or program selection.

Read that again with your own video page in mind. The requirement isn’t only about whether a description track exists. It’s about whether a person watching can find it and turn it on, in the same place they’d look for the volume.

So a video can have a perfectly good description track in the asset library and still fail. If the track ships as a separate file nobody links to, or lives in a second version of the video on a different page, or sits three menus deep, the control test hasn’t been met.

That’s a different problem from the one most teams budget for. It isn’t a content problem, it’s a delivery problem.

It Happens to Teams Who Did Everything Right

Here’s the part that deserves a second look. This defect showed up at the top of the list among federal agencies, which have the largest accessibility staffs, the most established programs and the most scrutiny in the country. These aren’t organizations that forgot about audio description.

What happens instead is a handoff. Someone produces the description. Someone else publishes the video. The publishing step runs on a player that was chosen years ago for a different reason, usually streaming reliability or cost, and that player has a captions button because everybody expects a captions button. It doesn’t have a description control, because until recently nobody asked it to.

Captions have a familiar icon, a settled expectation and a control in a predictable spot. Audio description doesn’t have those yet, and it’s still treated as optional by software that shouldn’t be treating it as optional.

One caveat about the source, and it matters. Section 508 covers federal agencies and the technology they buy and build. If you work for a city or a county, your video obligations come from the Americans with Disabilities Act (ADA) Title II instead, and the technical standard that rule adopts is Web Content Accessibility Guidelines (WCAG 2.1 Level AA). It’s a different rule with a different scope and a different date. The federal numbers don’t set your deadline. They tell you what the best-resourced video teams in the country are still getting wrong, which is a cheaper way to learn it than finding out locally.

What Audio Description Is, in One Paragraph

Since the term gets stretched: audio description is narration added to the soundtrack that describes the important visual details you can’t get from the audio alone. That’s close to the regulation’s own definition. In a meeting recording it’s the second voice telling you what’s on the slide, what the map shows, who stepped to the podium, what the vote tally on the screen said. It isn’t captions, which carry the audio to someone who can’t hear it. It isn’t a transcript or a summary, and it doesn’t interpret the meeting. We’ve written about what it does in a meeting recording at more length.

The Ten-Minute Audio Description Check

Open your own archive the way a resident would find it: the public page for last month’s council meeting, with no admin login and no preview link.

Then answer three questions. Can you find a control for audio description without leaving that page? Is it at the same level as the volume and playback controls, rather than in a settings submenu or a separate accessible version of the video? If you click it, does the description actually play?

If the answer to the first question is no, you’ve just reproduced the federal government’s most common video defect on your own site, and you know it before anyone files a complaint. If the answer is yes, you’re ahead of the agencies whose most-watched videos put this defect at the top of the list.

Either way, you now know whether your problem is production or delivery, and those get solved by different people.

MediaScribe Narrate produces audio description for finished recordings as a step in the publishing workflow you already run, which is the same handoff where this defect tends to appear.

Check One of Your Own Meetings

The federal assessment came from agencies looking honestly at their own most-watched video. The same look works at city scale, and it costs an afternoon. Talk to the MediaScribe team about running it on the meetings residents actually open.