nothing can be UIgrabbed via GOK

[patrickw]

Using gnome desktop and GOK ('direct selection' mode):

The terminator application does not present many useful user interface
elements within the GOK window. All that is typically seen through
GOK is "Terminal", "V Scrollbar", "Terminal". Not even any of
terminator's 'V Scrollbar's can be UIgrabbed in GOK. Choosing various
tabbed Terminator terminals should be possible through GOK, as well
as operating the scrollbars if they are presented at all. This would
improve the usefulness of terminator for GOK accessibility users.

[Chris Jones (cmsj)]

Thanks for the report - I am utterly unfamiliar with GNOME accessibility stuff, including GOK.
Would it be possible for you to provide some steps I can follow to enable/test this stuff, and what you would be expecting to see vs what actually happens?

[patrickw (patrick-wade)]

Chris - if you're using gnome, a quick way to turn on accessibility is to run:

# gconftool-2 -t bool -s /desktop/gnome/interface/accessibility true

Then log into the gnome session, and launch terminator, and then launch GOK. It should be under Applications->Universal Access->On-Screen Keyboard on most standard gnome app menus.

Once GOK is up, click the "Activate" button in its window, and then click the terminator item once it appears in gok's window.

Then, click "UI Grab" (usually a button in the bottom-right of the GOK window), and GOK should update its view to show the user interface elements of the Terminator application.

---------
If this worked correctly, one should be seeing terminator's primary interactable user interface widgets listed as clickable buttons in GOK's window. From there, a motion-impaired user could interact with terminator via these items in GOK's window. They should be able to resize panes, scroll the terminator scrollbars, and so forth... all through GOK.

[Jordan Callicoat (monkeesage)]

I can confirm this, but I get the same thing with Gnome-Terminal.

[Chris Jones (cmsj)]

If it affects G-T too then there's a fair possibility that it's actually the fault of the VTE widget, but I'm not sure.