It could be
both JAWS and the app. If you have latest JAWS 2018 (or
18.0) build, Calculator results might not be read (or at
least for me and others, it does not) due to the fact that
the app raises a UIA event JAWS doesn’t know about. I
thought this is fixed in build 1802.78 but it apparently
[mailto:email@example.com] On Behalf Of Steve
Sent: Friday, February 23, 2018 10:14 AM
Subject: Re: FW: [win10] Version 1709 and beyond:
screen readers must support uIA notification event in
order to announce various things from apps #ADVISORY
Here's a strange one for you. I posted this before, but it
might have been in a thread in which you weren't interested.
But I bet this will be of interest. It's regarding Calculator.
I have two Windows 10 systems, one generated from version
1603 and up-to-date as of this morning, and another generated
from the version 1709 Fall Creators Update, also up-to-date as
of this morning. On the newer system--the one generated from
the FCU--Calculator does not read results automatically JAWS
Key + Q reports the application name is
Microsoft.WindowsCalculator. On the older system--the one
generated from version 1603--calculation results are read
correctly, but on that system, the application name is
ApplicationFrame.dll. What do you make of that difference--not
just the application name difference, but the screenreader
behavior difference, too?
On 2/23/2018 12:46 PM, Joseph Lee wrote:
First, apologies for mentioning
competition, but I felt it is best to do so given the
overall context. Second, the advisory is deemed major (to
severe for some cases) and is applicable for people running
Windows 10 Fall Creators Update and beyond. The source of
this advisory is a Win10 forum hosted on Groups.IO at https://win10.groups.io/g/win10.