Success Criterion 1.3.5
Conformance level AA

Autocomplete Token Placed on the Wrong HTML Element

1.3.5 — Identify Input Purpose

Scenario

Setting

A language-learning app's lesson screen

What’s wrong

Token on the wrong control (on the fieldset wrapper, or a non-input element) so it doesn't apply.

Example

Here's a real case from a language-learning app's lesson screen: token on the wrong control (on the fieldset wrapper, or a non-input element) so it doesn't apply.

Why it matters

People with motor or cognitive disabilities who rely on browser autofill for personal data. Here, on a language-learning app's lesson screen, the result is they can't complete the form at all.

How to test

Inspect where the autocomplete attribute is placed in DevTools: it must be on the actual input, not on a wrapping fieldset or non-input element, or it won't apply.

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.

Outcome

After the fix, the same visitor to a language-learning app's lesson screen can now complete the form without guessing.

Who is affected

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

Learn more

Understanding Understanding document (opens in a new tab)