Writing Unique Accessible Names
Writing Unique Accessible Names records a distinct W3C-supported interface-writing task while keeping implementation mechanics outside the writing guidance.
When repeated controls or regions need to be distinguished, add the smallest meaningful context that makes each accessible name unambiguous.
Key details
Important caveats
Scope Boundary
Do not force artificial differences when controls truly perform the same action in the same context; uniqueness should communicate a meaningful distinction.
Further guidance
Content
Add the minimum distinguishing context—such as the affected item, destination, or section—when otherwise identical names would leave users unable to tell elements apart.
Practical Application
When repeated controls have different targets, add only the context needed to distinguish those targets—such as the item name, destination, or section—while keeping the action wording consistent.
Purpose
Distinct names make lists of controls and landmarks understandable when users navigate out of visual context.
Reader Check
If a screen-reader user encountered these controls in a list outside visual context, could they tell which item each control affects?
Worked Example
In a list of invoices, use names such as “Download invoice 1042” and “Download invoice 1043” instead of giving every button the identical name “Download.”
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.