Hello Ted,
based on how the screen looks in your particular case, have you considered/tried:
- posting UIAccessibilityAnnouncementNotification with a string to be spoken (e.g. it would include the new subtotal, like “New subtotal x $”)? This does not change VoiceOver cursor position. - posting UIAccessibiltiyScreenChangedNotification and passing as argument the same string (this behaves like passing nil, but speaks the passed string before announcing the automatically found element on the screen)?
I do not have a really clear idea of how your app behaves in the screen in question, so cannot really tell which of the two above (if any) would be more suitable.
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
|