W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2011

Action 501 - Guideline 2.8 (Intent)

From: Simon Harper <simon.harper@manchester.ac.uk>
Date: Thu, 24 Feb 2011 19:15:12 +0000
Message-ID: <4D66AE40.2000007@manchester.ac.uk>
To: UAWG list <w3c-wai-ua@w3.org>
Action 501 Intent etc for discussion.

2.8.1 (former 4.8.1) Configure Position:
When graphical user agent user interfaces have toolbars, the user can 
add, remove and configure the position of user agent user interface 
controls on those toolbars from a pre-defined set of controls. (Level AAA)


* Intent of Success Criterion 2.8.1 (former 4.8.1) :
Users with dexterity impairments or mobility impairments may have 
problems making the large movements required to select between 
non-adjacent toolbar controls which they need to use frequently. 
Enabling these controls to be situated together removes much the the 
strain, and pain, faced by these users, and increases productivity as 
task completion times are decreased.


* Examples of Success Criterion 2.8.1 (former 4.8.1) :
As part of her work as a legal secretary, Jane always needs to justify 
paragraphs, place them in a numbered list, and bold the first word of 
each list item. Because the online document processor she uses does not 
allow toolbars to be modified, and groups controls logically together - 
all paragraph formatting is grouped together, as are list manipulation 
and character highlighting - Jane experiences increased pain from her 
repetitive strain injury forcing her to take many more breaks. If the 
word processor allowed toolbar modification Jane could group 'justify' 
next to 'numbered list' next to 'bold' creating less requirement for 
movement and therefore less strain.

* Related Resources for Success Criterion 2.8.1 (former 4.8.1) :
o WAI-ARIA


====
2.8.2 (former 4.8.2) Restore Default Toolbars:
The user can restore the default toolbar configuration. (Level AAA)

* Intent of Success Criterion 2.8.2 (former 4.8.2) :
Mistakes happen. If a user has modified the toolbar incorrectly it can 
often be difficult to return to a stable state so that these errors can 
be corrected. There are additional pressures in this regard for people 
with learning difficulties who make more use of toolbars than they do of 
textual menus. Building an easily selectable mechanism to restore these 
defaults saves user time and reduces stress.

* Examples of Success Criterion 2.8.2 (former 4.8.2) :
Jack, is an 80 year old silver surfer who is intellectually very sharp 
but experiences tremors in his hands when required to make fine 
movements with the mouse. To help himself he is setting up the toolbar 
so that 'spacers' are placed between each component to prevent 
accidental selection of adjacent buttons. Today his tremors are 
particulaly bad and Jack makes a number of mistakes becoming 
increasingly frustrated that while trying to correct these errors he 
begins to make many more. Jack just wants to start over. Luckily the 
WebApp manufacturer has included an easy mechanism to restore the 
default toolbar configuration. Jack chooses this option and successfully 
starts over the next day.


* Related Resources for Success Criterion 2.8.2 (former 4.8.2) :
o WAI-ARIA
Cheers

Si.

=======================

Simon Harper
University of Manchester (UK)

More: http://simon.harper.name/about/card/
Received on Thursday, 24 February 2011 19:15:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 24 February 2011 19:15:45 GMT