E-mail List Archives
Re: Mobile Native apps - buttons that use colours and text without any borders.
From: Birkir R. Gunnarsson
Date: Jan 25, 2020 2:06PM
- Next message: Jonathan Avila: "Re: Mobile Native apps - buttons that use colours and text without any borders."
- Previous message: Jonathan Cohn: "Re: VoiceOver getting 'stuck'"
- Next message in Thread: Jonathan Avila: "Re: Mobile Native apps - buttons that use colours and text without any borders."
- Previous message in Thread: Murphy, Sean: "Re: Mobile Native apps - buttons that use colours and text without any borders."
- View all messages in this Thread
1.4.1 it is, but it explicitly applies to links embedded in a block of text.
I've found it weird that some WCAG requirements only apply to links
(1.4.1 and 2.4.4). I think all labels of interactive elements should
be unique (or unique in context) and you could just as well have a
button in the middle of a block of text as a link (else you can just
change the role of the link to a button to avoid having to pass either
requirement).
To the actual topic of discussion, 2.4.7 (keyboard focus) basically
gives you a pass if you are using operating system/browser defaults
for keyboard focus outline. Since this sitaution is similar I think
WCAG should give you a pass on it.
Since we care more about users than conformance, one big difference
between a native mobile app and the web is that the assistive
technologies are biult into the device itself (or at least the vast
majority of the devices we are looking at), unlike computers where you
often have to download, even purchase the assitsive technology you
need.
So I see an argument in users easily being able to configure operating
system buttons to have an outline, if it is a matter of changing a
setting (then again, we often rely on users being able to discover
these settings, just like we expect users to know how to navigate
tables, both assumptions tend to be wrong).
On the balance of things, I think this is acceptable, but wonder why
both operating systems have gotten away from visually presenting
actionable items as such, don't they want users to click buttons?
On 1/23/20, Murphy, Sean < <EMAIL REMOVED> > wrote:
> Steve,
>
> Your referring to SC 1.4.1 where you cannot only use colour alone. This is
> a mobile native app, not web. The sc 1.4.11 I will have a look at, thanks
> for that pointer.
>
> The standards provided are great. But I am more concern on everyday usage
> that this is occurring in all mobile native apps on both platforms on how
> people with Low vision and Colour Blindness are handling it. What about
> people who have cognitive issues as well. Has anyone done any studies in
> this space to find out if these types of buttons are easily understood and
> comprehended?
>
> Regards
> Sean Murphy
>
>
>
- Next message: Jonathan Avila: "Re: Mobile Native apps - buttons that use colours and text without any borders."
- Previous message: Jonathan Cohn: "Re: VoiceOver getting 'stuck'"
- Next message in Thread: Jonathan Avila: "Re: Mobile Native apps - buttons that use colours and text without any borders."
- Previous message in Thread: Murphy, Sean: "Re: Mobile Native apps - buttons that use colours and text without any borders."
- View all messages in this Thread