Who this is for: Teams explaining keyboard interaction.
What to prepare
- Verified keyboard sequence
- Focus-state evidence
- Destination and return states
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second illustrative keyboard-led demo for opening sample request R-061. Use a supplied recording or verified sequence from the actual product. Begin with a visible focus indicator in the request list. Show the real keys used to reach R-061, labeling each key at activation. Use Tab, arrow keys or another pattern only when observed; do not invent conventional behavior. Activate the request through the supported key and hold the resulting detail heading with its focus state visible. Show the actual return or close key if part of the task. Keep the cursor parked outside the active region. End on the confirmed destination or restored list focus. Describe this as one keyboard task, not an accessibility certification or a guarantee that all controls are keyboard usable.
Make it your own
- Key sequence
- Use observed inputs rather than assumed conventions.
- Focus style
- Preserve actual visible focus.
- Task boundary
- Limit the claim to the demonstrated path.
Capture focus evidence
Record the starting focus, traversal order, activation and result. Ensure a screenshot does not lose the visible focus styling. If a control cannot be reached in the observed workflow, report that limitation instead of animating a fictional focus jump.
Adapt the task
For a form, show labels and the actual focus sequence through required inputs. For a menu, include opening and closing behavior. Keep key annotations away from the focus ring and native labels.
Fix keyboard ambiguity
If the screen changes without a key label, add the verified input at that moment. If a pointer click secretly causes the result, recapture or change the description. Do not present a mouse-assisted path as keyboard-only.
Review checklist
- Every activation has a visible key label.
- Focus remains traceable.
- No broad compliance claim is made.