How to fix: missing autocomplete attributes

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.

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.

How to verify the fix

Shipping the change is not the same as passing 1.3.5. Re-run these checks against the page you edited before you close the ticket.

• Inspect personal-data inputs for autocomplete tokens.

What 1.3.5 requires

1.3.5 Identify Input Purpose (Level AA, Perceivable): Inputs collecting common personal information must have a programmatic purpose set, typically via the autocomplete attribute. Allows browsers and assistive tech to autofill, customize labels, and offer symbol-based help.

• Email input without autocomplete="email"

  1.3.5

• Address fields without autocomplete tokens

  1.3.5

Priority: Moderate

This will not stop a user completing a task on its own, but it accumulates. A page carrying several moderate findings degrades into one that is technically usable and practically exhausting — and an auditor counts them individually.

Because the cause is almost always a shared component rather than a single page, fix it where the component is defined and re-scan the whole site. Record 1.3.5 on the ticket verbatim: that string is what an auditor, a procurement questionnaire or a regulator will search for.