- Success Criterion 1.3.5
- Conformance level AA
Personal-Data Field With No Autocomplete Attribute at All
1.3.5 — Identify Input Purpose
Scenario
Setting
A job board's application form
What’s wrong
autocomplete omitted entirely on fields collecting the user's own info from the Input Purposes list (name, email, tel, address, cc-number…).
Example
Watch a job board's application form closely and you'll spot this: autocomplete omitted entirely on fields collecting the user's own info from the Input Purposes list (name, email, tel, address, cc-number…).
Why it matters
People with motor or cognitive disabilities who rely on browser autofill for personal data. On a job board's application form, this barrier means they have to guess at the correct format.
How to test
Inspect every field collecting personal info (name, email, phone, address, card) in DevTools: any missing an autocomplete attribute entirely fails.
How to fix
The field must carry the correct, valid autocomplete token (code telling browsers what the field collects) for its purpose so browsers and assistive tools can identify and autofill it.
Outcome
Corrected, a job board's application form now lets a visitor see exactly what went wrong and how to fix it.
Who is affected
People with motor or cognitive disabilities who rely on browser autofill for personal data.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Autocomplete Attribute Set to the Wrong Value for the Field
- Autocomplete Deliberately Disabled on a Personal-Data Field
- Autocomplete Token Placed on the Wrong HTML Element
- Custom Form Widget That Drops the Native Autocomplete Behavior
- Autocomplete Section Token Used Incorrectly, Breaking Its Value
- Login or Checkout Iframe That Strips Out Autocomplete Support