WEBSITE PLANNING

Review a Mobile Menu With Keyboard and Touch

Test mobile navigation states, keyboard focus, back-button behavior and menu overlap before approving a redesign.

List the menu states

Write down closed, open, selected section and returned-to-page states. At each state, identify the visible control, its accessible name and where keyboard focus belongs. The menu button should communicate the action clearly; an unexplained decorative icon is not enough for a reviewer to understand how the control is meant to work.

Reproduce the awkward cases

Try opening the menu, following a link, returning with the browser back button and rotating the phone. Check whether a fixed menu covers the page heading or quote button. Then use a keyboard to open and close the menu. Record an exact sequence such as open, expand Services, close, Tab. This separates a repeatable component defect from a vague impression that the mobile site feels difficult.

Approve the behavior as well as appearance

A proposed redesign may look simpler while hiding important destinations behind another unexplained tap. Agree which links belong in the primary menu and which can remain in contextual navigation. Validate the menu on a page with a long title and on the contact page. Keep screenshots and reproduction steps in the release note, and repeat the checks when shared navigation changes.

Reference and next step

Reference: W3C menu tutorial. For help reviewing a specific implementation, send the affected website address and describe the task customers are trying to finish.