E-mail List Archives
Thread: RE: use of access keys (was: Next and Previous Accesskey)
Number of posts in this thread: 2 (In chronological order)
From: John Foliot
Date: Tue, Oct 07 2003 9:54AM
Subject: RE: use of access keys (was: Next and Previous Accesskey)
No previous message | Next message →
> Has anyone ever assembled a comprehensive list of reserved keys?
While we would be loathe to call the list "comprehensive", we have assembled
a fairly detail listing of reserved keystroke combinations based upon our
research since last summer. The listing can be found at:
http://www.wats.ca/resources/accesskeysandkeystrokes/38
Note, the list is based on the Windoze OS only. Feedback from Mac users,
Linux users, etc. gratefully accepted and will be added to the list. The
same holds true for users of other, "alternative" browsers or users of
different adaptive technologies which may be affected by this issue.
The argument has been made that the user agents/applications *should*
over-ride HTML specified "commands", however we have noted that this is not
always the case. For example, Internet Explorer binds the keystroke ALT+D
to the address bar. An HTML defined accesskey for the letter D overrides the
keyboard binding to the address bar, and therefore disables that critical
keyboard shortcut for IE users. This is the perfect example of where
accesskeys can go wrong, as it is the exact opposite of what we believe
should happen.
The comment has been made that this is/could be/should be more than just an
issue that affects blind or other visually impaired users, and we cannot
agree more. What about those with cognitive disabilities? What happens if
they have learned to use certain keystroke combinations to use their
software tools (for example the above mentioned Alt+D)? What happens if you
"tell" the user that they can use "x" key (Alt+X) to do something, and their
software combination (browser, OS, whatever) does not support the declared
functionality? At that point, what is "broken"? Your code? Their tools?
Their usage (which could cause concern, frustration, anger...)? How can
this support accessibility?
There are other issues as well, including but not limited to
Internationalization (not all keyboards are the same), the number of
Accesskeys provided to the user (I once saw a site that had over 30
"Accesskeys"... who in their right mind can or will bother to learn all of
them?), and on and on. Don't get us wrong, the idea of Accesskeys is great
on paper, but given the current situation with User Agents and support, as
well as the lack of Standardization, Accesskeys simply are not providing the
right type of accessibility to be taken seriously or implemented with any
level of assurance. It is for that reason that we currently give them a
thumbs down...
JF
--
John Foliot = EMAIL ADDRESS REMOVED =
Web Accessibility Specialist / Co-founder of WATS.ca
Web Accessibility Testing and Services
http://www.wats.ca 1.866.932.4878 (North America)
>
From: Randy Pearson
Date: Thu, Oct 09 2003 7:14AM
Subject: RE: use of access keys (was: Next and Previous Accesskey)
← Previous message | No next message
>> For example, Internet Explorer binds the keystroke ALT+D
to the address bar. An HTML defined accesskey for the letter D overrides the
keyboard binding to the address bar, and therefore disables that critical
keyboard shortcut for IE users.
F6 key does that in MSIE also, and cannot be overriden by accesskeys.
Incredibly, F6 also now does this in Mozilla. Very convenient.
>> ... who in their right mind can or will bother to learn all of them?
For the average site, hardly anyone. But say you subscribe to a daily or
weekly web-based "magazine" which uses a page-at-a-time publication design.
I would love to have an accesskey for the Next Page link. Otherwise, I have
to both grab the mouse *and* scroll to the top/bottom to find the link. In a
case like this, I would learn this critical accesskey. (Yes, I realize some
browsers support <link> tags for this, but that's another matter, and even
those functions don't seem to have keyboard shortcuts.)
-- Randy
----
To subscribe, unsubscribe, suspend, or view list archives,
visit http://www.webaim.org/discussion/