- From: Shelley Powers <shelley.just@gmail.com>
- Date: Mon, 22 Mar 2010 19:41:22 -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 7:37 PM, Maciej Stachowiak <mjs@apple.com> wrote: > > On Mar 22, 2010, at 4:44 PM, Maciej Stachowiak 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 > > Here is a version of the test case that uses the <figure> element to give a > superior accessibility experience: > http://webkit.org/demos/accessible-ascii-art/butterfly-figure.html > > At least on OS X, it won't read the caption text twice to screen reader > users. > > (Yes, this is a completely correct use of role=img according to ARIA.) > > Regards, > Maciej > > Perhaps you need to file a bug to provide an accessible alternative in place of the warning currently associated with the pre element. Shelley
Received on Tuesday, 23 March 2010 00:41:55 UTC