Google Chrome, our new Open Source browser released on Tuesday<http://googleblog.blogspot.com/2008/09/fresh-take-on-browser.html>, strives to innovate and drive development on the web. This certainly extends to all of our users, and the issue of accessibility is no different. In the spirit of releasing early and iterating, this version of Chrome has focused on basic support for keyboard navigation and shortcuts<http://www.google.com/support/chrome/bin/answer.py?answer=95743&query=keyboard+shortcuts&topic=&type=>, as well as a clean user interface that is simple for all users to navigate. At the same time, we have laid the foundations in place for exposing the appropriate information through the Windows Accessibility APIs (used by screen readers, etc.), as well as support for WAI-ARIA<http://www.w3.org/WAI/intro/aria>. Users can expect rapid improvements in both of these areas in releases to come. Accessibility is important to us, and we have for some time worked on its implementation. We look forward to releasing this, and making further improvements for our users. Sincerely, Jonas Klink Software Engineer - Accessibility Google Inc. On 9/3/08, Joshue O Connor <joshue.oconnor@cfit.ie> wrote: > > > Hi Steve, > > Thanks for the overview of the somewhat limited accessibility features of > the new browser. I think the under the hood improvements with Chrome are > very impressive and it is a pity that it is let down by it's current > inability to work with screen readers. > > Cheers > > Josh > > > > -- Jonas Klink Software Engineer - Accessibility Google, Inc. Phone: 650.253.8701 Email: klink@google.com This email may be confidential or privileged. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it went to the wrong person. Thanks.
Received on Thursday, 4 September 2008 22:43:33 UTC