E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 9 (In chronological order)

From: glen walker
Date: Sat, Mar 30 2019 8:39AM
Subject: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?
No previous message | Next message →

I have buttons enabled in my VoiceOver rotor settings (iOS). When viewing
a webpage, I can change the rotor to "buttons" and then swipe up/down to
navigate by buttons. But if I'm in a native iOS app, such as the calendar
app, "buttons" does not appear on the rotor selection. The first several
elements in the calendar app are buttons so it seems like I should be able
to navigate to them via the rotor.

From: Birkir R. Gunnarsson
Date: Sat, Mar 30 2019 9:05AM
Subject: Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?
← Previous message | Next message →

VoiceOver options in native apps is much more limited than on web
content, so I think you got it there.


On 3/30/19, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
> I have buttons enabled in my VoiceOver rotor settings (iOS). When viewing
> a webpage, I can change the rotor to "buttons" and then swipe up/down to
> navigate by buttons. But if I'm in a native iOS app, such as the calendar
> app, "buttons" does not appear on the rotor selection. The first several
> elements in the calendar app are buttons so it seems like I should be able
> to navigate to them via the rotor.
> > > > >


--
Work hard. Have fun. Make history.

From: Maxability A11Y
Date: Sat, Mar 30 2019 9:13AM
Subject: Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?
← Previous message | Next message →

Interesting, I never realized. The rotor options on native apps are very limited. Perhaps only headings.


Regards - Rakesh,
M: 9948243336, E: = EMAIL ADDRESS REMOVED =
Sent from my iPhone

> On 30-Mar-2019, at 8:35 PM, Birkir R. Gunnarsson < = EMAIL ADDRESS REMOVED = > wrote:
>
> VoiceOver options in native apps is much more limited than on web
> content, so I think you got it there.
>
>
>> On 3/30/19, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
>> I have buttons enabled in my VoiceOver rotor settings (iOS). When viewing
>> a webpage, I can change the rotor to "buttons" and then swipe up/down to
>> navigate by buttons. But if I'm in a native iOS app, such as the calendar
>> app, "buttons" does not appear on the rotor selection. The first several
>> elements in the calendar app are buttons so it seems like I should be able
>> to navigate to them via the rotor.
>> >> >> >> >>
>
>
> --
> Work hard. Have fun. Make history.
> > > >

From: glen walker
Date: Sat, Mar 30 2019 9:21AM
Subject: Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?
← Previous message | Next message →

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 ADDRESS REMOVED = > wrote:

> VoiceOver options in native apps is much more limited than on web
> content, so I think you got it there.
>
>

From: Birkir R. Gunnarsson
Date: Sat, Mar 30 2019 2:30PM
Subject: Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?
← Previous message | Next message →

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 ADDRESS 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 ADDRESS 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.

From: Jonathan Cohn
Date: Sat, Mar 30 2019 4:01PM
Subject: Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?
← Previous message | Next message →

I thought I had remembered that there was a way to configure what rotor options an App needed, but now I don't know.

Best wishes,

Jonathan Cohn



> On Mar 30, 2019, at 11:13 AM, Maxability A11Y < = EMAIL ADDRESS REMOVED = > wrote:
>
> Interesting, I never realized. The rotor options on native apps are very limited. Perhaps only headings.
>
>
> Regards - Rakesh,
> M: 9948243336, E: = EMAIL ADDRESS REMOVED =
> Sent from my iPhone
>
>> On 30-Mar-2019, at 8:35 PM, Birkir R. Gunnarsson < = EMAIL ADDRESS REMOVED = > wrote:
>>
>> VoiceOver options in native apps is much more limited than on web
>> content, so I think you got it there.
>>
>>
>>> On 3/30/19, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
>>> I have buttons enabled in my VoiceOver rotor settings (iOS). When viewing
>>> a webpage, I can change the rotor to "buttons" and then swipe up/down to
>>> navigate by buttons. But if I'm in a native iOS app, such as the calendar
>>> app, "buttons" does not appear on the rotor selection. The first several
>>> elements in the calendar app are buttons so it seems like I should be able
>>> to navigate to them via the rotor.
>>> >>> >>> >>> >>>
>>
>>
>> --
>> Work hard. Have fun. Make history.
>> >> >> >> > > > >

From: glen walker
Date: Sat, Mar 30 2019 4:38PM
Subject: Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?
← Previous message | Next message →

Yes, you can configure your rotor via settings > general > accessibility >
voiceover > rotor

I have buttons checked and it shows up in my rotor on webpages but not for
apps.

On Sat, Mar 30, 2019 at 4:01 PM Jonathan Cohn < = EMAIL ADDRESS REMOVED = > wrote:

> I thought I had remembered that there was a way to configure what rotor
> options an App needed, but now I don't know.
>
>
>

From: Jonathan Cohn
Date: Sat, Mar 30 2019 5:19PM
Subject: Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?
← Previous message | Next message →

Glenn,

I was thinking on the developer side, I know that some apps add action items to the rotar. Can a developer of a native app also declare that there are buttons, articles or regions?

Best wishes,

Jonathan Cohn



> On Mar 30, 2019, at 6:38 PM, glen walker < = EMAIL ADDRESS REMOVED = > wrote:
>
> Yes, you can configure your rotor via settings > general > accessibility >
> voiceover > rotor
>
> I have buttons checked and it shows up in my rotor on webpages but not for
> apps.
>
> On Sat, Mar 30, 2019 at 4:01 PM Jonathan Cohn < = EMAIL ADDRESS REMOVED = > wrote:
>
>> I thought I had remembered that there was a way to configure what rotor
>> options an App needed, but now I don't know.
>>
>>
>>
> > > >

From: glen walker
Date: Sat, Mar 30 2019 5:33PM
Subject: Re: Does the VoiceOver (iOS) rotor only allow form element navigation on webpages?
← Previous message | No next message

Yes, a developer can have an "adjust value" customized rotor setting.

If the developer uses a UIButton, it should be exposed as a button to the
accessibility API and the developer shouldn't have to do anything for the
button setting in the rotor to work.

On Sat, Mar 30, 2019 at 5:19 PM Jonathan Cohn < = EMAIL ADDRESS REMOVED = > wrote:

> Glenn,
>
> I was thinking on the developer side, I know that some apps add action
> items to the rotar. Can a developer of a native app also declare that there
> are buttons, articles or regions?
>
> Best wishes,
>
> Jonathan Cohn
>
>
>