Autocomplete value is not valid

Why does it matter?

Browsers, password managers and assistive tools fill in and label fields from standard autocomplete values. A misspelt or misordered value, such as "e-mail" or "work shipping email", is ignored, so people with memory or motor difficulties have to type everything by hand.

Who it affects: Screen reader users, voice-control users who say a field's label to move to it, and people with memory or attention difficulties who lose a placeholder once they type.

What does Lumtera flag?

Fields whose autocomplete value does not follow the HTML autofill rules, checked the way the W3C ACT rule for valid autocomplete values does. A value built from real tokens in the wrong order or shape is an error. A value made only of words browsers do not know (often a trick to stop autofill) is for review, since it only matters when the field asks for the visitor's own details. "on", "off", empty values, hidden and disabled fields, and buttons are skipped.

Check ID input-autocomplete-invalid — use it to filter the content report or with wp lumtera issues --rule.

How do I fix it in WordPress?

Use one of the standard autocomplete values, such as "name", "email", "tel", "street-address", "postal-code" or "current-password", optionally preceded by "shipping" or "billing" (and, for phone numbers and emails, "home", "work" or "mobile"). To stop browsers filling in a field that is not about the visitor, use autocomplete="off". In form plugins, the autocomplete value is usually a field setting.

Example

<input type="email" name="email" autocomplete="e-mail">

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

How do I check the fix?

1. Update the post. The issue disappears from the Lumtera Accessibility sidebar on the next check, and from the site report on the next scan.
2. Click each field's label: the cursor should move into the field. With a screen reader, each field should announce its label when it receives focus.