WCAG 1.3.5 Identify Input Purpose
Input fields that collect common information about the user, such as name, email or address, should use the correct HTML autocomplete attribute so browsers and assistive tools can help fill them in.
Table of contents
What WCAG 1.3.5 Requires
Input fields that collect common information about the user, such as name, email or address, should use the correct HTML autocomplete attribute so browsers and assistive tools can help fill them in.
How to Test It by Hand
Inspect common fields (name, email, phone, address) and confirm they have a matching autocomplete value from the WCAG-defined list.
Common Failures
- An email field has no autocomplete="email" attribute.
- A checkout form's name and address fields are missing autocomplete tokens entirely.
Testing WCAG 1.3.5 With AccessBell
AccessBell's scanner runs axe-core, which includes 1 rule that catch code-level failures of this criterion. Automated checks help you spot issues quickly; a person still needs to review what they cannot judge.
autocomplete-valid: Ensure the autocomplete attribute is correct and suitable for the form field (details (opens in a new tab))
This criterion is included in: WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, EN 301 549 Checker.
Run a free scan to spot issues on your own pages.
Example Fix
- Use valid autocomplete tokens. They let browsers and assistive tech fill in personal details and identify the field purpose.
<input id="name" type="text" autocomplete="name">
<input id="email" type="email" autocomplete="email">
<input id="tel" type="tel" autocomplete="tel">
<input id="zip" type="text" autocomplete="postal-code">Related Criteria in Adaptable
- 1.3.1 Info and Relationships (Level A, WCAG 2.0)
- 1.3.2 Meaningful Sequence (Level A, WCAG 2.0)
- 1.3.3 Sensory Characteristics (Level A, WCAG 2.0)
- 1.3.4 Orientation (Level AA, WCAG 2.1)
- 1.3.6 Identify Purpose (Level AAA, WCAG 2.1)
Frequently Asked Questions
What does WCAG 1.3.5 require?
Input fields that collect common information about the user, such as name, email or address, should use the correct HTML autocomplete attribute so browsers and assistive tools can help fill them in.
Can AccessBell test WCAG 1.3.5 automatically?
Yes. AccessBell runs 1 automated rule that can catch failures of this criterion, including in our WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, EN 301 549 Checker. A person still needs to check what automation cannot judge.
What level is WCAG 1.3.5?
Level AA, added in WCAG 2.1. Level AA is the level referenced by the ADA, Section 508 and most accessibility laws.
Sources
- W3C: Understanding 1.3.5 Identify Input Purpose (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.