Well, I wrote to FS and haven't heard anything yet. As it was pointed out
to me, if someone is using the latest Jaws in some kind of accountancy
program, the potential for mis-information is very possible. You wouldn't
want to think a value is £400, when it's actually £40 etc. I hope they
address this soon. Best steve.
-----Original Message-----
From: Soronel Haetir
Sent: Friday, May 11, 2018 6:06 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Jaws 2018 Accessibility driver
And note that if you have some other screen reader set to start
(including prior versions of jaws) you will likely run into problems.
At least with conflicting versions of jaws it should detect that and
clear the startup option for the other version.
On 5/11/18, Soronel Haetir <soronel.haetir@xxxxxxxxx> wrote:
It's something that was added in the most recent jaws update you can
change it in settings center (jaws+6), then ctrl+shift+d to bring up
the default configuration (this setting can only be set on a global
basis). In the search box type "driver" and it is the only match.
The setting description is:
The accessibility driver is a system level driver installed by our
software that has been used for many years to provide screen
information to JAWS. This information is known as the Off Screen Model
(OSM) and is used primarily by review cursors like the JAWS Cursor and
Invisible Cursor as well as by JAWS scripts. As Windows 10
increasingly uses different methods of displaying information, this
legacy accessibility driver no longer works in many cases.
Clearing this check box configures JAWS to use new API Accessibility
Monitor technology we developed in order to help overcome the missing
information previously obtained from the Accessibility Driver.
This check box is selected by default.
On 5/11/18, Jonathan Cohn <jon.c.cohn@xxxxxxxxx> wrote:
Hello,
I am not familiar with this driver and how to control it. Can you show
some
links?
Thanks,
Jonathan
On May 10, 2018, at 4:05 PM, Steve Spamer <stevespamer68@xxxxxxxxx>
wrote:
Hi folks. Ok, so with the new Windows update and Jaws new accessibility
driver comes some frustrating issues.
I have the situation where 1 program works with the accessibility driver
enabled, and another where this driver needs to be disabled. Both
programs
show ghost text that only increases the more a program is used.
So, you open a program, text changes in that window and Jaws can still
read
the old text, even though it is not visible. This is the same behaviour
in
both programs, but with the opposite requirements of the accessibility
driver. This is directly affected by the latest Windows update in 1 of
the
programs that was previously unaffected.
So, my questions are anyone else experienced this? and is there any
reliable
avenue for reporting this to FS?, as previously reporting stuff has been
a
poiintless exercise. ThX steve.
Follow me on Twitter: @stevesax123
Visit the samplitude Access website. Jaws scripts for pro recording with
Samplitude in Windows: www.samplitudeaccess.org.uk
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
--
Soronel Haetir
soronel.haetir@xxxxxxxxx