Level AAPerceivableNew in 2.1
1.3.5

Identify Input Purpose

Fields that collect personal info (name, email, address) should use the right autocomplete value, so browsers can autofill them.

In plain English

When a field asks for something about the user, their name, email, phone, or address, the code should say so, using the standard autocomplete attribute. Do that, and browsers can autofill the field, and assistive tools can recognise what it is for.

For people with memory or motor difficulties, autofill is not a nicety, it is the difference between a quick checkout and a frustrating, error-prone one. It also speeds up conversion for everyone.

Who this is for

  • People with memory or cognitive differences, who rely on autofill instead of recalling and retyping details.
  • People with motor difficulties, for whom every avoided keystroke helps.
  • Everyone, who checks out faster when fields fill themselves.

How to check and fix it yourself

On your checkout, does the browser offer to autofill name, email, and address? If not, the autocomplete attributes are probably missing. Add the standard tokens:

<input name="email"  autocomplete="email">
<input name="fname"  autocomplete="given-name">
<input name="zip"    autocomplete="postal-code">
<input name="addr"   autocomplete="address-line1">

Where we can help

We review your checkout and account forms and list every field missing the right autocomplete value, with the exact token to add. It is a quick, high-value fix that shows up in a 10-minute self-check.

How to meet it

Techniques the W3C accepts as sufficient (summarized). Follow a link for the full method.

Frequently asked questions

What does identify input purpose require?+

Success Criterion 1.3.5 (Level AA, added in WCAG 2.1) says fields that collect information about the user, like name, email, phone, and address, must have their purpose identified in code, in practice by using the correct HTML autocomplete attribute.

Why does the autocomplete attribute matter for accessibility?+

It lets browsers and assistive tools autofill fields reliably, which is a big help for people with memory or motor difficulties who find repeated typing hard. It also powers tools that add icons or simplified labels to fields based on their purpose.

How do I add it?+

Set autocomplete to the standard token for each field, for example autocomplete="email", autocomplete="given-name", autocomplete="postal-code". Most platforms and checkouts support this; it is a small template change with a real usability payoff.

Reference

This is a plain-language explainer. The authoritative source is the W3C Web Content Accessibility Guidelines (WCAG) 2.2.

WCAG 2.2 © W3C. Excerpts are paraphrased; see the linked documents for the normative text.

Not sure if your store passes 1.3.5?

A human auditor checks this and every other criterion against your live store, and documents the result.

Book an audit