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: <deborah.kaplan@suberic.net>
Date: Mon, 15 Oct 2012 11:30:36 -0400 (EDT)
To: Harry Loots <harry.loots@ieee.org>
cc: Vivienne CONWAY <v.conway@ecu.edu.au>, Userite <richard@userite.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.64.1210151127150.15720@suberic.net>
On Mon, 15 Oct 2012, Harry Loots wrote:
> Alt+ 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, S and a few others are not bound to any
> browser as far as I am aware?

You will want to do your testing beyond just what is bound  to the
browser, however. Many people have other adaptive technologies in
place and the default settings of other adaptive tech may use
those key bindings -- I'm not sure of those in particular. I
know, for example, that people frequently put into place
keystroke bindings on websites (Ajax, not access key) which don't
interfere with anything built-in to the browser but DO interfere
with the mouseless browsing extension used by many keyboard
users.

(Another thing to take into account with access keys is how you
expose them to non-screen reader users. Frequently lists of
access keys are published via text hidden from visual display but
not from screen reader via CSS, and neither zoom nor
keyboard-only users ever know the list exists.)

-Deborah
Received on Monday, 15 October 2012 15:31:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 15 October 2012 15:31:12 GMT