Keeping Accessible Names Concise
Keeping Accessible Names Concise records a distinct W3C-supported interface-writing task while keeping implementation mechanics outside the writing guidance.
Keep accessible names brief—often one to three words—but add enough wording to preserve purpose and distinguish the element when context requires it.
Key details
Important caveats
Scope Boundary
One to three words is typical, not an absolute maximum; complex controls may require additional words when brevity would create ambiguity.
Further guidance
Content
Use the shortest wording that still communicates the necessary purpose and distinction; remove filler and duplicated context that assistive technology will already announce.
Purpose
Concise names reduce listening effort and improve navigation efficiency without sacrificing clarity.
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.