aria-label: when to use it, when to avoid it, and how it affects accessibility
When to use aria-label, when native HTML is better, which mistakes fail WCAG 2.5.3 and 4.1.2, and how to check an element's accessible name.

An aria-label gives an element a name that screen readers announce, but it only helps when the element has no visible text to name it. Used in the wrong place, it hides a problem instead of fixing it, or breaks the match between what people see and what assistive technology hears. This guide shows where aria-label belongs, where native HTML does the job better, and how to check the result.
Key points
aria-label sets an element's accessible name. Screen readers announce that name, and WCAG success criterion 4.1.2 requires every interactive control to have one.
Missing names are one of the most common accessibility barriers. They show up across most of the apps we audit, so they're worth checking first.
Native HTML comes first. A visible <label>, button text, or alt attribute names an element for everyone, while aria-label only reaches assistive technology.
The visible text must be part of the name. When an aria-label doesn't contain the words people see on screen, voice control users can't activate the control, and the page fails WCAG 2.5.3.
What does aria-label do for accessibility?
aria-label is a WAI-ARIA attribute that gives an element an accessible name as a text string (MDN reference). It isn't shown on screen. Browsers pass it to the accessibility API, and screen readers announce it when the element gets focus.
The accessible name is the text assistive technology uses to identify an element: "Search", "Close dialog", "Add to cart". A button with only a magnifying glass icon has no accessible name unless the code provides one, so a screen reader announces just "button".
Under WCAG, success criterion 4.1.2 Name, Role, Value (Level A) requires that the name and role of every user interface component can be determined by software. A control with no name fails it.
This isn't a rare edge case. Our audit of 50 iOS and Android apps found it in almost every app we tested:
96% of the apps we audited had controls with a missing or wrong name, role, or state, such as an icon read only as "button".
Native apps use platform properties rather than aria-label, but the requirement is the same: every control needs a name.
When should you use aria-label?
Use aria-label when an interactive element needs a name and there's no visible text on the page that could provide it. Typical cases:
Icon-only buttons: close, search, menu, play, share
Icon-only links: social media icons in a footer
Repeated landmarks: two <nav> elements, named "Main menu" and "Footer menu" so screen reader users can tell them apart
A search field with no visible label, where the design doesn't allow one
Here's an icon button with and without a name:
<!-- No accessible name: a screen reader says "button" -->
<button>
<svg aria-hidden="true">...</svg>
</button>
<!-- Accessible name: a screen reader says "Close dialog, button" -->
<button aria-label="Close dialog">
<svg aria-hidden="true">...</svg>
</button>The aria-hidden="true" on the SVG stops the screen reader from announcing the graphic separately. The button carries the name.
When is native HTML the better choice?
Native HTML is the better choice whenever a visible element can name the control. W3C's guide on using ARIA puts this as its first rule: if a native HTML element or attribute already has the semantics and behavior you need, use it instead of adding ARIA.
A visible label helps everyone: people with cognitive disabilities, people who zoom in, and voice control users who need words they can say. An aria-label only reaches assistive technology.
What you need to name | Use this | aria-label? |
A form field | A visible <label for="..."> | Only if no visible label is possible |
An image | The alt attribute (how to write alt text) | No |
A button with visible text | The text itself | No |
A section that has a visible heading | aria-labelledby pointing to the heading | No |
An icon-only button or link | aria-label | Yes |
aria-label vs. aria-labelledby vs. aria-describedby
These three attributes look alike but do different jobs. Two of them set the name, and one adds extra information after it.
Attribute | What it does | Example |
aria-label | Sets the name from a text string you write | <button aria-label="Search"> |
aria-labelledby | Sets the name from visible text elsewhere on the page, by ID | A dialog named by its visible title |
aria-describedby | Adds a description that's read after the name | Password rules under a password field |
When several sources are present, browsers follow the W3C accessible name computation. aria-labelledby wins over aria-label, and both win over a <label>, the element's own text, and the title attribute. So an aria-label on a button replaces the button's visible text for screen readers. That's how most mismatches start.
An aria-label that doesn't contain the words on screen leaves voice control users with a button they can see but can't name.
Which aria-label mistakes fail WCAG?
Most aria-label problems come from adding it where it isn't needed, or writing it without checking what's on screen. These are the ones to look for in code review.
Mistake | What happens | WCAG |
The aria-label doesn't contain the visible text (button shows "Buy", aria-label says "Add product to basket") | A voice control user says "click Buy" and nothing happens | Fails 2.5.3 Label in Name |
An icon button or link has no name at all | The screen reader announces only "button" or the link URL | Fails 4.1.2 Name, Role, Value |
aria-label on a <div> or <span> with no role | The ARIA spec prohibits naming these generic elements, so assistive technology may ignore the label | Can fail 4.1.2 |
aria-label on an element with role="presentation" or aria-hidden="true" | The element is removed from the accessibility tree, so the name is never announced | Can fail 4.1.2 if the element is interactive |
The aria-label includes the role ("Search button") | The screen reader says "Search button, button" | Not a failure, but noisy |
To pass 2.5.3, the accessible name has to contain the visible text. W3C also recommends putting that text at the start of the name. "Add product to basket" fails because it doesn't contain "Buy". "Buy, add product to basket" passes and follows the recommendation.
How do you check an element's accessible name?
You can check any element's name in a few minutes with tools you already have. An automated scan finds missing names quickly, but only a manual check tells you whether the name makes sense.
Open the browser's accessibility panel. In Chrome or Firefox developer tools, select the element and look at the Accessibility pane. It shows the computed name and where it comes from.
Run an automated scan. It flags buttons, links, and form fields with no name. Our comparison of manual and automated accessibility testing explains what each method catches.
Tab through the page with a screen reader. Use NVDA on Windows or VoiceOver on macOS, and listen to what each control announces.
Say the visible label out loud. With voice control (Voice Access on Windows or Voice Control on macOS), say "click" plus the text you see. If nothing happens, the name and the label don't match.
For a full review, Accessiway (a team.blue company) checks accessible names on every user journey as part of our web accessibility audit and remediation service. It's one part of our website accessibility solutions.
Where to begin?
Use aria-label only to name interactive elements that have no visible text, and make sure every name contains the words people see on screen.
Scan your site for buttons and links with no accessible name.
Check every icon-only button and link in the browser's accessibility panel.
Replace aria-labels with visible labels wherever the design allows, especially on form fields.
Fix any aria-label that doesn't start with the control's visible text.
Add an accessible name check to your code review, so new components ship with names.
Additional resources
How to plan a website accessibility audit, from scope to retest
The European standard that includes these WCAG criteria for web, apps, and documents
Want to know how your site handles accessible names today? Run our free website accessibility checker and see where your barriers are.
Content generated with the support of artificial intelligence and subject to human oversight and review

Editorial Board
An accessibility audit is more than a scan. How to do an accessibility audit, which standards apply, what the report should contain, and what it costs to have one done properly.
Audit & Testing

Editorial Board
For many people, morning coffee is a small ritual: a moment of pause before everything begins. If that gesture depends on an app, it shouldn't become an obstacle. That's where we started with Lavazza.
Digital Accessibility

Author
When the EAA and ADA both apply to a European company with US customers, what differs, and the shared, EU-only, and US-only tasks to tackle them.
Legislation