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

RE: Keyboard accessibility in UAAG2 - what we have

From: Jim Allan <jimallan@tsbvi.edu>
Date: Wed, 18 Jun 2008 13:40:02 -0500
To: <Peter.Korn@Sun.COM>
Cc: <w3c-wai-ua@w3.org>
Message-ID: <066001c8d172$b81d3d20$2857b760$@edu>

Thanks for this Peter. 
These are useful.
We are also looking for guidelines on how and when to include visual
indicators of shortcut keys (i.e. _F_ile [underlined F] to indicate that 'F'
is a hotkey in a menu or dialog box or tabbed pane) and accelerator keys
(i.e.  in a menu, 'Save  Ctrl S') to activate a function directly without
wading through many menus.

Jim

> -----Original Message-----
> From: Peter.Korn@Sun.COM [mailto:Peter.Korn@Sun.COM]
> Sent: Wednesday, June 18, 2008 1:33 PM
> To: Jim Allan
> Cc: w3c-wai-ua@w3.org
> Subject: Re: Keyboard accessibility in UAAG2 - what we have
> 
> Dear Jim,
> 
> For UNIX/Linux, please see the GNOME Accessibility Guide which describes
> in detail all of the keyboard shortcuts available on the graphical GNOME
> desktop of many UNIX/Linux systems, as well as the shortcuts used in a
> number of GNOME applications.  Note please further that Java Swing
> applications when using the "GTK+ Look and Feel" (or the "platform
> default L&F" when running on a GNOME desktop) will likewise utilize
> those shortcuts.
> 
> Find the GNOME Accessibility Guide at
> http://library.gnome.org/users/gnome-access-guide/stable/ (and
> specifically the keyboard navigation section at:
>
http://library.gnome.org/users/gnome-access-guide/stable/keynav-0.html.en),
> or you can read the entire guide as one file at:
> http://library.gnome.org/users/gnome-access-guide/2.22/gnome-access-
> guide.html
> 
> 
> Regards,
> 
> Peter Korn
> Accessibility Architect,
> Sun Microsystems, Inc.
> 
> 
> > Keyboard accessibility in UAAG 2
> >
> > Things we have
> > 1) Definitions - From
> > http://lists.w3.org/Archives/Public/w3c-wai-ua/2008AprJun/0004.html
> >
> > Are definitions adequate? Comments and discussions - send to the list
> >
> > 2) Working draft Operable Guideline
> > http://www.w3.org/TR/2008/WD-UAAG20-20080312/#principle-operable
> >
> > Please review.
> >
> > 3) Useful references. Should be included in Techniques.
> > Microsoft - http://msdn.microsoft.com/en-us/library/bb545460.aspx
> > And http://msdn.microsoft.com/en-us/library/bb545462.aspx
> > And Guidelines for Keyboard User Interface Design -
> > http://msdn.microsoft.com/en-us/library/ms971323.aspx
> >
> > Mozilla -
> > http://developer.mozilla.org/en/docs/XUL_Tutorial:Keyboard_Shortcuts
> >
> > Apple - Apple Human Interface Guidelines: Keyboard
> http://tinyurl.com/62bzx7
> >
> >
> > Unix/Linux - could not find anything (I am sure it is out there)
> >
> > Java - http://java.sun.com/products/jlf/ed1/dg/higi.htm#39314
> >
> > Additional resources? Send to the list
> >
> >
> > Jim Allan, Webmaster & Statewide Technical Support Specialist
> > Texas School for the Blind and Visually Impaired
> > 1100 W. 45th St., Austin, Texas 78756
> > voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
> > "We shape our tools and thereafter our tools shape us." McLuhan, 1964
> >
> >
> >
> >
> >
Received on Wednesday, 18 June 2008 18:44:37 GMT

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