Re: [orca-list] Advice on clicking clickables in Firefox?
- From: Peter Vágner <pvdeejay gmail com>
- To: Nolan Darilek <nolan thewordnerd info>, Orca <orca-list gnome org>
- Subject: Re: [orca-list] Advice on clicking clickables in Firefox?
- Date: Fri, 8 Jan 2016 20:09:53 +0100
Welcome back Nolan,
It's awesome to have one more clever guy onboard.
I don't have a proper reasoning why the Orca vs Firefox experience is
different to that with NVDA vs Firefox on Windows, however I think I
have at least understood how it works.
On Windows NVDA overrides enter keypress and alvais executes default
MSAA or IA2 action on the current browse mode element or on an element
in focus. It's why the clickables work because their only event handler
is on click in most cases. The same is true for links and buttons
because their default action is activate in most cases.
Orca does not trap enter keypress I think because without virtual
document stuff it would be kind of difficult to work out whether to pass
it to firefox or act accordingly. Hmmm. Or might be focus vs browse mode
switch good enough for this? I am not sure. BTW you can switch from
browse mode to focus mode and back with orca+a .
Greetings
Peter
On 08.01.2016 at 18:30 Nolan Darilek wrote:
Nice, thanks, I'll remember that.
Is there some reason that these can't just be triggered via enter
directly from Firefox? Great to have a way to do this, but it seems a
bit complex as a first method. Great for discoverability, but a bit
slow if you're actually on a clickable object but then have to find it
in a list.
Also, is there any way to find these Firefox/Gecko-specific
keybindings? I remember them being added over time but don't recall
what they were, and I don't see them in either the global keybindings
tab or the one that appears when I pull up Firefox-specific
preferences (though maybe I skimmed too quickly and missed them.)
On 01/08/2016 11:21 AM, Storm Dragon wrote:
Howdy,
If you have the clickable in focus, it will be selected in the list,
if not, you will have to scroll down to what you want to activate.
To get a list of clickables, press alt+shift+a and to activate it,
either tab to the activate button and press enter, or press alt+a.
HTH
Storm
On Fri, Jan 08, 2016 at 10:20:27AM -0600, Nolan Darilek wrote:
Switched back to Linux recently after a couple years on Windows and
NVDA. Please don't get the impression that this is a Windows/NVDA
fan post--I switched back to Linux because Windows itself irritated
me--but I'm hitting a few pain points that just aren't going away
using Orca after being away for nearly 2 years.
Clicking clickable text in Firefox that isn't a link is one example,
and the most painful aspect of it is that I can't come up with a
reliable test case. I position the caret on the text to be clicked.
I then use the Route Pointer command (which I think by default is
something like caps-9 in laptop mode but which I've rebound to
caps-backspace) and then simulate 1-2 left-clicks.
And here is where things diverge. Sometimes it works. Sometimes
nothing happens. Sometimes, despite the fact that I've pressed the
route command, clicking opens the overview panel, takes me to
another app or performs another action. I was trying to order food
on Grubhub last weekend and spent 15 minutes trying and failing to
click menu items before giving up with Linux for that task.
I ultimately had to switch to Firefox running under NVDA in a
Windows VM. Under NVDA, pressing enter on a clickable item almost
always triggers a click on that item. While the Grubhub ordering
process wasn't the most accessible, I didn't experience this routing
issue at all when I could simply press enter to simulate a click.
Is there some secret to accomplishing this? Ideally I could complain
to every website/app in which this behavior occurs and tell them
that clickables should be either links or buttons, but that would be
a full-time job, and pragmatic me just wants to get the task done. :)
Also, is there some reason that pressing enter in Firefox can't
trigger a click under Orca? That to me seems like the most pragmatic
solution. I don't want Orca to be an NVDA clone but when one or the
other does something useful, I'd hope that the other might copy the
pattern. UX will of course differ between Linux and Windows but
conventions can cross over and be incredibly useful. The reason I
point this out is that I'd really like to shut down my Windows VM,
but as it stands it's running almost constantly so I can switch over
and use websites that I can't get working under Orca.
Thanks.
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide:
https://help.gnome.org/users/gnome-help/stable/a11y.html
Log bugs and feature requests at http://bugzilla.gnome.org
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]