• Success Criterion 3.3.8
  • Conformance level AA

Password Manager Autofill Blocked by the Login Form

3.3.8 — Accessible Authentication (Minimum)

Scenario

Setting

A customer-support live-chat widget

What’s wrong

Blocking password managers (autocomplete off, fake fields, dynamic name randomization) with no other non-cognitive method.

Example 

<input type="text" name="user_field_38fa2" autocomplete="off">
<!-- the field name changes on every page load, defeating password manager matching -->

Why it matters

A visitor trying to start a support chat can't autofill their saved login, so they either give up or type the password from memory.

How to test

Try logging in with a saved password manager entry: if autocomplete="off", fake fields, or randomized field names prevent it from working, it fails.

How to fix

Use stable field names and standard autocomplete values, and never randomize them just to block password managers.

<input type="password" name="password" autocomplete="current-password">

Outcome

The visitor's password manager fills the field automatically and the chat session starts right away.

Who is affected

People with cognitive and memory disabilities who depend on password managers rather than memorizing credentials.

Learn more

Related scenarios