Form fields use invalid autocomplete values
Automated check autocomplete-valid, run with axe-core
- WCAG
- 1.3.5 Identify Input Purpose (Level AA)
- Severity
- Moderate: a degraded experience
- Typical effort
- Quick win, under 1 hour
- Category
- Forms and controls
Who this affects
People with motor or cognitive impairments who rely on the browser to fill in names, addresses and payment details.
Why it matters
Invalid autocomplete values stop browsers from filling fields automatically, which makes long checkout and registration forms far harder to complete.
How to fix it
Use valid values such as autocomplete="given-name", "email", "postal-code" or "cc-number", matching what each field asks for.
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
- Buttons have no discernible text
- Form field has more than one label
- Form buttons have no accessible name
- Image buttons have no text alternative