Does every action have an explicit trigger?
Hover can reveal a shortcut on desktop, but it is not a dependable primary interaction on touch. Keep essential actions reachable through a labelled control. When a preview or card has multiple actions, ensure that selecting the card and invoking an action remain distinct.
A useful test begins without a pointer: can someone reach the action, understand its label and activate it from the keyboard? Repeat the task on a touch device rather than assuming that a narrow desktop window covers touch behaviour.
Where should a panel open?
Panel placement depends on its trigger’s location. Moving a control from a bottom toolbar to a top navigation area changes the available space. Recheck the direction, alignment and maximum size instead of carrying over the old positioning.
At narrow widths, keep the action and its result within an understandable context. An overflow menu can reduce clutter, but hiding the only explanation of a selection or error inside it may make the interface harder to use.
Can a user leave the interaction predictably?
Opening is only half the behaviour. Review outside interaction, Escape, focus movement and the state after an action succeeds. Where a dialog is used, follow its established keyboard and focus pattern.
Avoid inventing a new interaction solely to match a visual treatment. An existing accessible primitive is usually a better starting point, provided its actual behaviour is checked in the final layout.
What remains visible while work is processing?
A background operation may continue while the user changes views. Ensure the status has a discoverable home and that completed output is associated with the correct object. A smaller viewport should not erase the information needed to understand the task.
Check long labels, translated copy, text enlargement and reduced motion. The layout should remain useful when decorative movement stops and when text occupies more space than the original design expected.
Run one complete task across input methods
Choose an object, open its controls, change a value, submit an operation, recover from an error and return to the surrounding workflow. Record where selection, focus or context becomes unclear.
This review complements screenshots. A screen can look balanced while a menu opens outside the usable area or a keyboard user loses their place after closing it.
- Keyboard: reachable trigger, visible focus and predictable return.
- Touch: explicit activation and reachable dismissal.
- Layout: long content, narrow width and enlarged text.
- Async work: visible pending, success and recovery states.