WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Link vs Button for "Cancel"

for

From: Birkir R. Gunnarsson
Date: Jan 9, 2018 9:15AM

Yeah, I forgot to add to my last post that we should use ARIA to
replicate the element's visual appearance except in situations where
that might prevent the user from operating the control.
In the case of link that looks like a button, add a button role, for
the exact reasons that Don explained.
The developer chose to use the incorrect semantics for a button, but
it still looks like a button, and people will refer to it as a button,
they don't dig into the code. So the assistive technology user should
perceive it as a button.




On 1/9/18, Don Mauck < <EMAIL REMOVED> > wrote:
> I disagree, from a training and support standpoint, if you tell someone to
> find a button, that's what they would expect to find. It is fine if you
> visual folks want things to look a certain way, but if you want it to look
> like a button, then at least use a "role=button". To me, any action control
> would be a button. Cancel may leave a page, however, I see in many of our
> applications "cancel" performs a partial page refresh, thus never leaving
> the page. I believe that in general, buttons perform actions and links take
> you somewhere even if it is on the same page.
> I think we need to remember that not all users will understand that when
> told to find a "button," it could be a link instead. No need to make things
> any more convoluted than necessary.
>
>