# Input Purpose: Autocomplete for Personal Data

Source: https://allyway.ai/glossary/input-purpose

Input purpose is WCAG success criterion 1.3.5 Identify Input Purpose: the purpose of each input field that collects information about the user can be programmatically determined, for example with the HTML autocomplete attribute.

Input purpose means that a form field asking for your own data tells the browser what it is for – your name, email address, phone number or postal code. In HTML this is done with the `autocomplete` attribute. Browsers can then fill the field for you, and assistive technology can show a familiar icon next to it. For people who struggle to remember or type personal details, that turns a long form into a few clicks.

## What it means

[WCAG 1.3.5 Identify Input Purpose](https://www.w3.org/WAI/WCAG22/Understanding/identify-input-purpose.html) is a Level AA criterion, added in WCAG 2.1 and part of [WCAG 2.2](https://allyway.ai/regulations/wcag-2-2). The purpose of each input field collecting information about the user must be programmatically determinable when two conditions are met: the field serves one of the purposes in the WCAG list "Input Purposes for User Interface Components", and the technology supports identifying it – which HTML does with `autocomplete`.

| Field asks for … | Covered by 1.3.5? | Example token |
|---|---|---|
| The user's own name | Yes | `name`, `given-name`, `family-name` |
| The user's email or phone | Yes | `email`, `tel` |
| The user's address | Yes | `street-address`, `postal-code`, `country-name` |
| The user's birthday | Yes | `bday` |
| A gift recipient's email | No – not the user's own data | – |
| A transfer amount or search term | No – not information about the user | – |

The list borrows its meanings from the HTML autofill specification. `type="email"` alone is not enough: it says that a field takes an email address, but not whose. Addresses can be marked with the section tokens `billing` and `shipping`, as in W3C's order form example.

Who benefits: people with language, memory or executive-function disabilities do not have to remember and type their details. People with motor impairments enter less by hand. Assistive technology can add icons – a cake for a birthday, a phone for a number – which helps people who recognize symbols more easily than words.

> **Note:** > **A label is still required**
> `autocomplete` does not replace a visible label. Every field still needs clear [form labels](https://allyway.ai/glossary/form-labels) that screen readers announce. Input purpose adds a machine-readable meaning on top.

## Examples

```html title="Example"
<form>
  <label for="fn">Full name</label>
  <input id="fn" name="fullname" autocomplete="name">

  <label for="em">Email</label>
  <input id="em" type="email" name="email" autocomplete="email">

  <label for="zip">Postal code</label>
  <input id="zip" name="zip" autocomplete="shipping postal-code">

  <label for="pw">Create a password</label>
  <input id="pw" type="password" autocomplete="new-password">
</form>
```

Each field asking for the user's own data names its purpose with a valid token. A wrong value such as `autocomplete="first_name"` is not a valid token – W3C lists incorrect autocomplete values as failure F107. Correct values also help with [redundant entry](https://allyway.ai/glossary/redundant-entry) and [accessible authentication](https://allyway.ai/glossary/accessible-authentication), because browsers and password managers can fill the fields.

**Do:** Do

Use valid autocomplete tokens on every field that collects the user's own data, combine them with `billing` or `shipping` for addresses, keep visible labels, and use `new-password` and `current-password` on login and sign-up forms.

**Don't:** Don't

Invent values like `firstname` or `phone-number`, set `autocomplete="off"` on name and address fields without a reason, rely on `type` or `name` alone, or add personal tokens to fields about someone else.

## How to check input purpose



## Questions

Q: Which form fields need the autocomplete attribute?
A: Fields that collect information about the user and match a purpose in the WCAG list – for example name, email, phone, address, birthday, username and password. Fields about other people or about the transaction, such as a recipient's address or an amount, are not covered.

Q: Is autocomplete="off" a WCAG violation?
A: 1.3.5 asks that the purpose of a listed field about the user can be programmatically determined, and `autocomplete="off"` exposes no purpose at all. W3C's sufficient technique is H98, using the correct autocomplete token. On fields outside the list, such as a search box, the criterion does not apply.

Q: What is the difference between input purpose and form labels?
A: A label tells people what to enter. Input purpose tells browsers and assistive technology the meaning of the field in a fixed vocabulary, so they can autofill it or add an icon. A field needs both.

Q: Do I need autocomplete under the European Accessibility Act?
A: WCAG 1.3.5 is Level AA, the level that the [European Accessibility Act](https://allyway.ai/regulations/eaa) expects through [EN 301 549](https://allyway.ai/regulations/en-301-549). Forms in shops and booking flows are typical places to check.

Q: How do I find missing autocomplete values on my website?
A: Check your forms in the browser's DevTools as described above. The [free WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) gives you an overview of code-level form issues across your pages.

Q: Can allyWay fix input purpose automatically?
A: Yes. allyWay finds autocomplete values that browsers don't understand and suggests the right autofill setting for each field in Scan & Fix. It is one of the [automatic accessibility fixes](https://allyway.ai/automatic-accessibility-fixes-for-website) that wait for your OK: nothing changes on your website until you approve the suggestion. [Start for free](https://app.allyway.ai/register) and make your forms easier to fill in.
