[nfbcs] Phrasing Things RE: JAWS and Google Chrome Browser

[Jude DaShiell]

For a very long time I did not try anything with google chrome like the 
pasielo group did.  I read what that group had published first.  When I 
found out about the webinar google was putting on I spent a few hours on 
the phone listening in.  Even after that I didn't necessarily believe 
what I had heard especially since at that time nvda wasn't supported.  
Later I tried out the combination with chromevox first and had no such 
problems as had been reported here.  I take it either some nvda support 
had been added or none was needed.  There are blind people over on the 
nvda list who insist on running google chrome without chromevox and they 
then complain about all the problems they're having even after they know 
perfectly well about chromevox and what chromevox is supposed to do.  I 
find those people very strange and for some odd reason can't get my mind 
around their logic processes.  So yes if I sound slightly frustrated 
with that kind of people you're entirely correct and I have no apologies 
for any of that.

On Tue, 9 Apr 2013, Nicole Torcolini wrote:

> I don't know if it was meant to come across that way, but, to me, that was
> kind of rude. 
> 
> -----Original Message-----
> From: nfbcs [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of Jude DaShiell
> Sent: Tuesday, April 09, 2013 7:55 PM
> To: NFB in Computer Science Mailing List
> Subject: Re: [nfbcs] JAWS and Google Chrome Browser
> 
> You had no business even trying to use google chrome without chromevox.  
> Two years ago google held a webinar and explained to all present that the
> chromevox add-on was where all screen reader support for screen readers will
> be placed for google chrome.  Let's get clear about something else here too.
> The most support chromevox has in it and the most mature support is for
> versions of jaws.  I use nvda at home and will never use jaws at home and I
> don't have any problem running google chrome with chromevox on windows7 at
> home.
> 
> On Mon, 8 Apr 2013, Aaron Cannon wrote:
> 
> > My experience with using Crome with Jaws 13 (just recently upgraded to 
> > 14, so can't comment if things have improved) was so-so to poor.  I 
> > found it less accessible than Firefox.  The browser GUI, such as the 
> > menus and option screens are much more difficult to navigate.  And as 
> > for using it to access the web, I found that it often had a difficult 
> > time communicating changes on the page to Jaws.  For example, when 
> > AJAX updated a portion of the page, or when a section of content was 
> > dynamically loaded, Jaws wouldn't read the new or updated content.
> > This same problem happens once in a while in Firefox as well, but 
> > refreshing the virtual buffer usually solves it.  Sadly, this is not 
> > the case in Crome, and I haven't been able to find any workarounds.
> > 
> > Good luck.
> > 
> > Aaron
> > 
> > _______________________________________________
> > nfbcs mailing list
> > nfbcs at nfbnet.org
> > http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> > To unsubscribe, change your list options or get your account info for
> nfbcs:
> > http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/jdashiel%40shellwor
> > ld.net
> > 
> > 
> 
> ---------------------------------------------------------------------------
> jude <jdashiel at shellworld.net>
> Microsoft, windows is accessible. why do blind people need screen readers?
> 
> 
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/ntorcolini%40wavecable.co
> m
> 
> 
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/jdashiel%40shellworld.net
> 
> 

---------------------------------------------------------------------------
jude <jdashiel at shellworld.net>
Microsoft, windows is accessible. why do blind people need screen readers?