UX Collective

We believe designers are thinkers as much as they are makers. https://linktr.ee/uxc

Follow publication

Should “cancel” be a button or a link?

Which one is UX best practice?

Karim Maassen
UX Collective
Published in
10 min readMar 21, 2022

Cancel as a link vs. Cancel as a button
Cancel as a link vs. Cancel as a button

A common type of dialogue that is often presented when interacting with a web app, is the “cancel” option. Usually when the user is filling out a form, or manipulating data (e.g. inside a side panel, detail page or modal view). One would typically see it next to a primary action, presented as a link. More and more however, this cancel option is presented as a button. Is this good or bad practice, and why?

Navigation vs. Action

When looking at a web app, a user typically has to deal with two types of interaction: navigation and actions. Both types of interactions are usually represented in a different but distinct way.

  1. Navigation is a link.
  2. Action is a button.

Why is this? Links stem from the early days of the world wide web. It’s what it makes it be a web (and also world-wide). Buttons are a form of skeuomorphism that translates the physical world of flipping switches and pressing buttons to do stuff, into the digital world of the internet. And thus, they are used differently:

Actions are manipulation of data the user is managing through the interface of the web app, while navigation is a state change of the interface the user is, well, navigating through. In other words, links (or navigation) don’t lead to changes of the underlying data, but can lead to the presentation of new pages, or a different presentation of the current page the user is navigating in (i.e. change the view). So when we look at it this way, we are basically saying that navigation is a state change of the UI and an action is data manipulation. In other words, going from one state to the other is the same as navigating from one state to the other. I’d like to note that actions (buttons) can lead to navigation, but it’s not a requirement.

Flow diagram indicating creating a new resource from a list of resources, making the user navigate to the newly created resource detail page.
Distinction between navigation ans actions

UI Design
How one would visualize a link and button is of course a design style decision, but typically links are blue underlined text and buttons are boxes with text inside of them. Both links and buttons can contain icons to emphasize the…

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Written by Karim Maassen

Product Design. Web Developer. Dutch Entrepreneur. Digital Communications Expert & Internet Pioneer. Founder of http://nwzer.com; User-generated News

Responses (25)

Write a response

Your conclusions do not take accessibility into account. They make it harder for people who like myself, who rely on assistive technology. Please reassess based on inclusive principles. As a keyboard only user, I have expectations of how a button…

--

I think we as designers get very hung up on the link vs buttons decision and for most users, it is much more simple: just click the thing that matches what I want to do.
Thus, the link vs button doesn't matter to users as much as "can I find the…

--

Hi, Karim!
As designers I'm guessing we agree that consistency is important. There is an organ which exists to create consistency online, namely w3.org. In their WCAG documentation it is stated that "A button is a widget that enables users to trigger…

--