• Success Criterion 1.3.5
  • Conformance level AA

Field Missing Both the Right Input Type and Autocomplete Token

1.3.5 — Identify Input Purpose

Scenario

Setting

A grocery delivery app's shopping cart

What’s wrong

type misuse combined with missing tokens (e.g., type="text" for email with no autocomplete="email") leaving no machine-readable purpose.

Example 

<label for="guest-email">Email for order updates</label>
<input id="guest-email" name="guest_email" type="text">

Why it matters

A shopper checking out as a guest gets no email keyboard on mobile and no autofill suggestion, making a quick checkout slower and more error-prone.

How to test

Inspect a field using type="text" for something like email with no autocomplete="email" token: without either signal, purpose can't be determined programmatically.

How to fix

Pair the correct input type with the matching autocomplete token so both the keyboard and autofill behave correctly.

<label for="guest-email">Email for order updates</label>
<input id="guest-email" name="guest_email" type="email" autocomplete="email">

Outcome

A guest shopper now gets the email keyboard on mobile and an autofill suggestion right at checkout.

Who is affected

Mobile users who lose the email-optimized keyboard, plus anyone relying on autofill, must type the address manually with the generic keyboard.

Learn more

Related scenarios