Accessible timed choices in interactive film: pause, extend, and define no-input behavior
Define pause, extension, timer-off, and no-input behavior so an interactive film can preserve urgency without turning time into an access barrier.
Introduction
Timed choices can create urgency, but a timer must not become a barrier to reading or operation. Decide whether time is essential, provide pause, extension, or timer-off paths, and define the no-input result explicitly.
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
At H04 an alarm sounds and the viewer chooses between closing a door and pursuing someone. The design shows only a shrinking bar and selects the first item after eight seconds. Longer locales, magnification, and switch scanning leave much less usable time.
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. Present complete choice information before timing begins. Pause freezes film and timer. Extension remains available more than once, and timer-off waits for explicit input. If no input is part of the story, disclose it as a separate outcome rather than disguising the first item as the viewer's decision.
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 |
H04 records timer_mode, remaining_time, and no_input_outcome. Returning from pause preserves remaining time; language changes preserve preference and re-present the choice; timer-off reaches the same two story exits without a penalty branch.
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. Measure the window from complete presentation to input closure for every timed node. Walk it in all five locales with keyboard, remote, and scanning input. Test pause on the final second, language changes after extension, tab departure, and two consecutive no-input events.
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
Slowing animation without extending the input window is a false fix. Pausing video while the timer continues creates invisible loss. Language switching that restarts the story breaks state. Silent submission of current focus is especially dangerous because focus is not intent.
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 timed node exposes adjustment before expiry; pause preserves remaining time; all locale copy fully appears; no-input behavior matches its explanation; and timer-off does not remove reachable endings.
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.
Live, synchronized multiplayer, or safety-critical experiences may have external limits that cannot be extended. This article addresses prerecorded interactive film; exceptions need a documented necessity, alternative, and disclosure.
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 Understanding SC 2.2.1: Timing Adjustable; W3C WCAG 2.2.
