musescore / musescore/MuseScore

Instrument Settings don't read with NVDA

Open
#25,404 5 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

accessibility P2
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
  1. Set up a score with an instrument, say a flute.
  2. Select Instruments radio button from the toolbar: "Palettes, Instruments, Properties"
  3. Tab and Arrow to the list of instruments and press Space on "Flute". (Note: This still says unselected see issue #19927.)
  4. Arrow (Right?) to Settings button. - note it would appear Up/Down arrows don't work here which is slightly unusual.
  5. Press Settings.
  6. Arrow to the name, abbreviation and Replace button.
  7. Press Replace.
  8. Use Tab and Arrows to change the flute to an oboe.
    ...

Notice that if using NVDA once settings has been pressed nothing more reads from that point. using arrow keys, tab, etc gets no speech output. This does work with JAWS.

Supporting files, videos and screenshots

No recording available.

What is the latest version of MuseScore Studio where this issue is present?

4.4.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

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.