- From: Sylvie Duchateau <sylvie.duchateau@snv.jussieu.fr>
- Date: Fri, 23 Jul 2010 12:54:09 +0200
- To: Shawn Henry <shawn@w3.org>
- Cc: "EOWG (E-mail)" <w3c-wai-eo@w3.org>
Hello Shawn, Your proposal seems good to me. As far as the second bullet is concerned, what about also talking about users who are deaf blind (they are mentionned in Understanding WCAG 2.0 and often forgotten elsewhere),b ut they can only rely on braille display (no access to synthetic speech). This second bullet could be: - Users who are blind and deaf blind use a dynamic braille display to get information from the web page. In the next bullet, I wonder if users with cognitive disabilities only use screen readers? I think there are possibilities to have software reading text that is selected with the mouse or copied and pasted in the clipboard. So I suggest for this bullet: - Users who have a cognitive impairment that makes it difficult or impossible to read, and have text read by speech synthesis when they select it with the mouse or copy it to the clipboard. Best Sylvie Sylvie Duchateau Association BrailleNet Tél.: +33(0] 1 44 27 26 25 Fax : +33 (0) 1 44 27 34 49 Web : http://www.accessiweb.org Le 22/07/2010 22:36, Shawn Henry a écrit : > Dear EOWG, > > I've just typed up our comments from a recent teleconference > discussion[1] of "HTML5: Techniques for providing useful text > alternatives, Working Draft 24 June 2010"[2]. I looked at one point > more carefully and have ideas *for your review and comment*. > > Currently under "Examples of scenarios where users benefit from text > alternatives for images" at > http://www.w3.org/TR/2010/WD-html-alt-techniques-20100624/#example-benefits > is listed: > - They have a very slow connection. - They have a vision impairment > and use text to speech software. - They have a cognitive impairment > and use text to speech software. - They are using a text-only browser. > - They are listening to the page being read out by a voice Web browser. > > We had already commented that this needs more explanation for people > who are not aware, for example, of screen reader use. Below is an > additional draft suggestion for an edit of that list and its intro. > > " > Examples of when people need text alternatives for images: > - Users who are blind or have a visual impairment and use a screen > reader that reads aloud the information from the web page (text to > speech software). [link to section in new How People with Disabilities > Use the Web once its done.] > - Users who are blind and use a dynamic braille display to get > information from the web page. - Users who have a cognitive impairment > that makes is difficult or impossible to read, and use a screen reader. > - Users who have a slow connection and turn off images to speed download. > - Users who turn off images to decrease bandwidth use in order to > lower their Internet usage fees. > - Users with a text-only browser. - Users listening to the page being > read out by a voice browser, for example, as they drive or otherwise > cannot read the web page. > > There are many benefits for web site developers and owners to include > text alternatives for images as well; for example, it improves search > engine optimization (SEO) because the text alternatives are available > to search engines, whereas images themselves basically are not. > > [could link <a > href="http://www.w3.org/WAI/bcase/fin.html#seo">improves search engine > optimization (SEO)</a>] > " > > Please reply with comments on the above draft idea. > > Thanks, > ~Shawn > > > > [1] Minutes from the EOWG teleconference are at > http://www.w3.org/2010/07/02-eo-minutes#item01 > Please keep in mind that these are rough minutes and may not reflect > what was actually said. > > [2] http://www.w3.org/TR/2010/WD-html-alt-techniques-20100624/ > > > > > ----- > Shawn Lawton Henry > W3C Web Accessibility Initiative (WAI) > e-mail: shawn@w3.org > phone: +1.617.395.7664 > about: http://www.w3.org/People/Shawn/ > > > > >
Received on Friday, 23 July 2010 10:52:10 UTC