This was reported on the Accessibility mailing list: https://groups.google.com/forum/#!topic/mozilla.accessibility/WB2Fd20OwmI Excerpt: I am using Firefox for Android on a Samsung Tab S, and use both Talkback and Brailleback. Normally, when I wish to activate a particular control with my Braille display, I press the touch cursor above one of the cells containing the text label. In Firefox, when I do this over the Menu control at the top of the screen, I receive the audible confirmation that this has been done, but I am then not allowed to move away from the top menu bar. I can move in-between the website name on the far left, and the Menu control on the far right, but nowhere else using Brailleback commands. However, when I swipe on the tablet screen, I am allowed to move passed the top menu bar, and find the regular Menu options such as Share and Settings. -- End of excerpt -- I was able to reproduce this. CC'ing MaxLi in case he is also interested in taking a look at this.
I think this may be a dup of bug 1062016. If you could verify that the patch their fixes it.
Dear Eitan, This has been partially resolved. Now when I pressing a touch cursor over Menu, focus is still reset to the beginning of the top menubar, over the web address, but using braille navigation keys, I can scroll out of the menubar. Unfortunately, the drop down menu is skipped, and I am placed in the contents of the FF page. The menu options, such as Share, are only accessible when I swipe with my finger on the tablet. Hope this helps. Dan
Summary: Not able to move into the opened menu using BrailleBack commands → [AccessFu] Not able to move into the opened menu using BrailleBack commands
This doesn't appear to be an AccessFu bug. It's entirely contained within the browser chrome. At least when I use the braille overlay (i.e. not an actual braille device), it seems like when I activate the menu bar with the braille display, the menu correctly opens, but accessibility focus remains on the menu button itself. Brailleback and Talkback use different algorithms for finding the next element, and that is likely the reason you're able to swipe to start exploring the menu but when going to the next element with the braille commands probably doesn't explore the menu commands.
Component: Disability Access APIs → General
Product: Core → Firefox for Android
Summary: [AccessFu] Not able to move into the opened menu using BrailleBack commands → Not able to move into the opened menu using BrailleBack commands
Do we have an idea of affected versions, Marco or Max? In particular, the tablet UI recently changed (35 or 36), so this might either be fixed if currently broken in release, or be a regression if the reporter is testing on Nightly.
status-firefox34: --- → ?
status-firefox35: --- → ?
status-firefox36: --- → ?
status-firefox37: --- → ?
I think this has been here for a pretty long time. I've can replicate this in both release and nightly on my Nexus 5 (so a new tablet UI wouldn't affect it).
status-firefox34: ? → affected
status-firefox35: ? → affected
status-firefox36: ? → affected
status-firefox37: ? → affected
Thanks for testing!
tracking-fennec: --- → ?
Eitan - Any thoughts on how to proceed here?
tracking-fennec: ? → +
I'll get to this next week (keeping the needinfo flag until addressed).
I have been trying different options, and I can't seem to get this working right. Ultimately, I think this is a brailleback bug. There is an inconsistency where talkback does the right thing when swiping right, but brailleback's scroll buttons get stuck. I'm going to open a bug for brailleback, and cross reference it with this.
Added brailleback bug for reference.
You need to log in before you can comment on or make changes to this bug.