musescore / musescore/MuseScore

No speech feedback whn downloading/installing language updates

Open
#31,741 0 comments 0 reactions 1 assignee View on GitHub

@shoogle is already working on this.

Since Jan 13, 2026.

accessibility needs review
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

With NVDA running go to:
Edit, Preferences and on the general Tab arrow down to the check for language updates button. Press enter.
If a dialogue appears saying there is an update when you press the download button nothing seems to happen. The screen reader gives no verbal feedback to say it is downloading or installing the update or when it is complete.
The user is left thinking nothing is happening, but navigation does seem to freeze for a few seconds.
I am still unsure if the button worked and gave no speech or if it didn't activate as when I had someone sighted come and click the button with the mouse they said they saw some text that said downloading and then the window disappeared same as it had for me previously. So probably just lack of speech and I had done it, but maybe someone could test the download button is fully keyboard accessible.

Supporting files, videos and screenshots

N/A

In which versions of MuseScore Studio is this issue present?

4.6

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.