Accessible Dropdown Patterns Overview
What you'll learn: How to recognize the difference between menu button patterns and navigation menu patterns, and when each is appropriate for dropdown interfaces.
The Two Core Dropdown Patterns
Not all dropdowns are created equal. In accessible web development, there are two distinct patterns that look similar but serve different purposes:
Menu Button Pattern – Think of this like a software application menu (File, Edit, View). Clicking a button reveals a list of actions the user can perform. Examples include "More actions," "Share options," or "Export formats." These use role="menu" and role="menuitem", support arrow key navigation, and typically close after selecting an action.
Navigation Menu Pattern – This is for groups of links that navigate somewhere, like a site's main navigation with category dropdowns. These use standard semantic HTML (<nav>, <ul>, <li>, <a>) and might use aria-expanded to indicate state. Users expect to Tab through links, not use arrow keys.
When to Use Each
Choose Menu Button when:
- Users perform commands or actions (delete, share, print)
- Selection triggers immediate behavior
- The dropdown behaves like desktop software menus
Choose Navigation Menu when:
- Users navigate to different pages or sections
- Items are primarily links
- It's part of your site's wayfinding structure
Using the wrong pattern confuses screen reader users who expect specific keyboard behaviors and announcements based on ARIA roles.
Key Takeaway: Menu buttons are for actions with role="menu", navigation menus are for links using semantic HTML—choose based on what users do with the dropdown, not how it looks.