How should buttons, links, and actions differ?
Choose links and buttons by their results, then define action priority and destructive-action guidance.
Buttons usually perform actions; links usually take users to another location. Determine the result before choosing appearance and page semantics so behaviour is predictable.
Keep these basics in mind
- Opening service details usually calls for a link. Saving, expanding content, and submitting a form usually call for buttons.
- They can look similar, but their web structure and behaviour still need to match their purposes. See USWDS button guidance and link guidance .
- A primary action is the most relevant next step in the current task. Secondary actions support it. Give actions clear priority rather than making all equally prominent.
- Hard-to-reverse actions such as deletion need their object and consequences explained. Icon buttons also need understandable names.
Choose an action part
Illustrative action classification
These are teaching scenarios.
| Entry | Result | Usual choice |
|---|---|---|
| View plan | Open plan details | Link |
| Save profile | Submit current edits | Button |
| Delete member | Perform deletion | Button with clear consequence guidance |
Walk through an example
On a plan page, View details opens another page. Start trial is also a link if it opens registration. Create account inside the registration form submits information and is a button. The team checks destinations and submission results so similar styling does not hide different action types.
Limits and common misunderstandings
Looking like a button does not establish purpose. Destructive actions do not all need identical confirmation dialogs; choose based on consequences and recovery options. Colour alone is insufficient: explain the action and its object.