Re: Add keyboard to .accessibilityElements
Re: Add keyboard to .accessibilityElements
- Subject: Re: Add keyboard to .accessibilityElements
- From: Sean Howell <email@hidden>
- Date: Tue, 10 May 2016 15:38:12 -0700
It stops at Cancel. Any further attempt to swipe right concludes with the bumper sounds indicating no more elements.
I have been able to use introspection on -[[UIApplication sharedApplication] windows] when the keyboard is present, to find the keyboard, but I’m not overly confident in the safety of it, particularly when dealing with 3rd party keyboards.
> On May 10, 2016, at 12:46 PM, email@hidden wrote:
>
> You won't be able to add the keyboard to your accessibilityElements list, since often the keyboards are in a different process
>
> however, if your cancel button is the last item accessible in your app itself, the keyboard should come next
>
> What does VoiceOver move to currently after the Cancel button
>
>> On May 10, 2016, at 11:45 AM, Sean Howell <email@hidden> wrote:
>>
>> I’ve got a heavily composited view hierarchy. As views are added and removed I’m setting the .accessibilityElements property on my view controller. One of my transient views is a UISearchBar. I want to mimic the behavior I find in LaunchPad’s search, in which swiping right from the ‘Cancel’ button brings the focus to the keyboard (‘q’ button). How can I add the keyboard to .accessibilityElements that will work both with the default keyboard, and 3rd party keyboards?
>>
>> Thanks
>>
>> Sean Howell
>> _______________________________________________
>> 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
>
_______________________________________________
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