Visible Label vs Accessible Name Checker
Voice-control users say the visible label to click a control ("Click Submit"). If the accessible name differs, the command fails — a WCAG 2.5.3 (Label in Name) violation. This tool compares both for every interactive element.
Tool interface
Results (WCAG 2.5.3)
| Element | Visible label | Accessible name | Status |
|---|
Introduction
When a button reads "Submit" but its aria-label is "Send", a voice-control
user saying "Click Submit" gets no match. This silent mismatch is one of the most
common real-world accessibility failures.
How it works
- Parses your HTML and finds interactive elements.
- Computes the visible label and the accessible name (W3C order).
- Flags any element where the visible text is not contained in the accessible name.
- Reports missing names and icon-only controls separately.
Privacy
All computation is local via DOMParser. No upload, no account, no API key.
Limitations
- Heuristic accessible-name computation; edge cases (CSS
::beforecontent, complex labelledby chains) may differ from a native accessibility tree.
FAQ
What is WCAG 2.5.3?
Label in Name: for controls with visible text, the accessible name must contain that visible text.
Is my markup uploaded?
No. Everything runs locally.