Stop Retrofitting: 5 Producer Tasks That Ensure WCAG Video Accessibility
Every accessible video needs five things: accurate synchronized captions, a transcript for audio-only or video-only content, audio descriptions where visuals carry information the audio doesn’t, a keyboard-operable player with visible caption and audio-description controls, and a QA pass that catches what automation misses. Anchor all five to WCAG 2.1 Level AA and Section 508. Auto-generated captions are a starting point, not a finish line. They still need a human to check them.
The Video Accessibility Checklist by Production Phase
Accessibility isn’t a task you bolt on after export. It’s a set of decisions that belong in every phase of a shoot, from the first script draft to the version you publish next year. Here’s the full breakdown, organized the way a producer actually works.
Preproduction
Tag speaker names directly in the script so captioners don’t have to guess who’s talking.
Flag any visual-only moments (a chart, a gesture, on-screen text) that will need an audio description.
Build in natural pauses where audio description can be inserted without talking over dialogue.
Assign ownership: who writes captions, who scripts audio description, and who signs off.
Production
Record clean, single-speaker audio whenever possible; overlapping dialogue is a captioner’s nightmare.
Keep on-screen text and lower-thirds in the upper two-thirds of the frame so captions don’t cover them.
Capture a separate reference audio track if you’re shooting multi-camera or with lav mics.
Postproduction
Draft captions and transcripts, then have a human verify them against the Section508 styling rules.
Write and record audio descriptions, timed to the pauses you reserved earlier.
Apply consistent caption styling: font, contrast, line breaks, and duration.
Publishing
Deploy a player with visible caption and audio-description toggles.
Export captions in WebVTT, SRT, and TTML.
Post a downloadable transcript alongside the video, not buried in a separate menu.
Maintenance
Keep version control on caption files so edits to the video don’t orphan old subtitles.
Give viewers a way to flag accessibility errors.
Re-run your QA checklist any time you re-cut or re-upload.
How Do You Reduce Retrofitting Work During Production?
Most accessibility budget overruns trace back to decisions made on set, not in the edit bay. Fix the workflow early to reduce both the cost and the timeline later.
Start by embedding speaker identification directly into the script, then call it out during blocking so talent and crew reinforce it on camera. Avoid overlapping dialogue wherever you can. Captioners and transcribers work faster, and more accurately, when speech falls below roughly 180 words per minute with clear breaks between speakers.
Placement matters more than people think. Keep on-screen text and lower-thirds in the upper two-thirds of frame, since caption bars typically sit at the bottom and will otherwise collide with your own graphics. Log every visual-only moment (a whiteboard diagram, a silent demonstration, a reaction shot) in your shot notes. Whoever writes the audio description later will need that record instead of re-watching hours of footage.
Record a separate clean audio or reference track with visible timecode when your setup allows it. This single habit saves caption editors from parsing overlapping mics after the fact.
Pro Tip: Schedule audio-description scripting at picture lock, not after final color. Locking picture first means the pauses you need for description won’t shift again, and you avoid re-timing the whole track twice.
What Makes Captions and Transcripts Compliant?
Compliant captions do more than transcribe dialogue. Per Section508.gov, captions must be time-synchronized, identify who’s speaking, and include meaningful non-speech audio like “[phone ringing]” or “[audience applauds].” Formatting matters just as much as content: captions should generally run no more than two lines, cap out around 45 characters per line, and stay on screen long enough for an average reader to finish them before the next line appears.
A few formatting rules worth locking into your style guide:
Never let captions scroll or flash. Static, timed text only.
Use consistent color and placement so viewers aren’t hunting for text each time it appears.
Break lines at natural phrase points, not mid-clause, so meaning doesn’t get chopped in half.
Transcripts follow separate but related rules. Audio-only content (a podcast episode packaged as video, for instance) needs a full text transcript. Video-only content, like a silent product demo, needs either a transcript or a narrated equivalent describing what’s shown.
Automated captions are a genuine time-saver, but they’re not a substitute for human review. Section508.gov’s own guidance points out that auto-generated captions routinely miss speaker changes, misfire on sound effects, and drop punctuation in ways that change meaning. If your video is going in front of a federal client, a training audience, or the public, budget for a human pass, even if that pass is just editing an automated draft rather than transcribing from scratch.
When Does a Video Need Audio Description?
Audio description is required whenever synchronized media contains visual-only information that the existing audio track doesn’t convey. Think of a training video where an instructor silently points to steps on a diagram, or a documentary that relies on on-screen text to deliver key facts. If a blind viewer would miss something essential by listening alone, that’s your trigger.
The efficient move is scripting AD markers during preproduction, right alongside your speaker tags, so you’re not scrambling to find pauses after the edit is locked. Puritano’s own audio description workflow walks through timing markers at picture lock specifically to avoid re-editing.
You have three practical delivery options:
A standalone audio-described version of the file, distributed alongside the original.
A secondary audio track selectable within the same file.
A full text description for video-only content, which doubles as a transcript equivalent.
Whichever route you choose, label the file clearly and add metadata so viewers and platforms can actually find the accessible version instead of stumbling into the wrong file.
What Should an Accessible Video Player Include?
Captions and audio description only help if the player lets people use them. Per Section508.gov, an accessible player needs keyboard-operable, focusable controls for play, pause, timeline scrubbing, volume, captions, and audio description, no mouse required.
Placement of those controls carries real weight. Caption and audio-description toggles need to sit at the same menu level as volume or program selection, not buried two submenus deep, because a control someone can’t find is functionally a control that doesn’t exist.
A few more baseline requirements worth confirming with any vendor or CMS:
Support for standard caption formats: WebVTT, SRT, and TTML at minimum.
A downloadable transcript link posted next to the player itself.
Visible focus indicators so keyboard and screen reader users can see which control is active.
Caption style customization (size, color, background) when your platform supports it.
How Do You Test a Video for Accessibility Before Publishing?
QA is where good intentions either hold up or fall apart. Run this as a formal acceptance step, not an afterthought:
Watch the full video with captions on, checking timing, speaker labels, and whether any lines get truncated or cut off.
Navigate the player using only a keyboard: confirm you can reach play, pause, timeline, volume, captions, and audio description without a mouse.
Test with a screen reader to verify labels and focus order actually make sense out loud.
Confirm caption files, transcripts, and audio-described versions all download correctly and match the current video edit.
Document every issue you find, fix it, and re-run the full checklist before publishing.
Pro Tip: Keep a simple pass/fail log for each test item. When you re-edit a video six months from now, that log tells you exactly which checks to re-run instead of starting QA from zero.
What Standards and Legal Rules Apply to Video Accessibility?
WCAG 2.1 Level AA is the baseline most federal guidance points to for synchronized media, covering captions, live captions, audio description, and media alternatives. Section 508 builds on that baseline for federal contexts; Section508.gov is the practical reference for specifics.
On the legal side, DOJ rulemaking under the ADA formally adopted WCAG 2.1 AA as the technical standard for state and local government web content, with staggered compliance deadlines that push into 2027 and 2028 depending on entity size. The rule also carves out narrow exceptions, archived content and certain preexisting documents among them, but the overall framing treats accessibility as ongoing work, not a one-time fix. If you’re bidding on public-sector or association work, write acceptance criteria tied to WCAG and Section 508 conformance directly into the contract rather than leaving it as a vague deliverable.
How Should Producers Build Accessibility Into a Bid or Schedule?
Assign ownership before the shoot starts: one person scripts speaker IDs and AD markers, one owns caption QA, one signs off before publishing. Skipping this step is how accessibility becomes everyone’s job and therefore nobody’s.
Every SOW should spell out exact deliverables: caption files in WebVTT and SRT, a downloadable transcript, a labeled audio-described version, and a named acceptance test, along with how many rounds of caption revisions are included. Budget a real line item for human-verified captioning, since industry guidance treats it as standard rather than optional, and build in lead time for audio-description scripting so it doesn’t get rushed at the end. Puritano’s Section 508 producer’s guide and WCAG vs. Section 508 breakdown both walk through how to write these line items into a federal bid without losing on price.
Hiring Puritano for Accessible Video Production
Some video production companies integrate accessibility into their project scope from the start rather than adding it after the fact. For training, government, and corporate clients, accessible delivery is built into how the project gets scoped from day one, not added after the fact. That means captions, transcripts, audio description, an accessible player configuration, and a QA pass are planned into the schedule and the bid, the same phases covered throughout this checklist.
If you’re producing content that has to hold up against WCAG 2.1 AA or Section 508 review, whether it’s a training module, a conference explainer, or an association campaign, Puritano’s video production services cover the full range from corporate explainer videos to broadcast documentaries. Well-built accessibility also tends to widen the audience your content reaches; accessible video correlates with better search visibility since captions and transcripts give search engines text to index. Reach out through the site for a quote, and bring your current deliverables list. Puritano will tell you plainly what’s already compliant and what still needs work.
Sources
FAQ
What Is the Minimum Video Accessibility Checklist?
The minimum covers five items: synchronized captions, a transcript for audio-only or video-only content, audio description where visuals carry essential information, a keyboard-operable player with visible caption controls, and a human QA pass. WCAG 2.1 AA and Section 508 are the standards to check against.
Are Automated Captions Good Enough for Compliance?
Automated captions alone typically aren’t sufficient, since they routinely misidentify speakers and miss non-speech sounds. Section508.gov’s guidance recommends human verification or professional captioning before publishing.
When Is Audio Description Legally Required?
Audio description is needed whenever a video’s visuals convey essential information the audio track doesn’t, like on-screen text or silent demonstrations. This falls under the synchronized media requirements referenced by both WCAG and Section 508.
What File Formats Should Captions Use?
Captions should be delivered in WebVTT, SRT, and ideally TTML to cover the widest range of players and platforms. A downloadable transcript should accompany the video regardless of which caption format the player uses.
Does Puritano Handle Accessibility Compliance for Video Projects?
Puritano builds captions, transcripts, audio description, and accessible player delivery into its production process for training, government, and corporate clients. Pricing is project-based and available by request through Puritano’s video production page.
Recommended
Comments