R

RatedWithAI

WCAG guidance

Scan your site

WCAG 2.1

1.3.5 Identify Input Purpose

Level AA success criterion

The purpose of input fields collecting personal information can be programmatically determined when using standard autocomplete tokens.

Why it matters

Users with cognitive disabilities, motor impairments, or those using assistive technologies benefit from browsers auto-filling forms. Icons can also be displayed based on input purpose.

Common violations

  • Forms without autocomplete attributes
  • Custom input types without semantic hints
  • Address forms that don't use standard tokens
  • Login forms missing username/password autocomplete

Code examples

Bad

<input type="text" name="fname">

Good

<input type="text" name="fname" autocomplete="given-name">

How to fix

Add appropriate autocomplete attribute values from the HTML specification (given-name, family-name, email, tel, street-address, etc.).

Related criteria

Related resources

Scan your site

Check your WCAG coverage in minutes

Start a free scan