- 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
<iframe src="https://payments.example.com/checkout" sandbox="allow-scripts allow-same-origin"></iframe> Why it matters
Midway through setting up their profile, a user taps the premium upsell to unlock unlimited likes and has to manually type their full card number and billing name because the embedded payment iframe strips autocomplete.
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
Inside that iframe, the card number and name fields have autocomplete stripped by the embedding configuration, so make sure sandboxed checkout iframes do not strip autocomplete tokens from their internal fields, and avoid sandbox flags that block autofill unnecessarily.
<iframe src="https://payments.example.com/checkout" sandbox="allow-scripts allow-same-origin allow-forms"></iframe> Outcome
Mid-setup, a user upgrading to premium can now autofill their saved card details inside the checkout iframe instead of retyping everything.
Who is affected
Users with saved payment autofill data, and people with motor disabilities who depend on it, must retype every field by hand mid-setup instead of finishing the upgrade quickly.
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