Accessible save and resume for interactive film: retain preferences, state, and context
Design save and resume around checkpoints, retained accessibility preferences, narrative state, and concise recaps so returning viewers do not have to reconfigure or remember everything.
Introduction
Accessible resume means more than returning to a timestamp. The viewer needs the correct narrative state, accessibility preferences, and essential context. A resume point should be explainable, reversible, and should not require repeating a step that already blocked the viewer.
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
A viewer exits at H05 and returns the next day to a single Continue control. The system starts H04, disables audio description and reduced motion, and hides the prior choice. The viewer cannot tell whether the save failed, the story rewound, or memory is wrong.
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. The save packet records node, completed choices, key state, playback position, caption locale, audio description, text, and motion preferences. Before resume, give a short recap and location with choices to continue, review known clues, or return to a safe prior node.
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 |
Resuming H05 says, “You found the blue box at the lighthouse and have not opened it,” then returns to a stable pre-choice point. If an update removed the old node, migrate to H05-SAFE, explain the move, and preserve state_box_seen.
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. Test autosave, explicit exit, browser close, device change, and content update. Compare state and preferences before and after. Verify that recaps in all five locales add no new clue, and check reading order, focus landing, and back behavior.
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
Saving only a timestamp loses branch variables; saving only story variables loses caption and control preferences. A long recap becomes a reading barrier, while a vague one fails to orient. Silent migration to a different scene damages trust.
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
Resume preserves every completed choice and accessibility preference; the recap uses known information only; focus lands on the primary continuation; the viewer can leave the recap or return to a safe point; old-save migration has an explicit outcome and failure path.
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.
Cross-device resume introduces account, privacy, and synchronization choices. Do not collect unnecessary assistive-technology data. This method defines experience and state evidence; retention, security, and regulatory review remain separate.
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: Help Users Find What They Need; W3C WCAG 2.2.
