Free scan

November 14, 2026

WCAG 1.3.5 Identify Input Purpose: Autocomplete for Accessible Forms

To satisfy WCAG Success Criterion 1.3.5, Identify Input Purpose (Level AA), every field that collects information about the user must expose its purpose programmatically, provided that purpose appears in the WCAG list of input purposes and the technology supports it. In HTML, the sufficient technique documented by the W3C (H98) is the autocomplete attribute, used with one of its predefined values, such as autocomplete="name" for the name, autocomplete="tel" for the telephone number or autocomplete="bday" for the date of birth. The goal the W3C states is straightforward: it is easier to fill out forms. Appropriate visible labels can help users understand the purpose of a field, but some people with cognitive disabilities may not understand it from the label alone. This Identify Input Purpose autocomplete guide explains what the criterion says, which values to use, which mistakes cause it to fail and who benefits from it.

What Success Criterion 1.3.5 Identify Input Purpose requires

The normative text of the criterion is brief: the purpose of each input field collecting information about the user can be programmatically determined when two conditions are both met. First, the input field serves a purpose identified in the list "Input Purposes for User Interface Components" (Section 7 of the WCAG 2.1 Recommendation). Second, the content is implemented using technologies with support for identifying the expected meaning for form input data.

"Programmatically determined" means that the information is supplied by the author in a way that different user agents, including assistive technologies, can extract and present to users in different modalities.

The W3C also clarifies that the word "input" is used generically. In HTML, the criterion is not limited to the <input> element; it also covers <textarea> and <select>.

Why the type attribute is not enough for form accessibility

The type attribute already offers a way to broadly indicate the intention of a field: <input type="tel">, <input type="email"> or <input type="password">. However, the W3C points out that these are only very broad categories, describing the type of input, but not necessarily its purpose. For instance, type="email" indicates that an email address is expected, but it does not clarify whether that address belongs to the user or to some other person.

The autocomplete attribute, by contrast, accepts only a limited number of specific, well-defined fixed values, which allows an identification of purpose that is more fine-grained than the type attribute. The WCAG list of input purposes borrows from the autofill definitions of the HTML specification, but conceptually it applies to other technologies as well. You can therefore distinguish, for example, between:

Identify Input Purpose: autocomplete code example in an HTML form

The following excerpt from a registration form declares the purpose of every field that relates to the user. Each field keeps its associated visible label: the label helps users understand the field's purpose, and autocomplete makes that purpose programmatically determinable.

For an order form with separate billing and shipping addresses, the W3C gives the example of a form that identifies the two sets of address fields by means of the autocomplete detail tokens "billing" and "shipping".

If a single field accepts two purposes, such as a combined "username or email address" field, and the technology does not allow multiple values to be declared, it is valid to provide either one value or the other, or to leave out the designation of input purpose altogether.

<form>
  <label for="given-name">First name</label>
  <input id="given-name" name="given-name" type="text" autocomplete="given-name">

  <label for="family-name">Last name</label>
  <input id="family-name" name="family-name" type="text" autocomplete="family-name">

  <label for="username">Username</label>
  <input id="username" name="username" type="text" autocomplete="username">

  <label for="birthdate">Date of birth</label>
  <input id="birthdate" name="birthdate" type="date" autocomplete="bday">

  <label for="phone">Telephone</label>
  <input id="phone" name="phone" type="tel" autocomplete="tel">
</form>

Who benefits from autocomplete?

The W3C describes concrete benefits for several groups of users with disabilities.

The W3C also gives an example for users who have difficulties reading: assistive technologies may display familiar icons next to input fields, such as a birthday cake in front of a field with autocomplete="bday" or a telephone in front of a field with autocomplete="tel".

Fields in scope, fields out of scope and edge cases

The criterion is specifically scoped to fields that collect information about the user. The list of input purposes includes a few values that may not strictly relate to the user, most prominently transaction-amount. A field for information that is not about the user does not need to expose its purpose programmatically, even if that purpose is included in the list.

Note that whether or not the browser actually fills in the field is not relevant when evaluating this criterion. What matters is that the purpose is exposed in the code. Conversely, a browser may guess the nature of a field through heuristics and pre-fill it anyway: that is not sufficient to meet the criterion.

Do you want, in some cases, to prevent autofill? That is possible, but the purpose of the fields must remain programmatically determinable. In HTML, there are methods to turn off autocompletion at form level while still specifying an explicit purpose on each field; for this, the W3C refers to the MDN page "How to turn off form autocompletion".

Finally, because autocomplete values are independent of language, the purpose of a field can still be identified consistently even for a user who may not be familiar with the text of the visible label, thanks to the fixed taxonomy of terms.

How to test the autocomplete attributes on your forms

The W3C documents one common failure for this criterion, F107: incorrect autocomplete attribute values. An approved test rule, "Autocomplete attribute has valid value", checks that the attribute's value is valid.

A simple verification process:

Frequently asked questions

What is WCAG 1.3.5 Identify Input Purpose?

It is a Level AA success criterion requiring that the purpose of each field collecting information about the user can be programmatically determined, when that purpose appears in the WCAG list of input purposes and the technology supports it. In HTML, the sufficient technique documented by the W3C (H98) is the autocomplete attribute.

Is type="email" or type="tel" enough for accessibility?

No. The type attribute describes a broad category of input, but not necessarily its purpose: type="email" does not say whether the address belongs to the user or to someone else. In HTML, the autocomplete attribute, with its predefined values, provides this finer-grained identification of purpose (sufficient technique H98).

Can you turn off autocomplete and still meet WCAG 1.3.5?

Yes, provided the purpose of the fields remains programmatically determinable. The W3C states that in HTML there are methods to turn off autofill at form level while still keeping an explicit purpose on the fields.

Does every form field need an autocomplete attribute?

No. Only fields that collect information about the user and whose purpose appears in the list are in scope. A field about another person, or about something other than the user, does not need to expose its purpose.

Does WCAG 1.3.5 apply to select and textarea elements?

Yes. The W3C specifies that the term "input" refers generically to form controls that accept user input: in HTML, this also covers <textarea> and <select>.

Does a misspelled autocomplete value fail WCAG 1.3.5?

Yes, for the fields in scope of the criterion. Failure F107 corresponds to the use of incorrect autocomplete attribute values, and the test rule "Autocomplete attribute has valid value" checks that the value is valid.

Further reading on Conformly

Sources

This article relies on the official sources listed at the end of the page.