- Success Criterion 1.3.5
- Conformance level AA
Autocomplete Section Token Used Incorrectly, Breaking Its Value
1.3.5 — Identify Input Purpose
Scenario
Setting
A coworking-space booking app
What’s wrong
Section-token misuse (section- prefixes) that break token validity.
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 the autocomplete value for section- prefix misuse: malformed section tokens invalidate the whole attribute value — check it against the WCAG token list.
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 coworking-space booking app, this barrier is gone for people with motor or cognitive disabilities who rely on browser autofill for personal data — they no longer have to work around this.
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
- Login or Checkout Iframe That Strips Out Autocomplete Support