WCAG 1.3.5 Identify Input Purpose: Using Autocomplete Attributes

Last updated: 2026-03-22

Level AA Perceivable WCAG 1.3.5

What This Criterion Requires

WCAG 1.3.5 requires that the purpose of each input field collecting information about the user can be programmatically determined when the input field serves a purpose identified in the WCAG input purposes list. This criterion was added in WCAG 2.1 and is primarily met by using the HTML autocomplete attribute with the correct token values from the specification. When input fields for common data like name, email, address, phone number, and credit card information include the appropriate autocomplete values, browsers and assistive technologies can offer enhanced support. This includes auto-filling form fields, displaying familiar icons next to fields, and providing personalized labels. The criterion applies to input fields that collect data about the user themselves (not about other people or entities). The full list of valid autocomplete values is defined in the HTML specification section on autofill, and includes tokens such as given-name, family-name, email, tel, street-address, postal-code, and cc-number among many others.

Why It Matters

Identifying input purpose benefits users with cognitive disabilities, motor impairments, and low vision in several important ways. Users with cognitive disabilities may struggle to remember personal information or to understand what information a form field is requesting. When the input purpose is programmatically identified, assistive technologies can display familiar icons next to form fields, making it easier to understand what is being asked. Users with motor impairments benefit significantly from autofill capabilities, as typing is difficult and time-consuming for them. Properly identified input purposes allow browsers to reliably auto-complete forms, reducing the amount of typing required. Users with low vision who use personalized stylesheets can apply custom icons or visual indicators to known input types. This criterion also reduces form abandonment for all users by making forms faster and easier to complete, which is especially valuable for e-commerce checkout flows and registration processes.

Common Failures and How to Fix Them

Form fields missing autocomplete attributes

A contact or checkout form collects standard personal information but none of the input fields include autocomplete attributes. Browsers cannot reliably autofill these fields, and assistive technologies cannot convey the field purpose through icons or labels.

Inaccessible 
<form>
  <label for="fname">First Name</label>
  <input type="text" id="fname" name="fname">
  
  <label for="lname">Last Name</label>
  <input type="text" id="lname" name="lname">
  
  <label for="email">Email</label>
  <input type="email" id="email" name="email">
  
  <label for="phone">Phone</label>
  <input type="tel" id="phone" name="phone">
</form>
Accessible 
<form>
  <label for="fname">First Name</label>
  <input type="text" id="fname" name="fname" autocomplete="given-name">
  
  <label for="lname">Last Name</label>
  <input type="text" id="lname" name="lname" autocomplete="family-name">
  
  <label for="email">Email</label>
  <input type="email" id="email" name="email" autocomplete="email">
  
  <label for="phone">Phone</label>
  <input type="tel" id="phone" name="phone" autocomplete="tel">
</form>

Incorrect or invalid autocomplete values

Form fields use autocomplete attributes but with incorrect or non-standard values that browsers and assistive technologies cannot interpret. The autocomplete attribute must use valid tokens from the HTML specification.

Inaccessible 
<form>
  <label for="address">Street Address</label>
  <input type="text" id="address" name="address" autocomplete="address">
  
  <label for="zip">Zip Code</label>
  <input type="text" id="zip" name="zip" autocomplete="zipcode">
  
  <label for="cc">Credit Card</label>
  <input type="text" id="cc" name="cc" autocomplete="credit-card">
</form>
Accessible 
<form>
  <label for="address">Street Address</label>
  <input type="text" id="address" name="address" autocomplete="street-address">
  
  <label for="zip">Zip Code</label>
  <input type="text" id="zip" name="zip" autocomplete="postal-code">
  
  <label for="cc">Credit Card</label>
  <input type="text" id="cc" name="cc" autocomplete="cc-number">
</form>

How to Test

  1. Inspect all form fields that collect personal user information and verify that each has an autocomplete attribute with a valid token value.
  2. Cross-reference the autocomplete values used against the HTML specification autofill field names to ensure correctness.
  3. Test the form in a browser and verify that autofill suggestions appear correctly for fields like name, email, address, and payment details.
  4. Use an automated accessibility scanner such as axe DevTools to flag missing or invalid autocomplete attributes on user input fields.

CMS-Specific Guidance

This criterion commonly causes issues on these platforms:

Further Reading

Related WCAG Criteria