Login CAPTCHA lacks accessible alternative (WCAG 2.2 SC 3.3.8)
This check looks at your login form for a CAPTCHA, the "prove you're not a robot" test, and whether it offers any accessible alternative alongside it, such as a passkey, a magic email link, or signing in with Google, Apple, or Microsoft. This site's login form has a CAPTCHA but no such alternative.
Why this matters
This can fail WCAG 2.2 Success Criterion 3.3.8, Accessible Authentication, because some CAPTCHAs and puzzle-style checks can be a real barrier for visitors with certain disabilities. WCAG 2.2 is a recent standard; whether it is legally required depends on your jurisdiction, and the European Accessibility Act currently points to EN 301 549, which is based on an earlier WCAG version. Accessibility claims have also been brought under laws such as the US Americans with Disabilities Act, so check with a legal adviser what applies to you.
How to fix it
Your developer should add at least one CAPTCHA-free way to sign in, such as a passkey, a device-based login method also called WebAuthn, a magic email link, or a "Sign in with Google/Apple/Microsoft" option. Budget around four hours, since this touches the authentication flow.
Turn website findings into an action plan
Create an account to start a Full Audit of your website, with supporting evidence and a prioritised action plan.
Start Full Audit