WCAG 2.5.3 · Level A
Label Content Name Mismatch
- What is broken
- A control's spoken name does not match its visible text, so saying what is on screen does not activate it.
- Who it affects
- Screen reader users hear an unlabelled control and cannot tell what it does without activating it to find out.
- How to fix it
- Make each control's accessible name begin with its visible label text.
Check your site for this issue
Free scan — no signup required. Covers WCAG 2.1 AA across 64 rules including this one.
Scan my site →Automated testing detects roughly a third of WCAG 2.1 success criteria. This rule is detected automatically; issues such as keyboard traps, focus order, and screen-reader flow still require manual review. Not legal advice.