- From: Doug Schepers <schepers@w3.org>
- Date: Thu, 15 Aug 2013 23:36:20 +0000
- To: James Craig <jcraig@apple.com>
- CC: Charles McCathie Nevile <chaals@yandex-team.ru>, "public-html-a11y@w3.org Force" <public-html-a11y@w3.org>, Jeanne Spellman <jeanne@w3.org>, Jan Richards <jrichards@ocadu.ca>
Hi, folks– On 8/15/13 6:26 PM, James Craig wrote: > On Aug 14, 2013, at 10:30 AM, Charles McCathie Nevile wrote: >> On Thu, 15 Aug 2013 02:22:00 +0400, James Craig wrote: >>> On Aug 13, 2013, at 9:31 PM, Charles McCathie Nevilewrote: >>> >>>> In the case of SVG we currently have a disconnect between >>>> theory and reality. Although my text on SVG accessibility is >>>> (after more than a decade) pretty solid on how to make the DOM >>>> accessible, in practice I believe that is only useful for the >>>> relatively small proportion of users who have VoiceOver. >> >>> Doug Schepers says this works pretty well with NVDA, too. Maybe >>> JAWS? >> >> Which browser? (I am very glad to hear this, by the way. I just >> haven't tested in a while, and last I did the results were that >> accessibility was very "limited"). > > I think he was using Firefox during his OWC preso last month. Not > sure. I was using Chrome+ChromeVox during that presentation, but have also used Firefox+FireVox in past presentations. I don't have NVDA, because I don't have a Windows machine. But I met briefly with a set of people (Glenda Sims, Estelle Weyl, Katie Haritos-Shea, and Denis Boudreau) who did some basic SVG-in-HTML testing with multiple browsers + NVDA/JAWS/VoiceOver, with generally positive results on reading SVG <title> elements. We didn't record the results, and I didn't examine the tests in detail, so I won't speak to the robustness of this testing, but anecdoteally, they all seemed to behave reasonably (the UAs, not the people :P). Again, this is why we need comprehensive testing... the plural of "anecdote" is not "data". Regards- -Doug
Received on Friday, 16 August 2013 13:49:13 UTC