- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Wed, 18 Jun 2008 13:04:05 -0500
- To: <w3c-wai-ua@w3.org>
There are 6 proposals from Jan in
http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JanMar/0058.html with
discussion. Each will be broken out to allow more discussion and counter
proposals. All of these proposals are new success criteria for Guideline 4
http://www.w3.org/TR/2008/WD-UAAG20-20080312/#principle-operable
Here is the first one.
"Chrome" is used to mean the application user interface. Separate from
content user interface. This proposal was slightly edited to include nits
and clarifications from the included discussion below.
(1) Visual Keyboard Shortcut Indicator ("Chrome") Provide a user
setting in which currently visible user interface "chrome" components
visually indicate their keyboard shortcuts, IF ANY (e.g., with
access key letters underlined).
Previous discussion.
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'
JR: I should have said "Access key" which is the proper term
(http://www.usabilityfirst.com/glossary/term_526.txl), which we should
define. I purposefully left out modifier+key (e.g. Ctrl+S) because if
the File menu is closed how will this be indicated?
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:09:02 UTC