- Important note: This Wiki page is edited by participants of the User Agent Accessibility Guidelines working group (UAWG). It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Guideline 2.8

From WAI UA Wiki
Revision as of 18:23, 10 June 2011 by Jeanne (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Guideline 2.8 (still 2.8)

Success Criterion 2.8.1 (former 4.8.1)

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)

The objective of this criteria is to allow the user to customize the toolbars of a user agent in ways that work best for the method in which he or she is using the browser. This can reduce keystrokes, bring buttons into view that are hidden by default or otherwise allow the user to interact with the user agent in a more efficient fashion. 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) :

Martin accesses the computer by pressing keys with a stick held in his mouth known as a mouthstick and gets around the user agent with taps on the tab and arrow keys. The designers of a user agent have decided to place a button for printing a web page as the last button on a toolbar. This button requires six presses of a right arrow key to reach for Carl and is the only button he uses on the toolbar. Using a preferences dialog, Martin is able to configure this toolbar to only show the Print button, reducing the number of presses he must issue with his mouthstick to one.

Success Criterion 2.8.2 (former 4.8.2)

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

Examples 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 particularly 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) :