WebAIM - Web Accessibility In Mind

E-mail List Archives

The buttons versus links debate

for

From: Iaffaldano, Michelangelo
Date: Jan 25, 2013 1:02PM

I would argue that in your scenarios either option is equally usable, provided that the link / button text and placement make the action very clear. But only usability testing can answer that with some certainty. This is equally true of no-AT users.
Cheers,
Michelangelo

-----Original Message-----
From: Sarah Ward [mailto: <EMAIL REMOVED> ]
Sent: January 25, 2013 4:25 AM
To: <EMAIL REMOVED>
Subject: [WebAIM] The buttons versers links debate

Hi everyone,

I'm trying to clarify when we should use a button rather than a link so that we can use the two consistently and provide the most appropriate experience to AT users.

Most of the time this is pretty simple: Use a link when it takes the user to another page, and use a button where the action is creating, adding, editing or deleting something. But there are a few scenarios I'm still struggling with and would like your advice on, particularly from what a screen reader user would expect or look for in these situations.

Situation 1) 

We have an 'Email to a friend' button (or link?) which opens an overlay which acts like a modal dialog. The user can then enter the appropriate details to send their information to a friend and submit (which definitely should be a button). Selecting the link that triggers this overlay is not actually editing any data at this point, its just showing some additional view/content and moving focus, so would this be classified as an internal link, or a button because the user is making an action to do something even though it is not modifying any data?

Situation 2)

We have a long form that is split into sections, and these sections collapse and expand as the user moves thorough the process on a single page. However the user can edit a section already completed using an 'Edit' link (or button?) Upon selecting this, the section expands and allows the user to edit the information they originally provided. My concern here is that all that happens by pressing this button did is expand information and display the appropriate form fields again. The user has not actually at this point edited any data. I don't think this can be considered an internal link either. The page unfortunately would not work at this point without JavaScript (a decision out of my control) in case this would be a deciding factor.

I would be interested to know which you think would be best in each case. Does anyone know of a good resource that defines when to use a link or button. My google searches have so far had mixed results. There's also the 'close' link debate to add to the overall confusion.

Thanks,
Sarah