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

Re: reCAPTCHA implementation problems

From: Ben Maurer <bmaurer@andrew.cmu.edu>
Date: Fri, 13 Jul 2007 16:42:45 -0700 (PDT)
To: Gez Lemon <gez.lemon@gmail.com>
cc: "Gregory J. Rosmaita" <oedipus@hicom.net>, wai-xtech@w3.org, Colin McMillen <mcmillen@cs.cmu.edu>
Message-ID: <Pine.LNX.4.64-044.0707131640310.14738@unix36.andrew.cmu.edu>

Hrm, the problem is, it *REALLY* breaks the average case if we make 
refresh, etc the next result of tab. For example, imagine this form (from 
wordpress)

Please enter a comment

Name <textbox>
Email <textbox>
Website <textbox>
Comment <textarea>

<recaptcha>

<submit>


When playing around with reCAPTCHA, I found that if I didn't have 
tabindex=-1 on stuff like refresh, what i'd do is to fill out the CAPTCHA 
then go <tab> <enter>. Because refresh had focus, i'd refresh the CAPTCHA 
destroying my work.

Any thoughts on how to make a balanced decision here?

-b

On Fri, 13 Jul 2007, Gez Lemon wrote:

> Hi Ben,
>
> On 13/07/07, Ben Maurer <bmaurer@andrew.cmu.edu> wrote:
>
> <quote>
> So we should probably look into using an element that is more button-like.
> Is tab index still going to be an issue here -- we still want to set
> tabindex to -1 for visual browsers because it makes more sense in that
> case.
> </quote>
>
> A tabindex attribute value of -1 will be a serious accessibility
> issue, regardless of the type of browser you're targeting. A value of
> -1 takes the control (link, button, or anything else that could
> receive focus) out of the tab order, which means it cannot be accessed
> by people using the keyboard. That won't just effect screen reader
> users, but anyone who is unable to use a pointing device. If you want
> to ensure the widget is accessible, then any links or buttons must be
> accessible with a keyboard.
>
> The only time a tabindex attribute value of -1 is appropriate is if
> you definitely do not want people to be able to navigate to the
> element with the keyboard, but need to be able to programmatically
> focus on the element - this isn't the case here. Requesting a new
> CAPTCHA, toggling between visual and audio CAPTCHAs, and getting help
> are essential functions that everyone should be able to access, so
> those elements must be available with the keyboard alone to be
> considered accessible.
>
> Cheers,
>
> Gez
>
> -- 
> _____________________________
> Supplement your vitamins
> http://juicystudio.com
>
>
Received on Friday, 13 July 2007 23:42:50 GMT

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