Resource guide

1.3.5 Identify Input Purpose

Form fields that collect personal information must have their purpose identified in code so browsers and tools can autofill and assist.

By Calling All Minds·Last updated April 2026

1.3.5

Success criterion

AA

Conformance level

Legal standard — required for EAA compliance.

What it means

When a form asks for a name, email address, phone number, or other personal information, the purpose of that field must be identifiable by browsers and assistive technologies. This allows autofill to work correctly and enables tools that show icons or familiar labels alongside fields.

This particularly helps people with cognitive disabilities who may find it much easier to recognise a familiar icon next to a field than to read and interpret a label.

In practice

Use the HTML autocomplete attribute with the correct values for the type of information being collected. For example: autocomplete="name", autocomplete="email", autocomplete="tel", autocomplete="street-address".

The full list of valid autocomplete values is defined in the HTML specification. Use the value that matches the purpose of the field most precisely.

Do not disable autofill on personal information fields. Some sites do this to prevent password managers from working, but it breaks this criterion and harms accessibility.

Common failures

  • Name field with no autocomplete attribute
  • Email field with autocomplete="off"
  • Address form where no fields have autocomplete values set

The tricky parts

This criterion only applies to fields that collect information about the user themselves, such as their own name, address, or payment details. It does not apply to fields where a user enters information about someone else, such as a recipient name on a gift order.

AXS Audit

AXS Audit checks your site against 1.3.5 and flags issues your team can act on straight away. It covers criteria that automated scanners often miss.

Explore AXS Audit