W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2008

RE: Visual keyboard accessibility indicators (was Re: User Agent Teleconference for February 28 2008 (new time 2pm Eastern))

From: Jim Allan <jimallan@tsbvi.edu>
Date: Mon, 3 Mar 2008 10:52:08 -0600
To: "'Jan Richards'" <jan.richards@utoronto.ca>, "'WAI-ua'" <w3c-wai-ua@w3.org>
Cc: "'Judy Brewer'" <jbrewer@w3.org>
Message-ID: <087301c87d4e$ebc0a090$c341e1b0$@edu>

Jims comments 
<jim></jim>

Jan wrote: 
As per my action item from today's call, here's what I see as the main 
pieces. I've also split them up since they may lend themselves to 
different priorities:

NOTE: Keyboard shortcut probably needs a definition that excludes 
keyboard controls for sequential navigation (arrow keys, ENTER, TAB, etc.)

(1) Visual Keyboard Shortcut Indicator ("Chrome"): Provide a user 
setting in which currently visible user interface "chrome" components 
visually indicated their keyboard shortcuts, IF ANY (e.g., with 
accesskey letters underlined).
<jim>example should also include modifier key plus letter for items in a
menu. My wording could use some work. I am trying to include not just the
top level user interface items (accesskey underlined) but the items in the
menus (Save Ctrl+S).
Also have a concern about 'accesskey'. It may be confused with the HTML
@accesskey. Suggest 'shortcut key' in place of 'accesskey'
Nit: 'indicated' should be 'indicate'
</jim>

(2) Ensure Keyboard Shortcuts: Any user interface "chrome" component 
that can receive *user interface focus* using the keyboard has a 
keyboard shortcut, unless the *operating environment* prevents this.
<jim>I like this. This provides for quick access to menu items. So, if I
need to open an email archive, I can hit 'ALT+F, A' rather than 'ALT+F and
multiple down arrows. 
I think we still need something about common actions that have shortcut keys
but are 2 submenu levels down (sort of like deep linking to a menu command).
For example, in Firefox changing text sizes is one submenu off of the 'view'
menu, but 'increase' and 'decrease' font size each have a shortcut key
combination (CTRL+ and CTRL-). My concern is that 'common actions' is hard
to define and may be too prescriptive.). 
</jim>

(3) Visual Keyboard Shortcut Indicator (Content Display): Provide a user 
setting in which any *recognized* keyboard shortcuts for currently 
visible content are visually indicated (e.g., with overlays).
<jim>what is an 'overlay'? 
</jim>

(4) Programmatically Available Keyboard Shortcuts ("Chrome" and Content 
Display): If a keyboard shortcut exists for a component, then it is 
available programmatically.

(5) Document Keyboard Shortcuts ("Chrome"): Any *warping keyboard 
shortcuts* (shortcuts to destinations requiring multiple mouse clicks) 
are listed in the documentation. Note: Separate lists are permitted for 
the "base" user agent, each extension and each plug-in.
<jim>Think this should be all keyboard shortcuts (those with modifier keys)
should be listed in the documentation. 

(6) Content Focus Keyboard Commands (Content Display): Users may request 
a list of all keyboard commands that are currently available and are 
"recognized" to move the content focus.
Received on Monday, 3 March 2008 16:53:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:53 GMT