Accessible name

Definition

An accessible name identifies a control, landmark, image, or other interface object to assistive technology. Visible text often supplies the best name.

Example

<button type="button">Save draft</button>

Here, “Save draft” is both visible and available to the accessibility tree. Prefer that agreement over an invisible label that contradicts the interface.

Where names come from

The browser computes a name from sources defined for the element. Visible button text commonly names a button. A label associated with an input names that input. Image alternative text can name an informative image, while link contents usually name a link. ARIA attributes can participate, but they should not replace a clear native relationship without a reason.

Name sources have precedence. Adding aria-label can override useful visible text and create a mismatch between what sighted users see and what assistive technology announces. Inspect the computed accessibility tree when more than one possible source is present.

Name versus description

A name answers “what is this?” A description supplies secondary instructions or context. For a password field, “Password” is the name; “At least 12 characters” may be a description associated with aria-describedby. Do not put all instructions into the name, because repeated navigation then becomes noisy.

Visible text and the accessible name should share the words people use to identify the control. That agreement supports voice control, screen sharing, and support instructions such as “Choose Save draft.”

Practical testing

Navigate by keyboard and confirm that every interactive control receives a specific name. Inspect the browser accessibility tree, then listen with a screen reader in form or link navigation. Check repeated controls especially closely: several links all named “Read more” are hard to distinguish outside their visual context.

Automated tools can find missing names and some conflicts, but they cannot decide whether a technically present name is accurate, concise, or useful for the current task.

Common failures

• Using a placeholder as the only input label.
• Giving an icon button only a tooltip that is not reliably exposed.
• Overriding visible wording with a contradictory aria-label.
• Repeating the control type in the name, such as “Button: Save.”
• Treating an accessible description as a substitute for a name.