Writing Accessible Menu Labels
Writing Accessible Menu Labels records a distinct W3C-supported interface-content task while keeping implementation mechanics outside the writing guidance.
Give a menu a concise name that communicates the purpose of the choices it contains, normally aligning that name with the control that opens the menu.
Key details
Important caveats
Scope Boundary
This page covers the menu container’s name; menubar names, individual menu-item wording, and menu-button labels remain separate concerns.
Further guidance
Content
Write a menu-level name only when needed to identify the choice set; keep it aligned with the opener or purpose instead of duplicating individual item text.
Practical Application
Name a menu for the set of choices it contains, normally aligning the wording with the control that opens it so users hear a consistent purpose across the trigger and the menu.
Purpose
Clear wording helps assistive-technology users understand the component or content in context without relying on implementation details.
Reader Check
Would the menu name still make sense if announced without the visual trigger, and does it distinguish the menu from other menus on the page?
Worked Example
Example: A button labeled “Export options” can open a menu with the accessible name “Export options.”
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
- Providing Accessible Names and Descriptions — W3C WAI ARIA APG (opens in a new tab)W3C Web Accessibility Initiative · W3C WAI-ARIA Authoring Practices guidance for descriptive accessible names, visible labels, and button/control naming.