Audio description across interactive film branches: script space, state, and version control
Plan audio description per branch by identifying essential visual information, reserving dialogue gaps, managing shared and route-specific versions, and preventing spoilers.
Introduction
Interactive film audio description must explain the image while respecting what each route is allowed to reveal. Mark essential visual information, available gaps, and branch permissions during writing and editing before choosing integrated description, a separate track, or descriptive text.
Interactive film accessibility cannot be reduced to a subtitle check before launch. The choice interface, playback controls, branch state, and media content form one complete journey. If any layer cannot be perceived, operated, or understood, a viewer can lose the means to continue. WCAG 2.2 defines the principles of perceivable, operable, understandable, and robust web content. This article translates relevant guidance into a production method for interactive film. It does not claim that following one article proves conformance; teams still need to confirm platform, market, and user-testing requirements.
Write an experience promise that can be accepted or rejected
The lighthouse branch at H05 visually reveals a keeper hiding a letter in a blue box; the warehouse branch does not yet know the box exists. Sharing “He pushes the blue box under the table” would leak the clue into the other route.
The examples use a fictional short film, The Letter from Fog Harbor. A viewer investigates a swapped letter at night and chooses among a warehouse, a waiting room, and a lighthouse. All people, routes, test records, and asset IDs are original teaching material. They are not real user research, completed test results, or automatic DramaFork features.
Start with one experience promise and one failure condition. The promise names who must complete which task, on what device, and under what condition. The failure condition identifies the point at which release must stop. “A keyboard-only viewer can complete every choice” is testable; “keyboard friendly” is not. Each description records source node, permitted information, spoiler boundary, time window, and locale. Let dialogue carry necessary action where natural, otherwise prepare a separate track. Prioritize action, reaction, and decision evidence over decorative detail.
Connect requirements, implementation, and evidence
| Field | Question | Evidence |
|---|---|---|
| Viewer task | What must the viewer perceive, decide, or control? | A concise task and context |
| Interaction rule | Does the default and alternative path reach the same result? | Input, focus, timing, or presentation rule |
| Branch effect | Do settings, backtracking, and re-entry preserve story state? | Entry, exit, and retained-state record |
| Acceptance | Who tests which device, and where does a failure return? | Route ID, action log, and owner |
H05-LIGHTHOUSE says the keeper pushes a blue box under the table. H05-WAREHOUSE describes an empty table and distant steps. After convergence at H06, later description may mention the box only when state_box_seen=true.
All four fields must refer to the same version. Updating a mockup without the route record makes it impossible to tell whether an old defect is fixed. Updating code without the experience promise turns “the control responds” into a false claim that the viewer understood it. Editorial, interaction, engineering, and QA are accepting a repeatable journey, not a screenshot.
Put the requirement into the production workflow
First, inventory the main route, short route, backtrack route, and no-input route. Mark every choice, playback control, and essential piece of information. Second, give each task a default and an alternative method that reach the same narrative result. Third, bind the rule to stable scene IDs, asset IDs, and state fields so that copy edits do not destroy traceability.
Fourth, test cheaply before polishing: complete a route by keyboard, at enlarged text size, with motion reduced, and after pausing and returning. Fifth, run cross-device and assistive-technology checks while recording steps, expected results, actual results, and evidence. Use one inventory for shot ID, node ID, state condition, dialogue gap, script version, recording version, and locale owner. Read every route aloud before recording. After mixing, check conflicts among description, dialogue, music, and choice cues.
A useful record does not say “looks fine.” It says: “Enter at H02, enable the alternative setting, choose the left action, verify clue_letter=true, and confirm that H03 acknowledges it.” That record covers entry, action, feedback, and exit. When it fails, the team can locate the fault in input, presentation, or narrative state.
Most failures occur at system boundaries
One linear description track misses alternate routes or leaks knowledge. Speeding narration to fit a gap harms comprehension. Translators who hear audio without seeing the matching shot and state can misidentify people, direction, or clues.
Accessibility controls also fail when they are buried in a settings page that an affected viewer cannot reach. Provide a discoverable entry at launch, at the first choice, and in the pause menu. A changed preference needs immediate perceivable feedback and must remain active at the next node. If it disappears after reload, fix it or disclose the limitation before release.
Automation can flag missing names, some contrast problems, and some focus defects. It cannot decide whether choice copy is understandable, whether audio description spoils another branch, or whether pausing breaks narrative comprehension. Route testing and participation by disabled users remain essential. Return content defects to editorial, media defects to sound or post-production, state defects to engineering, and scope conflicts to the accountable owner.
Release gates must cover the complete process
Every reachable route has description or an equivalent for essential visual information; wording stays within route knowledge; all locales match the same shot and condition; the mix is clear; enabling description does not change timing or story state.
The minimum release packet contains the feature scope, route inventory, preference defaults, interface copy in all five locales, devices and input methods tested, known limitations, defect owners, and one end-to-end record from opening to ending. W3C sources provide standards and explanatory guidance. The tables, node labels, and fictional case here are an editorial method, not a mandated W3C template.
WAI explains the purpose and forms of description for prerecorded video. Branch-state permissions and the version ledger here are a production extension. Confirm conformance level and delivery format for the actual platform and policy.
For the final check, ask someone outside the production team to reproduce the experience from the record. If they still need to ask what to press, how much time remains, what a cue means, or where a resumed session begins, the handoff is incomplete. Write the answer back into the rule and its evidence before publishing.
Sources: W3C WAI: Making Audio and Video Media Accessible; W3C WAI: Description of Visual Information.
