Menu & Menubar — Learning Bundle
This learning bundle compares two different terms. A menu lists commands. A menubar is an always-visible group of command menus. The bundle is not one standard interface term.
A real example
In an editor, the menubar opens File and Edit menus. People can move through them with the keyboard.
Main parts
- 01Current location
- 02Destination labels
- 03Focus order
- 04Responsive behavior
Use it when
Use this guide to build a menu or menubar for an app with many commands.
Do not use it when
Never give a normal website navigation bar the menu behavior of a desktop app.
Name used in code
role="menu" / role="menubar" Before you ship
Check that every member concept has its own name and link. Show all members in the same situation. Give a visible rule for when each one applies and which groups are valid. Never present the bundle as one canonical pattern or as parts that can be swapped freely.
Outcome: Use Menu & Menubar — Learning Bundle to compare its member concepts. Keep their boundaries clear, then decide which members apply and which can work together. User context: In an editor, the menubar opens File and Edit menus. People can move through them with the keyboard. Learning bundle to unpack: Menu & Menubar — Learning Bundle. Canonical members: Menu, Menubar Why this comparison helps: Use this guide to build a menu or menubar for an app with many commands. Do not treat the bundle as one pattern when: Never give a normal website navigation bar the menu behavior of a desktop app. Comparison requirements: Name every member concept on its own. Explain its job and limits. Show every member in the same real situation. Give a visible sign for when to use, combine, or leave out each member. Decision quality: Keep platform and evidence limits clear. Show which members can work together. Point out false matches, unsafe swaps, and cases that need another concept. Acceptance criteria: A reader can explain each member in one sentence and tell them apart in the example. They can defend the chosen member or valid group and open every canonical guide. Evidence and limits (evidence boundary): This is not a normative standard. Its name, limits, and expected behavior can change from one source to another. Unknowns to confirm: Target platform, decision setting, limits, and evidence needed to use, combine, or leave out members.
Check this request
Review the current use of Menu & Menubar — Learning Bundle. Definition: This learning bundle compares two different terms. A menu lists commands. A menubar is an always-visible group of command menus. The bundle is not one standard interface term. Release checks: Check that every member concept has its own name and link. Show all members in the same situation. Give a visible rule for when each one applies and which groups are valid. Never present the bundle as one canonical pattern or as parts that can be swapped freely. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.