On Oct 7, 2010, at 11:35 AM, James Dempsey wrote: On Oct 7, 2010, at 10:44 AM, Scott Kovatch wrote: I agree that a AT client could certainly accomplish the same thing with the existing accessibility APIs, but I'm not writing a client. That said, I need to make sure the corresponding accessibility attributes for the selection and selected text are settable. We already support getting the selected text, including attributes.
That is great - which hopefully means VoiceOver users, for instance, will be able to interact with your text areas.
Yes, and in fact they do quite readily right now. It's a bit surreal to hear VoiceOver read out your source code to you in Eclipse. :-) After re-reading the interface, I think one way a client could do this is to set the selected text range via AXSelectedTextRange and then send an action for Copy, Cut, Paste, etc., which we would expose for objects with an AXTextAreaRole.
If you have a particular client in mind, then this would work. For any general client, since no Copy/Cut/Paste actions are defined in the AX API, the client would not necessarily be expecting to find these actions, or have facilities for using them.
That's right. We are already working with Dragon to get Naturally Speaking to support this on Windows, and hopefully we can get them to think about how this could be done on the Mac. Speech recognition is the only client we can think of that would use this kind of functionality.
It certainly would be far, far easier if everyone just put Cmd-X, C, and V in their edit menus, and then this wouldn't be an issue, but sadly, in the Java world, it's not that easy.
I'm not familiar with whether there is a way to make an app scriptable without a bundle. The email@hidden would probably have better answers on that topic.
That's fine; I figured it might be off-topic for this list. I'll check that out if I need to go that route.
Thanks for the help/advice.
-- Scott K.
------------------ Scott Kovatch IBM Eclipse Platform Team Pleasanton, CA
|