musescore / musescore/MuseScore

No feedback with JAWS when entering text into Title/Composer/etc. fields

Open
#16,883 1 comment 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

I am using the latest version of Muse Score and the latest version of JAWS.

When I try to enter text into one of the edit fields for Song Title / Composer, etc. there is no feedback when using JAWS, After text is typed into one of these fields, the braille display appears blank. If I try to use the right/left arrows to navigate through the enterd text, no text is shown or spoken. Also, when navigating away from such a field and back again, JAWS does not speak any of the entered text or show it in braille. It is as if the field was blank.

When hitting JAWSKey+F1 to identify what kind of element has focus, JAWS does correctly identify these fields as a "edit" field.

Testing with the NVDA screen reader, everything works fine. Entered text is shown in braille, spoken when one navigates to the field, and one is able to navigate through the entered text using right/left arrow to verify the entered text and/or edit it.

--Pete

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

Start by reproducing the issue in MuseScore with JAWS using the Song Title and Composer edit fields, then compare the same fields with NVDA. Done means entered text is spoken, appears on the braille display, and remains navigable with the left and right arrows after leaving and revisiting the field.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
accessibility, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.