Bots & traffic
9 min readUpdatedWhat is a CAPTCHA challenge? Types, accessibility and privacy
Quick answer
A CAPTCHA challenge is a challenge–response test a website uses to tell a person from an automated program before it accepts a login, a form or a page request. The site issues a task, such as typing distorted text, picking images or ticking a box, and checks the answer on its server. Research shows bots now solve most visible puzzles at least as well as people, so a CAPTCHA works best as one late step, not the whole defence.
01What does CAPTCHA mean?
CAPTCHA stands for Completely Automated Public Turing test to tell Computers and Humans Apart, the expansion WCAG 2.2 uses in its glossary. The term comes from a 2003 paper by Luis von Ahn, Manuel Blum, Nicholas Hopper and John Langford, which described an automated test that humans can pass but current computer programs cannot, built on unsolved artificial intelligence problems. They noted the bargain: if the problem is ever solved, the test fails but AI moves forward. Two decades later, that has largely happened.
A CAPTCHA is a challenge–response test: the website issues a challenge, the visitor returns a response, and the website checks it. That is all 'CAPTCHA challenge response' means. What has changed is the challenge, from warped letters to image grids, checkboxes and checks that ask the visitor to do nothing at all.
02How does a CAPTCHA challenge and response work?
Most CAPTCHAs follow the same token lifecycle, whether they are third-party or self-hosted. The step that actually protects the form happens on the website's server, not in the puzzle.
- The page loads the widget or a challenge page, tied to the site by a public site key
- The visitor solves the task, or the browser passes a background check, and the widget issues a response token
- The form submits that token with its other fields
- The server sends the token and its secret key to the provider's verification endpoint, or checks it locally if self-hosted
- The result states whether the token is valid, when it was issued and for which hostname; only then is the request accepted
POST https://www.google.com/recaptcha/api/siteverify
secret=YOUR_SECRET_KEY&response=TOKEN_FROM_THE_FORM
{
"success": true,
"challenge_ts": "2026-10-25T09:14:02Z",
"hostname": "example.com"
}03What types of CAPTCHA are there?
Eight families cover almost everything in use. Human solve times come from two large studies: Bursztein and colleagues measured more than 318,000 CAPTCHAs in 2010, and Searles and colleagues had 1,400 participants solve 14,000 deployed CAPTCHAs for a 2023 USENIX Security paper. The bot column shows published attacks, most of them compiled by the 2023 paper for comparison.
| Type | The visitor | Human time | Accessibility | Bots in published attacks |
|---|---|---|---|---|
| Distorted text | Types warped characters | 9–15 s at 50–84% accuracy (2023); 9.8 s (2010) | Unusable without sight; transcription is a cognitive function test in WCAG 2.2 | Under 1 s, up to 99.8% accuracy |
| Image selection | Picks the tiles showing an object | 15–32 s (2023) | Object recognition is excepted at WCAG level AA, not AAA; needs sight | 85–98%; a 2024 ETH Zurich study solved 100% of reCAPTCHA v2 image challenges |
| Audio | Types words read over noise | 28.4 s; three listeners agreed 31% of the time (2010) | Hard for everyone, and still a transcription task | Speech recognition passed Google's audio reCAPTCHA 90% of the time, in research the W3C cites |
| Math or logic | Answers a sum or a simple question | Not measured in either study | A barrier with dyscalculia; calculations count as a cognitive function test | Any script that reads the question; see the math CAPTCHA guide |
| Checkbox | Ticks a box while a risk check runs | 3.1–4.9 s (2023) | Mostly usable with assistive technology, but may fall back to a puzzle | 1.4 s at 100% success |
| Slider or game | Drags a piece or rotates an object | 18–42 s (2023) | Needs precise pointer control | Slider: 5.3 s at 96% success |
| Proof of work | Nothing: the browser computes a puzzle | A short pause, once per session | No task for the person | Real browsers pass; it adds cost, not proof of a human. See proof-of-work challenges |
| Invisible or score-based | Nothing, unless the site escalates | None until escalated | Nothing to solve unless the fallback is a puzzle | Depends on browser and cookie signals, at a privacy cost |
04Are CAPTCHAs accessible? What WCAG 2.2 requires
Mostly not, and WCAG 2.2 says so. Success criterion 3.3.8, Accessible Authentication (Minimum), at level AA, forbids a cognitive function test in any login step unless another method or a helping mechanism exists, or the test only asks the user to recognise objects or content they supplied. WCAG counts transcription, calculations and puzzles as cognitive function tests.
So a text or math CAPTCHA on a login fails level AA without another way in, such as a passkey, while object-recognition grids pass at AA but not at AAA under criterion 3.3.9. The W3C's Understanding document adds that an audio version still requiring transcription is no alternative, and that the rule applies even when the CAPTCHA appears only after failed logins. Criterion 1.1.1 applies everywhere, contact forms included: it asks for a text alternative describing the CAPTCHA's purpose and a version for a different sense.
- Give every login a path without a puzzle: passkeys, an emailed sign-in link or a support contact
- Show a CAPTCHA only when risk is raised, and offer a different kind of challenge on request
- Test the whole flow with a screen reader and with the keyboard alone
05What data does a CAPTCHA collect?
Checkbox and invisible CAPTCHAs judge the browser more than the answer. The W3C note lists what the reCAPTCHA checkbox collects, including the browser language, Google cookies from the previous six months, clicks or touches, installed plugins and JavaScript objects, and the 2024 ETH Zurich study found that reCAPTCHA v2 relies heavily on cookie and browser history data. Any third-party CAPTCHA sends visitor data to its provider, which for EU audiences belongs in a privacy review; self-hosted ones keep it on the site's own servers.
Privacy Pass, standardised by the IETF in June 2024 as RFCs 9576 to 9578, lets a client show that it passed an issuer's check without revealing who it is. As OWASP's cheat sheet notes, a valid token shows that the client met the issuer's policy, not that a human is present.
06Can bots and AI solve CAPTCHAs?
Yes, most of them, usually faster and more accurately than people. Searles and colleagues found that published bots were more accurate than people on every type they could compare, at 85 to 100% and mostly above 96%, and faster on all of them except reCAPTCHA image challenges, where bots and people took similar time. Where software falls short, people fill in: OWASP notes that visible CAPTCHAs are outsourced to human solving farms for fractions of a cent per solve, and calls them a last-resort step-up rather than a primary defence.
07Why am I being asked to complete a CAPTCHA?
Because something about the visit made the site less sure, or because it is challenging everyone during an attack. Typical triggers are a shared address (a VPN, a mobile network or a company proxy), many requests in a short time, blocked cookies or scripts, and failed logins; the W3C notes that some CAPTCHAs appear only when ad blockers are present.
| Symptom | Likely cause | Generated by | What helps |
|---|---|---|---|
| A challenge on every page | Cookies are blocked, so the pass is never stored | The visitor's browser settings | Allow cookies for that site and reload |
| The challenge loops after solving | The token is rejected or never sent, often because an extension blocks the script | A browser extension, or the site's CDN | Disable the extension for that site, as in unblocking challenges.cloudflare.com; if it persists, report the time to the site |
| 'Verification failed' when a form is sent | The token expired first: two minutes for reCAPTCHA, five for Turnstile | The site's server | Solve it again just before sending; operators should refresh expired widgets |
| CAPTCHAs only when on a VPN | Many users share the exit address | The site's WAF or bot protection | Switch VPN server, or disconnect for that site |
| No audio option offered | The provider withheld it, as the W3C note reported for reCAPTCHA v2 in 2021 | The CAPTCHA provider | Ask the site for another way in |
08Which CAPTCHA should a site use?
Usually the least intrusive check that stops the traffic actually seen, shown to as few visitors as possible: rate limits and hidden honeypot fields first, a background challenge where automation persists, and an interactive puzzle only for clients that failed the lighter steps, with an accessible path around it. These guides cover each step.
| If you need to | Read |
|---|---|
| Build a simple self-hosted check and know its limits | Mathematical CAPTCHA: how to build one |
| Slow automated floods without a puzzle | What is a proof-of-work challenge? |
| Know which bots you are dealing with | What is a bot? |
| Set a policy for all automated traffic | What is bot management? |
| Protect logins from leaked passwords | What is credential stuffing? |
| Cap request rates fairly | What is rate limiting? and 429 Too Many Requests |
| Keep AI crawlers out | How to block AI crawlers |
| Let search engines through | Web crawlers and how to verify them |
Questions
Frequently asked questions
Sources
Sources and verification
- 01CAPTCHA: Using Hard AI Problems for Security (von Ahn, Blum, Hopper, Langford, 2003) · Carnegie Mellon University
- 02Web Content Accessibility Guidelines (WCAG) 2.2 · W3C
- 03Understanding Success Criterion 3.3.8: Accessible Authentication (Minimum) · W3C WAI
- 04Inaccessibility of CAPTCHA: Alternatives to Visual Turing Tests on the Web · W3C
- 05An Empirical Study & Evaluation of Modern CAPTCHAs (Searles et al., USENIX Security 2023) · USENIX
- 06How Good are Humans at Solving CAPTCHAs? A Large Scale Evaluation (Bursztein et al., 2010) · Stanford University
- 07Breaking reCAPTCHAv2 (Plesner, Vontobel, Wattenhofer, 2024) · arXiv
- 08Verifying the user's response · Google for Developers
- 09Turnstile server-side validation · Cloudflare docs
- 10RFC 9576: The Privacy Pass Architecture · IETF
- 11Bot Management and Anti-Automation Cheat Sheet · OWASP Cheat Sheet Series
Last updated