- Success Criterion 1.3.5
- Conformance level AA
Combined Field Whose Autocomplete Token Fits Only One Use Case
1.3.5 — Identify Input Purpose
Scenario
Setting
A budget airline's flight search results
What’s wrong
A multi-purpose field (e.g., "email or mobile number") tagged with a single token matching only one, or neither — of its accepted purposes.
Example
During an audit of a budget airline's flight search results: a multi-purpose field (e.g., "email or mobile number") tagged with a single token matching only one, or neither — of its accepted purposes.
Why it matters
People with motor or cognitive disabilities who rely on browser autofill for personal data. On a budget airline's flight search results, that means they can't tell what a field wants or why it failed.
How to test
Inspect a combined field (e.g., 'email or mobile number'): check whether its single autocomplete token can represent both accepted input types — if it only matches one, it 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
With the fix in place on a budget airline's flight search results, they finish the task in one attempt.
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