Yes, the screen reader accessibility of the GUI and the preferences definitely needs to be improved.
Some helpful additions coming to mind would be to add controls to read out the track title/artist of a particular deck, or read out the relative play poistion of a deck (or elapsed/remaining time).
To me the suggested solution sounds like all GUI controls should be focusable and navigation is supposed to work with Tab key. This is quite the contrary we tried to achieve for the controller and keyboard use case for users without sight impairment.
Also, with a basic regular 2 decks + mixer layout there are roughly 70-80 controls (only in the top section). IMO it's insane to navigate those with Tab in a rather time-critical DJ context.
Thus I don't consider the suggested approach feasible and an actual improvement.
Yes, the screen reader accessibility of the GUI and the preferences definitely needs to be improved.
Some helpful additions coming to mind would be to add controls to read out the track title/artist of a particular deck, or read out the relative play poistion of a deck (or elapsed/remaining time).
To me the suggested solution sounds like all GUI controls should be focusable and navigation is supposed to work with Tab key. This is quite the contrary we tried to achieve for the controller and keyboard use case for users without sight impairment.
Also, with a basic regular 2 decks + mixer layout there are roughly 70-80 controls (only in the top section). IMO it's insane to navigate those with Tab in a rather time-critical DJ context.
Thus I don't consider the suggested approach feasible and an actual improvement.
Most blind / sight-impaired users use optimized keyboard layouts, for example /mixxx. discourse. group/t/ this-is- a-mixx- keyboard- for-mixing- without- a-controller- or-mouse/ 23257/5 /mixxx. discourse. group/t/ custom- keyboard- mapping- for-blind- users/18067
https:/
https:/