-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accessibility / screen reader issue, after clicking the toolbar button, the shown up interface is not accessible with screen reader keyboard control #2072
Comments
uBlock Origin's tabbed dashboard uses an For example, do you have an issue reading this page: http://codepen.io/Mahmoud-Zakaria/pen/zKLrkY? |
Thanks for your reply. Raymond Hill 於 16/10/2016 20:09 寫道:
|
To help me find out which items are unknown, can you list the items which are known? |
Hi, thanks. Raymond Hill 於 16/10/2016 21:06 寫道:
|
OK I understand, you are referring to the UI of the popup panel, not the dashboard. |
I'm bumping this issue as it's still a serious problem. It's not so much the fact that it can't be navigated with the keyboard, but most of the controls aren't visible. Testing with Chrome and the free NVDA screen reader on Windows as well as VoiceOver on Mac OS, after pressing the uBlock button on the toolbar I can only see 2 unlabeled links that go to the logger and the actual dashboard. But I can't see the buttons that can be used to quickly turn uBlock off on a page. I guess it's not a standard HTML control so NVDA can't pick it up and you can't tab to it either. Setting the appropriate aria roll to tell screen readers the type of control (I guess checkbox would be appropriate for the uBlock toggle) and aria labels to explain what they do would make the extension a lot easier to use. Because right now whenever I want to exclude a site I have to manually drill down to the settings and paste the url into the exclusion list which is a bit frustrating. |
I made changes which hopefully fix the issue, but it's not something I can test myself. If you are willing to test with the development build of uBlock, that would be great to have feedback as to whether things are better now. The development build of uBlock can be installed from the Chrome store: https://chrome.google.com/webstore/detail/ublock-origin-dev-build/cgbcahbpdhpcegmbfconppldiemgcoii. |
Thanks for the quick fix 😊. It looks like the 2 links for dashboard and logger still don’t get labels read out on them. For the clickables, with NVDA they get read out, but JAWS (another Windows Screen Reader that’s also commonly used) doesn’t seem to pick them up.
Have a look at this blog post, I think it fits this situation pretty well. Adding the aria roll and label tags should completely fix the problem.
https://www.marcozehe.de/2013/04/24/easy-aria-tip-6-making-clickables-accessible/
|
The new dev build was finally cleared I was already using |
Hi,
This is perfect, everything works as expected now. The controls are now recognized and labeled and I can consistently get to them and toggle them on/off.
In the previous dev build the 2 links still didn’t have a label for some reason, so they just got read as “link”. But now they work fine as well.
Thanks for the quick fix! 😊
|
Read first: https://github.com/gorhill/uBlock/blob/master/CONTRIBUTING.md
Describe the issue
As title suggested, I am a screen reader user.
I try clicking the toolbar button however, the shown up interface seemed like is an overlay interface and is not accessible with screen reader using keyboard control.
The text was updated successfully, but these errors were encountered: