[graphic-forms-devel] Accessibility question
Jack Unrue
jdunrue at gmail.com
Sat Sep 1 22:35:19 UTC 2007
On 8/31/07, Ken Perry <whistler at blinksoft.com> wrote:
>
> Jack,
>
> I just tested your layout tester and found a problem. Is there no tab index
> property on the controls? You had asked me about accessibility earlier and
> one big part of accessibility for your forms would be to have tab index
> working and the ability to add short cut keys. Currently it seems the only
> way to use the buttons is to click on them with the mouse for example I have
> 4 buttons on the layout tester and can't tab between them and select them
> with enter is this true? Or is there a property I have not found in the API
> to add keyboard access.
Tab traversal logic is not yet implemented for top-level windows and
panels. This is logged as bug # 1458481 in the SF.net bug tracker. I suspect
I would leave tab traversal off by default in a window, and require the app
to enable it. But that's contingent on implementing the required stuff under
the hood to make it possible at all.
Tab traversal is implemented and enabled by default for dialogs. So perhaps
you could consider defining a dialog which would get invoked via a menu
item or something like that.
Control shortcuts are also not yet implemented -- or at least, I haven't
investigated what else needs to be done. You've probably noticed that
mnemonics work for menu items. The need to support accelerators is
logged as bug # 1458491.
--
Jack Unrue
More information about the Graphic-forms-devel
mailing list