Google Chrome Screen Reader Support update

Posted on Monday, 21 June 2010 by Steve Faulkner

Refer to Google Chrome accessibility update


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:

These screen readers do not yet recognize Chrome’s non-focusable web content (links, form fields and other focusable content is spoken as expected), so you will be unable to enter “browse mode”:

We hope to work with all screen reader developers to resolve any issues so that they can enable full support for Chrome.
The list above is not a comprehensive list of all screen readers, but in the interest of prioritizing support for the greatest number of users, we believe that supporting the screen readers above will have the greatest impact. If external developers are interested in helping to add support for additional screen readers, we would welcome the help.
For more detailed information about the technical design and current status, see the Accessibility Design Document.

About Steve Faulkner

Steven is the Senior Web Accessibility Consultant and Technical Director, TPG Europe. He joined The Paciello Group in 2006 and was previously a Senior Web Accessibility Consultant at vision australia. He is the creator and lead developer of the Web Accessibility Toolbar accessibility testing tool. Steve is a member of several groups, including the W3C HTML Working Group and the W3C Protocols and Formats Working Group. He is an editor of several specifications at the W3C including HTML 5.1, Using WAI-ARIA in HTML and HTML5: Techniques for providing useful text alternatives. He also develops and maintains www.HTML5accessibility.com

Comments

  1. Finally the sleeping giant has woken up!

    Hope others will learn a lesson and think about incorporating Accessibility in their products at the planning stage rather then post-release stage … … after facing user’s anger.

  2. Google had already been working on Chrome accessibility long before the petition…I guess nobody bothered to check out what’s being checked into the Chrome project.

  3. I think people were aware that Google have been working on the accessibility of Google Chrome, The issue is, why is it taking so long? Google certainly has the resources and skills in-house to make chrome usable with ATs, it appears that it has been a lack of will to commit the required resources, as it as not been a priority. From reading the chrome wiki, Google still has no plans to commit resources to chrome supporting AT on linux.

Comments are closed.

Recent Posts

See all posts in the blog archive

I‘d like to take this opportunity to thank you all for your great business and for your flexibility during our contract amendment. Your people are sensational.

Ray Douha, Sr. UI Planner, State of Minnesota