E-mail List Archives
Re: Missing control type of components in mobile
From: Srinivasu Chakravarthula
Date: Aug 3, 2017 1:59AM
- Next message: Srinivasu Chakravarthula: "Re: The Accessibility of Browser-based Development Environments"
- Previous message: surbhi Mudgal: "Missing control type of components in mobile"
- Next message in Thread: Patrick H. Lauke: "Re: Missing control type of components in mobile"
- Previous message in Thread: surbhi Mudgal: "Missing control type of components in mobile"
- View all messages in this Thread
I would mark it as a violation. Unless announcing role of an element, user
would not know it it's a button that does some action or link or something
else...
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 Thu, Aug 3, 2017 at 12:19 PM, surbhi Mudgal < <EMAIL REMOVED> >
wrote:
> Hi All,
>
> Hope all doing good.
>
> In mobile while testing an application on android with talkback observe
> that control type of the elements are not announced on focusing but
> talkback gives the instruction "double tap to activate".
>
> It's a violation under WCAG4.1.2 if the role is not exposed to screen
> readers but what could be the impact if control type is missing announcing
> the instructions like "double tap to activate"? Hearing to instruction user
> for sure activates items and I would like to know which users have more
> impact due to this behavior?
>
>
> Regards,
> Surbhi Mudgal.
> > > > >
- Next message: Srinivasu Chakravarthula: "Re: The Accessibility of Browser-based Development Environments"
- Previous message: surbhi Mudgal: "Missing control type of components in mobile"
- Next message in Thread: Patrick H. Lauke: "Re: Missing control type of components in mobile"
- Previous message in Thread: surbhi Mudgal: "Missing control type of components in mobile"
- View all messages in this Thread