A screen reader needs to know what a piece of a page is, not only what it looks like. The ARIA role menu describes a composite popup list of commands.
What this role means
A composite popup list of commands.
ARIA roles add meaning to the accessibility tree. They do not automatically make something clickable, move keyboard focus or build an interface. Those behaviors come from native HTML controls or from correctly implemented JavaScript.
See menu in a real page
<ul>
<li><button type="button">Copy</button></li>
<li><button type="button">Paste</button></li>
</ul>Read the example
You may notice that the snippet does not write role="menu" explicitly. That is intentional: the native element already communicates this meaning, so repeating the role would add unnecessary markup.
A menu widget requires arrow-key interaction; ordinary site navigation should use nav and links.
When to use it
Start with native HTML whenever possible. Add ARIA only when it provides missing meaning for an interface that you cannot build with the appropriate native element.
For custom interactive widgets, test with the keyboard and a screen reader. Depending on the pattern, you may need Enter or Space activation, arrow-key handling, state changes, focus movement and a clear accessible name. Assigning the role alone implements none of these.
Try it yourself
Put the example on a practice page and inspect it using your browser accessibility panel. If it includes interactive controls, reach them with Tab and check whether they work without a mouse. Explain whether the semantics come from native HTML or an explicit ARIA role.
Common Beginner Mistakes
- Adding
role="menu"without checking whether an ordinary HTML element already supplies the right semantics. - A menu widget requires arrow-key interaction; ordinary site navigation should use nav and links.
- Confusing the role announced by a screen reader with the behavior that the browser implements.
Key Takeaways
menuis related to a composite popup list of commands.- A menu widget requires arrow-key interaction; ordinary site navigation should use nav and links.
- Native HTML is the first choice; ARIA should clarify meaning, not replace working HTML.