Re: Jaws 12 works with Google Chrome

  • From: Don Marang <donald.marang@xxxxxxxxx>
  • To: programmingblind@xxxxxxxxxxxxx
  • Date: Tue, 31 May 2011 08:21:56 -0400

Were you using the development channel version from:
http://www.chromium.org/getting-involved/dev-channel
I first made that mistake. Most of the dialogs for installing and managing add-ons are difficult at this point, but using the JAWS cursor in these situations works fine. The web pages I tested worked flawlessly!
I also installed the developer channel on Vinux. It adds the channel to your Software Sources list for easy updates. After updating, I had no luck reading anything with orca. 


*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/31/2011 6:37 AM, Homme, James wrote:

Hi,
Strangely, I fired Chrome up over the weekend with JAWS 12, and I couldn't read 
anything. I'll check again. I was using Vista. Does that matter?

Jim

-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx 
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Sina Bahram
Sent: Sunday, May 29, 2011 1:09 AM
To: jawsscripts@xxxxxxxxxxxxx; programmingblind@xxxxxxxxxxxxx; 
blindwebbers@xxxxxxxxxxxxxxx
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


This e-mail and any attachments to it are confidential and are intended solely 
for use of the individual or entity to whom they are addressed.  If you have 
received this e-mail in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this e-mail without the author's prior permission. 
 The views expressed in this e-mail message do not necessarily represent the 
views of Highmark Inc., its subsidiaries, or affiliates.
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind

Other related posts:

  1. Home
  2. programmingblind
  3. Archive
  4. 05-2011