Update appears to have broken Musescore accessibility with NVDA


Quentin Christensen
 

One I don't think I saw mentioned - after you updated NVDA, had you restarted the PC?  We often see random issues in between updating NVDA (or other software) and restarting (not just shutting down) the PC.

After that, if you can pinpoint a specific issue, and especially if you can try with a portable copy of NVDA 2020.4 to confirm it is different in the newer version, please do write up an issue on: https://github.com/nvaccess/nvda/issues

Kind regards

Quentin.

On Fri, Jul 23, 2021 at 12:43 PM Brian Vogel <britechguy@...> wrote:
On Thu, Jul 22, 2021 at 09:52 PM, Jujube wrote:
I have not checked but this could also be a Musescore issue... both
parties may be at fault but I have no idea...
-
I agree, and it could be Windows factors.  The fun of the process of elimination begins!
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 



--
Quentin Christensen
Training and Support Manager


 

On Thu, Jul 22, 2021 at 09:52 PM, Jujube wrote:
I have not checked but this could also be a Musescore issue... both
parties may be at fault but I have no idea...
-
I agree, and it could be Windows factors.  The fun of the process of elimination begins!
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Jujube
 

I have not checked but this could also be a Musescore issue... both
parties may be at fault but I have no idea...

On 7/22/21, Brian Vogel <britechguy@gmail.com> wrote:
Christopher,

Have you tried uninstalling and immediately reinstalling NVDA 2021.1 with a
fresh copy of the installer?  There are several directions one could go
first but, to me, this is one of the easier ones before doing others.

--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

~ Liza Minnelli






 

Christopher,

Have you tried uninstalling and immediately reinstalling NVDA 2021.1 with a fresh copy of the installer?  There are several directions one could go first but, to me, this is one of the easier ones before doing others.

--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Christopher Bartlett
 

You are correct, 21H1, not insider build.  I'm no longer one of those folk who want to be on the bleeding edge, considering this machine is my professional, and music production hobby machine.

CWB


On Thu, Jul 22, 2021 at 6:45 PM Brian Vogel <britechguy@...> wrote:
On Thu, Jul 22, 2021 at 07:40 PM, Christopher Bartlett wrote:
21H2
-
I presume you mean 21H1, but for the sake of complete clarity.  If you're on an insider build, that adds complications.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 



--
Christopher Bartlett


 

On Thu, Jul 22, 2021 at 07:40 PM, Christopher Bartlett wrote:
21H2
-
I presume you mean 21H1, but for the sake of complete clarity.  If you're on an insider build, that adds complications.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Yep.  Discipline.  Accountability.  Joy.  Fun.  Responsibility.

That's what life is about.  And in that order.

        ~ Liza Minnelli

 


Christopher Bartlett
 

To be clear, I know how to edit text and tempo markings in MuseScore, and how to set them up.  What I was experiencing was that the dialogue described above does not appear for me: NVDA 2021.1 win 10 21H2 and MuseScore 3.62.  I should have put those in the first message.

CWB


On Thu, Jul 22, 2021 at 10:57 AM Jujube <ellaxyu@...> wrote:
Oh wow I will have to check that. I also use Musescore a bit but I
have not opened it as of late. I know NVDA has some of the best
support for Musescore and I have to admit that it was certainly a
factor in choosing it as my main screen reader so yeah...

On 7/22/21, Christopher Bartlett <themusicalbrewer@...> wrote:
> This may not affect a lot of people, but I went to edit a musical score
> this morning, and I had lost access to most of my controls.  I know that
> the Musescore folk have been doing a lot of accessibility-focused work, so
> I was a little surprised.  I'll also be reporting this on their forums.
> (fora?)
>
> Christopher Bartlett
> p.s.  Example, when attempting to edit a tempo marking, a dialogue is
> supposed to appear, allowing you to change the BPM, and the note length
> that forms the beat.  After updating to 2021.1, that dialogue may be
> visible, I don't know, but NVDA doesn't appear to see it, either in normal
> mode, nor even as an object in object navigation mode.
>
>
> --
> Christopher Bartlett
>
>
>
>
>
>







--
Christopher Bartlett


Jujube
 

Oh wow I will have to check that. I also use Musescore a bit but I
have not opened it as of late. I know NVDA has some of the best
support for Musescore and I have to admit that it was certainly a
factor in choosing it as my main screen reader so yeah...

On 7/22/21, Christopher Bartlett <themusicalbrewer@gmail.com> wrote:
This may not affect a lot of people, but I went to edit a musical score
this morning, and I had lost access to most of my controls. I know that
the Musescore folk have been doing a lot of accessibility-focused work, so
I was a little surprised. I'll also be reporting this on their forums.
(fora?)

Christopher Bartlett
p.s. Example, when attempting to edit a tempo marking, a dialogue is
supposed to appear, allowing you to change the BPM, and the note length
that forms the beat. After updating to 2021.1, that dialogue may be
visible, I don't know, but NVDA doesn't appear to see it, either in normal
mode, nor even as an object in object navigation mode.


--
Christopher Bartlett






umut korkmaz
 

Hi Christopher,

I sent you information in the first two messages.

I am using nvda latest version and musescore latest version. I don't have the problems you describe.

Regards,

Umut KORKMAZ

 

Windows 10 için Posta ile gönderildi

 

Kimden: Christopher Bartlett
Gönderilme: 22 Temmuz 2021 Perşembe 18:33
Kime: nvda@nvda.groups.io
Konu: [nvda] Update appears to have broken Musescore accessibility with NVDA

 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

 

Christopher Bartlett

p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


 

--

Christopher Bartlett

 


umut korkmaz
 

You can specify the Tempo (BPM) value of our work in the New score wizard at first; If we want, we can add it to the size of our work later.

Now let's first add the New tempo value to our work:

In our example, let's assume that the first 8 measures have a tempo value of 120, and from the 9th measure a value of 75 tempo.

We make sure that we are at the beginning of the first measure by using the Right and Left arrow keys in normal or note writing mode. We can also make sure that we are in the first dimension by opening the search field with CTRL+F and typing 1 and pressing enter.

By pressing ALT+Shift+T, we come to the Tempo writing area.

We find the number 80 after the equal sign with the right arrow and delete it with the del key, and write our new value, the value 120 in our example. and exit with the escape key.

When we switch to note-writing mode with the N key and hover over the first measure:

Pause Measure Measure 1 Beat 1 Tempo Quarter note (crotchet) stem up = 120

NVDA will voice the phrase to us and we'll make sure our value is added.

Again, regardless of the mode, come to the beginning of the 9th measure and open the tempo writing area with ALT+Shift+T; By deleting the digits after the equals, we enter the value 75 this time and exit with the escape key.

When we switch to the note-writing mode with N and come to the beginning of the 9th measure; NVDA tells us this time:

Pause Measure Measure 9 Beat 1 Tempo Quarter note (crotchet) stem up = 75

and we will make sure that the transaction is successful.

In this case: The first eight measures will play at 120 BPM, and the 9th measure and beyond will play at a tempo of 75 BPM.

If we wish, we can add the tempo values ​​by coming to the beginning of the measures we want after we have written our piece, or we can add the tempo values ​​to the beginning of the measures we want first, and then write our note.

We do not need to press enter after opening the typing area with ALT+Shift+T and typing the value.

After typing the value, we may need to press the escape key more than once.

 

Windows 10 için Posta ile gönderildi

 

Kimden: Christopher Bartlett
Gönderilme: 22 Temmuz 2021 Perşembe 18:33
Kime: nvda@nvda.groups.io
Konu: [nvda] Update appears to have broken Musescore accessibility with NVDA

 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

 

Christopher Bartlett

p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


 

--

Christopher Bartlett

 


umut korkmaz
 

We can continue our work with a different tempo number than the one we started in a piece. Let's assume that the first 16 measures in our work are 4/4 (four quarters), and the next four measures are 9/8 (nine eights).

1. We write down our first 16 measurements.

2. When we reach the 17th measure, we press the letter n to make sure that we are in step-by-step note entry mode.

3. Press Shift+F9 to open the main palette window.

4. In the tree view, we find the option Numbers with the down arrow key.

5. Press the Shift+tab keys once, select the 9/8 procedure number from the list that comes up with the arrow keys and press the enter key.

Now, we can see that the first 16 meters of our work have the number of 4/4, and from the 17th measure, the number of 9/8.

Let's say we want to go back to the 4/4 procedure number after the 33rd measure. In this case, it will be sufficient to repeat the above operations and this time select the 4/4 option from the list and press enter.

We can also add a measure that is not in the size list.

For this:

Again, in the measurement numbers window, when you type 5 in the first writing field and 8 in the second writing field, then find the add button with the tab key and press the enter key, five octal procedure numbers are added to the list.

However, the procedure numbers added later cannot be read by NVDA yet.

 

Windows 10 için Posta ile gönderildi

 

Kimden: Christopher Bartlett
Gönderilme: 22 Temmuz 2021 Perşembe 18:33
Kime: nvda@nvda.groups.io
Konu: [nvda] Update appears to have broken Musescore accessibility with NVDA

 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

 

Christopher Bartlett

p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


 

--

Christopher Bartlett

 


Christopher Bartlett
 

This may not affect a lot of people, but I went to edit a musical score this morning, and I had lost access to most of my controls.  I know that the Musescore folk have been doing a lot of accessibility-focused work, so I was a little surprised.  I'll also be reporting this on their forums.  (fora?)

Christopher Bartlett
p.s.  Example, when attempting to edit a tempo marking, a dialogue is supposed to appear, allowing you to change the BPM, and the note length that forms the beat.  After updating to 2021.1, that dialogue may be visible, I don't know, but NVDA doesn't appear to see it, either in normal mode, nor even as an object in object navigation mode.


--
Christopher Bartlett