Re: UITextInput & UIAccessibility
Re: UITextInput & UIAccessibility
- Subject: Re: UITextInput & UIAccessibility
- From: Chris Fleizach <email@hidden>
- Date: Fri, 13 Apr 2012 13:54:45 -0700
| Right now, custom text views do not work with accessibility. Please file a bug with a sample (if possible) and hopefully this deficiency will be addressed sometime soon.
On Apr 13, 2012, at 1:46 PM, Melissa Dominguez wrote: I have been working on a rich text editor using a view controller that implements UITextInput with custom views to display the text, controls, etc. I want to make it accessible for VoiceOver, but I'm having a hard time figuring out exactly what to do.
I assume I'm going to have to make one of my views implement UIAccessibilityContainer, but that's where I get stuck. I'd like to have the full Rotor experience, but I'm not sure how to a) enable it for my app and b) access the settings from it. If it were enabled and I could get the desired granularity, then I could manually implement the methods in UIAccessibiltyContainer (ie, given the desired granularity, figure out how many units of that kind there are, etc) by calling the methods in the tokenizer. But it seems the sort of thing that Apple would likely already have wired up, provided I set the right settings and perhaps implement a few methods. (I think this because, for example, hardware keyboard navigation via arrow keys just works, provided you've implemented the right properties and sent the right notifications. This seems like the same sort of thing.)
Are there any documents on how UIAccessibility and UITextInput are meant to interact?
Thanks, Melissa
|
_______________________________________________
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