1.3.5: Identify Input Purpose

What it means

Form fields that collect common personal information should expose their purpose to browsers and assistive tech. This helps autofill and password managers put the right data in the right field.

Use standard autocomplete tokens on inputs like name, email, and address.

How to fix it

• Add appropriate autocomplete attributes (for example autocomplete=“email”).
• Match tokens to the data you actually collect — do not mark a nickname field as given-name.
• Use visible labels that align with the autocomplete purpose.
• Test that major browsers offer to fill saved details on login and checkout forms.

Quick examples

• Good: The email field uses type=“email” and autocomplete=“email”.
• Bad: Address fields have no autocomplete tokens, so browsers cannot suggest saved details.
• Good: Credit card fields use autocomplete=“cc-number” on the card number input.
• Bad: Every text field uses autocomplete=“off” on a standard login form.