In one paragraph
Elements must have their visible text as part of their accessible name addresses controls whose visible label and programmatic name do not align. Include the visible wording in the name where the criterion applies; beginning with it is best practice rather than a separate mandatory position rule. The supplied WebAuditOS configuration does not run this experimental check, so manually verify the actual labels and names.
Why it matters
WCAG 2.5.3 supports users who speak the words they see to activate controls. An interface showing Buy now but naming the control Add item to cart creates an avoidable mismatch. Screen-reader and sighted collaborators also benefit from consistent wording.
An expanded accessible name is not inherently wrong. A visible Read more with a name Read more about delivery preserves the visible words and can provide useful context. The original problem is missing or changed label text, not simply the existence of additional words.
The criterion's scope and interpretation matter. Symbolic icons and most punctuation or capitalisation differences are not treated as naive exact-string mismatches. A control with no visible text can still need an accessible name under other requirements even when Label in Name does not apply to that component.
How WebAuditOS evaluates this finding
The supplied label-content-name-mismatch description compares visible content with the accessible name on selected widgets and includes heuristic exclusions or uncertain cases. Its scope does not equal every possible visible form-label relationship.
The source says this experimental rule is not executed in the current tag-selected scan. It therefore raises no finding here. No result is not a pass for visible-label agreement, and the rule's nominal impact is not a reported severity under that configuration.
How to fix it
- Inventory controls with visible wording and explicit aria-label or aria-labelledby overrides. Inspect the browser's computed name rather than reading only one attribute.
- Prefer native content naming when it already says the right thing. An ordinary example is:
<button type="button">Search</button>There is no need to add an unrelated hidden name solely to appear more accessible.
- When useful context is added, retain the visible label in an appropriate sequence. Search products can be an appropriate name for a visibly labelled Search control, while Find catalogue items replaces the wording users can see.
- Keep supplemental instructions in an appropriate description where suitable instead of forcing paragraphs into the name. aria-describedby does not replace the name's visible-label requirement.
- Review state changes and translations. A visually updated button can retain an old ARIA name if two text sources are maintained separately. Prefer a coherent source of wording.
- Distinguish human-readable labels from symbolic glyphs. A play symbol can have an action name such as Play without requiring the symbol itself to be spoken as literal text. Do not apply simplistic string equality to every icon or mathematical label.
- Test representative voice interaction and screen-reader output with actual visible wording. Include fields, compact responsive labels, and repeated controls, even when the experimental rule's selected roles would miss them.
- Record manual review and rescan other name-presence checks. A control can have a non-empty name yet still fail this requirement, and the supplied report does not currently expose the experimental mismatch result.
What the fix can break
Adding aria-label can override an accurate native label. Remove unnecessary overrides rather than layering contradictory sources.
Expanding names can make repeated controls verbose, while deleting all context can make them ambiguous. Preserve the visible phrase and add only useful distinctions.
Do not rewrite every label to an internal technical action name. People should be able to use the interface with the words actually presented to them.
Questions
Must visible wording be at the start?
It is best practice. The criterion requires containment of the visible text, subject to its proper interpretation, not a separate universal start-position rule.
Is Read more about pricing always a mismatch?
Not when Read more is the visible label and the computed name correctly contains it. Additional useful context can be appropriate.
Does no finding establish success?
No. The supplied experimental check is not run, and manual verification remains necessary.
Which related checks help?
Review button names, link names, and the automation limits guide.
What severity does this get in the report?
None today, because the rule is not run. If it were, an axe finding takes its severity from the impact axe reports, mapped critical and serious to high, moderate to medium, minor to low, and this rule is declared serious, so it would arrive as high. That is why the panel above states a conformance level rather than a severity.