UX Design Coach

The design looked finished until someone tried to leave the dialog

Run a five-minute keyboard critique on the prototype’s least photogenic moment.

By Ashley Kays Rabbitt · November 18, 2026

A designer asks for feedback on a beautiful confirmation dialog. Everyone comments on the illustration. Then someone opens it using a keyboard, presses Tab, and watches the focus indicator move to the navigation behind the overlay. The person can still see the dialog, but the controls they are operating have changed.

W3C’s accessibility checks give reviewers a place to start with keyboard operation and visible focus. For dialog-specific behavior, the ARIA Authoring Practices pattern explains where focus belongs while a modal is open and what typically happens when it closes. Bring both into the critique. W3C WAI • First checks for web accessibility W3C WAI • Modal dialog design pattern

Where keyboard focus belongs
OpenFocus enters the dialog
CancelReturn to the original trigger
RemoveFocus the next logical item

Give the reviewer a job

Start on the “Remove guest” button in a fictional event guest list. Open the dialog with the keyboard, move between its controls, cancel, and invite the same guest to a different table. Have another person record the visible focus location after every step. “Tab order feels weird” is hard to act on. “After Cancel, focus returned to the top of the guest list” is a reproducible observation.

Next, try the destructive choice using a disposable prototype record. If the original button disappears with the removed row, choose a sensible new focus target, such as the next guest or the list heading. Include that rule in the design handoff. A generic instruction to “return to trigger” leaves engineering no answer in precisely this case.

Keep a four-column critique note: action, expected focus, observed focus, recovery. Re-test the complete job after the change. The review is successful when the participant knows where they are and can continue working without reaching for a mouse.