All WCAG criteria
WCAG 2.5.3 · OperableLevel A

2.5.3Label in Name

For UI components with text labels, the accessible name must contain (and ideally start with) the visible text.

Common failures

Patterns that fail this criterion.

  • 01Button labeled "Submit" with `aria-label="Send form"` — voice control users say "click Submit" and nothing happens
  • 02Icon button with visible "Cart" tooltip but `aria-label="Shopping basket"`
How to test

Testing approach: automated.

axe-core checks that the accessible name includes the visible text.

axe-core rules

label-content-name-mismatch
How to fix

Remediation steps.

  1. 1

    Default: no aria-label needed

    If a button has visible text, that text becomes the accessible name automatically. No aria-label required.

  2. 2

    If you need both

    Make sure the aria-label starts with the visible text. "Submit form" not "Send".

Scan for WCAG 2.5.3 on your site

Find every violation in 42 seconds.

AccessProof runs axe-core 4.9.1 against your site and flags every WCAG criterion with the offending element selector. WCAG 2.5.3 is one of 49 criteria we check on every scan.

Start free auditTry free scanner — no signup
Related criteria

Often appears with…

WCAG 4.1.2 · Level A

Name, Role, Value

All 50 WCAG 2.1 Level A + AA success criteria explained.

View the full checklist