musescore / musescore/MuseScore
Screen Reader does not report direction when items are flipped.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Accessibility issue (e.g. for keyboard-only or screen reader users)
Description with steps to reproduce
In version 4.6 a number of keys now announce their function when pressed. Pressing X to flip an item now results in speech feedback that says "flipped direction". But this does not tell the user whether the item was flipped up or down, e.g. whether the stem is now up or down or the item is now above or below the staff. There is also no other way to find this information out.
Ideally key presses should always announce the action that has taken place. In this instance "flipped Up", or "flipped down".
Supporting files, videos and screenshots
N/A
In which versions of MuseScore Studio is this issue present?
4.6.3
Regression
I was unable to check
Operating system
windows 11 with NVDA
Additional context
No response
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
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.
Research direction
Reproduce the issue in MuseScore Studio 4.6.3 on Windows 11 with NVDA by pressing X to flip an item. Trace the screen-reader feedback for that key action; done means the announcement identifies whether the item was flipped up or down.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- accessibility, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100