frameworkExperience & interface

Menu and Menu Button

A menu presents a compact list of commands or choices, while a menu button is the control that opens and closes that menu.

Download Markdown (.md)

01What it means

A menu is a transient or persistent list of actions, functions, or states that follows platform-like navigation conventions. A menu button exposes a menu on activation. Context menus, pull-down menus, and menu bars are variants; a menu is distinct from a select or listbox used primarily to choose a form value.[1][2]

02Why it matters

Menus conserve space and group related commands, but they hide options and introduce focus, keyboard, positioning, and dismissal rules. Naming the pattern precisely prevents teams from calling every popup a dropdown and implementing incompatible behavior.

03When to use it

Use a menu for a set of related commands that should not all remain visible, especially secondary or contextual actions. Keep frequent primary actions visible, use a select or combobox for form values, and use ordinary navigation links when application-style menu behavior adds no value.

04How it works

  1. Define whether the items are commands, navigation destinations, selectable states, or submenus.
  2. Place the most important items first and group related items with restrained separators.
  3. Expose the opener’s expanded state and move focus into the menu when it opens.
  4. Support expected arrow-key, type-ahead, activation, and Escape behavior.
  5. Close on selection or dismissal, return focus appropriately, and test edge positioning and touch targets.

05A practical example

Example

A project card keeps Open visible as its primary action and places Rename, Duplicate, Move, and Archive in a labeled More actions menu button. Keyboard users can open the menu, move between items with arrow keys, dismiss it with Escape, and return to the opener.

06Where it breaks

Hidden commands are less discoverable, nested menus are difficult on touch and with magnification, and custom menu widgets are complex. Familiar-looking menu labels can still be ambiguous when scope or consequences are unclear.

Common mistakes

  • Using menu semantics for a basic list of page links without implementing menu keyboard behavior.
  • Mixing actions and form-value selection without a clear interaction model.
  • Opening a menu without exposing expanded state or managing focus.
  • Putting the primary or only recovery action inside an obscure overflow menu.

07Sources

  1. Menu and Menubar PatternW3C Web Accessibility Initiative · Technical guidanceMenu and Menubar Pattern
  2. MenusApple · Institutional guidelineMenus
View saved topics

Start typing to search titles, definitions, categories, and frameworks.