musescore / musescore/MuseScore

Unable to select an accidental with keyboard navigation

Open
#31,739 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

There seems to be no way to navigate to an accidental with the keyboard independetly of the note it is attached to in order to change its properties, in particular add a reminder accidental bracket just around the accidental.

STEPS:

  1. Enter a few notes into a score including 1 with an accidental.
  2. Use Alt + arrow keys to navigate along element by element. Notice the navigation moves to the note with the accidental and speech announces this including the accidental, but it skips the accidental itself.
    This is correct behaviour for the Alt arrow and we wouldn't want it to move to every accidental independetly of the note it is attached to, but there needs to be some other way to do this, for example Ctrl Alt arrows to make a micro movement to individual aspects within an element.
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.