Quick Answer
WCAG 2.2 does not ban passwords or CAPTCHAs. Success Criterion 3.3.8 (Level AA) says no step in signing in can require a cognitive function test, such as remembering a password or solving a puzzle, unless a listed condition applies: another way in, a tool that helps the user, recognizing objects, or recognizing your own uploaded content. Level AAA (3.3.9) removes the last two conditions. Every step counts, including a second factor and account recovery.
Introduction
You have a bill to pay or a class to join. You type your details, and then the site asks you to retype distorted letters, or to remember a code from three screens ago. For some people, the visit ends right there.
Signing in is the door to banking, school, health care, work and government services. If the door will not open, nothing behind it matters.
Login steps can be hard for people with cognitive disabilities, such as some memory, reading, number-processing or perception-processing differences. Needs vary from person to person, so one fix never fits everyone.
WCAG 2.2 added two rules for this, one at Level AA and one at Level AAA. People often explain them with jargon, or stretch them into bans that the rules do not contain.
This guide explains what the rules say and how common login methods fit. It also shows how to test your own sign-in flow, and why the legal standard depends on where you are.
What Does Accessible Authentication Mean in WCAG 2.2?
WCAG 2.2 became a W3C Recommendation on 5 October 2023, and W3C published an updated version on 12 December 2024. WCAG 2.2 added two success criteria about signing in. Success Criterion 3.3.8, Accessible Authentication (Minimum), is Level AA. Success Criterion 3.3.9, Accessible Authentication (Enhanced), is Level AAA.
Both rules are about one thing: a cognitive function test. W3C defines it as a task that asks the user to remember, manipulate or transcribe information. Memorizing a password, retyping a code, spelling words, doing sums and solving puzzles all count.
Some things are not cognitive function tests. W3C says a name, an email address and a phone number are not. Hardware security keys, app prompts that ask you to confirm a sign-in, and device methods such as Face ID or Windows Hello are not either.
The rule covers signing in to an account that already exists. W3C says it does not cover creating a username or starting an account, although the same fixes can help there. It does cover every step in the process. W3C says that includes each step of multi-factor authentication, and the methods people use to recover an account.
|
Criterion |
Level |
What it means |
|---|---|---|
|
AA |
A sign-in step cannot require a cognitive function test unless one of four conditions is met |
|
|
AAA |
The same rule, with the object-recognition and personal-content conditions removed |
What Are the Exceptions Under WCAG 2.2?
The four conditions are easy to mix up, so here they are in plain words.
|
Exception |
What it means |
Example |
|---|---|---|
|
Alternative |
Another way to sign in that does not need a cognitive function test |
A sign-in link sent by email |
|
Mechanism |
A tool that helps the user finish the test |
Password manager support or paste |
|
Object recognition |
The test is to recognize objects |
Pick the pictures that show a car |
|
Personal content |
The test is to identify non-text content the user supplied |
Pick the photo you uploaded to your profile |
Level AA allows all four. Level AAA allows only the first two. The W3C pages linked in the criterion table in the first section explain these conditions in more detail.
An exception is a way to pass the rule, not proof of a good design. W3C says object-recognition methods "should be avoided if possible," and that picture-based personal content "will still be a barrier for some people."
Nothing here bans passwords, CAPTCHAs or puzzles. The rule only sets the conditions for when one can be required.
Which CAPTCHAs Are Allowed Under WCAG 2.2?
It depends on the task the person must do, not on the brand of the CAPTCHA. Here is how the common types fit.
|
Challenge |
Level AA (3.3.8) |
Level AAA (3.3.9) |
|---|---|---|
|
Retype distorted text |
Typing what you see is transcription, so provide another sign-in method that does not need a cognitive function test |
Same |
|
Audio version you must type |
Typing what you hear is still transcription, so it does not count as another way in |
Same |
|
Math or logic puzzle |
It is a cognitive function test, and the object-recognition and personal-content exceptions do not cover it. W3C says an alternative sign-in method without a cognitive function test must be provided |
Same |
|
Pick pictures that show an object |
Allowed by the object-recognition exception |
Needs another way in or a helping tool |
|
Pick pictures you uploaded |
Allowed by the personal-content exception |
Needs another way in or a helping tool |
|
Invisible or risk-based check |
Test what appears when it asks for a challenge |
Same |
Audio CAPTCHAs surprise many teams. An audio clip feels like a fix for people who cannot see the letters. But if the person still has to type the characters they hear, W3C says it cannot be used as the alternative.
Invisible CAPTCHAs need care too. They may skip the challenge for most visitors, but the rule still applies. W3C says the criterion covers a CAPTCHA used to stop bots whether it shows every time or only in some situations. So test what happens when the system decides a visitor looks suspicious.
Finally, "allowed under an exception" does not mean "easy for everyone." A team that passes the rule with a picture test may still lock out real people.
How Should Passwords, Password Managers and Paste Work?
Passwords are not banned. The rule asks you to avoid making people memorize or retype them without help.
Password managers and browser autofill do that work for the user. For them to work, the sign-in fields need clear accessible names and correct HTML markup, such as autocomplete attributes, so browsers and password managers can identify and fill them. W3C's H100 technique gives examples of properly marked-up email and password inputs, and W3C lists it as a sufficient technique for both 3.3.8 and 3.3.9. Techniques are examples, not required methods, and meeting one of them does not by itself guarantee that every password manager will work.
Two common habits can break this. Blocking paste can stop people from using a password manager's copy-and-paste workflow, and blocking autofill can stop managers from filling the fields. W3C says either can fail the criterion when users are left without another way in. Asking users to enter only selected characters of a password, such as the first, third and fifth, adds a transcription step. Keep password manager support, autofill and paste working wherever the flow allows.
Security guidance points the same way. NIST's digital identity guidance says verifiers shall allow the use of password managers and autofill, and should permit the paste function when a password is entered, to help password manager use when autofill APIs are unavailable. It also says verifiers shall not impose other composition rules, such as forcing a mix of character types. Note the two different words. "Shall" is a requirement. "Should" is a strong recommendation.
Here are the mistakes to look for:
- Turning paste off in password fields
- Blocking password manager autofill
- Clearing a field when autofill is detected
- Asking users to retype only parts of a password
- Showing vague errors that leave users unsure how to recover
Are One-Time Codes, Two-Factor Authentication and Passkeys Accessible?
A second step can undo a good password field. A password field can pass while the next step blocks someone, so check each step.
A one-time code that a person must read and retype is a transcription task. Let people paste the code or use autofill, so they do not have to retype it. Better still, offer another way in.
Some methods avoid the problem. W3C says hardware security keys, app prompts that ask you to confirm sign-in, and device methods such as Face ID or Windows Hello are not cognitive function tests. It also lists email-link sign-in as a technique that meets the criterion, and it names WebAuthn as a possible future technique for another way in.
Passkeys can cut the need to remember a password. Whether your set-up works for everyone still depends on the full journey: setting it up, choosing a device, signing in and getting back in.
|
Method |
What to check |
|---|---|
|
Email or SMS code |
Can users paste or autofill the code without retyping it? |
|
Authenticator app |
Can users finish the approval step without an inaccessible challenge? |
|
Hardware security key |
Can users complete the process with the device and interaction method they have? |
|
Passkey or WebAuthn |
Are setup, sign-in, device choice and recovery accessible? |
|
Email sign-in link |
Can users open the link and finish without another inaccessible step? |
|
Biometric sign-in |
Is there a usable alternative for people who cannot or do not use it? |
Do not forget recovery. Lost phones, new devices, expired codes and forgotten passwords can leave people stuck. Include them in your review.
Offering a choice of methods helps because no one method works for everyone. Many sign-in steps happen inside apps. BarrierBreak's mobile accessibility testing covers native and web apps, with people with disabilities testing them using assistive technology.
How Can You Reduce Bot Abuse Without Blocking People?
A CAPTCHA is one way to reduce automated abuse, not the only way. NIST's digital identity guidance requires controls against online guessing for the authenticator types it specifies. Where its general limit applies, 100 consecutive failed attempts is an upper bound, not a target, and agencies may set lower limits. NIST also lists a bot-detection challenge among its optional additional techniques. Weigh the threat you face, the risk of blocking real users and the accessibility impact before choosing a control.
W3C has also written about other options. Its note on the inaccessibility of CAPTCHA lists non-interactive methods, such as hidden form fields that catch bots and checks that look at how risky a visit seems. It also describes proof-of-personhood ideas built on WebAuthn. It tells teams to use the least intrusive method that works, and it points out privacy trade-offs for some options. Keep in mind that this note is a Group Draft Note from December 2021, and W3C does not endorse it. Treat it as background, not as a rule.
If an interactive challenge is necessary, consider offering different challenge types and limiting how often people meet them. Test each option with people with disabilities, review its privacy effects, and make sure someone who is blocked can reach a person for help.
Do not call any invisible CAPTCHA or tracking method accessible or private without checking. Review security and accessibility together. One should not weaken the other.
Does the Law Require WCAG 2.2 Accessible Authentication?
WCAG is a technical standard. A law, a rule or a contract decides which version you must meet, so the answer depends on who you are and where you work.
In the United States, the DOJ's Title II rule for state and local governments requires WCAG 2.1 Level AA. Success Criterion 3.3.8 is new in WCAG 2.2, so that rule does not name it. DOJ's fact sheet also says governments must still meet their other obligations under the ADA, so treat WCAG as the technical standard, not the whole of the law.
That does not make 2.2 irrelevant. The WCAG 2.2 Recommendation says content that meets WCAG 2.2 also meets WCAG 2.0 and 2.1, and 2.2 can be another way to meet policies written for those versions. It adds one caution. Authors working under a 2.0 or 2.1 policy "may need to continue to test and report 4.1.1," the one criterion WCAG 2.2 removed.
Europe is changing too. EN 301 549 is the standard linked to EU accessibility laws, including the European Accessibility Act. ETSI published EN 301 549 V4.1.1 in September 2026, and it updates its web clauses to align with WCAG 2.2. Publication alone does not give a presumption of conformity. That applies only once the standard is cited in the Official Journal of the European Union. When the European Commission's AccessibleEU centre posted its update on 7 September 2026, V4.1.1 was not yet the legal reference standard. The current reference was still V3.2.1 (2021), which is based on WCAG 2.1 Level AA. Check the current citation status before you rely on V4.1.1 for a legal decision.
Confirm your own law, sector rules and contracts with a qualified adviser.
How Do You Test an Authentication Flow for Accessibility?
Test the whole flow, not only the username and password boxes.
- Sign in with a password manager.
- Check that autofill and paste work in the password and code fields.
- Look for any step that asks someone to remember, retype, calculate or solve.
- Test each multi-factor option, including app prompts and device methods.
- Test any CAPTCHA that appears after failed attempts or other risk signals.
- Test password reset, account recovery, expired codes and lost-device cases.
- Complete the flow with a keyboard and with screen readers.
- Check error messages, focus, time limits and recovery options.
- Include people with disabilities in testing where possible.
- Retest after any change to your login provider, CAPTCHA service or login component.
Automated tools can find some problems, but not all. W3C notes that a page can pass quick checks and still have significant barriers. A tool cannot tell you whether a real person can finish signing in. BarrierBreak's WCAG testing service uses manual evaluation with native screen readers and testers with disabilities. For quick automated checks while your team builds, A11yInspect can help, as long as you pair it with manual testing of the full flow.
Skills matter too. Developers and designers who understand the rule build better login steps. BarrierBreak's digital accessibility training is offered virtually and on site. If you want help reviewing your sign-in flow, you can get in touch with BarrierBreak.
Conclusion
WCAG 2.2 does not ban passwords or every CAPTCHA. It sets conditions on cognitive function tests. A method that passes under a Level AA exception can still shut out some people, and Level AAA is stricter. Check every step, including recovery, and confirm the legal standard that applies to you. Then remove avoidable retyping and give people another way in.
Frequently Asked Questions
Is a CAPTCHA allowed under WCAG 2.2?
Sometimes. WCAG 2.2 does not ban CAPTCHAs, but a challenge that needs text typed from an image or audio, or a puzzle solved, must be paired with another sign-in method that does not rely on a cognitive function test. Picking pictures of objects, or of your own uploaded images, has an exception at Level AA but not at Level AAA.
What is a cognitive function test?
W3C defines it as a task that needs the user to remember, manipulate or transcribe information. Examples include memorizing a password, retyping a code and solving a puzzle.
What is the difference between WCAG 3.3.8 and 3.3.9?
3.3.8 is Level AA and 3.3.9 is Level AAA. Both limit cognitive function tests in sign-in. 3.3.9 removes the object-recognition and personal-content exceptions.
Does WCAG 2.2 allow websites to block paste in password fields?
Not as the only way in. W3C says blocking paste or autofill in authentication fields fails the criterion unless another way in is available.
Are one-time codes, passkeys and hardware security keys accessible?
It depends on the full journey. W3C says hardware keys and app prompts are not cognitive function tests. Codes people must retype are transcription tasks, so allow paste or autofill, and test setup and recovery.
Does the law require WCAG 2.2 accessible authentication?
It depends on the law and version that apply to you. The U.S. DOJ Title II rule uses WCAG 2.1 AA, while EN 301 549 V4.1.1 aligns with WCAG 2.2. Check your own requirements.
Further Reading
The post What Does WCAG 2.2 Allow for Logins and CAPTCHAs? appeared first on Digital Accessibility Testing | A11yNow Compliance Platform | A11yInspect Testing Tools | BarrierBreak.





