_fix #293229, fix #66961: incorrect screenreader feedback on score change
In AccessibleScoreView::text() where we should be returning the name of the score,
we were returning "???" with a "TODO" that shows an attempt to get the name() of the score.
It didn't work because we really need to get title().
In addition, the previous-score command was not working correctly,
instead getting the next score.
Combined with the lack of screenreader feedback
this made it difficult to track which score you are editing.
The fix was just a matter of changing "1" to "-1" in the call to changeScore()._
Comments
Relates to #277496: [EPIC] Accessibility issues/suggestions
https://github.com/musescore/MuseScore/pull/5221
New PR https://github.com/musescore/MuseScore/pull/5325
Fixed in branch master, commit c004f199fa
_fix #293229, fix #66961: incorrect screenreader feedback on score change
In AccessibleScoreView::text() where we should be returning the name of the score,
we were returning "???" with a "TODO" that shows an attempt to get the name() of the score.
It didn't work because we really need to get title().
In addition, the previous-score command was not working correctly,
instead getting the next score.
Combined with the lack of screenreader feedback
this made it difficult to track which score you are editing.
The fix was just a matter of changing "1" to "-1" in the call to changeScore()._
Fixed in branch master, commit 5fa3c1c04a
_Merge pull request #5325 from MarcSabatella/293329-read-tab
fix #293229, fix #66961: incorrect screenreader feedback on score change_
Automatically closed -- issue fixed for 2 weeks with no activity.