Goal
Make authentication usable without forcing memory-based puzzles.
Loading ...
Success Criterion · WCAG 3.3.8
A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: an alternative authentication method that does not rely on a cognitive function test, a mechanism to assist the user in completing the cognitive function test, or an object recognition test where the object is personally chosen by the user.
Goal
Make authentication usable without forcing memory-based puzzles.
What to do
Do not require users to solve cognitive function tests (like memorizing passwords) without offering accessible alternatives.
Why it matters
Memory and cognitive puzzles can exclude users with cognitive disabilities; password managers and copy/paste support are critical.
Success criterion
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process, unless that step provides at least one of the following: (1) Alternative: Another authentication method that does not rely on a cognitive function test; (2) Mechanism: A mechanism is available to assist the user in completing the cognitive function test; (3) Object recognition: The cognitive function test is to recognize objects; (4) Personal content: The cognitive function test is to identify non-text content the user provided to the Web site.
Intent
Benefits
Why it matters
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may be locked out if login requires remembering complex passwords with no help.
Blocking paste or password managers can make authentication unusable.
Authentication must not rely solely on memory or puzzles. Allow password managers, copy/paste, and provide alternative methods (magic links, passkeys, OTP) or assistance. This is a WCAG 2.2 Level AA addition.
Reference: All summaries and highlights originate from Understanding WCAG 3.3.8 and the W3C quick reference.
Examples
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Pass
Password field allows paste and password manager fill.
Fail
Paste is disabled and password manager autofill is blocked.
Pass
User can use passkey or email magic link instead of memorizing password.
Fail
Only option is a complex password with no assistance.
Evidence to keep
Capture artifacts for VPATs, procurement reviews, and regression testing.
Official resources
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Testing ideas
Related success criteria