- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Thu, 10 Mar 2011 11:44:05 -0600
- To: simon.harper@manchester.ac.uk
- Cc: uawg list <w3c-wai-ua@w3.org>
Also, was playing with FF4 RC - the toolbars show/hide in the order in which they are installed. In IE, the toolbars have handles and allow different orders vertically and you can put 2 or more tool bars on one line. At a AAA level the handles would be very useful. On Thu, Mar 10, 2011 at 11:01 AM, Jim Allan <jimallan@tsbvi.edu> wrote: > 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/ >> >> >> > > > > -- > 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 > -- 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
Received on Thursday, 10 March 2011 17:44:47 UTC