7AAVDH22 Chap.7 Accessible Interaction Prototypes
Accessible Interaction Prototypes
Storyboard the encounter
The accessible-design seminar asks teams to define audiences, interaction sequences, interfaces and physical-digital touchpoints around their 3D content. A storyboard should show where the encounter begins, what evidence appears, what the user does, how the system responds and what can happen next.
Include the physical setting and device whenever they change the action.
Prototype interpretation, not decoration
Keep the heritage purpose visible in every frame. If users compare surface traces, show how they reach the comparison and where provenance appears. If they hear multiple accounts, show attribution, sequence and navigation. Decorative transitions should not occupy more attention than the evidence.
A low-fidelity prototype is useful because the reasoning can change before technical investment hardens it.
Attach a barrier question to each action
For every tap, movement, reading or listening step, ask who may be unable to complete it and why. Decide whether an alternative action preserves the essential task. A transcript may replace words but not spatial sound unless position is described.
Keyboard operation may exist while a poor focus order still hides the comparison. Test the route, not only the presence of features.
Observe the first divergence
Give participants an interpretative task without explaining the intended route. Record the first point where their expectation and the prototype differ. Ask what they thought would happen and what evidence they believe supports the response.
Repair the earliest failed assumption, then retest understanding rather than rewarding interface completion.
Include physical-digital transitions
A sign that introduces scanning, a device handover, a headset fitting, a location cue and the return from screen to object are all touchpoints. Desk tests may hide glare, noise, crowding, poor reception or divided attention.
Conduct a context-aware walkthrough when possible and label anticipated behaviour separately from observed behaviour.
Turn versions into report evidence
Preserve dated storyboards, task scripts, anonymised observations, decisions and revised sequences. A useful iteration record states the version, observed behaviour, challenged assumption, design change and next test.
It can also preserve unresolved trade-offs, such as a larger control covering evidence or a text route weakening spatial comparison. Critical reflection needs those decisions, not only the final interface.
What this chapter covers
- 01
Storyboard
- 02
Interaction Sequence
- 03
Physical Touchpoint
- 04
Paper Prototype
- 05
Task Observation
- 06
Iteration Record
Worked example · free
Repair a hotspot timeline
- 2Restate the essential interpretative task.
- 3Repair control, source cues and alternative route.
- 3Specify the next observation and outcome.
Key terms
- Storyboard
- Storyboard is a sequence of frames showing context, evidence, user action, interface response and transition.
- Touchpoint
- Touchpoint is a physical or digital moment where users encounter information, controls, equipment or staff.
- Paper Prototype
- Paper Prototype is a low-cost representation used to test sequence, expectation and interpretation before implementation.
- Task Observation
- Task Observation records how a participant attempts an essential action without being taught the intended route.
- Iteration Record
- Iteration Record links a tested version, observed behaviour, challenged assumption, revision and next test.
Accessible Interaction Prototypes FAQ
What should a heritage storyboard include?
Show entry context, heritage evidence, user action, system response, physical-digital transitions, alternative routes and the next interpretative possibility. A storyboard should expose assumptions and decisions rather than imitate the final visual style.
How many users prove a prototype works?
No small test proves universal success. Individual observations can reveal interface and interpretation problems, while repeated patterns support revision. Cultural authority and wider accessibility may require different participants, consultation and methods. Report the tested scope honestly.
How does prototype evidence enter the report?
Describe the tested version and task, report the observation, identify the challenged assumption, show the revision and name the next test. Connect the change to heritage purpose, access or interpretation rather than presenting preference feedback alone.
Assessment move
Draw the essential interaction in six frames and write the heritage evidence visible in each one. Add one alternative route and one physical-digital transition. Ask another person to complete a single interpretative task without guidance, record the first divergence and revise that frame. Preserve both versions and write a five-line iteration record.
Repeat later in the intended context or state which contextual assumptions remain untested. Run a second test in which the control works but the participant misunderstands the heritage claim, then revise the evidence or sequence rather than the button. Compare the two failures to keep usability and interpretation distinct.
Record what the participant actually did and said before assigning a cause, and keep the unresolved alternative explanation.