# CAPTCHA: Accessible Bot Checks Under WCAG 1.1.1

Source: https://allyway.ai/glossary/captcha

A CAPTCHA is a test meant to confirm that a person, not a computer, is using a website. WCAG 1.1.1 requires a text alternative that describes its purpose and at least one alternative form using a different sense.

A CAPTCHA is a small test that should prove a real person – not a script – is filling in a form or logging in. The classic version asks you to type distorted letters from an image or an audio clip. For many people with disabilities, that bot check is the point where they cannot go any further.

## What it means

CAPTCHA stands for "Completely Automated Public Turing test to tell Computers and Humans Apart". The rule for it sits in [WCAG 1.1.1 Non-text Content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html), a Level A criterion of [WCAG 2.2](https://allyway.ai/regulations/wcag-2-2). A CAPTCHA image usually has no real [alt text](https://allyway.ai/glossary/alt-text) – a text alternative would let robots solve it too. So WCAG allows an exception, with two conditions:

| Requirement | What it means in practice | W3C technique |
|---|---|---|
| Describe the purpose | A text alternative says what the test is for, e.g. "Type the characters in the image to show you are human" | G143 |
| Offer another sense | A second form of the test uses a different output mode, e.g. audio next to a visual puzzle | G144 |

W3C is frank about the limits: every type of CAPTCHA is unsolvable for users with certain disabilities. A visual puzzle fails blind users, an audio clip fails deaf users, and someone who is deafblind may not be able to use either. That is why the W3C Understanding page recommends going beyond the minimum: more than two modes, a human support contact who can bypass the test, and no CAPTCHA at all for users who are already logged in.

> **Note:** > **CAPTCHAs also touch WCAG 3.3.8**
> On login and sign-up pages, a test that asks people to remember, transcribe or manipulate information is a cognitive function test. [Accessible authentication](https://allyway.ai/glossary/accessible-authentication) (3.3.8, Level AA) only allows such a test with an alternative or a helping mechanism – recognizing objects is one of its exceptions.

Who is affected: blind and low-vision users with a [screen reader](https://allyway.ai/glossary/screen-reader), deaf users facing an audio-only test, people with dyslexia or cognitive disabilities who struggle with distorted text, and people who use only the keyboard when the checkbox or puzzle cannot be reached with Tab.

## Examples

A contact form with an image CAPTCHA that meets the minimum: the purpose is described in text and an audio version is offered.

```html title="Example"
<fieldset>
  <legend>Security check</legend>
  <img src="captcha.png"
       alt="Security check: type the characters shown in this image to show you are human.">
  <label for="captcha">Characters from the image</label>
  <input id="captcha" name="captcha" autocomplete="off">
  <button type="button">Play audio version instead</button>
  <button type="button">Get a new image</button>
</fieldset>
```

**Do:** Do

Describe what the test is for in text. Offer at least two different senses, plus a way to reach a person. Make every part – checkbox, puzzle, audio button – usable with [keyboard navigation](https://allyway.ai/glossary/keyboard-navigation). Skip the CAPTCHA for logged-in users and consider invisible checks on the server first.

**Don't:** Don't

Use `alt="captcha"` or no text at all. Offer only a distorted image. Place a puzzle that requires dragging or exact mouse movements without another option. Let the test time out before a screen reader user can finish it.

## How to check a CAPTCHA



## Questions

Q: Are CAPTCHAs allowed under WCAG?
A: Yes. WCAG 1.1.1 makes an exception for CAPTCHAs, as long as a text alternative describes their purpose and alternative forms for different senses are offered. A single visual CAPTCHA without alternatives fails the criterion.

Q: Is an audio CAPTCHA enough to make it accessible?
A: No. An audio CAPTCHA helps blind users but excludes deaf users if it is the only option. WCAG asks for forms using different types of sensory perception, so the audio version should exist next to the visual one, not instead of it.

Q: What is the most accessible alternative to a CAPTCHA?
A: W3C recommends not requiring CAPTCHAs from authorized users at all and offering a human contact who can bypass the test. Checks that work in the background without a puzzle avoid the barrier for everyone, as long as there is still a way through when they block a real person.

Q: Does the European Accessibility Act cover CAPTCHAs?
A: The [European Accessibility Act](https://allyway.ai/regulations/eaa) refers to [EN 301 549](https://allyway.ai/glossary/en-301-549), which takes over WCAG 1.1.1 as clause 9.1.1.1. A CAPTCHA in a checkout or account flow is therefore part of what has to work for people with disabilities.

Q: How can I test my forms for accessibility problems?
A: Start with the manual steps above, because no tool can judge whether a puzzle is solvable. For the issues a tool can find – like missing labels or alt texts – the [free WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) checks your homepage against WCAG 2.2 AA.
