I guess not all betas are created equal! Sorry you had so much trouble with
that.
--Pete
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx <jawsscripts-bounce@xxxxxxxxxxxxx> On
Behalf Of Doug Lee
Sent: Thursday, January 2, 2020 2:40 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: QT framework and MuseScore
I'll probably have to try again with the non-beta sometime. The beta will
not start at all now; nothing happens, even after I tried deleting its .ini
file from %APPDATA%\MuseScore.
On Thu, Jan 02, 2020 at 02:35:54PM -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.
Doug,
Here is the documentation for using MuseScore 3 with a screen reader:
https://musescore.org/en/handbook/3/accessibility
As I remembered, it seems like one should just be able to start using the
program since, after dismissing the "Quick Start" menu by hitting escape,
the program opens with a blank score. From there I just hit "N" to get into
note entry mode and start typing notes. Then arrow keys will move between
notes and alt+arrow between elements such as notes, key signatures, etc.
NVDA speaks all of this while JAWS does not.
Hope that helps. You might want to at least try NVDA just to see how nice
the experience is! Don't know if the problems you are seeing is just
because it is a beta.
--pete
-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx <jawsscripts-bounce@xxxxxxxxxxxxx> On
Behalf Of Doug Lee
Sent: Thursday, January 2, 2020 2:12 PM
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: QT framework and MuseScore
Well my experience so far is a bit problematic:
I downloaded the beta, figuring that would be the best version to use while
working with developers.
I installed with default settings and launched, but all I saw was a single
window with no MSAA or UIA.
Per your directions from earlier in this thread, I tried pressing Esc a few
times, but with no effect. I then typed Alt+F4, and this closed the current
window and left me in a MuseScore Startup window.
I again tried Esc a few times, then typed Alt+F4 again. The application
closed.
I then tried running the application from both the Desktop window and the
Start screen programs entry, but nothing happens; the app will not launch
and there is no error message.
On Thu, Jan 02, 2020 at 02:06:43PM -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.
Doug,
Here are two more replies from one of the MuseScore developers that might be
helpul.
First, in response to my reply about various ways JAWS scripts can find
info:
"This is great information, thanks! Seems like it should be possible to get
this working, then. For instance, the info in the status bar is, while not
ideal, better than nothing, so if you knew how to find the status bar and
read when it changed, that's something right there. Does the JAWS tool you
have see the status bar? Should show as a standard status bar type of
widget. We don't deal with Windows directly, everything goes through Qt,
which is what enables us to be cross platform. So I can tell you Qt object
names etc, maybe they relate in some way you can use? Or maybe unstead of
reading the status bar, you can access the scoreview widget directly and
grab that accessible text we are placing there. One of the names you could
look for, if you have a way of finding this, is "Ms::ScoreView"."
Comment from Pete: At a quick glance using the JAWS script utility mode I
didn't see the windows that he describes, but I'll take another closer look.
I don't know if I
can use the JAWS GetWindowClass() and other functions to do this or if I
have to use some special MSAA or UIA constructs.
The second comment is about why they use the version of QT that they do:
"We do currently use 5.9.8, although we briefly flirted with using 5.12.5,
and I recall that the MSAA to UIA change was one of the reasons we wanted
to. 5.12.5 seems to work better for accessibility in some ways but led to
problems elsewhere, so we rolled back. If it helps, I'm also happy to try to
make sure we provide a 5.12.5-based build for accessibility purposes."
Comment from Pete: Again, depending on how JAWS can access this information
I don't know whether it is worth asking them to put together a version of
MuseScore based on the later version of QT or not. Looks like they are
willing to work with us though, so that is always good news!
Anyway, let me know your thoughts since I think you have much more
experience in this arena than I do.
Thanks again.
--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
--
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
