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

Re: Access Keys as a means to passing 2.4.1 Bypass Blocks

From: Harry Loots <harry.loots@ieee.org>
Date: Tue, 16 Oct 2012 14:24:12 +0200
Message-ID: <CA++-QFeaQC1pBOpTHna4uv47dJxouCCX_uX4MxWdqWduef0pag@mail.gmail.com>
To: Vivienne CONWAY <v.conway@ecu.edu.au>
Cc: David Woolley <forums@david-woolley.me.uk>, Userite <richard@userite.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
On 16 October 2012 08:48, Vivienne CONWAY <v.conway@ecu.edu.au> wrote:

> ... access keys ....  If only we could get people to have them always
> visible


Amen!


> I just think we need to be more open to having the accessibility features
> visible - demonstrates our desire to make things easier for people.
>
>
All people!


> By the way, I'm still not sure why headings satisfy this criterion.  If
> you rely on the heading, it then requires subjective analysis to determine
> if the headings are sufficient to enable people to satisfactorily skip the
> repeated content.The headings only help screen reader users, not people who
> rely on tab control or have low vision.
>

I was also of the opinion that headings only help screen reader users -
but... since HTML5 allows both accesskey and tabindex on any element, it
should now be possible to utilise headings, to allow all keyboard users to
jump to new zones. Using an accesskey, as a shortcut to some/all page
headings, should be easy enough, but using tabindex as means to tab to
headings, without causing interference to natural order of tabbing may be a
huge task, and may make the use of tabindex impractical, except in smaller
sites or simple forms.

food for thought, though...

Kind regards, Harry
Received on Tuesday, 16 October 2012 12:24:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 16 October 2012 12:24:39 GMT