Form buttons have no accessible name
Automated check input-button-name, run with axe-core
- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Severity
- Blocker: a task cannot be completed
- Typical effort
- Quick win, under 1 hour
- Category
- Forms and controls
Who this affects
Screen reader and voice-control users trying to submit a form.
Why it matters
A submit control with no name blocks form completion — the highest-consequence failure on any commercial site.
How to fix it
Set a value attribute on <input type="submit">, or use a <button> with text content.
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 input widgets 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
- Image buttons have no text alternative