[Accessibility] - Note input in MuseScore 3.5 beta not read

• Jun 14, 2020 - 09:09
Reported version
P0 - Critical
S2 - Critical

When inputting notes in Musescore 3.5 beta, it automatically enters the steptime input mode. When I press arrow keys, NVDA doesn't read anything. Also, note input doesn't read at all, I can only hear midi playback. To enable navigation reading, I have to press n or esc to make it read again. This means blind can't instantly hear what he/she input by screen reader.


Title [Accessibility] - Steptime input in Musescore 3.5 beta not read [Accessibility] - Note input in Musescore 3.5 beta not read

When in drum staff, the drum input mode not only doesn't read, but also doesn't put any note in when pressing any key. When I tried it in Musescore 2.3.2, all drum notes are read and sound. Strange, there's such a big regression between 3.4 and 3.5.


Regression No Yes
Priority P0 - Critical

There was a change so that pressing "N" would actually tell you that you were entering note input mode, but aside from that it shouldn't have changed anything about when or how notes are read. Can you give precise steps to reproduce the problem?

Also regarding drum staves, that sounds unrelated, can you open a new issue and attach the specific score, and again, precise steps to reproduce the problem? Could be that the drumset for the staff in question simply does not have shortcuts defined.

Actually, while it's somewhat erratic, I can confirm that navigation in note input mode does not read notes. So:

1) press "N" to enter note input mode
2) type C D E F to enter four quarter notes (for me, the letters are read as I type them, but not the full note information as in 3.4.2)
3) press Left to move the cursor backwards

Result: nothing is read, not even as you press Left multiple times, or press Right.

So yes, this is a critical regression. Probably the two symptoms - no full information upon typing, but also no reading as you navigate - as related and the same fix would apply to both.

It seems that https://github.com/musescore/MuseScore/pull/6210 fixes this along with the other issues it was originally designed to fix. Here is a build that you can test if you like:


FYI, the other improvements that should have come with 3.5 Beta have to read with editing text, you should hear characters being read as you move the cursor, Also feedback on using articulation shortcuts like Shift+S to toggle staccato. Thanks to Peter Jonas (@shoogle) for this work!

Thank you, this build works very well, normal notes and drumset input all read out. Drumset input can be tried using up/down arrow keys to reach various instruments, and NVDA reads the names correctly. Also, expanding palette becomes smooth, no crash. The only thing is the inspector for hairpins is still not able to read, and this was submitted as a separate issue before.

Status PR created fixed

Fixed in branch 3.x, commit 303bb526af

_fix #306726: Improve status for playback, note input, and normal modes


  • Display mode text for "Normal mode".

  • Avoid screen reader output on entering playback mode so that the
    screen reader does not talk over the music.

Also fixes an accessibility bug in commit 3960396 in PR #6173 that
caused the screen reader to say "note input mode" periodically rather
than just once upon entering that mode. This interfered with the usual
screen reader output for that mode, as reported in #306726._

Title [Accessibility] - Note input in Musescore 3.5 beta not read [Accessibility] - Note input in MuseScore 3.5 beta not read

Fix typo in issue title

Fix version