- Success Criterion 1.3.5
- Conformance level AA
1.3.5 · Identify Input Purpose
Lesson overview · Identify Input Purpose
In plain language
Fields that collect the user's own details (name, email, phone, address, card) must carry the correct autocomplete attribute.
Who it affects
People with motor or cognitive disabilities who rely on browser autofill for personal data.
How to check
Inspect personal-data fields for a valid, correct autocomplete token; test that browser autofill actually fills them.
Common misconception
Setting the input type (like type="email") is not the same as setting autocomplete. Browsers and password managers rely specifically on the autocomplete attribute to know what a field collects.
Learn more
Scenarios in this lesson
- 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
- Login or Checkout Iframe That Strips Out Autocomplete Support
- Field Missing Both the Right Input Type and Autocomplete Token
- Combined Field Whose Autocomplete Token Fits Only One Use Case