Navigation Menus vs Application Menus
What you'll learn: You'll discover the critical difference between menus that link to pages and menus that trigger actions—and why screen readers care.
The Two Types of Menus
Not all dropdown menus are created equal. When you click a menu, it might either navigate you somewhere new or perform an action right where you are.
Navigation menus contain links that take you to different pages or sections. Think of a website's main navigation with options like "About," "Products," or "Contact." These use standard <a> elements and often the <nav> landmark.
Application menus contain commands that execute actions within the current page—like "Copy," "Delete," or "Export." These behave more like desktop application menus and use button elements with menu and menuitem roles.
Why This Distinction Matters
Screen readers announce these differently:
- Navigation menus are typically announced as links within a navigation region. Users expect to press Enter to follow the link.
- Application menus use the
menu/menuitemARIA roles and are announced as interactive controls. Users expect arrow keys to work and Enter/Space to trigger actions.
The Analogy
Think of a restaurant menu (navigation) versus a TV remote control (application). Both present options, but one helps you choose where to go while the other helps you do something right now.
Use <nav> + <a> for navigation. Use button + role="menu" for actions. Mixing them up confuses assistive technology users about what will happen when they activate an item.
Key Takeaway: Navigation menus use links and take users places; application menus use buttons and perform actions. Match your markup to the behavior users expect.