Who this is for: Product teams writing a precise visual brief for a software update.
What to prepare
- Matched captures from the documented keyboard task.
- The tested environment and current focus behavior.
- Approved claim wording and known limits.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second explanation for a fictional file-picker dialog with an updated focus indicator on its action buttons. Keep the same dialog, theme, viewport and illustrative file in both versions. Establish the keyboard task and show the supplied focus sequence. Label the previous and current treatments without exaggerating the old state. Hold on the currently focused button long enough to inspect the indicator. Use an editorial annotation to identify focus if needed, but distinguish it from the actual product UI. State the verified scope: the named buttons and tested context. Do not claim that every screen is accessible or that a standard has been met without separate evidence. End with a concise text summary of the change and the approved route for reporting a remaining issue. Avoid rapid flashing emphasis.
Make it your own
- Tested task
- Use the exact interaction covered by the team's evidence.
- Environment
- Keep the approved theme, device and input conditions explicit.
- Claim boundary
- State what was verified and avoid untested generalization.
Keep the comparison honest
Changing background contrast or enlarging the new indicator only in production can distort the product comparison. Show the actual treatment at an equivalent scale. If an annotation helps viewers find it, label or style that annotation as explanatory.
Adapt the supporting text for independent understanding
Name the button and action in narration or visible copy rather than relying on “this” and a subtle outline. Provide a readable summary alongside the video. Any standards claim needs current source evidence and appropriate review beyond this creative brief.
Repair overbroad claims
Replace “Now accessible for everyone” with the specific implemented and tested change. If evidence covers only one theme, do not alternate through untested themes for visual variety. The final scope should match the source record.
Review checklist
- The task and environment match the supplied test evidence.
- Product focus treatment is distinguishable from annotations.
- The claim stays within the tested scope.
- The explanation itself has clear textual support.