search

RequestPolicyContinued / requestpolicy

a web browser extension that gives you control over cross-site requests. Available for XUL/XPCOM-based browsers.
https://github.com/RequestPolicyContinued/requestpolicy/wiki
Other
252 stars 35 forks source link

Focus on context submenu voices #837

Open ABuffEr opened 7 years ago

ABuffEr commented 7 years ago

Hi, I installed RequestPolicy Continued 1.0.beta12.4 in Firefox 54.0.1 (32-bit) on Windows 7 (64-bit). It's my first time with this continuation (I used original project for years), and I verified that problem is not present in 0.5 legacy, so it's probably born with menu refactoring in 1.0 branch. The problem: when I open context menu and press enter on add-on voice (that not appears as a voice with submenu), then submenu voices does not receive focus. Visually everything works, voices appear correctly, but I'm blind and, using NVDA (open source screen reader), I'm not able to reach those voices.

myrdd commented 7 years ago

Hi, I'm afraid the menu is quite bad for accessibility. When you open RPC by using the context menu entry, the context menu will close and the RPC menu opens somewhere else. Does it make a difference if you open the menu using the keyboard shortcut instead? It's Alt Shift R. Is it possible for you to focus the menu manually?

ABuffEr commented 7 years ago

Hi, and sorry for the delay...

Does it make a difference if you open the menu using the keyboard shortcut instead? It's  Alt Shift R . No difference, alas :( Is it possible for you to focus the menu manually? Partially. After various attempts, I found a way to read those voices, but without interaction (simulated mouse clicks, enter etc), so, at this point, I will write rules manually in RPC options. Anyway, you have done a very very good work, after some days I didn't have no need to edit/insert new rules yet. :)

myrdd commented 7 years ago

I've read that making an user interface screen reader compatible is—more or less—as easy as making it navigable with the keyboard. So I tried to achieve keyboard navigation, but I failed to do so. For whatever reason I cannot capture keypress events in the menu popup. Since I'm currently migrating the addon to WebExtension technology, I hope that making the menu keyboard navigable is easier to achieve then. Hopefully you can work around this bug until then.