-
Notifications
You must be signed in to change notification settings - Fork 76
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
uBO UI isn’t accessible via TalkBack screen reader on Android #3223
Comments
It does not work in the popup mode. Works from the logger (when you manage to turn it on), except for the Zapper, Picker and Reporter buttons. Dynamic filtering also cannot be changed. Host names are read correctly. Scrolling the top menu in the dashboard is difficult. Accessing the logger form Support tab in the Dashboard is difficult, because for some reason links are read separately, sentence does not start with "The logger", but reads only "is the primary tool to diagnose filter-related issues." The Reload, DOM inspector and Toggle the popup panel buttons are not accessible, but the console button works fine. The Clear logger button is skipped - should probably be described as disabled. |
For example, Dark Reader popup is read correctly, so it must be something in uBO. The Reload, DOM inspector and Toggle the popup panel buttons works when page is selected from selector, but not in "Current tab" mode. |
Toggling the popup in logger in reader mode does not set focus to the popup panel, so it cannot be navigated :\ |
Prerequisites
I tried to reproduce the issue when...
Description
uBlock Origin extension UI isn’t accessible via TalkBack screen reader on Android.
A specific URL where the issue occurs.
everywhere
Steps to Reproduce
Expected behavior
The UI’s text and buttons are readable and double-tappable via TalkBack.
Actual behavior
The UI sounds like blank space and isn’t functional when TalkBack is enabled.
uBO version
1.57.2
Browser name and version
Mozilla Firefox for Android 125.2.0
Operating System and version
Android 14
The text was updated successfully, but these errors were encountered: