WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [iOS app] acctivate button inside tile

for

From: Jonathan Cohn
Date: Nov 22, 2023 8:52AM

VoiceOver has a "QuickNav" mode where the arrow keys act just like swipe
actions. Does this answer your question?

On Wed, Nov 22, 2023 at 8:44 AM David Farough < <EMAIL REMOVED> >
wrote:

> I am only guessing here, but if an additional swipe takes you to the
> button, then it should be reachable using the right arrow key.
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Graham Armfield
> Sent: Wednesday, November 22, 2023 7:45 AM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] [iOS app] acctivate button inside tile
>
> Hi All,
>
> I know the discussion so far has focused on Voiceover users and
> differentiating between multiple interactive elements. But I'm also
> wondering about the experience for keyboard users who have hooked up their
> Bluetooth keyboards to their iPhone. How do they differentiate between the
> items?
>
> Regards
> Graham Armfield
> Coolfields Consulting
>
> On Mon, 20 Nov 2023, 6:14 pm Malthe Jepsen, < <EMAIL REMOVED> > wrote:
>
> > That's an excellent question. For what it's worth I love the
> > flexibility of VoiceOver actions in the rotor, as it minimizes the
> > amount of elements in the focus order, which makes navigation through
> > dynamic content, such as a feed, much more efficient, as it requires
> les swipes per new item.
> > I would advocate for including the secondary actions, such as "add to
> > favorites", in the rotor.
> > Lots of other apps do this, including Apple's own phone and mail apps.
> > Regarding your question about it being announced late in the reading
> flow:
> > This is VoiceOver standard behaviour, so hopefully the user will catch
> > it or attempt engaging the rotor. You can also add an accessibility
> > hint to the item in question to emphasize that the rotor can be used
> here.
> > Keep in mind that this is just my personal opinion.
> >
> > Best
> > Malthe
> > > On 20 Nov 2023, at 14.02, Bart Simons < <EMAIL REMOVED> >
> wrote:
> > >
> > > Hello,
> > >
> > > We test the accessibility of an iOS app. There are tiles with a
> > relatively long information. You click the tile to perform an action.
> > But the tile also contains a button that triggers a different action
> > such as an "Info" icon that provides more information or an asterisk
> > to mark as favorite.
> > >
> > > The developers have grouped the information so that VoiceOver reads
> > > the
> > whole tile content in one go and no need for multiple swipe actions to
> > read the tile's content. This is helpful as not to loose context.
> > >
> > > But the developers say that they don't know to make the button
> > > inside
> > the tile accessible. Ideally it can be reached with the next swipe but
> > developers say they cannot focus a button that is part of a tile that
> > in itself is clickable.
> > >
> > > Is there really no way to do that?
> > >
> > > They propose to add a custom action to the tile. Swiping down with
> > VoiceOver would then provide access to "more info" or "mark as favorite".
> > >
> > > I have a few remarks on this:
> > > VoiceOver announces the existence of custom actions only after
> > > reading
> > the relatively long information in the tile. It is very likely that a
> > VoiceOVer user will not listen until the end and thus not discover the
> > message that custom actions are available.
> > >
> > > I think that custom actions are meant as shortcuts to provide quick
> > access to actions that also can be performed in another way. Is it
> > acceptable that a function is only available through a custom action?
> > >
> > > Do you know of a better soulution to, on the one hand group
> > > information
> > in a clickable tile but on the other hand also provide access to a
> > button inside the tile?
> > >
> > > Thanks in advance
> > >
> > > Bart Simons
> > > AnySurfer - Voor een toegankelijker internet
> > > +32 2210 6149
> > > https://ww/
> > > w.anysurfer.be%2F&data%7C01%7Cdavid.farough%40cfp-psc.gc.ca%7Cd76
> > > 92cd5494f4ac2060308dbeb58f120%7C961b30aad4394bc7b6749c4a389b0be3%7C0
> > > %7C0%7C638362539467951250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD
> > > AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sda
> > > ta=V5sSoNTEE2UorVaBCtlAaQlt%2Fm2B3XWpfq8NZxa0dpc%3D&reserved=0
> > >
> > >
> > > > > > > > > http://lis/
> > > t.webaim.org%2F&data%7C01%7Cdavid.farough%40cfp-psc.gc.ca%7Cd7692
> > > cd5494f4ac2060308dbeb58f120%7C961b30aad4394bc7b6749c4a389b0be3%7C0%7
> > > C0%7C638362539467951250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAi
> > > LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata
> > > =%2BLfkiaMOi2xy45b4NKKo%2F0BzA7enVbakNyeWB%2Fklnt4%3D&reserved=0
> > > List archives at
> > > http://web/
> > > aim.org%2Fdiscussion%2Farchives&data%7C01%7Cdavid.farough%40cfp-p
> > > sc.gc.ca%7Cd7692cd5494f4ac2060308dbeb58f120%7C961b30aad4394bc7b6749c
> > > 4a389b0be3%7C0%7C0%7C638362539467951250%7CUnknown%7CTWFpbGZsb3d8eyJW
> > > IjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300
> > > 0%7C%7C%7C&sdata=%2F77NjA9pC2%2FsXYz9KLo633j2cq9jgSHMnRQd66h1KRg%3D&
> > > reserved=0 > >
> > > > > > http://list/.
> > webaim.org%2F&data%7C01%7Cdavid.farough%40cfp-psc.gc.ca%7Cd7692cd54
> > 94f4ac2060308dbeb58f120%7C961b30aad4394bc7b6749c4a389b0be3%7C0%7C0%7C6
> > 38362539467951250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi
> > V2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BLfkiaM
> > Oi2xy45b4NKKo%2F0BzA7enVbakNyeWB%2Fklnt4%3D&reserved=0
> > List archives at
> > http://webai/
> > m.org%2Fdiscussion%2Farchives&data%7C01%7Cdavid.farough%40cfp-psc.g
> > c.ca%7Cd7692cd5494f4ac2060308dbeb58f120%7C961b30aad4394bc7b6749c4a389b
> > 0be3%7C0%7C0%7C638362539467951250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4w
> > LjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C
> > &sdata=%2F77NjA9pC2%2FsXYz9KLo633j2cq9jgSHMnRQd66h1KRg%3D&reserved=0
> > > >
> > > > > > > > >