WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?

for

From: Birkir R. Gunnarsson
Date: Mar 30, 2019 2:30PM

Apple moves in mysterious ways.
I guess their assumption is that native apps have a lo more limited
set of components.
I need to check whether the rotor is context dependent (VoiceOver
checks what types of controls are on the screen and adjusts the rotor)
though in my informal experience I think it is not.


On 3/30/19, glen walker < <EMAIL REMOVED> > wrote:
> 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.
>>
>>
> > > > >


--
Work hard. Have fun. Make history.