*Sent:* Sunday, May 29, 2011 1:04 PM
*To:* programmingblind@xxxxxxxxxxxxx
*Subject:* RE: Jaws 12 works with Google Chrome
Now since you guys say that the same scripts used for firefox are
those used in Chrome, then why doesn't the latest 4.0 version of
firefox work with JAWS?
*From:*programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] *On Behalf Of *Stefan
Moisei
*Sent:* Sunday, May 29, 2011 1:03 PM
*To:* programmingblind@xxxxxxxxxxxxx
*Subject:* Re: Jaws 12 works with Google Chrome
That's right. You need a development build to test the latest
accessibility features. See here:
http://www.chromium.org/getting-involved/dev-channel
----- Original Message -----
*From:*Don Marang <mailto:donald.marang@xxxxxxxxx>
*To:*programmingblind@xxxxxxxxxxxxx
<mailto:programmingblind@xxxxxxxxxxxxx>
*Sent:*Sunday, May 29, 2011 4:45 PM
*Subject:*Re: Jaws 12 works with Google Chrome
JAWS 12 certainly does not work with the stable 11.0.696.71
version of Chrome. Is there a specific dev version or nightly
build I should try? Where can I get it?
*Don Marang*
Vinux Software Development Coordinator - vinuxproject.org
<http://www.vinuxproject.org/>
There is just so much stuff in the world that, to me, is devoid of
any real substance, value, and content that I just try to make
sure that I am working on things that matter.
-- Dean Kamen
On 5/29/2011 9:37 AM, Stefan Moisei wrote:
Yeah, I noticed the same thing.
However, at least for me, not all things work correctly yet.
First, some larger edit boxes don't work. You can type in them,
but jaws doesn't read anything. I think this was documented in the
chrome accessibility wiki article.
Second, jaws doesn't read flash objects at all.
Third, sometimes larger pages are not loaded into the virtual
buffer and I have to load the same address again. Refresh doesn't
work, I have to press alt+d and enter.
Finally, some pages are not updated in the virtual buffer. After I
click a link, the page doesn't change for jaws, even though the
title does.
Those happen with google chrome 13.0.772.0 dev-m and jaws 12.0.1158.
Despite these problems, I'm also very excited about chrome's
accessibility improvement and hope it will soon be fully accessible.
----- Original Message ----- From: "Sina Bahram"
<sbahram@xxxxxxxxx> <mailto:sbahram@xxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
<mailto:jawsscripts@xxxxxxxxxxxxx>;
<programmingblind@xxxxxxxxxxxxx>
<mailto:programmingblind@xxxxxxxxxxxxx>;
<blindwebbers@xxxxxxxxxxxxxxx> <mailto:blindwebbers@xxxxxxxxxxxxxxx>
Sent: Sunday, May 29, 2011 8:08 AM
Subject: Jaws 12 works with Google Chrome
Sorry for the cross posting, but as this fundamentally affects, or
at least can, how most of us interact with the web, I thought I'd
share.
I fired up the latest Google chrome, as I do from time to time, to
play around with it, and I noticed that jaws 12 started reading
me the page. First I thought, oh cute, the virtual cursor
recognition finally got smart enough to recognize the chrome
window as
non-static text, but then I said, hmm, that's reading awfully
well, so I hit h and navigated by header, and I went to different
URLs, and they all read correctly.
Further investigation shows that jaws is aliasing chrome to
Firefox. The Firefox scripts, in fact, are what is loaded if you
do an
insert+q.
So, apparently no longer is NVDA the only windows screen reader
that supports chrome.
Good to see, I thought.
Btw, I checked, and sure enough, the line:
chrome=Firefox
appears in the default confignames.ini shipping with jaws.
Would have been nice to know ... just a thought.
Take care,
Sina
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
