musescore / musescore/MuseScore

Element Inspector Key for Accessibility

Open
#32,173 0 comments 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

Your idea
A key that can be pressed to read out additional info for any element.  This would for a text element read out all the font attributes such as font, size, colour, bold, etc. For music elements it would state what it is, any directionality (such as stem/up beamed above, triplet sign below), , note head type, grouping, visibility, etc.  An obvious shortcut for this would be Insert F as that is used in NVDA to give this sort of info in text editing. 
Problem to be solved

Currently to know most of this information will require many many tabs and arrows to find it in a settings menu dialogue or properties. Even when you get to it many of those do not report correctly till you change and then hope you got it right to change back or are unsure if they always enter the box on the top option and so you still don't know what was actually selected. This is utterly impractical to check lots of elements/notes. Instead of one quick key press and pause for a second you would have to fight your way round the navigation of the text style pop-up to find all those things. Many such as stem direction, beaming, where some elements sit above/below (for staff text) is currently undiscoverable with a screen reader. However, all this info is too verbose to have it read out all the time as you navigate so having a specific shortcut to get it when required is the norm. This is all information that the sighted user has at a glance when they look at the object, we need it with a key stroke "at a glance" rather than buried in settings.

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

The issue names no source file, test, or entry point. Start by locating the existing screen-reader accessibility and keyboard-shortcut entry points, then define the supported element metadata and testable spoken output. Done should cover the agreed element types and shortcut behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.