ARIA · WCAG 2.0 Level A
ARIA input fields must have an accessible name
Ensure every ARIA input field has an accessible name.
What it means
The aria-input-field-name rule flags elements that fail this check. It maps to WCAG success criterion 4.1.2.
Who it affects
Screen reader and voice control users, who depend on ARIA roles and attributes being valid.
How to fix it
Custom inputs (role="combobox", "textbox", "slider" and so on) need an accessible name.
<div role="combobox" aria-labelledby="city-l" …></div>Check it on your site
Run a free scan. If this rule fails, the results list the affected elements. Deque, which maintains axe-core, also documents this rule in detail: Deque University: aria-input-field-name.
Quick answers
What does the axe rule "aria-input-field-name" check?
Ensure every ARIA input field has an accessible name.
How do I fix "ARIA input fields must have an accessible name"?
Custom inputs (role="combobox", "textbox", "slider" and so on) need an accessible name.
Who is affected by aria-input-field-name failures?
Screen reader and voice control users, who depend on ARIA roles and attributes being valid.
Automated accessibility scan. Results are informational and may not identify every accessibility issue. This service is not legal advice, a compliance certification, or a substitute for comprehensive manual accessibility testing.