- 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
<label for="phone">Phone Number</label>
<input id="phone" name="phone" type="tel"> Why it matters
An applicant filling out yet another job application has to retype their phone number instead of it filling in automatically, adding friction to a long form.
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
Add the matching autocomplete token to every field that collects a listed personal data type, even when the field type already seems obvious.
<label for="phone">Phone Number</label>
<input id="phone" name="phone" type="tel" autocomplete="tel"> Outcome
An applicant's phone number now autofills instantly, saving a manual retype on a long application.
Who is affected
Users with motor or cognitive disabilities who rely on autofill to complete forms accurately face extra manual typing and higher error risk.
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