Custom input widgets have no accessible name
Automated check aria-input-field-name, run with axe-core
- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Severity
- Blocker: a task cannot be completed
- Typical effort
- Moderate, 1 to 4 hours
- Category
- Forms and controls
Who this affects
Screen reader users interacting with custom comboboxes, sliders and date pickers.
Why it matters
Hand-built widgets that replace native inputs almost always lose their name, so the control is unusable without sight.
How to fix it
Add aria-label or aria-labelledby to the element carrying the ARIA role. Prefer native HTML controls where possible — they are accessible by default.
Check your own website
The free scan tests 3 pages against WCAG 2.2 A and AA in about 30 seconds. No sign-up.
Related checks: Forms and controls
- Custom buttons, links or menu items have no accessible name
- Dialogs have no accessible name
- Custom checkboxes, switches or radio buttons have no accessible name
- Form fields use invalid autocomplete values
- Buttons have no discernible text
- Form field has more than one label
- Form buttons have no accessible name
- Image buttons have no text alternative