- From: Shelley Powers <shelley.just@gmail.com>
- Date: Mon, 22 Mar 2010 19:02:17 -0500
- To: Maciej Stachowiak <mjs@apple.com>
- Cc: "Edward O'Connor" <hober0@gmail.com>, HTMLWG WG <public-html@w3.org>
On Mon, Mar 22, 2010 at 6:44 PM, Maciej Stachowiak <mjs@apple.com> wrote: > > On Mar 22, 2010, at 4:30 PM, Edward O'Connor wrote: > >>> I will be honest, I'm not including this in the proposal. Not to say >>> it couldn't be included, but I hope would follow an experiment I did, >>> first, before adding a pre for ascii art in as option: >>> >>> If you don't have a screen reader installed for testing, I would >>> recommend installing NVDA on Windows, and then start the screen reader >>> and Firefox. >> >> Sorry, this machine doesn't actually have a sound card, and anyway I >> don't have a screen reader installed on it. Perhaps you could describe >> the results of your experiment on the list? Thanks. > > Safari+VoiceOver on Mac will attempt to read the characters inside <pre> > until the user invokes the command to skip the element. > > However, the following slightly modified version will do the right thing, at > least in Safari on Mac OS X: > http://webkit.org/demos/accessible-ascii-art/butterfly.html > > Regards, > Maciej > > But then, there isn't fallback for the reader to understand what the heck is going on. I don't want to debate my change proposal before I submit it, but I think a screen shot of the ASCII art, such as the following provides the art without the gibberish. And a person can always link the ascii art, if for some reason it's absolutely essential to include all the characters. Or they don't have to use figure. http://burningbird.net/graphics/ascii.jpg Shelley
Received on Tuesday, 23 March 2010 00:02:52 UTC