On Aug 24, 2006, at 1:52 PM, Tomas Zahradnicky wrote:
kAXFocusedUIElementAttribute will return the element in the
application that has "keyboard focus", not "VO cursor focus".
By default, keyboard focus will follow the VO cursor (though the
user can turn this off in the VoiceOver Utility), but only when
the element that the VO cursor is on can receive keyboard focus.
Not all UI elements can receive keyboard focus (e.g. static text
elements).
So there is no guarantee that the keyboard focused element (given
by kAXFocusedUIElementAttribute) will be what the VO cursor is
currently focused on.
The window I accessorize consists entirely of my own HIViews so I
could go around the above limitation by supporting focus and that
should work reliably, shoudn't it?
Not reliably, no, since the user can turn off keyboard focus tracking
in the VoiceOver Utility (or ctrl-opt-shift-F3). In that state the
VoiceOver cursor will move from element to element but won't drag the
keyboard focus along with it.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/accessibility-dev/email@hidden
This email sent to email@hidden
