musescore / musescore/MuseScore

Add ability to jump between similar elements such as system text or chord symbols with keyboard.

Open
#27,628 1 comment 1 reaction 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

Your idea

I am a screen reader user. Currently when I have system text or a chord symbol focused and press control right arrow, focus does not move and NVDA repeats the name of the focused element. It would be amazing to be able to jump to next system text. A score I'm working on has things like "verse" "chorus" as system text. Would be a major time saver to b able to jump like that. Or between rehearsal marks.

Problem to be solved

It is difficult for blind users to efficiently jump around a score. This would be a great tool to have. I've tried using control f to jump to rehearsal marks, but that seems to take screen reader focus to the topmost staff. Maybe that's another issue, but I point it out here to illustrate that I have yet to find a great method of quickly jumping around in time while working on a score.

Prior art

No response

Additional context

No response

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

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

No files, tests, or implementation entry points are identified. Reproduce the behavior with NVDA using Ctrl+Right Arrow on system text, chord symbols, and rehearsal marks, then inspect existing keyboard navigation and define tests for jumping to the next matching element without moving focus to the topmost staff.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
accessibility, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.