Re: Problem when too many elements in UIAccessibilityContainer
Re: Problem when too many elements in UIAccessibilityContainer
- Subject: Re: Problem when too many elements in UIAccessibilityContainer
- From: Richard Groves <email@hidden>
- Date: Fri, 26 Jul 2013 16:00:07 +0100
Hi,
Thanks Chris - implementing that hierarchy with two types of view implementing the UIAccessibilityContainer protocol (UIView and UIScrollView) has got me to a position where it is worked (code is pushed to github if anyone wants to see). I'm still getting some of the console messages of the **** Accessibility: Could not find a valid index for .... type when I come back from the detail pages and remove a bunch of elements from the accessibility hierarchy so I'll spend a bit more time looking into that before trying to roll it back into the main app.
It's pretty tricky to flatten out all the hierarchies so the active accessibility elements are directly in the containers, but I guess if it is ok for containers to contain other containers it is possible to implement anything in the end.
Cheers,
Richard
On Thu, Jul 25, 2013 at 3:59 PM, Chris Fleizach
<email@hidden> wrote:
Skipping the scroll view is probably a side effect.
Another option is that you implement the UIAccessibilityContainer protocol on each subview (or at least the scroll view)
So you'd have
A11yContainer
-> AXContainerScrollView (subclass of UIScrollView)
-> each view
-> other view
_______________________________________________
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