Personal-data inputs should declare an autocomplete token

Rule missing-autocomplete · Deeper checks · impact minor · Static + live

↩ Back to the rules index · WCAG cross-reference

Why it matters#

The existing autocomplete-valid rule checks that a declared autocomplete value is syntactically valid. This rule checks the other side: contact-information inputs that have no autocomplete at all. Without it, browsers and password managers cannot pre-fill the field, which is especially important for users with motor or cognitive disabilities.

How to fix#

Add the appropriate autocomplete token (e.g. autocomplete="email", "tel", "name", "street-address").

Example#

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

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

Example#

<input type="tel" id="phone">

<input type="tel" id="phone" autocomplete="tel">

WCAG success criteria#

1.3.5 Identify Input Purpose — Level AA#

Inputs collecting common user information should declare their purpose (e.g. a valid autocomplete token) so browsers and AT can assist.

Understanding 1.3.5

Standards#

This rule contributes to the following standards:

WCAG AA EN 301 549

References#

• WCAG — Identify Input Purpose