Proposal for placement of keyboard items

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


I'm generally OK with this apart from the requirement 'visually  
displayed..', I'm unsure if specifying this explicitly is the best  
option - what if the application does not present itself visually?  
Maybe it should say something like - 'in the same manner as the  
application presents its interface (eg visually, aurally , etc)

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



Visible again - I understand the context here but it seems ambiguous  
to me

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


Agreed

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


Can we not just mash this up with 1 above?

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


Agreed.


Cheers
Si.

====
Simon Harper
University of Manchester (UK)

Human Centred Web Lab: http://hcw.cs.manchester.ac.uk
My Site: http://hcw.cs.manchester.ac.uk/people/harper/
My Diary (iCal): http://hcw.cs.manchester.ac.uk/diaries/SimonHarper.ics


+----------------------[ NEW &  
INTERESTING ]--------------------------------------+
   ASSETS 2008                . 13-15 Oct 2008 . http:// 
www.sigaccess.org/assets08
+----------------------------------------------------------------------- 
----------+

Received on Friday, 1 August 2008 16:43:29 UTC