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

Re: Action 501 - Guideline 2.8 Reformulation

From: Greg Lowney <gcl-0039@access-research.org>
Date: Thu, 10 Mar 2011 09:55:32 -0800
Message-ID: <4D791094.404@access-research.org>
To: Jim Allan <jimallan@tsbvi.edu>
CC: simon.harper@manchester.ac.uk, uawg list <w3c-wai-ua@w3.org>
I am concerned about the phrase "from a predefined set", as it sounds like it could prohibit the user from adding their own custom controls, and that "configure the position" could be taken as meaning finely and arbitrarily adjusting the position (as with icons on the OS X desktop). It seems that what we want to require is that the user can, at minimum, "add, remove, and reorder the available controls" on a toolbar or similar container.

Additional benefits include reducing distraction, and potentially reducing the amount of space on the screen taken up with toolbars and the like.

Adding, removing, and repositioning toolbars is certainly a good thing for all the same reasons. I have no objection to combining the two success criteria if they have the same priority, which as usual would have the advantage of keeping the count down, but the disadvantage of making it harder to track and give credit when a product supports one but not the other (e.g. if they allow the contents of a toolbar to be customized, but not its location).

Speaking of which, whether we want to include them or not, some additional recommendations for toolbars include: (a) let user customize the text or icons used for toolbar buttons, which can be used to substitute highly visible or highly differentiated icons; (b) let users choose to have toolbar buttons represented by icons and/or text; (c) provide a choice of sizes for toolbar icons and text; (d) let users create custom toolbars so the display can easily be switched between standard and customized views, which is not easily done if one can only change the contents of the standard toolbars. Many of these features are fairly well supported by suites such as Microsoft Office and Mozilla.

In the first example, the last sentence says Jane when it means Mary.

The second SC, 2.8.2 Restore Default Toolbars, would be clearer if we don't break up the phrase too much, and while the group wanted to explicitly reference things beyond toolbars, the comma-separated list is a bit much to put in the middle of a sentence. Perhaps rephrase "The user can restore the default toolbar, panel, inspector, configuration" to something like "The user can restore the default configuration of toolbars and similar controls" or "The user can restore toolbars and similar controls to their default configuration"?

-------- Original Message  --------
Subject: Re: Action 501 - Guideline 2.8 Reformulation
From: Jim Allan <jimallan@tsbvi.edu>
To: simon.harper@manchester.ac.uk
Cc: uawg list <w3c-wai-ua@w3.org>
Date: 3/10/2011 9:01 AM
> Simon and group,
> I am working on  a new SC about showing/hiding toolbars. When I
> started on it this morning, I thought of rewriting the current 2.8.1
> to include the showing/hiding of the actual toolbar in addition to the
> individual controls. This would also give the user the ability (that
> does not yet exist) to rearrange the display order of the toolbars.
> Currently, you can show/hide toolbars but only in the order in which
> the toolbars were installed.
> What are your thoughts about extending 2.8.1 to include whole toolbars
> in addition to components within toolbars?
> I will continue working on the IER and new SC, in the interim.
> On Wed, Mar 9, 2011 at 8:34 AM, Simon Harper
> <simon.harper@manchester.ac.uk>  wrote:
>> Action 501 SC / Intent Reformulation
>>  From Minutes:
>> http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0076.html
>> Links to:
>> http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JanMar/0073.html
>> Modified Taking into Account:
>> http://www.w3.org/2002/09/wbs/36791/20110301/results
>> Guideline 2.8 (former 4.8) Provide toolbar configuration.
>> 2.8.1 (former 4.8.1) Configure Position:
>> When graphical user agent user interfaces have toolbars, panels, inspectors,
>> or similar,
>> the user can add, remove and configure the position of user agent user
>> interface
>> controls from a pre-defined set. (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 controls which they need to use frequently.
>> Similarly users with low vision may have to excessively
>> move their magnified view-port to see frequently used controls.
>> Enabling these controls to be situated together removes much of the
>> strain 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 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. Further, Jane's colleague Mary
>> has no problems with her hands, but because of her vision problems,
>> it takes longer for her to focus on a given part of the screen.
>> Grouping justify, numbered list and bold together allows Jane to
>> avoid excess reorienting and keep up with her colleagues.
>> * Related Resources for Success Criterion 2.8.1 (former 4.8.1) :
>> ====
>> 2.8.2 (former 4.8.2) Restore Default Toolbars:
>> The user can restore the default toolbar, panel, inspector, 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 web 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
>> Browser 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) :
>> Cheers
>> Si.
>> =======================
>> Simon Harper
>> University of Manchester (UK)
>> More: http://simon.harper.name/about/card/
Received on Thursday, 10 March 2011 17:59:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:40 UTC