QT should be using MSAA if it is an accessible QT app. Since NVDA is working
there should be some MSAA available.
For starters, what happens if you set JAWS's configuration (using
configuration manager) to use Enhanced MSAA? You could also set it to use
MSAA for lists views for good measures.
If you just search for MSAA there are only two settings to toggle.
As a second experiment, try unchecking the Accessibility Driver which you
will have to edit the default configuration to do.
Travis
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx <jawsscripts-bounce@xxxxxxxxxxxxx> On
Behalf Of Peter Torpey
Sent: Wednesday, January 1, 2020 5:56 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Questions about JAWS interacting with QT framework
I recently started playing around with Musescore, a program for creating and
reading musical scores.
The program works very well with the default configuration of NVDA. As one
navigates through a score, NVDA speaks each note name, each note duration,
position in the score, etc.
When I use JAWS 2020, however, JAWS does not speak any of this information.
So I was wondering why this was and figured maybe I could script something
up to make Musescore work with JAWS as it does with NVDA. Below is a
response I got from one of the Musescore developers which references the QT
framework that apparently is sending this info to NVDA. I don't know what
this QT framework is or how/if JAWS can be made to grab information from it.
If anyone has any thoughts or suggestions I would appreciate it.
Here is the response from the Musescore developer:
"We'd love to get MuseScore working with JAWS (and Narrator, and VoiceOver,
and Orca) but so far no luck. If you can help that would be fantastic!
It is sort of true that we use the status bar for thew accessibility text,
but not totally. The same function generates both, but they are customized
differently. At the end of each command that might change the selection, we
generate the status text and the accessibility text. We use the Qt framework
to handle this and most other UI elements. Specifically, we define the score
view to be a QAccessibleWidget, and override the QAccessibleWidget::text
with a value of QAccessible::Name to return the accessibility text.
Everything seems to be working right but somehow NVDA is the only
screenreader that actually reads anything by default. Apparently JAWS will
if transfer keyboard focus elsewhere then back? It's frustrating that we
haven't been able to figure out the problem, and we've been looking at
totally different ways of solving it but I suspect it will turn out to be
some simple one-line change that is what we're missing."
--Pete
__________�
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
__________�
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
