[nfbcs] JAWS and Google Chrome Browser

[Jude DaShiell]

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%40shellworld.net
> 
> 

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