Hello! I am curious, you say you are using NVDA, but with which version of MuseScore? Right now NVDA really doesn't work well at all with MuseScore due to a conflict between it and the Qt libraries we use. Are you saying you are able to hear other text, but not tempo? That's not what I find. For me, with the current version of MuseScore, nothing in the score is read as I navigate, unless I move the mouse. But when I move the mouse, it does read the tempo.
Can you explain more about how you are using MuseScore with NVDA?
The next version of Qt due out later this week should allow us to make the next version of MuseScore (3.3) work extremely well with NVDA. We may be able to provide a build for testing purposes very soon.
I notice that while tempo markings will read for me in my development builds, the note symbols (the quarter note, etc) do not. So I have added code to fix this, in https://github.com/musescore/MuseScore/pull/5270. So when this is merged, and we are able to switch to Qt 5.12.5, all should be well.
_fix #293971: tempo markings do not read the note symbols
Screenreaders do not generally know how to read music symbols,
so we need to provide our own "translations".
I had added the makeReadable() function for this,
but it only handled accidentals.
I have now added added code to handle all the "common" symbols
from the Special Characters palette.
To avoid code duplication, I moved the definition of the list
from textpalette.cpp to the Sym class._
Comments
Hello! I am curious, you say you are using NVDA, but with which version of MuseScore? Right now NVDA really doesn't work well at all with MuseScore due to a conflict between it and the Qt libraries we use. Are you saying you are able to hear other text, but not tempo? That's not what I find. For me, with the current version of MuseScore, nothing in the score is read as I navigate, unless I move the mouse. But when I move the mouse, it does read the tempo.
Can you explain more about how you are using MuseScore with NVDA?
The next version of Qt due out later this week should allow us to make the next version of MuseScore (3.3) work extremely well with NVDA. We may be able to provide a build for testing purposes very soon.
I notice that while tempo markings will read for me in my development builds, the note symbols (the quarter note, etc) do not. So I have added code to fix this, in https://github.com/musescore/MuseScore/pull/5270. So when this is merged, and we are able to switch to Qt 5.12.5, all should be well.
Fixed in branch master, commit 903d723076
_fix #293971: tempo markings do not read the note symbols
Screenreaders do not generally know how to read music symbols,
so we need to provide our own "translations".
I had added the makeReadable() function for this,
but it only handled accidentals.
I have now added added code to handle all the "common" symbols
from the Special Characters palette.
To avoid code duplication, I moved the definition of the list
from textpalette.cpp to the Sym class._
Automatically closed -- issue fixed for 2 weeks with no activity.