Re: Manipulating the VoiceOver cursor programmatically
Re: Manipulating the VoiceOver cursor programmatically
- Subject: Re: Manipulating the VoiceOver cursor programmatically
- From: Josh Scotland <email@hidden>
- Date: Thu, 24 Apr 2014 15:07:18 -0700
On Apr 24, 2014, at 2:01 PM, David Gatwood < email@hidden> wrote: Is there a better, cleaner way to force the VoiceOver cursor to leave an element that's no longer visible, and to convince VoiceOver to forget about an element, or am I stuck with less-than-ideal behavior pre-10.9?
Depending on the situation, you might be stuck using API introduced in 10.9. NSAccessibilityLayoutChangedNotification gives AX clients (e.g. VoiceOver) a way to respond and update cursor context. Posting it after a view disappears is proper usage.
Also, why don't table views automatically hide themselves from accessibility when you call setHidden with a value of YES? Should I file a bug on that?
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden