Redirection bar not annouced by NVDA
I recently performed a user test session with a user of assistive technologies. During the test, one of the websites visited presented a redirection, and firefox notified the user accordingly, with a top gray bar with an "allow" button. The bar was not focused, and the user had no way to reach it unless indicated by sighted people.
This is a big problem for this user, the page stays blank, the only thing he gets NVDA to say is the full url of the page (including http), not even the title of the page. Once indicated, the user managed to "tab trough" the button, but because of a user error he ended up searching again, which might seem a small problem, but this user took at least 3 minutes to read a search results page, and his energy was limited. This is one of the reasons he failed to complete the task, which is very relevant to his life as an autonomous human being.
Alternatively, we indicated the user to press Alt+P in this case, and he could effectively overcome the bar and proceed to the redirection. But again, he had no way to discover the bar on his own.
I would like help in properly reporting, replicating this issue and understanding the follow-up process until it gets fixed.
Thanks.
The user was on Windows 7, using Firefox 53 and NVDA screen reader (unknown version). I'm attaching the interface element and the code that causes it.
由martinszy于修改
所有回复 (6)
I reported it as a bug in bugzilla by recommendation of people in IRC https://bugzilla.mozilla.org/show_bug.cgi?id=1370032
A well made bug report.
There is a way to turn off this notice. But being the user can't see the warning . . . . . . . Some redirects end up at junk pages.
Type about:preferences#advanced<enter> in the address bar. Under Advanced, select General Turn off Warn me when websites try to redirect or reload the page.
I don't know if this works with screen readers
https://addons.mozilla.org/en-US/firefox/addon/redirect-control/ Redirect Control This add-on enables the user to allow or deny redirects from web pages. You can also create rules to allow redirects that you approve of.
Thanks, but both your proposals put the burden of overcoming this issue on the user, and I don't think that is the appropriate focus on this situation. The burden should be on Firefox developers to fix it, so this user, and the many that face this same issue every day, don't have to understand the innards of the browsers just to access a website.
The bug is filed, is there anything else I could do to help in solving it? Take into account that I'm not familiar with Firefox's codebase right now.
Does it make a difference whether multi-process windows is enabled?
Bug 1029143 - Implement accessibility for sandboxed e10s
I don't know, I will have to try it. I didn't attempt to reproduce the bug on my system as I use a different OS.
In my OS (linux mint) the bar appears but the redirect happens anyway, even if I don't allow it, so it's ok that the bar is not focused.