Fix · Moderate · should fix soon
How to fix: missing autocomplete attributes
Browsers cannot autofill names, addresses, or payment fields. Helps users with cognitive and motor disabilities; also speeds up forms.
- WCAG references
- 1.3.5
- Severity
- Moderate
What it looks like in the wild
Browsers cannot autofill names, addresses, or payment fields.
The screen-reader user, keyboard user, or low-vision user encountering this issue does not get an error message. The page just stops working for them. Which is why this kind of bug rarely shows up in your error tracker; it shows up in support tickets, lawsuits, and abandoned conversions.
Why it fails WCAG
Helps users with cognitive and motor disabilities; also speeds up forms.
Map this back to 1.3.5 when you log the bug. Auditors and procurement teams expect that mapping; "broken" is not enough context.
The wrong pattern (avoid)
<input id="ln" type="text">The right pattern (copy this)
<input id="ln" type="text" autocomplete="family-name">Notes from real audits
Full token list: name, given-name, family-name, email, tel, username, current-password, new-password, street-address, address-level1, address-level2, postal-code, country.
autocomplete="off" disables autofill — use it only for security-sensitive fields like one-time codes, not for names or addresses.
Password managers use these tokens to identify fields correctly across browsers and operating systems.
Related fixes
How to fix: missing alt text on images
1.1.1
How to fix: low color contrast
1.4.3, 1.4.11
How to fix: form fields without labels
3.3.2, 1.3.1, 4.1.2
How to fix: missing H1 / wrong heading order
2.4.6, 1.3.1
WCAG 1.3.5 — Identify Input Purpose
Inputs collecting common personal information must have a programmatic purpose set, typica
All fix recipes
Browse fixes by severity
Find every accessibility issue on your site in 60 seconds.
Free public scan. No card. AI-generated fixes for every issue we find.