musescore / musescore/MuseScore

Improve Accessibility for Cross Stave Slurs

Open
#20,098 0 comments 0 reactions 2 assignees View on GitHub

@DmitryArefiev is already working on this.

Since Nov 21, 2023.

accessibility needs review P1
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

Slurs/phrase marks that cross a staff and then return back again, e.g. start in the bass clef of a piano score, cross over some treble notes and back to bass are only possible to create by dragging the slur manually into the correct looking position. This means they are only actually attached to one staff where they start and end and so when exported to xml for Braille do not show that they cross the staff. It is also not possible for a blind user to move them to make them look correct, or know from a screen reader that they cross the staff if reading a score where they have been dragged to look correct.

The ideal would be that when notes are selected across two staves the slur curves appropriately to take in all notes (currently it only arches over the one that the first and last note are on) and also has an anchor point on the first note each time it crosses the staff that is announced by a screen reader as something like “slur continues cross staff”, in a similar way to how cross beams are announced.

Steps to reproduce
  1. Create a few bars of piano music with a melody that starts in the LH, moves up to a few notes in the RH and then back to LH.
  2. Select all these notes.
  3. Press s to add a slur.
  4. Note the slur only arches over the lower staff.
  5. Arrow along these LH notes and notice the screen reader gives no indication the slur includes RH notes.
Screenshots/Screen recordings

No response

MuseScore Version

4.1

Regression

I don't know

Operating system

Windows 10 with NVDA

Additional context

No response

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.