Success Criterion 1.3.5
Conformance level AA

Autocomplete Deliberately Disabled on a Personal-Data Field

1.3.5 — Identify Input Purpose

Scenario

Setting

An e-book reader's library page

What’s wrong

autocomplete="off" (or ="nope" hacks) on user-data fields — purpose no longer programmatically determinable.

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

Try triggering browser autofill on the field: if autocomplete="off" (or a similar hack) is present on a personal-data field, autofill won't work and 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 an e-book reader's library page, this barrier is gone for people with motor or cognitive disabilities who rely on browser autofill for personal data — they reach the same outcome without extra effort.

Who is affected