W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2003

RE: Captcha and inaccessiblity

From: Geoff Deering <gdeering@acslink.net.au>
Date: Tue, 21 Oct 2003 05:59:30 +1000
To: "Matt May" <mcmay@w3.org>
Cc: "Charles McCathieNevile" <charles@w3.org>, "Tom Croucher" <tcroucher@netalleynetworks.com>, <w3c-wai-gl@w3.org>
Message-ID: <NBBBJPNFCLNLAADCLFJBOENIFBAA.gdeering@acslink.net.au>

That's great.

FYI There's also a discussion on the same subject addressing accessibility
over at slashdot

http://slashdot.org/article.pl?sid=03/10/19/2322252&mode=nested&tid=111&tid=
126


-----Original Message-----
From: Matt May


On Sunday, October 19, 2003, at 03:39  PM, Geoff Deering wrote:
> I think there is a need for a "Techniques for Accessible Form Handling"
> document or the like so that developers are given viable alternatives
> to
> prevent machine spamming of forms.

The WAI Protocols and Formats Working Group has been working on a
document specifically addressing CAPTCHA, and hopes to submit a draft
Note for the Technical Reports page[1] this week. It describes the
problems inherent in CAPTCHA, and seven categories of potential
solutions, including logic or word puzzles, server heuristics, and
public-key infrastructure.

I would hesitate to have a detailed discussion in WCAG about CAPTCHA,
since it is a technique with documented exploits which limit its
lifespan to perhaps only another year or two. The researchers behind
CAPTCHA are already working on alternative approaches themselves.
Further, this design already fails both versions of WCAG (and every
evaluation tool) because it doesn't offer alt text for a necessary
textual component.

I will let this list know when the document is up.

[1] http://www.w3.org/TR/
Received on Monday, 20 October 2003 16:00:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:26 GMT