# Accessible Name

An accessible name is the programmatically determined label that assistive technologies use to identify an interface element.

- Type: term
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/accessible-name/>)

## What it means

An accessible name identifies the purpose of a control, landmark, image, or other element in the accessibility tree. Browsers compute it from sources such as associated labels, element content, alternative text, or ARIA naming attributes according to a defined precedence. It is distinct from an accessible description, which supplies supplementary detail.

## Why it matters

Screen-reader users navigate and operate interfaces through announced names, roles, states, and values. Clear names also support voice control, automated testing, and consistent component APIs; missing or mismatched names make controls difficult or impossible to identify.

## When to use it

Ensure every interactive element and any non-text content requiring identification has an appropriate accessible name. Prefer visible text and native labeling mechanisms; use ARIA naming when native semantics cannot express the relationship.

## How it works

1. Identify what each element needs to communicate when encountered outside its visual context.
2. Provide a persistent visible label and associate it with the element using native HTML where possible.
3. Use alternative text or ARIA naming only for cases that native content and labels do not cover.
4. Keep the accessible name aligned with visible wording, especially for speech-input users.
5. Inspect the computed accessibility tree and test ambiguous, repeated, icon-only, and changing controls.

## A practical example

A magnifying-glass icon button has visible nearby text “Search” and the same computed accessible name. When it changes to a close action, both the icon and accessible name change to “Close search,” so visual, screen-reader, and voice-control users receive one consistent purpose.

## Where it breaks

A correct name does not supply keyboard behavior, focus handling, role, state, or clear visible design. Naming rules have precedence, so adding aria-label can unexpectedly replace useful descendant text; assistive-technology output can also vary.

## Common mistakes

- Using placeholder text as the only name for a form field.
- Giving a control an accessible name that differs from its visible label.
- Adding aria-label when existing native text already provides the correct name.
- Confusing an accessible description or tooltip with the primary name.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/accessible-name/#visualization-accessible-name>)

## Sources

1. [Accessible Name and Description Computation 1.2](<https://www.w3.org/TR/accname-1.2/>) — World Wide Web Consortium · Technical specification
2. [Understanding Success Criterion 4.1.2: Name, Role, Value](<https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html>) — W3C Web Accessibility Initiative · Standards guidance

## Related topics

- [Accessibility Tree](<https://wiki.soroush.uk/topic/accessibility-tree/>)
- [Semantic HTML](<https://wiki.soroush.uk/topic/semantic-html/>)
- [Screen Reader Design](<https://wiki.soroush.uk/topic/screen-reader-design/>)
