“Click here. Now you can see it worked.”
The pointer moves. A row changes color. The presenter advances to the next screen.
Someone listening receives two claims without the information connecting them. Which control changed the record? What result appeared? What should the viewer understand before the next step?
For a prerecorded software demo, start by listing the visual information the spoken script leaves unexplained. Then decide how that information will reach someone who cannot see the screen adequately.
W3C's description guidance covers meaningful visuals, including displayed text. It describes integrated narration, separate described videos, and player-dependent description files. The method below applies those options to a fictional training demo. Its worksheet and scripts are editorial proposals, not a product specification or conformance test.
Define the Work the Demonstration Must Explain
Write a task statement before reviewing the recording. State the starting condition, the intended action, and the visible evidence of the result. Keep the statement small enough to follow in one demonstration.
For this fictional example, a reviewer must return an incomplete supplier record to the intake team. The screen begins on a record called “Sample supplier A.” The intended result is a status reading “Changes requested.” Nothing gets sent to a real person.
The training task is to understand that sequence. It is not to learn an entire procurement system or reproduce every menu in the interface.
Use a training needs analysis when the actual learning task remains unclear. Description cannot repair a lesson that never establishes what the viewer needs to learn.
Record the demonstrated application version or capture date for a real product. Record the viewport and any selected mode that changes the controls. In this example, the application and every label are invented. No vendor behavior is implied.
Keep the production copy synthetic too. Build sample records before recording. A description script should not introduce a private name merely because it happens to appear in a screen capture.
Inventory Controls, States, and Outcomes Before Rewriting
Watch the rough cut once with sound. Watch it again while writing the visual-information sheet. Identify the information needed to follow the task, rather than describing every pixel.
Here is the fictional rough cut:
| Step | Narration | What the screen shows |
|---|---|---|
| One | “Start here.” | Record heading “Sample supplier A”; status “Ready for review” |
| Two | “Click here.” | Presenter selects the control labeled “Request changes” |
| Three | “Add this.” | A dialog titled “Request changes”; field labeled “Reason”; text “Tax reference missing” |
| Four | “Now you can see it worked.” | Dialog closes after “Confirm”; status reads “Changes requested” |
The rough narration omits the record identity, starting state, control label, dialog title, field label, entered reason, confirmation action, and resulting status. Those are eight task-relevant information items in this proposed inventory. They are not eight independently measured accessibility failures.
The row's color is also visible. In this lesson, the explicit status text communicates the result. Put the status wording into the narration. Do not require the listener to understand what a color means.
Keep uncertain consequences out of the script. A changed status does not prove an email was delivered or a colleague read the request. If the lesson needs those outcomes, show and explain separate evidence for them.
That boundary resembles the lead-form confirmation review: describe the state the interface establishes. Leave downstream assumptions visible as assumptions.
Use a Visual-Information Review Sheet
Copy the following fields into the production document. Use one row for a visual event whose meaning the viewer needs. The fictional rows show how to connect an omission to a concrete script decision.
| Visual event | Needed meaning | Existing spoken coverage | Proposed description | Review evidence |
|---|---|---|---|---|
| Record opens | Identity and starting state | “Start here” | Name Sample supplier A and Ready for review | Heading and status visible before action |
| Control selected | Which action starts the request | “Click here” | Name Request changes | Exact label visible beside pointer |
| Dialog opens | Where to enter the explanation | “Add this” | Name dialog, Reason field, and entered text | Dialog title and field visible |
| Confirmation finishes | What changed after confirmation | “It worked” | Name Confirm and Changes requested | Dialog closes; new status appears |
For an actual review, add the time span, script owner, open question, and decision status. A screenshot reference can help an editor locate the event. Preserve the recording version with the sheet.
Write “not established” when the evidence is incomplete. If the pointer obscures the label, request another capture. If the status changes too quickly to verify, slow the edit or hold the frame. Avoid converting a reviewer guess into narration.
Separate content decisions from recording decisions. “Name the status” is a script change. “Hold the result frame longer” is an edit change. Give each an owner so that the revised narration and the revised video meet at the same point.
Rewrite the Script With Integrated Description
For a new instructional recording, W3C describes integrated description as placing relevant visual information in the main script. That option fits this proposed demo because the presenter can explain the action while performing it.
Use the following replacement script. Each paragraph corresponds to one step in the fictional sequence. The wording is written for rehearsal, not timed against an existing audio file.
“Sample supplier A is open. Its status is Ready for review. The tax reference is missing, so this example returns the record for correction.”
“Select Request changes. The Request changes dialog opens.”
“In the Reason field, enter Tax reference missing. The reason is now visible in the field.”
“Select Confirm. The dialog closes. The record status changes from Ready for review to Changes requested. The example ends at this status change.”
The sequence names all eight information items in the inventory. The reason supplies the record's missing input without inventing a customer history. The final sentence bounds the outcome. It makes no claim about a notification, a permanent save, or another person's response.
Rehearse the action order against the screen. Name the control before selecting it. Let the dialog open before describing its contents. Speak the resulting status after it appears. If the recording cannot accommodate the words, revise the capture or edit.
Do not rush the explanation to preserve the rough cut's length. This proposed script has no duration promise. The recording needs enough space for its actual content.
Choose the Delivery Method Against the Recording You Have
Integrated narration is one option. An existing locked recording may require a different production plan. First inventory the missing visuals and the available audio space. Then check what the delivery player can do.
W3C's method guidance distinguishes a separate described video from description supplied through a supported player. A timed text description file or alternate audio track depends on actual player capability. Uploading a file alone does not prove anyone can hear it.
Use this decision table as a planning aid:
| Production situation | Proposed next step | Evidence to request |
|---|---|---|
| New demo with an editable script | Rehearse integrated description | Main narration explains the inventoried visuals |
| Existing demo with useful pauses | Assess a described version or supported track | Description fits without covering meaningful speech |
| Existing demo with continuous speech | Plan a separately edited described video | Added time carries the explanation in sequence |
| Team proposes an alternate track | Test the exact delivery player | A viewer can locate, enable, and hear that track |
If a separate version becomes the chosen method, identify it clearly where the video is offered. Keep its task and content version aligned with the original. Assign someone to update both after a product change.
Do not call a separate version current because its filename includes “final.” Compare its demonstrated controls, spoken instructions, and outcomes with the release being taught.
A description production plan addresses visual information in recorded media. It does not establish keyboard access in the underlying application or cover every part of an accessible player.
Run a Listening-Only Rehearsal
Give a reviewer the task statement and the revised audio. Ask them to listen without watching the screen. Use their answers to locate missing context, not to produce a generalized pass rate.
For the fictional script, ask which record starts the demo, what state it begins in, which control opens the request, and what changes after confirmation. Compare the answers with the inventory.
If the reviewer says “the request was emailed,” return to the narration. Does any sentence imply that outcome? Does “Confirm” sound like a delivery guarantee? Clarify the observed result without inventing system behavior.
Use this proposed rehearsal checklist:
- Identify the demonstrated task and its starting state from the audio.
- Follow the action order without locating the pointer.
- Recover the exact control and field labels needed for the lesson.
- Distinguish an entered value from a completed confirmation.
- Explain the resulting state using the spoken evidence.
- Mark every phrase that depends on “here,” “there,” or “as shown.”
- Check that added description does not cover meaningful speech or sounds.
- Replay the revised audio with the video to inspect synchronization.
- Record unresolved gaps, owners, and the recording version.
Listening without the screen is an editorial check. It does not replace evaluation with disabled users or a broader accessibility review. Record what the rehearsal established and what it left untested.
Keep the Described Version Attached to Its Evidence
Hand over the visual-information sheet, approved script, recording identifiers, delivery method, and rehearsal note together. Name who owns later changes to labels or states. Keep the review questions beside the production asset.
Suppose a later fictional edit renames Request changes to Return for correction. Reopen every affected inventory row. Update the spoken label, capture, and review note together. A label correction can also affect an instruction elsewhere in the demonstration.
When the narration changes, send the final audio through caption review too. Captions represent the revised audio in text. Audio description communicates the essential visuals through sound. Both need to refer to the same recording.
The video marketing guide addresses discovery and distribution. Keep this production decision grounded in whether the lesson's information reaches the listener.
W3C guidance informs this method. The worksheet does not determine jurisdiction-specific legal duties or certify complete accessibility conformance. The deliverable is a documented description plan and a checked recording version.
Name the action. Speak the result.
Sources
- W3C WAI: Description of Visual Information. Visual-information scope, integrated description, separate described videos, timing considerations, and player-dependent files. Checked 2026.10.28. The application and review worksheets are fictional editorial examples.