Success Criterion 1.3.5
Conformance level AA

Combined Field Whose Autocomplete Token Fits Only One Use Case

1.3.5 — Identify Input Purpose

Scenario

Setting

A budget airline's flight search results

What’s wrong

A multi-purpose field (e.g., "email or mobile number") tagged with a single token matching only one, or neither — of its accepted purposes.

Example

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

Why it matters

People with motor or cognitive disabilities who rely on browser autofill for personal data.

How to test

Inspect a combined field (e.g., 'email or mobile number'): check whether its single autocomplete token can represent both accepted input types — if it only matches one, it fails.

How to fix

The field must carry the correct, valid autocomplete token (code telling browsers what the field collects) for its purpose so browsers and assistive tools can identify and autofill it.

<input type="text" name="email" autocomplete="email">

autocomplete lets browsers and AT identify common input purposes and offer autofill support.

Outcome

On a budget airline's flight search results, this barrier is gone for people with motor or cognitive disabilities who rely on browser autofill for personal data — they can complete the task without hitting this wall.

Who is affected