Does WCAG require the visible label in the name?
Yes. WCAG 2.5.3 requires a control’s accessible name to contain its visible text label, including text presented as an image. Matching those words helps people activate controls by voice. Start with the displayed wording, then check the name the browser actually exposes rather than assuming the markup is correct.
ADASupport · Published and sources checked November 16, 2026

Why can a button work with a mouse but fail by voice?
A person may say the words printed on a button while speech software uses its accessible name to find the target. If those strings disagree, the visible instruction may not identify the control. Mouse testing alone will not reveal this mismatch because pointing does not depend on the name.
Imagine a button that displays “Send request” but has aria-label="Contact office". The button may respond to a click, yet its programmatic name omits the visible label. This is an illustrative implementation mistake, not a report about a particular website.
Source: W3C Understanding Label in Name.
How should developers repair a mismatched accessible name?
Prefer the control’s visible text as its naming source. For a native button, its text content often supplies the name without extra ARIA. For a field, use a properly associated visible label. If additional naming text is necessary, retain the visible words and test the computed result.
For the illustrative button above, <button>Send request</button> avoids the competing label. Where context is genuinely needed, an accessible name such as “Send request for an audit” preserves the displayed words. Do not treat adding aria-label to every element as an accessibility upgrade.
What should a practical label-in-name check record?
Record the visible label, the browser’s computed accessible name, the element type, and the page state for each tested control. Compare the strings and investigate missing or replaced wording. Repeat after validation messages, language changes, or dynamic updates, because the initial page may not represent the interaction people actually use.
Suggested test record: page URL; control and state; visible wording; computed name; mismatch; proposed repair; retest result. This is an editorial QA workflow, not a substitute for the complete WCAG conformance process. Include navigation, search, forms, and repeated card actions in the sample.
Which official sources support this check?
Use the normative WCAG success criterion for the requirement, the W3C Understanding document for interpretation, and the ARIA Authoring Practices Guide for naming patterns. These resources serve different purposes. The references below were checked on November 16, 2026; applying one criterion does not establish whole-site conformance.
What other accessibility checks belong in the same review?
Check the surrounding form and interaction rather than treating a corrected name as the finish line. A field can have a matching name while its instructions remain unclear, and a correctly named button can still be unreachable by keyboard. Use the related guides below to plan those separate checks.
Must the accessible name be exactly the visible label?
Not necessarily. The criterion requires the accessible name to contain the visible text label, rather than requiring every name to be identical. Keeping the displayed wording at the beginning is a W3C best practice. Extra context should be useful and should not replace the words people can see.
Does an icon-only button fail Label in Name?
Not merely because it has no visible text. Label in Name addresses controls whose labels include text or images of text. An icon-only control still needs an appropriate accessible name under other requirements. Evaluate its purpose and naming separately instead of treating this criterion as permission to leave it unnamed.
Can a passing label check prove that a website meets WCAG?
No. A label comparison addresses only part of an accessibility evaluation. A conformance assessment must consider the applicable success criteria, full pages, and complete processes. Keep the label result as one documented test, alongside checks of keyboard operation, focus, form errors, contrast, and other relevant requirements.