# Target Action: Make the Button People Should Press Obvious

> Learn how to make one main button clear, easy to read, easy to press, and easy to understand at a glance.

**In short:** A target action is the one main button a screen wants people to press, and it should be clear, easy to read, easy to press and easy to understand.

From "UI/UX basics", a free course by Venkat R. Murty: https://designervenkat.online/learn/ui-ux/target-action

## What is a target action?

A target action is the one thing you most want a person to do on a screen. Designers often call this a call to action, or CTA. It usually appears as a button, such as one that says Save or Sign up. This lesson shows how to make that button clear, easy to press, and easy to understand.

Most people do not read a web page word by word. They scan. A button must therefore make sense in a quick glance.

- **Call to action (CTA):** The step you want a user to take, such as signing up or paying.
- **Primary button:** The main button on a screen. It is styled to stand out most.
- **Secondary action:** A helpful extra choice. It is shown more quietly than the main button.
- **Microcopy:** Short text in an interface, such as button labels and error messages.
- **Tap target:** The area on screen that responds when someone clicks or taps.

## Why give each screen one main action?

Show one primary button on each screen. If two buttons look equally strong, people hesitate and must choose between them. Give the main action a solid colour and make the other choices plainer.

- **Main button:** Filled with a strong colour and placed where the eye lands after the content.
- **Quiet choice:** An outline button or plain text link for an optional step.
- **Link or button:** Buttons trigger an action on the page. Links take the user to another page or section.

Good labels make the main button work. A label should tell the user what they get, and it should be short.

### How do you write labels that name the result?

A label should describe the outcome, not the system. The label Send invoice tells the user more than Submit does.

1. **Start with a verb:** Begin with a word like Save, Download, or Book.
2. **Name the result:** Say what the user gets. Avoid words that only describe the software.
3. **Read it aloud:** Ask whether a first-time user would know what happens when they press it.
4. **Match the rest of the product:** Use the same words for the same action on every screen.

> **Tip:** Avoid vague labels such as OK. They leave people guessing about what will happen next.

## How do you make the button easy to press?

A button must be big enough to press with a finger or a mouse. The Web Content Accessibility Guidelines (WCAG) set a minimum size for clickable areas called pointer targets. Under WCAG 2.2, a pointer target should be at least 24 by 24 CSS pixels. A CSS pixel is the unit designers use when they set widths and heights in a web page.

If a target is smaller, it can still pass when enough empty space surrounds it. The stricter AAA level asks for 44 by 44 CSS pixels. In short, a smaller target is not automatically a failure. The rule lists exceptions, such as enough spacing around the target, an equivalent control that does the same job, an inline link inside a sentence, a control the browser itself sets, and an essential control that cannot be made larger without losing its purpose.

> **Tip:** Padding can make the clickable area larger without changing how the button looks.

## How do you make the button stand out?

- **Contrast:** The button colour should differ clearly from the background. One guide argues that contrast matters more than the exact colour.
- **Room to breathe:** Leave empty space around the button so other items do not crowd it. Fingers are larger than a mouse pointer.
- **Right moment:** Place the button where the user has enough information to decide. Some guides advise this.
- **Same look:** Style the same kind of button the same way across the product, so people learn it once.

## Check labels with a small script

This script flags labels that are vague or too long. The limit of five words is a simple rule chosen for this example, not an official standard.

```python
labels = ['Submit', 'Save changes', 'OK', 'Download the free guide and print it today']
vague = ['submit', 'ok', 'click here']
for label in labels:
    words = label.split()
    if label.lower() in vague:
        print(label + ': vague')
    elif len(words) > 5:
        print(label + ': too long')
    else:
        print(label + ': good')
```

Output:

```text
Submit: vague
Save changes: good
OK: vague
Download the free guide and print it today: too long

```

## Quick check

**Quick check:** Which label is best for the main button that saves a form?

A. Submit
B. OK
C. Save changes
D. Click here

**Answer:** C. Save changes starts with a verb and names the result. Submit names the system's action, and OK and Click here are vague.

## Sources

- [Equal Web: WCAG 2.5.8 Target Size (Minimum), how to meet it](https://www.equalweb.com/wcag/criteria/2-5-8/)
- [WCAG rules: 2.5.8 Target Size (Minimum), Level AA](https://wcagrules.com/learn/2-5-8-target-size-minimum)
- [accessibility.build: WCAG 2.5.8 Target Size (Minimum) guide](https://accessibility.build/wcag/2-5-8)
- [Calling All Minds: WCAG 2.5.8 Target Size Minimum explained](https://callingallminds.com/resources/wcag/2.5.8-target-size-minimum)
- [Digital Accessible: WCAG target size, the 24 by 24 pixel rule](https://digitalaccessible.com/wcag-target-size/)
- [SaaS Factor: UX button design, types and principles](https://www.saasfactor.co/blogs/ux-button-design)
- [eChai Ventures: how to write clear button and error messages](https://echai.ventures/startingup/product-design-ux/how-do-i-write-clear-button-and-error-messages-so-users-know-exactly-what-to-do-next)
- [Parallel HQ: 10 UX writing principles, 2026 guide](https://www.parallelhq.com/blog/ux-writing-best-practices)
- [Websitespellchecker: website microcopy examples](https://www.websitespellchecker.com/articles/website-microcopy-examples)
- [Patrick Iverson: microcopy, the smallest words on your website](https://patrickiverson.com/working-with-a-designer/microcopy-smallest-words-website/)
- [Design Radar: best practices for designing buttons](https://designradar.substack.com/p/best-practices-for-designing-buttons)
- [Canvas Builder: call-to-action button design tips](https://canvasbuilder.co/blog/cta-button-design-tips-2)
- [Witscode: CTA button best practices](https://witscode.com/blogs/cta-button-best-practices)
- [Button Design Guide (Goodreads author blog)](https://www.goodreads.com/author_blog_posts/20216082-button-design-guide-how-to-get-site-visitors-to-actually-click-your-but)
- [FNA Technology: UX writing and microcopy rules](https://fnatechnology.com/blog/ux-writing-microcopy-best-practices)
