Re: jaws and chrome behaving equally badly on 2 machines
toggle quoted messageShow quoted text
Yes, VFO seems to be getting bewildered about a lot of quirks of late. Not knocking them, just stating what I’ve been noticing.
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Stan Holdeman
Sent: Sunday, December 31, 2017 8:50 AM
Subject: Re: jaws and chrome behaving equally badly on 2 machines
For me jaws 18 reads Chrome just fine, but J2018 will not read web Content.
This is before and after many repairs, reinstalls, updates and even move to Windows 10 creator update.
I first installed J2018 in mid-November. It worked fine for about a week then stopped reading web content in Chrome.
VFO tech support seems to be bewildered.
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Ray T. Mahorney via Groups.Io
running jaws 15 on a win7 64 machine and jaws13 on a win7 32 bit machine and chrome seems to behave badly on both. Whenever I try to visit a website regardless Chrome either crashes or does not read screen contents. Chrome behaves nicely with NVDA on both machines but not apparently chrome and JAWS. uninstalling and reinstalling chrome did not help nor did clearing the cashes on both machines. both have adiquit memory to run both chrome and jaws. This is a recent development which has been puzzling me for months. I can't think of anything I've done to cause this equally bad behavior on both machines. What might I be missing?