test and improve screen reader accessibility in Preferences

Bug #1882262 reported by ronso0
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Confirmed
Low
Unassigned
Changed in mixxx:
status: New → Confirmed
ronso0 (ronso0)
Changed in mixxx:
importance: Undecided → Low
Owen Williams (ywwg)
summary: - test and improve screen reader sccessibility in Preferences
+ test and improve screen reader accessibility in Preferences
Revision history for this message
ronso0 (ronso0) wrote :

Findings with Orca in Mixxx 2.3 beta on Ubuntu Studio 20.04

opening Preferences, pressing Tab

=========
Live Broadcasting: (* focused widget [spoken text])
* Help [pushbutton]
* Restore Defaults []
* Apply []
* Cancel []
* Okay []
* (appearantly, now the entire inner Pref page has focus (up/down cause scroll moves)
(pressing Tab a few times, no feedback)
= stuck. neither Tab nor Shift+Tab move the focus

So IMO a necessary first step is to make sure all pages can be navigated with Tab and arrow keys. From a first look, I think this involves restructuring some page layouts by removing all not strictly necessary wrappers, but also review pages that dynamically populated in C++.

Then we need to assign tabstops to generate a predictable Tab order (this would help ALL users btw).

After that, let's look into https://doc.qt.io/qt-5/qaccessible.html ...

Revision history for this message
ronso0 (ronso0) wrote :

navigation in Broadcasting is fixed in https://github.com/mixxxdj/mixxx/pull/3156

Revision history for this message
ronso0 (ronso0) wrote :

well, have to say my test wasn't very efficient, mostly due to Orca being unreliable I guess.
Some widgets are described, some aren't. When I reverse the cycle with Shift+Tab, some widgets are described while others described earlier aren't anymore.

ronso0 (ronso0)
tags: added: preferences
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/10000

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.