Success criterion 3.3.8
3.3.8 Accessible Authentication (Minimum)
When logging in isn’t a memory test.
1. What is the goal of this criterion?
Imagine you want to log in to your online banking quickly – but instead of simply pasting your password from your password manager, you have to solve a puzzle, remember a complicated sequence of numbers, or enter the 3rd, 6th and 12th character of your password one by one. Frustrating? For people with cognitive disabilities, this can be the reason they can’t use important online services at all.
The goal of WCAG Success Criterion 3.3.8 is to make sure login processes are accessible to everyone – without turning them into memory tests or puzzle games. Authentication should be secure and easy to use.
The criterion is new in WCAG 2.2 and sits at Level AA.
2. What exactly does it require?
Specifically: no step in a login process may require a cognitive function test – unless that step offers at least one of the following:
Alternative: another authentication method that doesn’t involve a cognitive test (e.g. passkeys/WebAuthn, sign-in via a third-party provider, or a link sent by email).
Supporting mechanism: help is available, such as pasting from the clipboard or support for password managers and browser autofill.
Object recognition: the test only involves recognising objects (e.g. “Select all images with cars” in a CAPTCHA).
Personal content: the test only asks you to recognise non-text content you provided yourself (e.g. an image you uploaded when you registered).
A cognitive function test is anything you have to remember, transcribe or solve: knowing passwords by heart, typing in codes, arithmetic, puzzles or entering individual characters of a password.
Important: this applies to every step – including the second factor, CAPTCHAs that only appear after several failed attempts, and account recovery. An audio CAPTCHA where you have to type what you hear, on the other hand, isn’t a valid alternative. Creating a new account isn’t covered by the criterion; it’s about existing users logging in.
3. Why does it matter for accessibility?
Imagine you find it hard to remember things, or you have dyslexia – and every time you want to log in somewhere, it becomes an ordeal. That’s exactly what many people experience every day.
Accessible authentication helps:
- people with cognitive disabilities, memory difficulties or learning difficulties to access online services.
- older people who struggle with complex password requirements.
- people with dyslexia or dyscalculia who have trouble transcribing or calculating.
- everyone in stressful situations where concentration is limited.
- people who use assistive technologies and rely on pasting from the clipboard or autofill.
And last but not least: accessible login is often the more secure login too – password managers and passkeys protect better than memorable, weak passwords.
4. How to meet the criterion
The good news: modern, secure authentication is often more accessible than older methods by default. Here are some proven tips:
Ground rules for accessible login:
- Allow pasting usernames and passwords from the clipboard.
- Don’t block autofill by browsers and password managers.
- Use correct HTML for login fields:
autocomplete="username"andautocomplete="current-password"(see Identify Input Purpose), plus clear accessible names. - Offer modern alternatives such as passkeys/WebAuthn (fingerprint, face recognition, hardware keys).
- Enable single sign-on via trusted providers.
- Provide a button that optionally shows the password in plain text.
For two-factor authentication:
- Allow codes from text messages or authenticator apps to be pasted, and support
autocomplete="one-time-code". - Don’t split codes into one input field per digit – or make sure pasting still fills in the whole code.
- Use push notification approvals instead of manual code entry.
- Offer hardware tokens or biometric alternatives.
- Never ask for individual characters of a code or password.
For CAPTCHAs:
- Avoid CAPTCHAs at login wherever possible and use invisible safeguards such as rate limiting instead.
- Audio alternatives that require typing don’t meet the criterion.
- Object recognition (“Select all traffic lights”) is allowed at Level AA but remains a barrier for many people – and is no longer permitted under Accessible Authentication (Enhanced).
What to avoid:
- Blocking paste in password and code fields.
- Arithmetic tasks or logic puzzles.
- Asking for individual password characters (“Enter the 1st, 3rd and 5th character”).
- Overly tight time limits with no way to extend them (see Timing Adjustable).
5. Why this criterion matters for businesses
Accessible authentication isn’t just a matter of inclusion – it brings tangible benefits for your business.
1. Reach a wider audience
Hard-to-use login processes cost you customers. Anyone who fails at login won’t buy, book or use your service. Accessible login makes your services usable for more people – including older people.
2. Improve security and usability at the same time
Modern methods such as passkeys aren’t just more accessible – they’re also considered more secure than classic passwords. Password managers encourage long, unique passwords. So you improve security and accessibility in one go.
3. Lower support costs
Complicated login procedures lead to more support requests about forgotten passwords, locked accounts and login problems. Accessible, modern authentication reduces that effort.
On the legal side: 3.3.8 is new in WCAG 2.2. The harmonised standard EN 301 549, which the European Accessibility Act and its German implementation, the Barrierefreiheitsstärkungsgesetz (BFSG), rely on, currently refers to WCAG 2.1 Level AA for web content – so 3.3.8 isn’t explicitly required there yet. But for online shops and banking services covered by the EAA, an accessible login is essential: without it, the entire service is out of reach. This section is general information, not legal advice.
6. The success criterion in the W3C’s words
Success Criterion 3.3.8 Accessible Authentication (Minimum) (Level AA)
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:
- Alternative: Another authentication method that does not rely on a cognitive function test.
- Mechanism: A mechanism is available to assist the user in completing the cognitive function test.
- Object Recognition: The cognitive function test is to recognize objects.
- Personal Content: The cognitive function test is to identify non-text content the user provided to the website.
Note 1: “Object recognition” and “Personal content” may be represented by images, video, or audio.
Note 2: Examples of mechanisms that satisfy this criterion include:
- support for password entry by password managers to reduce memory need, and
- copy and paste to reduce the cognitive burden of re-typing.
In short: no step in a login may force a cognitive test such as remembering a password or solving a puzzle – unless there’s an alternative, help such as password managers and paste, or the test only involves recognising objects or your own content.
Official explanation from the W3C
The W3C explains every success criterion in depth – with intent, examples and techniques.
Understanding 3.3.8 (opens in a new tab)