What autocomplete values should my form fields have?

We count the fields that plainly take personal details and carry no autocomplete attribute.

What it is

The `autocomplete` attribute states what a field is for in a fixed vocabulary: `email`, `tel`, `name`, `organization`, `postal-code`, `street-address` and so on. It is a machine-readable declaration, not a hint to the user.

A field needs one when its type is email, tel or text. It also needs one when its name or id contains email, phone, tel, name, company, address, zip or postal.

The Evidence gives both numbers: how many fields want a token, and how many of the form's fields there are. This Check runs only on pages that have a form.

Why an agent needs it

A label tells an agent what a field is called in your language. A token tells it what the field is, in the same words on every site.

That difference decides whether an agent fills your form or abandons it. "Work email", "Business e-mail" and "Company address" are 3 labels and one token.

The Fix

Add `autocomplete` to every field that takes a personal detail. Use `email`, `tel`, `name`, `given-name`, `family-name`, `organization` and the address tokens.

Use the standard token, not your internal field name. `autocomplete="work-email"` is not in the vocabulary and is ignored.

Pair each token with a real label. Together they make the field unambiguous, and they also let a browser autofill it for the humans on the same form.

This one is a change in your own markup or edge configuration, so the Fix Pack cannot write it for you. A Report names every page it affects, with the Evidence.

More in Interaction Readiness

All 24 Checks·Check library 2026-08-27