musescore / musescore/MuseScore

Issues with speech output in percussion 'Customise kit' dialog

Open
#32,789 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accessibility
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

There are a number of non standard and confusing speech issues within the customise kit dialog in the Percussion panel.

STEPS:

  1. Create a score with a drum kit and navigate to that staff. Press Tab several times till you hear percussion, tab twice more to layout and then press down arrow to get to customise Kit. Press enter.
  2. press various arrows, note you don’t seem to be able to navigate and no speech output to know what this is.
  3. Press Tab – you hear “Tree view 56” but no idea what this is or what it is for, e.g. is it a combo box, a spin button and what is its function.
  4. Tab forward a few more times, the rest seem to have some labels, until you get to “None button enter” which makes no sense.
  5. Tab again and hear “Stem direction Combo Box Up collapsed down” Again very confusing are they currently set to up or down?
  6. Tab again and hear “Load Button Enter”, this may make sense if I checked more documentation, but is certainly not obvious from this description of the buttons function.
  7. The following few tabs give the Save As, OK, Cancel, etc all of which weirdly say “button enter” after them, button is OK, but enter is unnecessary as any screen reader user knows to press enter to activate a button it is like telling a person to “click me with mouse”!
  8. Now shift tab back through this dialog and notice that at lots of places it restates the title “customise kit dialog shortcut” before announcing the item.
  9.  Shift Tab back till you get to the place where it announces “Tree View”, press down arrow several times and notice that at no point does this tell you something is selected.  Attempt to select with space and then Tab followed by Shift Tab to confirm speech on this item, it still does not say selected.  There are several list boxes in this dialog with no item showing selected states which makes it very hard to know what is selected when you enter them, especially if you have to use arrows to move to initiate speech.
    
  10. Tab forward to Note head type and notice it says “Combo Box down” after the selection. I thought this was referring to stem, but now think it is saying you press a down arrow to open it? If the screen reader says collapsed or list, etc the user will automatically try arrows, these additional instructions are confusing if it is not clear it is an instruction rather than a description, so either omit or say press down arrow to select. Again tabbing to the next couple the voice also says down after it, a Braille reader might think this has to do with interval direction or stem direction, etc.
Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.7 beta

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Customize kit dialog with Windows 11 and NVDA, following the numbered keyboard-navigation steps in the report. Inspect the dialog's accessibility announcements, roles, labels, selection states, and redundant speech; it is done when each control communicates its purpose and state clearly while navigating by keyboard and screen reader.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
accessibility, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.