Visible label text matches the accessible name
What this criterion checks
This criterion maps to 2.5.3 Label in Name. A detailed plain-language description is maintained in the WebLens criteria catalogue; the WCAG sub-test breakdown below describes exactly what the agent checks and what it does not.
How it's assessed
WebLens walks each user journey, captures a screenshot at every step, and an agent reasons over that evidence. See the how WebLens works for the full pipeline and the deterministic checks layered in for accessibility.
Sub-test coverage
2.5.3 Label in Name is broken into 2 sub-tests. Coverage is honest about where the agent is reliable, where it only partially checks the requirement, and where a human reviewer is still needed.
1 full1 partial
- The name assistive technology sees for each control contains the text that is visually displayedFull
Our tool checks controls whose role supports naming-from-content — buttons, links, tabs, menu items, and similar elements where the visible text is expected to be the accessible name. For example, if a button shows "Search," the accessible name must include "Search." This catches cases where the visible text and the programmatic name are completely different. Note: form fields that have a separate label element (like a text input with a label tag) are not checked by this specific rule, as those are covered by a different check. A person should verify that all control types on the page are covered between the different checks.
- Visible label appears at the start of the accessible name for reliable voice activationPartial
While the criterion only requires that the visible text appears somewhere in the accessible name, voice users have the best experience when it appears at the beginning. A button showing "Save" with an accessible name of "Click to Save document" technically passes but may cause voice commands to fail. Our tool detects name mismatches but does not specifically flag label-at-start positioning. Real-world edge cases — like the example where a "Start" button required voice users to say "start navigation" instead — can pass the automated check but still fail in practice. A person should test critical controls with actual voice commands to catch these scenarios.
How reliable it is
This criterion is still building up testing data, so confirm its findings as you review. See Accuracy & confidence for how the confidence tags are set.