Autocomplete and Input Purpose

WCAG 1.3.5 applies when a field collects information about the user and its purpose appears in the WCAG-defined input-purpose list. A visible label explains the field; a valid HTML autocomplete token programmatically identifies its purpose to browsers, password managers, and personalization tools. You generally need both.

Tokens are language-independent. Translate the visible label, not values such as name, email, street-address, postal-code, username, current-password, and new-password. Do not disable autocomplete as a generic security measure; protect sensitive data through appropriate application and device controls.

<label>Full name <input name="field1" /></label>
<label>Email <input name="field2" /></label>

<label>Full name <input name="name" autocomplete="name" /></label>
<label>Email <input name="email" type="email" autocomplete="email" /></label>
<label>Postal code <input name="postal-code" autocomplete="postal-code" /></label>

Test it

Validate token spelling, then test browser autofill and at least one password manager with representative localized data. Confirm that autofilled values remain visible, editable, and correctly associated with their labels. Avoid collecting personal data solely to demonstrate the feature in production analytics or test logs.

Resources

• Understanding 1.3.5 Identify Input Purpose 
• HTML autocomplete tokens 
• Form Labeling
• Accessible Authentication