Missing items Orca screenreader doesn't read in the inspector

• Jan 28, 2020 - 18:10
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

OS: Opensuse Leap 15.1, MuseScore version 3.4.1 (AppImage, OS: openSUSE Leap 15.1, 20414b2), Orca version: 3.34.1

See also:#299387: Support screenreaders other than NVDA

Using tab/shift tab for navigation.

Expected result: by entering or changing a value inside the inspector Orca should also read the description before
Actual result: for some settings it reads the value, but not the description before

Not sure, if it's the best way to report it, but I could imagine to check it for each element inside a score.

In general:

  • Orca doesn't read the section of the settings (for example "element", "chord", "segment" and so on), not sure, if it works with NVDA, but should be an orientation for the user.
  • Also I noticed: From "minimum distance" it switches to "stacking order", then to "color", then to "offset". But not sure, if it's confusing for users with visual impairments.
  • Aware, that settings like "offset" or other probably are not important for blind users, I think it could be important for orientation, where he actual is inside the inspector.

Comments

Also I noticed, if a note is selected Orca doesn't read "velocity" before the value field, but it does in inspector properties for dynamics.