Accessibility regressions in youtube-dlg 0.4
See original GitHub issuePlease follow the guide below
- You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
- Put an
x
into all the boxes [ ] relevant to your issue (like that [x]) - Use Preview tab to see how your issue will actually look like
WARNING
All invalid issues will be rejected!!
Before going further
-
If your problem is a bug with youtube-dl or a request for new site support please report it here
-
Make sure you are using the latest youtube-dl-gui version (Click the
Settings
icon and thenAbout
to view the current version) -
Make sure you are using the latest youtube-dl version (Click the
Settings
icon and thenUpdate
to update to the latest youtube-dl version) -
Make sure you searched the bugtracker for similar issues including closed ones
-
Make sure to read the FAQs file
- I think my problem is NOT with youtube-dl
- I’ve verified and i assure that I’m running youtube-dl-gui 0.4
- I assure that i am using the latest version of youtube-dl
- Searched bugtracker
- I’ve read the FAQs file
What is the purpose of your issue?
- Bug report
- Feature request (request for a new functionality)
- Question
- Other
Please remove any sections between (—) if they are not related to your issue
Bug report
If the problem occurs when downloading a URL please provide the full verbose output as follows:
- Restart youtube-dl-gui
- Go to
Options > Extra
tab - Enable Debug youtube-dl
- Go to
Options > Advanced
tab and Clear your log content - Try to download the URL
- Copy the whole log content and insert it between the ``` part below
delete me and insert your log content here
What operating system do you use ?
Windows 10 Build 1703.
List of actions to perform to reproduce the problem:
- Load a screen reader, such as Narrator using control-windows enter in build 1703 or windows-enter in previous builds of windows.
- Navigate the main screen using tab and shift tab keys.
What is the expected behaviour ?
The buttons on the main screen should announce with names such as delete button, settings button, etc. This was the behaviour in the previous youtube-dlg, 0.3.8.
What happens instead ?
The screen reader simply says “button” for most buttons on the main screen. This makes it tricky to know what the buttons will do.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:17 (3 by maintainers)
Top GitHub Comments
The UI is cluttered, but a lot of UIs are cluttered. I think it would be usable if screen readers are able to identify the buttons and controls. It would also help if controls had accelerator keys (alt+u for URLs, alt+d for downloads, something like that) so it would be easy to jump to a specific control.
This page has suggestions written for Gnome. They should translate to WX. https://developer.gnome.org/accessibility-devel-guide/stable/gad-ui-guidelines.html.en
Hi, I just downloaded this to test it for a friend who is not so comfortable fiddling with command line, and was sad to see the label issues. The unfortunate fact is that even if the buttons have labels, they are not in a place that any screen-reader knows how to understand.
I don’t agree that we need a “blind interface” at all. If you’re worried about clutter we could add access keys such as alt+d for download. These keys would be announced when the user moves to the button, so an attentive user can memorize them. We’re used to tabbing through interfaces with several buttons and this is far from the worst thing I’ve ever seen. It would be usable if everything had a label; it would be great if hotkeys also existed. Don’t worry about a separate interface; that’s more work on your end and it’s almost never a good idea. Thank you for taking a look.