Accessible Name
An accessible name is the programmatic name used to identify an interface element to assistive technologies.
It tells someone what a button, link, form control, image, or other relevant element is or does.
What It Means in Practice
A visible button may simply say:
Search
That text can also become its accessible name.
For other elements, the accessible name may come from a <label>, alt text, aria-label, aria-labelledby, or other supported markup.
The important part is that the element has a meaningful name that reflects its purpose.
How It Works
Browsers calculate accessible names from the page's HTML and accessibility information.
Native HTML often provides the simplest route. A properly associated form label, meaningful button text, or well-written image alternative can provide the necessary name without additional ARIA.
When visible text already identifies a control, the accessible name should normally remain consistent with that visible wording.
Why It Matters
Visual design often provides context that is unavailable to someone using a screen reader or voice-control software.
Without an accessible name, a control may be announced simply as “button” or “link,” leaving the user without enough information to know what it does.
Common Problems
Common problems include:
- Icon-only buttons without names
- Form inputs without associated labels
- Generic link text
aria-labeloverriding useful visible text- Accessible names that do not match visible labels
- Informative images without useful alt text
How to Improve
Prefer clear visible labels and semantic HTML.
Use ARIA naming techniques when native markup cannot provide the necessary name, and verify important controls during manual accessibility testing.