CAPTCHA
Topic | Technique | WCAG AA Requirement |
---|---|---|
Text Alternatives | Text Alternative Describing the Purpose: If the CAPTCHA is not text-based (e.g. image or audio), a text alternative MUST communicate the purpose of the CAPTCHA, so that the user knows that this task must be completed before proceeding to the next step.
|
Required WCAG 1.1.1 |
Text-Based CAPTCHA: A method SHOULD be available in a text-based format (either as the main CAPTCHA or as an alternative) that can be converted by a screen reader to braille output.
|
Best Practice | |
Sensory Alternatives | Sensory alternative: If a blind user cannot pass the original CAPTCHA, an alternative method MUST be provided in another sensory modality (e.g. audio). | Required WCAG 1.1.1 |
Keyboard Accessibility | User input controls in a CAPTCHA (or in an alternative representation) must meet all the keyboard functionality requirements (see the Device-Independent User Input requirements). | Required Multiple |
Dynamic Content | Any dynamic content in a CAPTCHA (or in an alternative method) must meet all the Dynamic Content (JavaScript, AJAX) requirements. | Required Multiple |
Custom Widgets | Any custom widgets in a CAPTCHA (or in an alternative method) must meet all the Custom Widgets (JavaScript, ARIA) requirements. | Required Multiple |
Color and Contrast | Any visual elements in a CAPTCHA (or in an alternative method) must meet all the Color and Contrast requirements. | Required Multiple |
Avoid CAPTCHAs if Possible
CAPTCHAs require human problem-solving skills — which can be difficult or impossible for users with cognitive disabilities — and often require sensory abilities — which can be difficult or impossible for users who are blind, deafblind, or deaf. It is best to avoid CAPTCHAs altogether, and instead implement smart algorithms that do not require human input.