bad accessibility for screen readers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Program has several critical accessibility bugs. This bugs dowsn't allow to use program with screen reader comfortable.
1. Not all parameters accessible in tab order.
Tab order can focus only search field, table with tracks and tree view with categories tracks, autoDJ and ETC.
I suggest to make parameters accessible with tab shift tab and use tabs as category of parameters. Tabs must switch by pressing control+tab or shift+control+tab.
How I suggest categorize parameters^
1 deck tab, 2 deck tab etc.
Tab and shift tab must switch focus between parameters inside selected tab.
arrows must move faders or scroll through the list.
2. Headphone Cue (Pre-fader listen) and other parameters, which have on and off states, this states must be reported by screen reader.
3. fader values must speak by screen readers. Screen readers detects this faders as groups.
For example^ screen readers detects faders but without values^ группа Raise Pitch
Left-click: Sets the pitch higher.
Right-click: Sets the pitch higher in small steps.
Change the step-size in the Preferences -> Interface menu.
Shortcut: F6
Shortcut: Shift+F6
P. S. It's amazing, but this program though bad accessible, but accessible despite that has wrotten in QT. Thanks for your work, developers!
tags: | added: usability |
Changed in mixxx: | |
status: | New → Incomplete |
Changed in mixxx: | |
status: | Incomplete → Confirmed |
For me is unclear what are the tasks we can do to improve the situation.
Can you file separate bugs foe each issue?
What happens and what should happen instead?
Which Screenreader do you use on which Os?