Re: [WebAIM] Using Google Chrome with a screen reader

Hi Aaron,

I was very happy to receive this invitation, and I am happy to say that
Google would most certainly be interested in partaking in the collaboration
of defining the WAI-ARIA exposure. Since I am tightly involved with Google
Chrome and WebKit, please do include me in your weekly call, and any other
discussions you have.

To briefly introduce myself, I have been working with accessibility in
various forms for going on 5 years now, ranging from client-side MSAA
implementations to web accessibility and proper usage of WAI-ARIA. I have
practical, in-depth experience with implementing a variety of MSAA servers
and clients, and on the web side dealing with issues concerning HTML/XHTML,
CSS, JavaScript and more. I have worked primarily with visually impaired in
my professional and academic career (did my thesis on Accessible Educational
Gaming for the visually impaired), but have much experience also working
with solutions for motoric disabilities, hearing impaired, colorblind and
dyslexic users.

Looking forward to getting involved with the working group, and getting to
know all of you!

Sincerely,
Jonas Klink
Software Engineer - Accessibility
Google. Inc.

On 9/5/08, Aaron M Leventhal <aleventh@us.ibm.com> wrote:
>
>
> Hi Jonas,
>
> Would Google be willing to collaborate with the other browser developers in
> defining how WAI-ARIA is properly exposed? We have weekly calls.
>
> Apple, Microsoft, Opera and Mozilla are working together on this. It's
> great to have everyone on board so far, and I hope Google will join this
> industry harmonization effort.
>
> We're working on a doc here:
> http://developer.mozilla.org/en/docs/ARIA_User_Agent_Implementors_Guide
>
> - Aaron
>
>
>
>  From: "Steven Faulkner" <faulkner.steve@gmail.com> To: wai-xtech@w3.org
> Date: 09/05/2008 12:30 PM Subject: Re: [WebAIM] Using Google Chrome with a
> screen reader
> ------------------------------
>
>
>
>
> Hi Jonas
>
> It's good to hear that Google have plans for rapid improvements in the
> accessibility of Google Chrome. Providing a simple user interface is
> definitely a usability improvement that potentially benefits all
> users, but at present for many people with disabilities Google Chrome
> is simply unusable.
>
> Here at TPG we work with many companies that use web browsers as a
> software platform and we have already been contacted by clients who
> want to take advantage of the potential Google Chrome holds for the
> delivery of better performing more robust accessible rich internet
> applications, but will not be able to do so until Google Chrome
> provides the required support.
>
> It would be a real step forward for accessibility on the web if Google
> made a public commitment to make Google Chrome conformant with the
> W3C's User Agent Accessibility Guidelines, and, like the Mozilla
> Foundation, work with users with disabilities and Assistive Technology
> vendors to ensure that Google Chrome is the most accessible browser
> available.
>
>
> with regards
>
> Steve Faulkner
> Technical Director - TPG Europe
> Director - Web Accessibility Tools Consortium
>
> www.paciellogroup.com | www.wat-c.org
> Web Accessibility Toolbar -
> http://www.paciellogroup.com/resources/wat-ie-about.html
>
>
> 2008/9/4 Jonas Klink <klink@google.com>:
> > Google Chrome, our new Open Source browser released on Tuesday, 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, 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. 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
> >>
> >>
> >
>
>
>
> --
> with regards
>
> Steve Faulkner
> Technical Director - TPG Europe
> Director - Web Accessibility Tools Consortium
>
> www.paciellogroup.com | www.wat-c.org
> Web Accessibility Toolbar -
> http://www.paciellogroup.com/resources/wat-ie-about.html
>
>
>
>