musescore / musescore/MuseScore
Poor Speech output with JAWS Screen Reader
@DmitryArefiev is already working on this.
Since Nov 28, 2023.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Bug description
When editing a score with NVDA, the score is read accurately, for example: Note C 5 crotchet, , bar 1 beat 1 staccato above staccato above
(Note the double comma and the repetition of the articulation)
However, with JAWS, the output is:
Segment, bar 1 beat 1, chord automatic,, Note C 5 crotchet, bar 1 beat 1
Expected behaviour: The output should be the same in all screen readers and in the order of most important info first, e.g. note name, duration, bar, etc (as it is in NVDA)
Actual output: Note the verbose mention of segment, chord automatic, and so on, and the omission of the articulation.
The omissions in JAWS include some very important items such as not reading accidentals.
Steps to reproduce
- Start Jaws screen reader.
- Open any score with a variety of notes, accidentals, articulations, chord symbols, lyrics, expression and other elements.
- Use right arrow to move along the score hearing what the screen reader says for each note.
- Quit Jaws and start NVDA.
- Repeat the same test to compare what the output should sound like.
Screenshots/Screen recordings
No response
MuseScore Version
4.1.1.232071203
Regression
I don't know
Operating system
Windows 10 & 11
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.