'Toggle' component improvements

Open
#24,625 0 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

accessibility P2 UI UX/interaction
Existing issues with toggles
  • The label next to a toggle is not read aloud by screenreaders (tested on macOS VoiceOver)
  • In white high-contrast mode, the white circle of the toggle is nearly invisible on the white background (if not for the slight shadow)
    image
  • While you can infer that "circle on right side of toggle + accent color background = ON" because it's a common pattern, we should make the ON state more explicit for high-contrast mode for users who can't see differences in color
  • Toggles do not have hover or hit states
  • Toggles cannot be toggled by clicking on their text label (like you can do with checkboxes)
Requirements
image
  • Add a checkmark (U+F477 in the MusescoreIcon font) to the 'On' state in high contrast mode, as well as other changes to strokes and color
  • Hover and hit states
  • Make the toggle text label clickable
  • Make toggle labels readable by screenreaders (they can still be called checkboxes as they are now, but the label should be spoken first, i.e. "[Toggle label name], [checked/unchecked], checkbox")

To whoever works on this, message me for the Figma link and the latest MusescoreIcon font with the thicker checkmark.

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

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.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.