[Accessibility] - Arpeggio not able to span two staves using screen reader

• Oct 24, 2020 - 00:08
Reported version
Ergonomical (UX)
S3 - Major

As part of our project, I'm now trying to enter a score I arranged in 2011 for a tour to Sweden, to test Musescore's accessibility. At measure 3, I want to enter an arpeggio spanning two staves. The manual says the handle should be dragged to the other staff. However, as a blind, I can't do it, even by pressing up arrow for a minute on the arpeggio. The inspector is also not accessible in this symbol since it's a line, not note or other things. So, I hope the future version can implement a command to apply the arpeggio to other staves or voices, by just shift+arrow selecting corresponding notes in different voices/staves. Also, for Musescore, we should invent the code indicating an arpeggio is cross-staff, so that the braille transcription tool can get correct data from Musescore (not Musicxml) to get a correct translation. Now none of the notation software can do this, so I think Musescore can be the first one.

Attachment Size
Jasmine Flower.mscz 10.38 KB


You can make an arpeggio extend to a chord in the same voice in the bottom staff as it is applied to in the top staff. Alt+arrow to the arpeggio, tab to the bottom grab box, then press ctrl+shift+down arrow and the arpeggio will be extended to the other staff in the same voice.

In Ombres you will see I used this to span the arpeggio across 3 staves in m252. In m352 I put the bottom note of the chord in the bottom staff in voice 2 so I could extend the arpeggio from voice 2 of the top staff.

If you confirm you get the proper feedback from NVDA you can close this issue.

Severity S2 - Critical S3 - Major
Type Performance Ergonomical (UX)

Of course, we eventually want to be able to support these "for real". Meanwhile, I can confirm that it's "possible" to extend the arpeggio manually, it's just all but possible to know when you've gotten it to look right. That's not really something we could do anything about, except, again, to fix it for real. But it's certainly worth keeping on the radar.

I suspected NVDA didn't give any feedback when you moved from one end of the arpeggio to the other. The arpeggio has 2 grab boxes. When you move to it the top one is selected. If you want to extend it up (from the bottom staff to the top) you can press ctrl+shift+up arrow. If you want to extend it down, press tab to move to the other grab box and press ctrl+shift+down arrow. I call them grab boxes because people can use the mouse to grab (click) one of the boxes and drag the end by the box to make it look shorter or longer.

It's not correct. When you apply it correctly it still doesn't play back correctly. I'll send you an email with this corrected and we can discuss it there. Note: I mistakenly said you can extend it up with ctrl+shift+up arrow. It's not working though I thought it did at one time. You must apply it to the top staff and use ctrl+shift+down arrow to extend it down.

Thank you Mike. Now this issue can be closed, but I'll open another to let NVDA read arpeggio's (and probably other line objects') handles, so that we can press key on correct things.