- Success Criterion 1.3.5
- Conformance level AA
Autocomplete Deliberately Disabled on a Personal-Data Field
1.3.5 — Identify Input Purpose
Scenario
Setting
An e-book reader's library page
What’s wrong
autocomplete="off" (or ="nope" hacks) on user-data fields — purpose no longer programmatically determinable.
Example
An e-book reader's library page is a good example: autocomplete="off" (or ="nope" hacks) on user-data fields — purpose no longer programmatically determinable.
Why it matters
People with motor or cognitive disabilities who rely on browser autofill for personal data. On an e-book reader's library page, that means they lose their progress and have to start over.
How to test
Try triggering browser autofill on the field: if autocomplete="off" (or a similar hack) is present on a personal-data field, autofill won't work and 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 an e-book reader's library page, 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 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