WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Link vs Button for "Cancel"

for

From: JP Jamous
Date: Jan 8, 2018 1:46PM

In addition, I have found it to be an excellent UX design practice to use role="button" if the link is styled as a button visually. I cannot count the many times I would be interacting with a sighted user and state, "Click on the whatever link." The user would always say, "I don't see a link, rather a button." In some situations, it can be quite confusing.

I know this does not fall under WCAG, but I find it a best user experience for users across the board.

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Steve Faulkner
Sent: Monday, January 8, 2018 2:34 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Link vs Button for "Cancel"

>
> The "cancel" takes the user to another page thus behaves like a link.


does it have a href with a URL? if so sounds like a link to me

--

Regards

SteveF
Current Standards Work @W3C
<http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w3c/>;

On 8 January 2018 at 20:28, Renato Iwashima < <EMAIL REMOVED> > wrote:

> Hi,
>
> I have a form that contains a submit button and a cancel link. The "cancel"
> takes the user to another page thus behaves like a link.
>
> But because it is a destructive action and is related to the form, I
> wonder if it should actually be a button. If thats the case, does it
> mean I need to implement JS to actually route the user to navigate to a different page?
> Can I just leave it as a link?
>
> Thanks!
> > > archives at http://webaim.org/discussion/archives
> >