Success Criterion 1.3.5
Conformance level AA
W3C reference F107

Autocomplete Attribute Set to the Wrong Value for the Field

1.3.5 — Identify Input Purpose

Scenario

Setting

A nonprofit's donation form

What’s wrong

The autocomplete attribute has an invalid or wrong value (e.g., 'given-name' on a surname field) — browsers and tools can't identify or autofill the field.

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

Inspect the field's autocomplete value in DevTools: it must exactly match a valid Input Purpose token for what it collects (e.g., "tel" for phone) — a mismatched token fails.

How to fix

Use the exact valid autocomplete token (code telling browsers what the field collects) that matches the field's purpose.

<input type="text" name="email" autocomplete="email">

autocomplete lets browsers and AT identify common input purposes and offer autofill support.

Outcome

On a nonprofit's donation form, this barrier is gone for people with motor or cognitive disabilities who rely on browser autofill for personal data — they no longer have to work around this.

Who is affected