E-mail List Archives
Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?
From: glen walker
Date: Mar 30, 2019 9:21AM
- Next message: Karlen Communications: "Re: Making Accessible PDF's Without Using Adobe Pro"
- Previous message: Maxability A11Y: "Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?"
- Previous message in Thread: Maxability A11Y: "Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?"
- View all messages in this Thread
From a web perspective, if Safari is surfacing a <button> element via the
UIAccessibility API so that VoiceOver knows how to announce it, and if a
button in a native app is announced the same way so presumably is also
going through the UIAccessibility API, why couldn't the button setting on
the rotor work on a native app?
On Sat, Mar 30, 2019 at 9:05 AM Birkir R. Gunnarsson <
<EMAIL REMOVED> > wrote:
> VoiceOver options in native apps is much more limited than on web
> content, so I think you got it there.
>
>
- Next message: Karlen Communications: "Re: Making Accessible PDF's Without Using Adobe Pro"
- Previous message: Maxability A11Y: "Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?"
- Previous message in Thread: Maxability A11Y: "Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?"
- View all messages in this Thread