E-mail List Archives

Search E-mail List Archives for

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

From: Ajay Sharma
Date: Sun, Feb 18 2018 2:59AM
Subject: Few questions related to mobile app accessibility
No previous message | Next message →

Hi,

We have an app for both iOS and Android that works on VoIP much like Skype, where the buttons like mute, disconnect, start audio call start video call etc do not have any role associated. So on this we have different opinions, first, it is obvious from the label of the elements that would make the user understand that it is interactive and what would happen upon double tapping on that, this situation could commonly be seen in apps nowadays such as items under hamburger menus generally do not have any role another instance could be in mailing apps, the emails in the lists do not have any role.
The second opinion wants to have buttons as roles for those elements

Another situation is if it is good to make screen reader announce "expanded / collapsed" upon hamburger menus even if the focus is limited within the menu until it is closed?

Lastly, making screen reader announce "selected" on the tabs that appear on the app and take screen reader focus to the content of expanded tab would fall under compliance issue or under usability?

Looking forward for your thoughts on what should be the best behaviour in this situation.

Best Regards,
Ajay

From: Srinivasu Chakravarthula
Date: Sun, Feb 18 2018 3:37AM
Subject: Re: Few questions related to mobile app accessibility
← Previous message | No next message

I believe it's important to have roles assigned to elements unless you are
using native elements. So that accessibility APIs are supported. Mark-up is
more for machine to understand than real users.

Yes, announcing state of elements provides better experience to the users.

Thanks,
Vasu

Regards,

Srinivasu Chakravarthula - Twitter: http://twitter.com/CSrinivasu/
Website: http://www.srinivasu.org | http://serveominclusion.com

Let's create an inclusive web!

Lead Accessibility Consultant, Informatica


On Sun, Feb 18, 2018 at 3:29 PM, Ajay Sharma < = EMAIL ADDRESS REMOVED = >
wrote:

> Hi,
>
> We have an app for both iOS and Android that works on VoIP much like
> Skype, where the buttons like mute, disconnect, start audio call start
> video call etc do not have any role associated. So on this we have
> different opinions, first, it is obvious from the label of the elements
> that would make the user understand that it is interactive and what would
> happen upon double tapping on that, this situation could commonly be seen
> in apps nowadays such as items under hamburger menus generally do not have
> any role another instance could be in mailing apps, the emails in the
> lists do not have any role.
> The second opinion wants to have buttons as roles for those elements
>
> Another situation is if it is good to make screen reader announce
> "expanded / collapsed" upon hamburger menus even if the focus is limited
> within the menu until it is closed?
>
> Lastly, making screen reader announce "selected" on the tabs that appear
> on the app and take screen reader focus to the content of expanded tab
> would fall under compliance issue or under usability?
>
> Looking forward for your thoughts on what should be the best behaviour in
> this situation.
>
> Best Regards,
> Ajay
> > > > >