- From: Greg Lowney <gcl-0039@access-research.org>
- Date: Mon, 02 Jan 2012 17:59:09 -0800
- To: WAI-UA list <w3c-wai-ua@w3.org>
- Message-ID: <4F0260ED.90704@access-research.org>
I've added the following to our Wiki page "User Agent issues effecting A11y" at http://www.w3.org/WAI/UA/work/wiki/User_Agent_issues_effecting_A11y#Accesskeys: How browsers react when an accesskey is pressed varies widely in terms of: * what modifier key(s) are used to trigger the accesskey * if multiple elements share an accesskey, which is used * whether the keyboard focus moves to the element * whether the element is scrolled into view * whether the element is activated In particular, allowing the user to cycle through elements with conflicting accesskeys allows much more efficient access to them than sequential navigation through all operable elements, but it also makes it more difficult to use them in preprogrammed macros. *Browser* *Modifier* *Conflict* *Chooses* *Moves Focus* *Scrolls* *Activates* Windows Alt+ Yes Yes Yes Windows Alt+ Conflict Next Yes Yes No Firefox 3 Alt+Shift+ Yes Yes Yes Firefox 3 Alt+Shift+ Conflict FIRST Yes Yes No Firefox 8 Alt+Shift+ Yes Yes Yes Firefox 8 Alt+Shift+ Conflict Next Yes Yes Yes Chrome 16 Alt+Shift+ NO NO YES Chrome 16 Alt+Shift+ Conflict LAST NO NO YES Safari 5.1 Alt+Shift+ NO NO YES Safari 5.1 Alt+Shift+ Conflict LAST NO NO YES Opera 11.11 Shift+Esc, Yes Yes Yes Opera 11.11 Shift+Esc, Conflict FIRST Yes Yes YES Gnome Ctrl+ ? ? ? ? Gnome Ctrl+ Conflict ? ? ? ? KDE Alt+ ? ? ? ? KDE Alt+ Conflict ? ? ? ?
Received on Tuesday, 3 January 2012 01:59:37 UTC