- From: Ian Pouncey <w3c@ipouncey.co.uk>
- Date: Fri, 21 Oct 2011 13:34:20 +0100
- To: w3c-wai-eo@w3.org
I can't really comment on the technical accuracy of much of this document, but other review notes follow. Ian. --- # Media Accessibility User Requirements W3C Editor's Draft 21 September 2011 http://www.w3.org/WAI/PF/media-a11y-reqs/ ## General comments - [2] Unnecessarily convoluted use of language, for example 'information presented temporarily' in 2.2. 3.x sections used clearer language than 2.x. - [3] It became uncomfortable to read the last part of each 3.x section, with so much bold text. ## 2.1 Blindness - [2] 'People who are blind cannot access information if it is presented only in the visual mode' -> only true if the definition of blind is having no usable vision, a definition that does not apply to most people who are registered blind. Following section corrects this to some extent, but the difference should be explained here. - [2] 'people who are blind use a screen reader and/or refreshable braille display' -> braille displays work with screen readers, the 'or' makes no sense. 'people who are blind use a screen reader and optionally a refreshable braille display'. ## 2.2 Low vision - [3] 'Glare caused by excessive scattering in the eye can be a significant problem, especially for very bright content or surroundings' -> medical information. 'Excessive white space can cause glare, a significant problem, especially for very bright content or surroundings'. ## 2.7 Dexterity/mobility impairment - [1] 'People with physical disabilities such as dexterity' -> I don't think 'dexterity' counts as a disability. A lack of it, maybe. ## 3.2 - [2] 'synchronisation points with the video' -> struggling to parse this sentence, should this be 'synchronisation points within the video'? ## 3.6 Captioning - [3] 'by associating different colors to different speakers' -> is the continued use of colour a technique that should be encouraged? If not refer back to 2.3: Atypical color perception ## 3.7 Enhanced captions/subtitles - [3] 'This can be realised through inclusion of <a> elements or buttons into timed text cues' -> <a> but not <button>, be consistent if referring to HTML elements.
Received on Friday, 21 October 2011 12:34:48 UTC