So now that I know the version of QT being used (see note below), how do I
know whether the version on which MuseScore is written is using MSAA or UIA
and what is the best approach once I know the answer? I've never explicitly
dealt with either in a script. Does the JAWS Utility mode give me any help
here or do I have to get into the BX tool?
Thanks.
\
--Pete
-----Original Message-----
From: Peter Torpey <ptorpey00@xxxxxxxxx>
Sent: Wednesday, January 1, 2020 10:24 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: RE: [jawsscripts] Re: Questions about JAWS interacting with QT
framework
Doug,
I don't know what to do with this info, but from virtualizing the Details
tab of the QT5Core.dll properties as you described:
Qt5Core.dll Properties
Ge Details curity GeneDe
Property Value
File description C++ Application Development Framework Type Application
extension File version 5.9.8.0 Product name Qt5 Product version 5.9.8.0
Copyright Copyright (C) 2019 The Qt Company Ltd.
Size 5.56 MB
Date modified 11/8/2019 9:20 AM
Language English (United States)
Original filename Qt5Core.dll
Remove Properties and Personal Information OK Cancel Apply
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx <jawsscripts-bounce@xxxxxxxxxxxxx> On
Behalf Of Doug Lee
Sent: Wednesday, January 1, 2020 10:07 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Questions about JAWS interacting with QT
framework
The QT version might help; should be available in a Details tab if you pull
Properties for Qt5core.dll in this app's program folder via Windows
Explorer. A fairly recent QT update switched completely from MSAA to UIA for
accessibility support, as evidenced by my scripting efforts for the
TeamSpeak client. That client uses QT 5.12.3 according to that method of
checking.
On Wed, Jan 01, 2020 at 04:55:46PM -0700, Peter Torpey wrote:
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.
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
--
Doug Lee, Lead Accessibility Architect
Level Access - over 1,000 organizations trust us to help them achieve and
maintain digital accessibility compliance!
mailto:Doug.Lee@xxxxxxxxxxxxxxx http://www.LevelAccess.com "While they were
saying among themselves it cannot be done, it was done." --Helen Keller
__________o?=
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
