Tools & Interaction
Turn a static filter panel into an interaction record
Imagine a small resource library with a search field, a category selector and an Apply button. A drawing shows where these controls sit, but not how someone operates them from a keyboard. This fictional worksheet helps a team record intended behaviour for review before implementation and subsequent testing.
01
List the controls in a meaningful working order
Name each control and describe its purpose before writing the intended focus sequence. In the library example, a reader enters a query, optionally chooses a category and applies the selection. Record the visible label and the information needed to understand each control. Include a clear way to recognise which element has focus. Do not assume that the order in a design file automatically defines a useful keyboard sequence. The document should explain the intended path in terms that both the designer and developer can discuss.
02
Specify the action and the resulting state
For each control, describe what the relevant keyboard action is expected to do, following the conventions of the chosen native control or documented component. Record what changes after Apply is activated and where focus should remain or move. If no results match, describe the message and how the reader can revise the selection. Keep unresolved component behaviour marked as a question rather than inventing a shortcut. The worksheet should connect the action to an observable result, including information that must remain available after the update.
03
Separate the proposed sequence from tested behaviour
Write a few example journeys, such as a successful search and a search with no matching resources. List the expected focus positions and visible responses for each. After implementation, record actual observations separately and note the environment used for the check. A written intention is not evidence that the interface works as specified or meets every accessibility requirement. Use discrepancies to revise the implementation or clarify the specification, retaining a version identifier so the team knows which behaviour each observation refers to.