Hi all,
the bug is still present in iOS 10. The code workaround exactly as I presented earlier in this thread no longer works on iOS 10: while navigating the results by flicking in VO works, navigating the results by touch exploration in VO no longer work.
However with a small adjustment, the workaround works correctly on iOS 10 (instead of setting accessibilityViewIsModal on searchController.view, it should be set on searchController.view.superview). That small adjustment in turn does not work on iOS 9.
In the end, one has to check the OS version at runtime to choose which version of the workaround to apply. Just be advised that this all still is an awful non-robust workaround (though quite instant), and also that it might stop working in future iOS versions due to some internal change, including very well likely also when Apple fixes the original bug. Therefore you might want to consider being explicit in what iOS versions each version of the workaround applies to.
On another note, I think this bug is also present in one iOS stock UI: Settings.app > Safari > Passwords. The situation and symptoms are just the same as described earlier in this thread: as soon as the search text field is entered (active), then no matter if empty or non-zero length search string is entered, the table below becomes completely inaccessible. It is of course a speculation that it is caused by the same issue as in this thread, but based on the same situation and symptoms, I would bet 95% it is the case. I reported that as
rdar://28653030 "Safari "Passwords" search results in Settings.app not accessible at all”.
Kind regards,
—
Boris Dušek
A11Y LTD.
On Jun 8, 2016, at 12:05 PM, Boris Dušek <
email@hidden> wrote:
Thanks Clare,
Boris
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