All WCAG criteria
WCAG 1.3.5 · PerceivableLevel AA

1.3.5Identify Input Purpose

Form inputs collecting user information must be programmatically identifiable (using HTML autocomplete attribute) to enable browser-level autofill and assistive tech personalization.

Common failures

Patterns that fail this criterion.

  • 01Email input without `autocomplete="email"`
  • 02Shipping address fields without `autocomplete="street-address"`, etc.
  • 03Credit card form without `autocomplete="cc-number"`, `autocomplete="cc-exp"`, etc.
How to test

Testing approach: automated.

axe-core checks for missing autocomplete on common input purposes.

axe-core rules

autocomplete-valid
How to fix

Remediation steps.

  1. 1

    Use HTML autocomplete tokens

    List of valid tokens: https://www.w3.org/TR/WCAG21/#input-purposes — 53 standard purposes.

  2. 2

    Combine with proper input type

    `type="email"`, `type="tel"`, `type="url"` already trigger appropriate keyboards on mobile.

Scan for WCAG 1.3.5 on your site

Find every violation in 42 seconds.

AccessProof runs axe-core 4.9.1 against your site and flags every WCAG criterion with the offending element selector. WCAG 1.3.5 is one of 49 criteria we check on every scan.

Start free auditTry free scanner — no signup
Related criteria

Often appears with…

WCAG 3.3.2 · Level A

Labels or Instructions

All 50 WCAG 2.1 Level A + AA success criteria explained.

View the full checklist