All issues

Search results

CAPTCHA expansion

Status: Open.

#49 In w3c/captcha-accessibility;

· martinthomson opened on Mar 24, 2026

Typo "Cloudglare" instead "Cloudflare"

Status: Open.

#48 In w3c/captcha-accessibility;

· AvnerHadjadj opened on Feb 1, 2026

Essential Tremor and Puzzle Captcha

Status: Open.

#47 In w3c/captcha-accessibility;

· steveMc434 opened on Jan 17, 2026

Myproj

Status: Open.

#46 In w3c/captcha-accessibility;

· hghRm opened on Nov 28, 2025

Consider distinguishing "legacy" from "state of the art" approaches to allowing only human interaction with an application.

Status: Open.

#42 In w3c/captcha-accessibility;

· jasonjgw opened on Apr 6, 2022

What should be the principal conclusions of this version of the document?

Status: Open.

#23 In w3c/captcha-accessibility;

· jasonjgw opened on Feb 10, 2022

UA-driven CAPTCHA with Trust Tokens

Status: Open.

#16 In w3c/captcha-accessibility;

· Malvoz opened on Jan 12, 2022

Working Draft Feedback: More nuanced verdict of the effectiveness of CAPTCHA

Status: Open.

#21 In w3c/captcha-accessibility;

· hpetersFC opened on Jan 11, 2022

Working Draft Feedback: Positive examples of accessible CAPTCHA

Status: Open.

#22 In w3c/captcha-accessibility;

· hpetersFC opened on Jan 10, 2022

Replace or generalize the example in section 2.2.4

Status: Open.

#12 In w3c/captcha-accessibility;

· jasonjgw opened on Dec 28, 2021

Should we cite the WCAG 2.2 "Accessible Authentication" proposal? If so, what should be the approach taken?

Status: Open.

#11 In w3c/captcha-accessibility;

· jasonjgw opened on Dec 28, 2021

Consider including email address verification under Multi-Party Approaches?

Status: Open.

#10 In w3c/captcha-accessibility;

· WestonThayer opened on Dec 17, 2021