- Success Criterion 1.3.5
- Conformance level AA
Field Missing Both the Right Input Type and Autocomplete Token
1.3.5 — Identify Input Purpose
Scenario
Setting
A grocery delivery app's shopping cart
What’s wrong
type misuse combined with missing tokens (e.g., type="text" for email with no autocomplete="email") leaving no machine-readable purpose.
Example
<input type="text" name="email">Why it matters
People with motor or cognitive disabilities who rely on browser autofill for personal data.
How to test
Inspect a field using type="text" for something like email with no autocomplete="email" token: without either signal, purpose can't be determined programmatically.
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.
<input type="text" name="email" autocomplete="email">autocomplete lets browsers and AT identify common input purposes and offer autofill support.
Outcome
On a grocery delivery app's shopping cart, this barrier is gone for people with motor or cognitive disabilities who rely on browser autofill for personal data — they reach the same outcome without extra effort.
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
- Personal-Data Field With No Autocomplete Attribute at All
- 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