WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Web accessibility questions

for

From: Patrick H. Lauke
Date: Mar 9, 2019 12:26PM

On 09/03/2019 18:58, JP Jamous wrote:
[...]
> When it comes to someone like me who is blind and relies on JAWS versus my wife who is sighted, we start arguing. She tells me to click on the "transfer" button and JAWS is reading it as "Transfer" link. I almost lost my marriage and ended up in a divorce because of this type of implementation. *Smiles*

Pro tip: most non-AT users don't understand nor care about the
difference between a button or a link. Especially if they also use
native applications, where there's no such tangible distinction anyway.
The important thing is that if something behaves as a link, it should be
coded as a link, and if something behaves as a button, it should use a
<button> (or relevant <input>) element. How it's then styled is mostly
irrelevant to regular users, and it's quite common for prominent links
to be styled as pills/buttons/etc. It's not an unusual visual
presentation. For communication purposes, it's either easiest to just
refer to things as "controls" in general (which covers both), or...to
just have a bit of understanding that button and link are likely to be
used interchangeably by non-AT users. No need to call a divorce lawyer
over hairsplitting ;)

P
--
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke