“Are CAPTCHAs accessible, and what does WCAG require?”

Are CAPTCHAs accessible, and what does WCAG require?

Updated October 17, 2026By the CaptchaKit team

Short answer

Many CAPTCHAs are hard to use with assistive technology. WCAG 1.1.1 requires a text alternative that explains the CAPTCHA's purpose and an alternative form in a different sensory mode. WCAG 3.3.8 (AA) restricts cognitive tests in authentication. CaptchaKit adds keyboard play and an in-widget alternative question, but you should still test your own page.

What the W3C says

The W3C's note on the inaccessibility of CAPTCHA says the traditional character-based CAPTCHA is largely inaccessible and insecure, prefers non-interactive approaches, and says that when an interactive test is needed, offering several challenge types helps. That is a draft group note from December 2021, so read it as guidance, not law.

WCAG 2.2 success criterion 1.1.1 (Non-text Content) says a CAPTCHA needs a text alternative that identifies its purpose, and alternative forms that use different sensory output modes so that more people can complete it.

Success criterion 3.3.8

WCAG 2.2 success criterion 3.3.8 (Accessible Authentication, Minimum) is Level AA. It says a cognitive function test, such as remembering a password or solving a puzzle, cannot be required to log in unless there is an alternative, a mechanism to help, an object-recognition test, or personal content. The W3C's explainer says audio transcription cannot meet the alternative exception.

If your CAPTCHA sits in front of a login form, read this one with your accessibility auditor, because the outcome depends on which test your widget uses and how the page is built.

What vendors say about themselves

Cloudflare states Turnstile is WCAG 2.2 AA compliant. ALTCHA states WCAG 2.2 AA accessibility for its core. hCaptcha says "We believe so" when asked about WCAG 2.2 AA and also offers a text-based Accessibility Challenge and a cookie that visitors register by email. Treat all of these as vendor statements and test.

What CaptchaKit provides

Every CaptchaKit widget shows a "Can't play? Accessible check" link that switches to a screen-reader-friendly question. Answering it issues the same one-time pass token, so your server code does not change. All games are playable from the keyboard (arrows, space, enter or number keys, shown in each game's footer) and announce progress through live regions. Pipe Connect is listed as a no-timer puzzle for accessibility-first sites.

We do not claim that CaptchaKit meets any WCAG level. That depends on your page, your theme and your audit. Test with a keyboard only, then with a screen reader, then ask a real user.

A short test you can run today

Tab through the form without a mouse and confirm focus reaches the widget. Turn on a screen reader and confirm the widget's state is announced. Block images and sound and confirm there is still a path. Check color contrast in both of the widget's themes. Look at your CaptchaKit setup in the docs for the data-theme option.

Why alternative forms matter

A CAPTCHA that relies on sight excludes blind visitors. One that relies on sound excludes deaf visitors. One that relies on fine motor control excludes people who use switch devices or voice control. The WCAG wording asks for alternatives in different sensory modes for that reason, and the W3C note recommends offering several challenge types.

Even with alternatives, some tools break for some people. hCaptcha's own help page notes that aggressive ad blockers or cross-site cookie settings can stop its accessibility cookie from working. Testing with real assistive technology catches problems no vendor statement will.

Choosing for accessibility

Start from your audience. If many of your visitors use screen readers, voice control or switch devices, a non-interactive or invisible approach avoids the problem for most of them. If you want a visible challenge, make sure it has a keyboard path and an alternative that is not a repeat of the same test.

Then document it. Keep a short accessibility note listing the CAPTCHA, how a keyboard user passes it, what the alternative is, and the date you last tested. If a user reports a problem, you have somewhere to start. Our comparison with hCaptcha shows two different alternative routes side by side.

Questions

Is a CAPTCHA required to be accessible?

WCAG 1.1.1 asks for a text alternative and alternative forms for CAPTCHA. Whether WCAG applies to you depends on your jurisdiction and laws.

Does CaptchaKit meet WCAG 2.2 AA?

We provide keyboard play, live-region announcements and an alternative question. Audit your own page.

Can a screen reader user pass CaptchaKit?

The widget offers a screen-reader-friendly question through the "Can't play? Accessible check" link, and issues the same token.

What is the least intrusive CAPTCHA for accessibility?

The W3C prefers non-interactive approaches. Invisible and proof-of-work tools take that path. A visible game suits sites that accept a visible step.

Do I need an audio CAPTCHA?

The W3C explainer for 3.3.8 notes audio transcription cannot satisfy the alternative exception. Plan an alternative that does not depend only on audio.

Which CaptchaKit game is best for accessibility?

Pipe Connect is listed for accessibility-first sites and has no timer. Test any game you choose.