- Success Criterion 3.3.8
- Conformance level AA
Password Field Scripted to Block Paste Entirely
3.3.8 — Accessible Authentication (Minimum)
Scenario
Setting
An insurance company's claims form
What’s wrong
Password fields with onpaste="return false" or JS paste blocking — memorization/transcription cognitive test with no alternative.
Example
<input type="password" id="claim-password" onpaste="return false" oncopy="return false"> Why it matters
A claimant logging in to check a pending claim can't paste their password from a manager and must recall and type it under stress.
How to test
Try to paste into a password field (right-click Paste or Ctrl/Cmd+V): if onpaste="return false" or similar JS blocks it, it fails.
How to fix
Remove any onpaste or oncopy blocking code entirely. It has no security benefit and only adds a memorization requirement.
<input type="password" id="claim-password">
<!-- paste is allowed by default; nothing blocks it --> Outcome
The claimant pastes their saved password and reaches their claim status without retyping anything from memory.
Who is affected
People with cognitive disabilities, and anyone relying on a password manager, who lose their normal, faster way of authenticating.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Password Field That Blocks Pasting or Splits the Code Up
- Password Manager Autofill Blocked by the Login Form
- Visual CAPTCHA Required With No Non-Visual Alternative
- Puzzle CAPTCHA Gating Login With No Alternative Method
- One-Time Code Split Into Boxes That Reject a Pasted Code
- Displayed Code Required to Be Retyped With Copying Disabled