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

Re: Action: Proposal for placement of keyboard items

From: Jan Richards <jan.richards@utoronto.ca>
Date: Fri, 01 Aug 2008 15:19:45 -0400
Message-ID: <489361D1.4020000@utoronto.ca>
To: w3c-wai-ua@w3.org

Some thoughts...

Jim Allan wrote:
> 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.

It's a stretch. :) I think this hides the part that Judy was hoping 
would get stressed....the visibility.


> 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.

Not sure about this...the note on 3.3 puts me off.


> 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.

OK - maybe keyboard commands need to be an example.

> 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. 

Should be a "THAT" before "have direct keyboard command". OK.

> 
> 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.

OK.

Cheers,
Jan



> 
> 
> 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
> 
> 
> 
> 

-- 
Jan Richards, M.Sc.
User Interface Design Specialist
Adaptive Technology Resource Centre (ATRC)
Faculty of Information (i-school)
University of Toronto

   Email: jan.richards@utoronto.ca
   Web:   http://jan.atrc.utoronto.ca
   Phone: 416-946-7060
   Fax:   416-971-2896
Received on Friday, 1 August 2008 19:18:16 GMT

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