GNOME Bugzilla – Bug 125311
cannot keynav and select links in Gnome-About
Last modified: 2007-11-12 22:23:35 UTC
There is no apparent way to traverse and choose the hyperlinks in Gnome-About via the keyboard. Currently, the only traversal is between the 'Layered Pane' and the 'Close' button.
This bug is also affecting navigation with GOK's 'UI Grab' - There is nothing to Grab.
As per Bill Haneman's suggestion for keynavigability of the hyper links (in bug #125295), I'm attaching a patch which creates a context menu containing the hyperlinks. This context menu can be invoked throu' shift+F10. Quoting Bill Haneman's suggestion for reference ------- Additional Comment #9 From bill.haneman@sun.com 2004-02-05 10:27 ------- regarding the links: it occurs to me that we could provide an F10 keybinding that treated them as though the horizontal list of links were a menu bar. That would avoid the need to implement AtkHypertext, etc. Similarly, if we created a context menu for gnome-about, which was exposed as an action on the toplevel accessible, we could put all the links there. We could then avoid the necessity to make the links keyboard navigable since we'd have equivalent functionality available from the keyboard.
Created attachment 26475 [details] [review] Proposed patch
Uggh, a popup menu? Really? That sucks ... Maybe we should make this thing some fancy HTML with Java script and embed mozilla or something if we can't even get simple keynav with the canvas :/
*** Bug 149199 has been marked as a duplicate of this bug. ***
I agree that the popup solution is sucky. However, can we apply it now, so that at least the user has _some_ way to do this, until we get a more elegant solution (either specific to the gnome-about app, or in the canvas)?
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs. Filter on "SUN A11Y SPAM" to ignore.
Apologies for spam... ensuring Sun a11y folks are cc'ed on all current accessibility bugs.
gnome-about has been rewritten in python and doesn't use a canvas anymore. This bug is fixed now. See bug 481585 for more details.