Action: Proposal for placement of keyboard items

The following are from http://www.tsbvi.edu/technology/uawg/thrashing.htm
They are from the Remove section. 
Proposals are for moving the items below to specific sections of UAAG20
http://www.w3.org/tr/uaag20

1. Any currently visible UI operable controls that have direct UI keyboard
commands (that activate or move focus), have their keyboard commands
visually displayed in context (next to menu item, underline character) Level
A [Remove - should be in PRINCIPLE 3: Ensure that the user interface is
perceivable]

Proposal: Move to Guideline 3.11 Help user to use and orient within
viewports
Make it 3.11.7

Rationale: It may be a stretch, I am considering the browser User Interface
as a viewport. In order for many users to effectively use the functions in
the interface, the controls must be visually indicated.

2. User configuration has an option to display keyboard shortcuts for all
visible controls. Level ? [New. This needs more work] [Remove - should be in
PRINCIPLE 3: Ensure that the user interface is perceivable]

Proposal: Move to Guideline 3.3 Provide control of content that may reduce
accessibility
make it 3.3.13 

Rationale: Many of the Success criteria in this guideline have a user
configuration option. Not having keyboard shortcuts visible is an
accessibility issue for people who have physical (keyboard operation) and
memory (remembering relevant keystrokes) limitations.

3. Any currently available UI direct keyboard commands (that activate or
move focus) are available programmatically. Level A [Remove - should be in
PRINCIPLE 2. Facilitate access by assistive technologies]

Proposal: remove. 

Rationale: This is already part of Guideline 2.5 Programmatic operation of
user agent user interface. Specifically, Success Criteria 2.5.1:
Programmatic read access is provided to user agent user interface controls,
selection, content focus, and user interface focus. Keyboard commands are
part of user interface controls.

4. Any currently visible CONTENT interactive controls have direct UI
keyboard commands (accesskey or variation), have their keyboard commands
visually displayed in context (next to item, overlay) or in a list. Level A
[Remove - should be in PRINCIPLE 3: Ensure that the user interface is
perceivable]

Proposal: Move to Guideline 3.11 Help user to use and orient within
viewports
Make it 3.11.8

Rationale: The content area is a viewport. In order for many users to
effectively use the functions in the interface, the controls must be
visually indicated. 

5. Any currently available CONTENT direct keyboard commands (accesskey or
variation) are available programmatically Level A [Remove - should be in
PRINCIPLE 2. Facilitate access by assistive technologies]

Proposal: move to Guideline 2.4 Programmatic access to information about
rendered content
make it 2.4.4

Rationale: Accesskey or other future recognized keybindings are part of
information about rendered content that assistive technology needs to know
about in order to function properly.


Jim Allan, Accessibility Coordinator & Webmaster 
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, 30 July 2008 16:09:33 UTC