E-mail List Archives
Thread: Re: Using Google Chrome with a screen reader
Number of posts in this thread: 5 (In chronological order)
From: Joshue O Connor
Date: Wed, Sep 03 2008 4:20AM
Subject: Re: Using Google Chrome with a screen reader
No previous message | Next message →
Hi,
Sorry for cross posting.
I just tried to use a beta of Google Chrome with JAWS 9 and Window Eyes
on Win XP. The only output I got from JAWS 9 was tab, tab, as I moved
though a webpage with no ability to browse by headings, jump to form
fields etc. With Window Eyes there was no output at all. Does anyone
know if Google plan to make Chrome play nice with AT?
Cheers
Josh
********************************************************************
NOTICE: The information contained in this email and any attachments
is confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of
the content of it or of any attachment; you are requested to notify
the sender immediately of your receipt of the email and then to
delete it and any attachments from your system.
NCBI endeavours to ensure that emails and any attachments generated
by its staff are free from viruses or other contaminants. However,
it cannot accept any responsibility for any such which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent the views of NCBI
********************************************************************
From: Steven Faulkner
Date: Wed, Sep 03 2008 4:30AM
Subject: Re: Using Google Chrome with a screen reader
← Previous message | Next message →
Hi Josh I have been looking into Google chrome accessibility support,
here is what I have found:
Google chrome accessibility - http://www.paciellogroup.com/blog/?p=92
2008/9/3 Joshue O Connor < = EMAIL ADDRESS REMOVED = >:
> Hi,
>
> Sorry for cross posting.
>
> I just tried to use a beta of Google Chrome with JAWS 9 and Window Eyes
> on Win XP. The only output I got from JAWS 9 was tab, tab, as I moved
> though a webpage with no ability to browse by headings, jump to form
> fields etc. With Window Eyes there was no output at all. Does anyone
> know if Google plan to make Chrome play nice with AT?
>
> Cheers
>
> Josh
>
> ********************************************************************
>
> NOTICE: The information contained in this email and any attachments
> is confidential and may be privileged. If you are not the intended
> recipient you should not use, disclose, distribute or copy any of
> the content of it or of any attachment; you are requested to notify
> the sender immediately of your receipt of the email and then to
> delete it and any attachments from your system.
>
> NCBI endeavours to ensure that emails and any attachments generated
> by its staff are free from viruses or other contaminants. However,
> it cannot accept any responsibility for any such which are
> transmitted. We therefore recommend you scan all attachments.
>
> Please note that the statements and views expressed in this email
> and any attachments are those of the author and do not necessarily
> represent the views of NCBI
>
>
> ********************************************************************
>
>
>
>
From: Joshue O Connor
Date: Wed, Sep 03 2008 4:50AM
Subject: Re: Using Google Chrome with a screen reader
← Previous message | Next message →
Hi DotJay,
> So, it sounds like very few interface elements are exposed through
> accessibility APIs (e.g. MSAA).
Yes. In fact it seems like practically none actually. Unless the release
version /dramatically/ improves it currently looks like a non starter in
accessibility terms.
Cheers
Josh
********************************************************************
NOTICE: The information contained in this email and any attachments
is confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of
the content of it or of any attachment; you are requested to notify
the sender immediately of your receipt of the email and then to
delete it and any attachments from your system.
NCBI endeavours to ensure that emails and any attachments generated
by its staff are free from viruses or other contaminants. However,
it cannot accept any responsibility for any such which are
transmitted. We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email
and any attachments are those of the author and do not necessarily
represent the views of NCBI
********************************************************************
From: Jon Gibbins (dotjay)
Date: Wed, Sep 03 2008 5:00AM
Subject: Re: Using Google Chrome with a screen reader
← Previous message | Next message →
Joshue O Connor wrote:
> I just tried to use a beta of Google Chrome with JAWS 9 and Window Eyes
> on Win XP. The only output I got from JAWS 9 was tab, tab, as I moved
> though a webpage with no ability to browse by headings, jump to form
> fields etc. With Window Eyes there was no output at all. Does anyone
> know if Google plan to make Chrome play nice with AT?
So, it sounds like very few interface elements are exposed through
accessibility APIs (e.g. MSAA).
And just as I'm typing this, Steve Faulkner has just published his
analysis if Google Chrome accessibility:
http://www.paciellogroup.com/blog/?p=92
J
--
dotjay / Jon Gibbins
w: dotjay.co.uk
From: Steven Faulkner
Date: Fri, Sep 05 2008 4:30AM
Subject: Re: Using Google Chrome with a screen reader
← Previous message | No next message
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 < = EMAIL ADDRESS REMOVED = >:
> 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 < = EMAIL ADDRESS REMOVED = > 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: = EMAIL ADDRESS REMOVED =
>
> 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.