Writing Accessible Names That Convey Purpose
Writing Accessible Names That Convey Purpose records a distinct W3C-supported interface-writing task while keeping implementation mechanics outside the writing guidance.
Write an accessible name that tells users the element’s purpose or intent and makes it distinguishable from similar elements on the page.
Key details
Important caveats
Scope Boundary
This page covers name composition; role selection, state properties, and implementation technique remain separate accessibility concerns.
Further guidance
Content
Name the action, destination, field, region, or object in terms that tell users what the element is for rather than merely describing its appearance.
Practical Application
Write names around the user’s task or destination so similar controls can be distinguished without relying on nearby visuals, position, or icon shape; include the object when a bare verb would be ambiguous.
Purpose
Purpose-led wording lets users predict what an element does and distinguish it from nearby controls or regions.
Reader Check
If the element were announced out of context beside similar controls, would its name still reveal what it does or where it goes?
Worked Example
Example: Prefer “Download invoice PDF” to a repeated “Download” label when the page also offers downloads for a receipt and a statement.
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.