Accessible names from a user perspective
An accessible name is the programmatic label that assistive technology use to identify an element. It tells users what a button, link, form field, or other interactive control is called, even when that name isn’t visible on screen.
In accessibility, conversations about accessible names often focus on screen readers. Buttons need labels, images need alternative text, and form fields need names.
All of this is true, but screen readers are only part of the story.
Accessible names are also used by voice control software, Braille displays, switch control solutions and other assistive technology. The same accessible name can be perceived very differently depending on how someone interacts with a page. What works well for one group of users may create challenges for another.
Accessible names and voice control
Different users experience accessible names in different ways. Some users only hear them through a screen reader. Others both see the interface and hear speech output. Users with motor impairmens and users who have reading- and writing impairments who primarily interact visually may depend on accessible names, based on what assistive technology they prefer.
Voice control users are a good example. They see what is written on the screen, but when they speak a command, the software matches what they say against the accessible name (at code level) rather than the visible label.
This relationship between visible labels and accessible names is one of the reasons behind the “Label in Name” requirement in EN 301 549 and WCAG.
The criterion requires that the accessible name contains the visible label so that users can speak what they see and successfully interact with controls.
Imagine a menu button with no visible label, only the familiar hamburger icon. Most voice control users would probably think of it as a menu and try a command such as “Click menu”. However, if the accessible name is “Open main navigation panel”, the software may be looking for something entirely different.
From the user’s perspective there is no obvious way to know this. The expected command may fail, even though the button has an accessible name. Instead, the user might need to display labels, show numbered markers or use a navigation grid to activate the control. The task is still possible, but it requires a lot more effort.

Beyond “Label in Name”
Meeting the requirement Label in name is important, but it isn’t always enough.
Different voice control solutions match names in different ways. Some use exact matching and expect users to speak the entire accessible name. Apple’s Voice Control on iOS and macOS often work this way. Others can match the beginning of a name, while some use partial or fuzzy matching and can find words elsewhere in the label. In our testing, Android’s Voice Access often behaved more like this. Some solutions can also take semantic information into account.
The result is that the position of words inside a name can affect how easy it is to use.
Consider a search field with the accessible name “Enter your search text”. The word “search” is present, so the control may satisfy the Label in Name-requirement. However, some voice control solutions may struggle because the important word appears late in the name, while others may expect users to say the entire phrase.
Another example is a menu icon with the accessible name “Toggle navigation”. The control meets the “Label in Name” requirement, but how many users would naturally think to say “Toggle navigation” when they want to open a menu? Most would probably try “Menu” or “Open menu” first.
These examples illustrate the difference between compliance and real accessibility. A control can satisfy minimum legal accessibility requirements and still make it hard or almost impossible to use as intended.
Do screen reader users need all that extra information?
It is common to add additional words to accessible names in an attempt to provide more context. The intention is usually good. However, screen readers already provide a lot of information through semantics. A correctly coded search field is announced as a search field, an expandable menu can communicate its state through attributes such as aria-expanded, and checkboxes can communicate whether they are checked or unchecked.
As a result, the extra wording added to accessible names is not always necessary. Sometimes it simply makes the name longer and, to be honest, no one enjoys an unnecessarily chatty screen reader.
Long accessible names can also create challenges for Braille display users. Braille displays have a limited number of cells, and some mobile displays can be very small. When names become unnecessarily long, more of the display is used by information that may not actually help the user.
When users see one thing and hear another
Many assistive technology users both see and hear the interface. They may look at a button labelled “Menu” while hearing “Open main navigation”. The visible label says one thing while the accessible name says another.
When the extra wording doesn’t add meaningful information, users are left with more information to process without a clear benefit. The result can be increased cognitive load.
What can designers and developers do?
One of the simplest ways to improve accessible names is to think about them early in the design process.
For designers, that often means using visible labels whenever possible instead of relying on icons alone. Visible labels make controls easier to understand and provide a clear foundation for accessible names. When a control doesn’t have a visible label, designers can help by defining the intended accessible name and documenting it through annotations.
For developers, it means understanding how accessible names are calculated and being careful when using ARIA attributes that replace native labels.
It’s particularly important to understand that aria-label and aria-labelledby override native labels. If a button already has a visible label, adding an aria-label doesn’t add information to the accessible name. It replaces it.
When additional explanation is needed, aria-describedby is often a better option. Rather than changing the accessible name, it provides supplementary information that screen readers can announce after the name. Users who need that additional context can access it, while the accessible name itself remains short and predictable.
Accessible names are part of the user experience
Accessible names are often treated as something that only matters to screen reader users. In reality, they affect a much wider group of people, including voice control users, Braille display users and people who combine multiple assistive technology.
The same accessible name can be experienced in very different ways depending on the technology being used. That’s why accessible names are not just a technical requirement. They’re part of the user experience.
Keeping them simple, keeping them consistent and thinking carefully before giving a control an accessible name that differs from its visible label can make a big difference.