Following last weeks post about Google Chrome accessibility which was prompted by The Google Chrome Screen Reader Accessibility Petition created by Alex Hiironen, new information about Google Chrome screen reader support has been added to the Google Chrome (Chromium) wiki:
Supported Screen Readers
The latest versions of these screen readers have partial support for Chrome now:
System Access to Go (Windows)
VoiceOver (Mac OS X)
These [...]
Here at TPG we have been working on a new tool to inspect elements on a web page and be able to view the HTML code, ARIA attributes (if any) and the information being conveyed by the browser to accessibility APIs, all in one neatish interface. We have given it the catchy moniker “AViewer” and a [...]
Testing of the latest builds of the major Windows browsers indicates Google Chrome’s ARIA role support improving, 18 of 47 roles are now correctly mapped to MSAA roles. There has been no change in Opera or IE support and only minimal improvement in Safari/Webkit support. There has been a minor regression in Firefox support in the [...]
When Google first released Chrome back in September 2008, I carried out a quick and dirty accessibility analysis of it. With the release of Google chrome 2.0 I though it worthwhile to have another look to see what improvements have been made. While there has been progress, for many users with disabilities, Google Chrome is [...]
For the roles defined in WAI-ARIA it is expected that browsers expose the role values via an accessibility API, on the Windows platform the information is usually exposed using the Microsoft Active Accessibility (MSAA) Application Programming Interface (API). Use of an Accessibility API such as MSAA means that Assistive Technology can access the role information [...]