E-mail List Archives
Re: WCAG Violation for use of tabindex=0 on static elements.
From: Lucy Greco
Date: Mar 16, 2016 2:51PM
- Next message: Moore,Michael (Accessibility) (HHSC): "Re: WCAG Violation for use of tabindex=0 on staticelements."
- Previous message: Moore,Michael (Accessibility) (HHSC): "Re: WCAG Violation for use of tabindex=0 on staticelements."
- Next message in Thread: Moore,Michael (Accessibility) (HHSC): "Re: WCAG Violation for use of tabindex=0 on staticelements."
- Previous message in Thread: Moore,Michael (Accessibility) (HHSC): "Re: WCAG Violation for use of tabindex=0 on staticelements."
- View all messages in this Thread
hello mike:
i would ask them to try and tab throu the page with out a mouse and then
find one of the hand restriktors that trace includes in there educational
kit and then ask them to do it again then tell them the point of web
acccess is to do no harm and let them know every time a person with carpel
tunnal has to hit a key the dev is doing harm smile hope this helps lucy
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces
On Wed, Mar 16, 2016 at 1:25 PM, Moore,Michael (Accessibility) (HHSC) <
<EMAIL REMOVED> > wrote:
> Thanks Marc,
>
> I was considering that one but talked myself out of it because the
> sequence seemed to be correct. It goes left to right from top to bottom.
> On further reflection though I may be able to argue that the correct
> sequence is to move logically from active element to active element. The
> addition of tabindex="0" on inactive elements is interrupting that sequence
> in a major way.
>
>
> Mike Moore
> Accessibility Coordinator
> Texas Health and Human Services Commission
> Civil Rights Office
>
>
- Next message: Moore,Michael (Accessibility) (HHSC): "Re: WCAG Violation for use of tabindex=0 on staticelements."
- Previous message: Moore,Michael (Accessibility) (HHSC): "Re: WCAG Violation for use of tabindex=0 on staticelements."
- Next message in Thread: Moore,Michael (Accessibility) (HHSC): "Re: WCAG Violation for use of tabindex=0 on staticelements."
- Previous message in Thread: Moore,Michael (Accessibility) (HHSC): "Re: WCAG Violation for use of tabindex=0 on staticelements."
- View all messages in this Thread