1. Define what the video needs to communicate
Write down its purpose, audience, language and useful next action. List speech, meaningful sounds, on-screen text and essential gestures. The WAI planning guide distinguishes needs according to the content and whether media is prerecorded or live.
In a fictional demonstration, someone shows where to find a document without naming the button. Mark that step as information that needs another way to be understood. Assign someone to approve the content and someone to check its integration. Agree the deliverables before requesting publication.
2. Review captions against the final edit
WAI describes accessibility captions as synchronized text containing speech and meaningful sounds. Translating speech alone may therefore leave gaps. WAI also explains that automatic captions must be checked and corrected for full accuracy.
For acceptance, watch the entire video with the selected track. Check names, negatives, speaker changes and timing. Make sure lines do not cover important information. Keep the reviewed file with its matching video version; do not approve an old caption track against a new edit.
3. Make the accompanying text easy to find
A descriptive transcript also includes essential visual information, WAI explains. Its guide recommends making transcripts easy to find, for example below the video. This supports reading separately from the player; it does not by itself establish overall accessibility.
Prepare structured text identifying speakers and useful steps. In the fictional demonstration, include the name of the button shown and the expected result. Review links and specialist terms. For each published language, clearly state the video language and available text languages, without advertising a translation that does not exist.
4. Address information that is only visible
WAI’s description guide explains that essential visual information also needs to reach people who cannot see it. One approach is to include it in the speech during production. A transcript does not automatically replace every need for audio description.
Listen without watching, then compare what you understand with the initial inventory. If a step remains unexplained, have a qualified person decide which narration or described version to provide. Record outstanding work. This practical exercise does not replace a complete assessment of applicable requirements.
5. Check the player in the actual page
WAI lists keyboard operation, visible focus and clear labels among accessible player functions. Selecting a player therefore needs to be followed by checking its integration.
In an isolated preview, try play, pause, volume, track selection and returning from full screen using the keyboard. Check that you can leave the player and reach the next content. Repeat on a phone in portrait and landscape. As a project acceptance rule, request visitor-initiated playback and obvious access to the text if the video does not start.
6. Keep an acceptance record for each version
Use the worksheet below to record the page, video version, languages, devices and observed result. Check the title and link to the next action too. If the player fails to load, visitors should still understand the subject and find the accompanying text under your agreed criteria.
Assign each correction and repeat the affected check after changes. If a language or adaptation is missing, record that limit in the publication decision. After changing the edit, text or player, check that they still match. An opening page is not sufficient evidence that the whole video is ready.
Acceptance worksheet for a prerecorded video
| Area | Expected result to agree | Evidence to keep |
|---|---|---|
| Content | Audio and visual information identified | Dated inventory |
| Captions | Accurate, synchronized track | Version and corrections |
| Transcript | Complete, easy-to-find text | Address and language |
| Description | Essential visual information addressed | Decision and selected version |
| Player | Usable controls and keyboard exit | Device, browser and observations |
| Follow-up | Limits and owners identified | Acceptance record |
Frequently asked questions
Does each site language need a different video?
Agree the languages actually needed with your team. A page may present a video in another language, but should clearly identify available tracks and text. Check each intended combination before publishing.
Is a transcript enough to approve the video?
No. Check captions, visual information and the player separately according to the content and agreed requirements. Text is a useful deliverable, not an overall certificate.
Does this worksheet also cover live streaming?
No. Live media needs preparation and resources suited to real-time delivery. Define separate acceptance checks; do not automatically transfer approval from a recording.
Prepare your next video
Choose an existing video, gather its files and complete the inventory first. Then agree the adaptations and acceptance checks before setting a publication date.
Sources and scope
Primary guides checked on November 4, 2026. WAI attributions link from the relevant sections. The example, checking process and worksheet are editorial proposals; no client outcome, service commitment or compliance audit is claimed.
