WCAG 2.2 success criterion 2.5.3, Label in Name, is a Level A requirement: accessible name contains the visible label.
Read the criterion in the W3C Recommendation, WCAG 2.2 (opens in a new tab).
How BearScan checks it
Accessible name contains the visible label
Checked automatically: loads the page in a browser. Severity: medium. Voice-control users speak the visible label; if it is not in the accessible name, the command silently fails.
An approximation: For up to 400 visible links, buttons and fields, the text a person can see on the control (hidden, clipped and off-screen text left out; a field's own label) is compared with the accessible name Chromium computes for it, ignoring case, punctuation and spacing. A name that does not contain the visible words fails. A label drawn only by an image or an icon font has no text to compare, and a control past the first 400 is not compared. axe-core's experimental label-content-name-mismatch is folded in.
How to fix it. Make the accessible name start with, or at least contain, the control's visible text. An aria-label that replaces the visible wording is the usual cause.
All WCAG 2.2 criteria · Next: 2.5.4 Motion Actuation
Questions
Is WCAG 2.5.3 required by the ADA?
The ADA doesn't name a technical standard for businesses, but the Justice Department's 2022 guidance points businesses to WCAG, and its 2024 rule for state and local governments adopted WCAG 2.1 Level AA, which includes 2.5.3.
Can an automated tool check WCAG 2.5.3?
Mostly. BearScan checks it automatically (loads the page in a browser). A clean result still isn't proof every page passes, only the pages scanned.
How do I fix a WCAG 2.5.3 failure?
Make the accessible name start with, or at least contain, the control's visible text. An aria-label that replaces the visible wording is the usual cause.