Label in Name: Visible Text in the Accessible Name
Also called: Visible label in accessible name, Accessible name mismatch, WCAG 2.5.3
Definition
Label in Name is WCAG success criterion 2.5.3 (Level A). For user interface components with labels that include text or images of text, the accessible name contains the text that is presented visually.
Label in name means that the words people see on a button, link or field are also part of the name that software reads. A button shows "Send", but its code says aria-label="Submit form" – a voice control user says "Click Send" and nothing happens. WCAG 2.5.3 closes that gap between visible label and accessible name.
What it means
WCAG 2.5.3 Label in Name is a Level A criterion: for user interface components with labels that include text or images of text, the name contains the text that is presented visually. The intent, in W3C's words: the words that visually label a component are also the words associated with it programmatically.
| Visible label | Accessible name | Result |
|---|---|---|
| Search | Search | Passes – name matches label |
| Search | Search for a value | Passes – name starts with the label |
| First Name: | Given name | Fails – different words |
| Send | Submit form | Fails – the visible word is missing |
W3C notes more details: capitalization and most punctuation are generally ignored, symbolic characters such as a "B" on a bold button are not labels, and components without a visible text label are out of scope. A placeholder counts as the label only when there is no other text nearby that serves as one.
Who benefits: people using voice control, who activate controls by saying the label they see, and screen reader users who can see the screen, who hear names that match the text in front of them.
Examples
<!-- Fails: aria-label replaces the visible text "Send" -->
<button type="submit" aria-label="Submit form">Send</button>
<!-- Passes: no aria-label, the visible text is the name -->
<button type="submit">Send</button>
<!-- Passes: the name starts with the visible text -->
<a href="/report.pdf" aria-label="Read more about the 2026 annual report">Read more</a>
<!-- Passes: the label element gives the field its name -->
<label for="email">Email address</label>
<input id="email" type="email" autocomplete="email">The most common cause of failures is an aria-label that overrides the visible text. W3C advises care with aria-label and aria-labelledby when a visible label already exists. For fields, a real <label> element is the safest choice – see form labels.
Let visible text be the name wherever you can, start any longer name with the exact visible words, keep abbreviations and formulas as they are written, and use a <label> element for every field.
Add an aria-label with different words to a button that already has text, label a link "Learn more" while its name says "Product details", or rewrite visible text in the name for "SEO".
How to check label in name
Questions
What is the difference between a label and an accessible name?
The label is the text people see next to or on a control. The accessible name is what software, such as screen readers and voice control, uses to identify it. WCAG 2.5.3 asks that the name contains the visible label.
Does the accessible name have to match the label exactly?
No. It must contain the visible text. W3C recommends matching where practical and starting the name with the label text when you add more words.
Does case or punctuation matter?
Generally not. W3C notes that capitalization and most punctuation are ignored for this criterion, but recommends keeping capitals where they signal an abbreviation.
Does Label in Name apply to icon buttons?
Not if the icon has no visible text. A button with only a symbol has no text label, so the criterion does not apply – it still needs a clear accessible name under other criteria.
Related terms
Accessible Name: What It Is and How It Is Computed
The accessible name is the text that browsers pass to assistive technology to identify an element – for example the words a screen reader announces for a button, link or form field. WCAG 4.1.2 requires a programmatically determinable name for every user interface component.
Read definition: Accessible Name: What It Is and How It Is Computedaria-label: How to Name Elements Correctly
aria-label is an ARIA attribute that sets the accessible name of an element as a text string. Screen readers announce this name instead of the element's content, so it is used mainly for controls without visible text, such as icon buttons.
Read definition: aria-label: How to Name Elements CorrectlyForm Labels: Clear Labels and Instructions
Form labels are the visible texts that name what a form field expects, such as “Email address”. WCAG 3.3.2 requires labels or instructions wherever content asks for user input, including formats and required fields.
Read definition: Form Labels: Clear Labels and InstructionsScreen Reader: How It Reads Websites and What It Needs
A screen reader is assistive software that reads the content and controls of a screen aloud or outputs them on a braille display. It relies on the names, roles and states that a website exposes through the browser's accessibility tree.
Read definition: Screen Reader: How It Reads Websites and What It Needs