Re: iOS 4 custom alert view
Re: iOS 4 custom alert view
- Subject: Re: iOS 4 custom alert view
- From: Chris Fleizach <email@hidden>
- Date: Tue, 24 Jan 2012 08:46:55 -0800
In 5.0 we added
- (BOOL)accessibilityViewIsModal and
- (BOOL)accessibilityElementsHidden
to help this situation.
Your only option in 4.3 is to iterate the entire sub-tree setting isAccessibilityElement = NO
On Jan 24, 2012, at 8:40 AM, Fritz Anderson wrote:
> My iPad app must be runnable on iOS 4.3, and has to collect passwords. Because iOS 4 did not provide a password dialog, I have to provide my own.
>
> The way I do this is to overlay my view with an image view that blocks access to the root view, and then put a password pseudo-dialog view on top of that. The pseudo dialog contains a prompt label, a secure text field, and two cancel/OK buttons. When the dialog view appears, I announce the prompt.
>
> The problem is that VoiceOver doesn't understand that the buttons I'm blocking should no longer be available. Now that I think of it, that's reasonable.
>
> When the password view appears, VoiceOver speaks the first word of my announcement, and then selects and speaks the bar button that reveals the master view. Other tap/swipe selections seem to be inactive, but if the user double-taps at the bar button selection, my app is in an unanticipated state.
>
> What are my options? Do I have to disable (or turn off isAccessibilityElement) for all my interactive elements before showing my dialog?
>
> — F
>
>
> _______________________________________________
> 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