Menu and Menuitem Roles
You'll learn how to use ARIA menu roles to create application-style dropdown menus that screen readers interpret as interactive widgets, not simple navigation links.
What Are Menu Roles?
When building dropdown menus that behave like desktop application menus (think File, Edit, View menus in software), you need to tell assistive technologies these aren't ordinary navigation links. ARIA provides four specific roles:
menu: Container for menu itemsmenuitem: A clickable action in the menumenuitemcheckbox: A toggleable option (on/off state)menuitemradio: One option in a mutually exclusive group
These roles create application mode behavior in screen readers, where arrow keys navigate items instead of reading line-by-line.
The Structure Pattern
A typical menu structure looks like this:
<button aria-haspopup="true" aria-expanded="false">
Actions
</button>
<div role="menu">
<button role="menuitem">Save</button>
<button role="menuitem">Delete</button>
<button role="menuitemcheckbox" aria-checked="false">
Show Grid
</button>
</div>
Think of it like a restaurant menu: the menu container (role="menu") holds individual choices (menuitem), some of which might be customizable options (menuitemcheckbox).
When to Use These Roles
Use menu roles for application-style actions (Save, Delete, Copy), not site navigation. Navigation links should remain as regular <nav> elements with lists and links. Menu roles tell screen readers: "This behaves like desktop software, use arrow keys and expect actions, not page changes."
Key Takeaway: Use menu, menuitem, menuitemcheckbox, and menuitemradio roles only for application-style menus with keyboard-driven actions, not for standard website navigation—this triggers specialized screen reader behavior.