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

Re: Using tab stop on important text

From: Devarshi Pant <devarshipant@gmail.com>
Date: Tue, 29 Nov 2011 12:21:04 -0500
Message-ID: <CAJGQbjvBAJ1sU-yLDXRHcz6MJJuudMx8TBfq7A1b0SEauc1OJw@mail.gmail.com>
To: Jonathan Avila <jon.avila@ssbbartgroup.com>
Cc: w3c-wai-ig@w3.org
*Jonathan wrote: Adding additional tab stops to headings would only
add to the number of times to the user must tab. Providing other ways
for keyboard users to
navigate other than tab would be preferential. *

Yes, putting a tab stop would add to the number of stops, but do we
know for sure that keyboard only users are inconvenienced with added
tab stops? You are correct, there should be other ways—I hope browser
vendors could provide a solution.

Leon—I agree with you. I have often seen instructional text placed
between form fields, which is often difficult to get to, especially
when you don’t know where to arrow down from when running a screen
reader. Users generally tab when filling out forms, and a tab index of
zero, when applied judiciously, does accommodate user groups. I was
hoping we can get some direction on a WCAG technique (the intent of
this post) that can set the parameters (when, where, how, etc.) for
those who are interested.

*Phil wrote: Sounds to me like you're trying to play the role of
assistive technology
when you BOTH make it a heading AND add a tabindex.  Requiring the author
/ developer to add even more mark-up in addition to the heading tag is not
the best approach in my opinion.  Shouldn't AT developers take on any
additional responsibility for the behavior you are suggesting if not
already provided? *

AT vendors already expose html headings, so I am not sure how they may
help in this regard, considering we put a tab index attribute. Yes,
project teams / developers should ideally be doing this, and here is
why: Adding a tab index attribute (of just *zero*) in certain designs
could help users who tab. A keyboard only user, without an AT, would
be benefitted. Users with learning disabilities may learn better. If
it accommodates more users, it should be encouraged.

Thanks,
Devarshi

On 11/28/11, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote:
> [Devarshi wrote] 1. Page headers could have a tabindex attribute of zero
> (sequential focus navigation) allowing keyboard only users to access
> important sections in the page, without having to tab extensively.
>
> Adding additional tab stops to headings would only add to the number of
> times to the user must tab.  Providing other ways for keyboard users to
> navigate other than tab would be preferential.
>
> I do believe it is helpful to place error messages as tab stops.  Other
> scrolling areas such as license text would also need to be tab stops in
> order for users of speech recognition to be able to scroll them with voice
> commands.  Read only fields that are enabled should also be keyboard
> accessible.
>
> Jonathan
Received on Tuesday, 29 November 2011 17:21:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 29 November 2011 17:21:33 GMT