Thread Subject: Re: Proposals regarding keyboard shortcuts

Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.

From: Andrew Kirkpatrick
Date: Tue, Feb 12 2008 6:50 AM

Judy and peter,
I'm hoping you can provide a little more detail on the distinction between a keyboard shortcut and keyboard convention, relating to your new propsed provision. I'm not confident that this is going to be clear - is it that conventions are general to an entire app or type of control and shortcuts are for a specific instance of a control?
AWK


---
Andrew Kirkpatrick

Adobe Systems

= EMAIL ADDRESS REMOVED =

617.219.2209

-----Original Message-----
From: Judy Brewer [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Tuesday, February 12, 2008 05:34 AM Pacific Standard Time
To: TEITAC Committee; Peter Korn
Subject: [teitac-committee] Proposals regarding keyboard shortcuts

Following is a two-part proposal to address documentation and
visibility of keyboard shortcuts, based on discussion between Peter
Korn and myself over the past several weeks.

We reached rough agreement on the first part of the proposal, but had
not completed addressing each other's concerns about the alternatives
in the second part of the proposal.

We're forwarding this at the Chairs' request so as to be available
for discussion on the list and during the related agenda item for the
Feb 12 TEITAC teleconference.

Regards,

- Judy

1. Draft new provision to go in section 3 "User Interface and
Electronic Content Provisions", with suggested placement following
current 3-S, "Keyboard Operation":
------------------------------------
Visual Indication of Keyboard Shortcuts:
All keyboard commands associated directly with user interface
controls should be visible within the visual user interface in at
least one mode, and available programmatically to AT.
Note: This includes commands such as those used to activate a menu
or button, but not non-visible conventions such as ALT-TAB or Ctrl-Arrow.

Rationale for proposing this addition: We added the visibility
clause noting that this is a specific problem for several classes of
users. Note that there are a variety of ways of achieving "at least
one mode," including a global system setting, pressing a key to
highlight the shortcuts, etc. We recommend placing this new clause,
and the programmatic availability to AT, here rather than in
documentation because it is about what the product must do, not what
the documentation about the product must do.

--------------------

2. Draft new 1.1-B (two alternative versions):
---------version (1)------------
Information about keyboard shortcuts - including keyboard commands
and keyboard navigation mechanisms - must be documented in at least
one of the following places:
a. integrated help system / context-sensitive help
b. centralized on-line documentation
c. printed user documentation
When the documentation lists specific pointing-device based
actions that are unique to the product or content, the keyboard
commands must also be listed. Wherever commercially reasonable and
logically practicable, all keyboard shortcuts, commands, and
navigation should be documented in at least one centralized location.

----------version (2)----------------
Information about keyboard shortcuts - including available
keyboard commands and keyboard navigation mechanisms - must be
listed in centrally located user documentation, and available in
context-sensitive help.

###

--
Judy Brewer +1.617.258.9741 http://www.w3.org/WAI
Director, Web Accessibility Initiative (WAI), World Wide Web Consortium (W3C)
MIT/CSAIL Building 32-G526
32 Vassar Street
Cambridge, MA, 02139, USA

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University