Re: [note: two-level nav in WAI-ARIA] [was: Re: reCAPTCHA implementation problems]

Hey,

On Tue, 17 Jul 2007, Gez Lemon wrote:
> The benefits of reducing items in the tab order are obvious, and I'm
> sure that everyone subscribed to this list will appreciate that. I'm
> sorry that I overlooked that point from my original response, but it
> seemed to me that we were dealing with a scenario where keyboard
> accessibility wasn't a priority at all - I apologise for not making
> that clearer, but in the meantime, there is at least one person
> included in this thread (CC'd back in) that doesn't think any kind of
> provision for keyboard accessibility is important, and I mistakenly
> have focused on that person. Further responses will be worded so that
> it's clear to this list what I mean by keyboard accessibility.

I think you're talking about me :-).

Please don't get me wrong, I want to make reCAPTCHA as accessible as 
possible. However, when a11y changes also change behavior for other users, 
we obviously need to evaluate that much more carefully. If the change 
doesn't work as well for the majority of our users, we'll look for ways to 
fix the issue. Should no workarounds be available, we'll have to balance 
the impact on the general population with exactly what features would be 
made less accessible (for example, for a visual user, disabling the three 
buttons on the side isn't the end of the world, they can still solve the 
CAPTCHA).

About keyboard navigation specifically -- as you mention, it's obvious 
that having the tab order include EVERYTHING in the document isn't ideal. 
Tabs should go through logical components with second level navigation 
available. Until better browser support is available to do this, we need 
to figure out a work around. The one's I've seen so far are:

- "screw it" let's put everything in the tab order
 	- Pro: accessible to everybody
 	- Cons
 		- May not be ideal for the majority of the population
 		- Potentially confusing tab order (reCAPTCHA is very
 		  limited due to the constraint of living in the author's
 		  document)

- Access keys
 	- Pro: invisible to normal users
 	- Con: depends on the UA for exposure. Could conflict with primary
 	  site.

-b

Received on Wednesday, 18 July 2007 01:35:14 UTC