1.3.5 Identify Input Purpose

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.

Can AccessBell Test This Automatically?

Yes. AccessBell's scanner runs axe-core, which includes 1 rule that catch code-level failures of this criterion:

• 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.

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.

Example Fix

1. 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 RelationshipsLevel A · WCAG 2.0
• 1.3.2 Meaningful SequenceLevel A · WCAG 2.0
• 1.3.3 Sensory CharacteristicsLevel A · WCAG 2.0
• 1.3.4 OrientationLevel AA · WCAG 2.1
• 1.3.6 Identify PurposeLevel AAA · WCAG 2.1

WCAG 1.3.5 Questions