Who this is for: Product teams planning a truthful and usable release storyboard.
What to prepare
- Before-and-after evidence for the same interaction.
- Documented test environment and scope.
- Approved claim wording and remaining limitations.
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Task context
Show the illustrative file-picker dialog and identify keyboard operation.
On screen:Choose a file using the documented keyboard path.
- 02
5–11s
Previous treatment
Show the supplied prior focus appearance at a matched scale.
On screen:Previous focus treatment.
- 03
11–18s
Current treatment
Repeat the same path using the updated action-button indicator.
On screen:Updated focus on these action buttons.
- 04
18–25s
Inspection
Hold the focused control; distinguish any explanatory annotation from actual UI.
On screen:Identify the focused action.
- 05
25–30s
Scope and feedback
Show the documented test scope and approved issue-reporting route.
On screen:This demonstration covers the stated tested context.
Make it your own
- Task
- Name the interaction covered by the evidence.
- Change
- Specify the actual implemented treatment.
- Test scope
- Retain tested and untested conditions distinctly.
Control the comparison
Use the same theme, viewport and task. Do not improve the new version through editorial contrast changes that are absent from the product. Identify any annotation as explanatory rather than part of the interface.
Adapt the information channel
Include a readable textual summary and meaningful narration or captions as appropriate. For a nonvisual interaction change, use the owner's approved evidence rather than forcing a purely visual comparison that cannot establish the result.
Review the claim boundary
A specific fix can be valuable without a broad compliance claim. If standards language is needed, obtain current primary-source evidence and suitable review of that exact claim. Keep future testing separate from completed evidence.
Review checklist
- The matched task and environment are documented.
- Editorial annotations do not alter the product evidence.
- The claim stays within tested scope.
- The explanation includes clear textual support.