- Success Criterion 1.3.5
- Conformance level AA
Login or Checkout Iframe That Strips Out Autocomplete Support
1.3.5 — Identify Input Purpose
Scenario
Setting
A dating app's profile setup
What’s wrong
Login/checkout iframes stripping autocomplete via attribute or sandbox, defeating purpose identification.
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
Try autofilling a login/checkout field inside an iframe: if the iframe's sandbox or attributes strip autocomplete, it fails even if the token itself looks correct.
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 dating app's profile setup, this barrier is gone for people with motor or cognitive disabilities who rely on browser autofill for personal data — they can finish what they came here to do.
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