No screenreader feedback on palette search

• Aug 11, 2019 - 22:20
Reported version
3.2
Priority
P1 - High
Type
Ergonomical (UX)
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore
Tags
accessibility

If you create a shortcut for palette search, there is no screenreader feedback when it is invoked to indicate you are in the search box, and more importantly, the names of the palette elements are not read as you navigate.

This may be fixed by the pending GSoC work, but I also have a fix for now using the current palette implementation.

Comments

• Sep 17, 2019 - 18:43
Status PR created ⇒ fixed

Fixed in branch master, commit ef018c2f5b

_fix #293228: accessibility for QML palettes

The QML palette implementation is inherently much more accessible than the original,
but it needs a few small changes to work correctly:

1) the palette-search command was incorrectly still tranferring focus to the old search box.
Fixed to transfer focus to the paletteWidget itself,
with a TODO noting that we really should be getting the search box within the palette.
I just don't know how to access individual QML widgets.

2) search box had no accessible text so it only read "edit",
fixed to inherit the placeholder text ("Search").

3) Names of key signatures and other palette cells that include unpronounceable Unicode characters
were not being read correctly (eg, Eb major reads as just "E major").
Fix is to call makeReadable() on the cell name for the AccessibleTextRole,
and to be sure that role name is exposed in the model._

Reply

Fix version
3.3.0