The WCAG 2.0 requirements and techniques regarding CAPTCHA include:
- WCAG requirements 1.1.1 Non-text Content: CAPTCHA
CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
- G143: Providing a text alternative that describes the purpose of the CAPTCHA
- G144: Ensuring that the Web Page contains another CAPTCHA serving the same purpose using a different modality
I evaluate the Google reCAPTCHA v2 with these two demo:
It seems that reCAPTCHA v2 has the provided the describe text (in aria-live="polite" div), and the alternative accessibility solution for screen readers, which can fulfil the above requirement.
And I learned from this answer that automated accessibility tools, e.g. the WAVE tool, may return specific false positive. Beyond that the reCAPTCHA seems fine on my scans.
So, are there any violations? Can we say reCAPTCHA v2 is currently conforming to WCAG 2.0 AA?