RE: Jaws 12 works with Google Chrome

  • From: "Sina Bahram" <sbahram@xxxxxxxxx>
  • To: <programmingblind@xxxxxxxxxxxxx>
  • Date: Tue, 31 May 2011 01:02:19 -0400

Yeh that's odd that it's differing across users, but not surprising with beta 
software and unannounced alpha support from the screen
reader, *smile*.

Take care,
Sina



-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx 
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of inthane
Sent: Tuesday, May 31, 2011 12:35 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Jaws 12 works with Google Chrome

maybe for you, if you actually read the original message, it does read them 
for Sena

inthane
. Moderator, Blind Access Help.
. Owner: Alacorn Computer Enterprises
 "own the might and majesty of an alacorn"
www.alacorncomputer.com
. proprietor: Inthane's Grab Bag
 for blind computer users and Programmers!
http://grabbag.alacorncomputer.com
----- Original Message ----- 
From: "Oriol Gómez" <ogomez.s92@xxxxxxxxx>
To: <programmingblind@xxxxxxxxxxxxx>
Sent: Sunday, May 29, 2011 3:50 AM
Subject: Re: Jaws 12 works with Google Chrome


> The problem with chrome taht I ahve seen is that it does nto read any
> menus or bookmarks or anything.
> So it's still not usable.
>
> On 5/29/11, John G <jglists0@xxxxxxxxx> wrote:
>> I wonder if our beloved Window-Eyes has caught up with the rest of
>> the civilised world in this matter. <smile>
>>
>> At 06:08 29/05/2011, you wrote:
>>>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
>>
>>
> __________
> 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

__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind

Other related posts: