W3C home > Mailing lists > Public > wai-xtech@w3.org > July 2007

Re: reCAPTCHA implementation problems

From: Gez Lemon <gez.lemon@gmail.com>
Date: Sat, 14 Jul 2007 02:18:59 +0100
Message-ID: <e2a28a920707131818g641097b6pbad8508f4af45ed0@mail.gmail.com>
To: "Ben Maurer" <bmaurer@andrew.cmu.edu>
Cc: "Gregory J. Rosmaita" <oedipus@hicom.net>, wai-xtech@w3.org, "Colin McMillen" <mcmillen@cs.cmu.edu>

Hi Ben,

On 14/07/07, Ben Maurer <bmaurer@andrew.cmu.edu> wrote:

<quote>
Doesn't the refresh button make sense *after* the challenge.
</quote>

It makes sense to put the refresh button after the challenge, but not
after the edit box that prompts the user to answer the challenge. At
the moment, you pose the challenge, request that the user answers the
challenge, and then after they have responded to the challenge, inform
the user that they could change the challenge if they found it
difficult (plus other options) - unfortunately, users with visual and
mobility impairments are very unlikely to discover those options, as
they're not easily available to them.

Ben Maurer wrote:
<quote>
It still degrades the experience for a visual user quite a bit though. Now
they have to tab three times before they can get to the input textbox.
What I'd really like is to have an out-of-band set of buttons that the
user can easily move in to.
</quote>

Requiring keyboard users to cycle through three tabs is a small price
to pay, in comparison to people who cannot readily change aspects
about themselves, to compensate for people who will completely miss
those options if they are not available with the keyboard alone.
Putting tabbing through three elements above the needs of people with
disabilities will always be at odds with accessibility.

Ben Maurer wrote:
<quote>
Sadly, *right now* CAPTCHAs are pretty much the only thing stoping a
number of services from serious abuse. Our goal is to make them as
accessible as we can without allowing bots though.
</quote>

My goal would also be to make these services as accessible as
possible. Sadly, if a services is not keyboard accessible, the service
cannot be considered to be accessible at all. The ultimate solution
would be to block access to bots without blocking users with
disabilities; testing humans by their ability to perform a task will
always be at odds with this quest (sensory, mobility, and cognitive
difficulties); in the meantime, we at least need to ensure that basic
input/output devices are capable of allowing anyone to perform a task
that a bot is (7 out of 8 times) unable to perform.

Cheers,

Gez




-- 
_____________________________
Supplement your vitamins
http://juicystudio.com
Received on Saturday, 14 July 2007 01:19:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:15:43 GMT