- From: Catherine Laws <claws@us.ibm.com>
- Date: Thu, 17 May 2007 18:17:31 -0500
- To: w3c-wai-ua@w3.org
- Message-ID: <OFDAD4AA21.566177E9-ON862572DE.005DAB26-862572DE.007FF29D@us.ibm.com>
Here are the notes for the guidelines I reviewed. General comment: Checkpoint 8.2 Conform to specifications is too generic to put down as related to any one specific guideline. 1.0 Perceive Visual Information 1.1 Visual information also available in auditory form Current: 1.3, 2.2, 2.3, 2.5, 2.6, 8.2 ckl: I don't think UAAG has any checkpoints that require providing visual information also in auditory form. However, when there is auditory output, there are checkpoints for controlling that output - 2.5, 2.6, 3.2, 4.4, 4.5, 4.7, 4.8, 4.10 1.2 Visual information also available in tactile form Current: 1.3, 2.2, 2.3, 2.5, 2.6, 8.2 ckl: I don't think UAAG has any checkpoints to address this. 1.3 Sufficient brightness for visually presented information (luminance for displays -- illumination for printed) Current: NA ckl: Agree, NA. 1.4 Sufficient contrast between all visual information and its background Current: CP 4.3, CP 4.14, CP 6.9, CP 8.2, CP 10.2, CP 10.3, CP 10.6, CP 11.6 ckl: I say 3.1, 4.3, 4.6, 7.3, 10.2, 10.3 1.5 Any information (other than the color itself) that is presented through color to be also presented in another way that does not rely on color. Current: CP 1.3, CP 8.1, CP 8.2, CP 10.2, CP 10.3, CP 10.6 ckl: 1.3, 3.1, 3.3, 4.3, 4.6, 6.4, 7.3, 10.2, 10.3, 10.6 1.6 Ability to change the colors of information.. Current: CP 4.3, CP 4.14, CP 6.9, CP 8.2, CP 11.6 ckl: 4.3, 7.3, 10.2, 10.3, 11.6 1.7 Text readable with reduced visual accuity Note: Automatically scroll large print text horizontally or vertically on a screen without the need to manually manipulate the source material. Current: CP 4.1, CP 4.14, CP 5.1, CP 5.2, CP 5.3, CP 5.4, CP 6.9, CP 8.2, CP 9.3, CP 10.2, CP 10.6 ckl: 1.3, 3.3, 5.1, 5.2, 5.3, 5.4, 9.3, 9.8, 10.1, 10.2, 10.6, 10.7, 11.5 1.8 Information within viewable range of those of short stature or seated in wheelchairs Current: NA ckl: agree 1.9 Ability to avoid reflective glare current: NA ckl: agree 1.10 Ability to avoid glare from excessive brightness (of material or surrounding) current: NA ckl: agree 1.11 Ability to pause, and re-play information presented using audio, video or animation. Current: CP 4.5, ckl: 2.5, 4.5, 11.5 2.0 Perceive auditory information 2.1 Auditory information also available in visual form current: CP 1.3, CP 2.5, CP 4.6, CP 8.1, CP 8.2 ckl: 1.3, 2.3, 2.5, 2.6, 4.6, 12.1 2.2 Auditory information also available in tactile form Current: CP 1.3, CP 2.5, CP 4.6, CP 8.1, CP 8.2 ckl: I don't think UAAG specifically addresses this. 2.3 Ability to adjust the volume to a suitable level. current: CP 4.7, CP 4.8, CP 4.10 ckl: 4.7, 4.8, 4.10, 11.5 (to control system volume related to input) 2.4 Auditory events, alerts etc, be multi-frequency current: CP 4.11 ckl: 4.4, 4.11, 4.12 Interpret as ability to change pitch 2.5 When vibration is used as a substitute for different auditory events then some need vibration to have different vibration patterns (rather than vibration frequency or strength) current: NA ckl: General UAAG section of guidelines 4. Ensure user control of rendering could cover this but there is no specific guideline. 3.0 Perceive existence and location of actionable components 3.1 Locate and identify all keys and controls via non-visual means without activating them. Note: touch sensitive or very light touch controls located where they will not be touched while tactilely finding keys they must use to operate device. current: CP 6.1, CP 6.2, CP 6.3, CP 6.4, CP 9.5, CP 9.6, CP 9.9, CP 10.4 ckl: 7.4, 9.3, 9.5, 9.6, 9.7, 9.9, 11.1, 11.2, 12.3 Not sure the programmatic guidelines (6.1, 6.2, 6.3, 6.4) help with this, but documentation, navigation mechanisms, and operating system conventions do. 3.2 To have non-actionable elements (logos, decorative details) not look or feel like buttons or controls current: CP 6.1, CP 6.2, CP 6.3, CP 6.4, CP 9.5, CP 9.6, CP 9.9, CP 10.4 ckl: 2.8 discuss no repair text for empty content (indicated by alt="") for purely decorative images, but I don't think UAAG directly specifies this requirement in a guideline. 3.3 Sufficient landmarks to be able to quickly re-find controls tactilely during use. Note: Nibs, groupings, spacing are examples of tactile landmarks. current: NA ckl: 9.9, 9.10, 10.1, 10.4, 10.7 I think checkpoints dealing with structure navigation, outline views, important elements, and where am I in a structure all address this requirements. Plus I think updates related to ARIA will also address this. 3.4 Controls that visually contrast with their surroundings. Note: some benefit from ability to adjust colors of on screen controls current: CP 4.3, CP 4.14, CP 6.9, CP 8.2, CP 10.2, CP 10.3, CP 10.6, CP 11.6 ckl: 4.14, 7.3, 9.2, 9.3, 10.2, 10.3, 11.6 I think guidelines that discuss following OS conventions for rendering controls and showing focus are important. Text color configuration won't help although style sheets can help. 3.5 Controls be in places where they can be easily found with low vision and with no sight. current: CP 6.1, CP 6.2, CP 6.3, CP 6.4, CP 9.5, CP 9.6, CP 9.9, CP 10.4 ckl: 6.5, 6.6, 7.1, 9.1, 9.2, 9.3, 9.4, 9.5, 9.6, 9.7, 9.9, 10.2, 10.5, 10.6, 10.7, 11.5 Checkpoints that deal with focus, navigation, and the current viewport as well as programming interfaces for it. 3.6 Controls within viewable range of people of short stature or seated in wheelchairs. current: NA ckl: agree 3.7 Focus and pointing indicators that are visible with low vision. current: CP 5.1, CP 7.1, CP 7.2, CP 7.3, CP 7.4, CP 9.1, CP 9.2, CP 9.3, CP 10.2, CP 10.6 ckl: 6.5, 6.6, 7.1, 9.1, 9.2, 9.3, 9.4, 9.5, 9.6, 9.7, 9.9, 10.2, 10.5, 10.6, 10.7, 11.5 Checkpoints that deal with focus, navigation, and the current viewport as well as programming interfaces for it. 3.8 Information describing the layout of the operational parts. current: CP 6.1, CP 6.2, CP 6.3, CP 6.4, CP 9.6, CP 9.9, CP 10.4 ckl: Are operational parts controls, or also important structural elements? if so, then the current checkpoints are ok. Cathy Laws Manager - IBM Software Group (SWG) Accessibility Architecture and Development 11501 Burnet Road, Bldg 902 Office 2C016, Austin, Texas 78758 Phone: (512) 838-4595 FAX: (512) 246-8502 E-mail: claws@us.ibm.com, Web: http://www.ibm.com/able Faith is being sure of what we hope for and certain of what we do not see.
Received on Thursday, 17 May 2007 23:17:49 UTC