Button Design: Make Calls to Action Easier to Click
Good button design means a button that looks pressable, is big enough for a thumb, says what happens when you press it, and stands out from the page. Build hover, focus, pressed and disabled states, keep contrast strong, and allow one primary action per screen. Seed Light builds buttons this way.

A button is the smallest part of a website and the only part that matters at the moment somebody decides to act.
Most button design ui fails in ordinary ways. Too small for a thumb, too faint to find, labelled with a word that promises nothing.
This guide covers the five things that make a button work, with the accessibility rules that apply to each, and the mistakes worth checking for today.
Key Takeaways
- It must look pressable. A styled box, not a line of coloured text.
- Size it for a thumb. Phones are where buttons get pressed.
- One primary action per screen. Everything else steps back.
- Label the outcome. Submit tells somebody nothing at all.
- Build every state. Hover, focus, pressed and disabled.
What Makes a Good Button
A button has to announce itself before anybody reads it. People scan a page for things that look pressable, and anything that does not look pressable is skipped.
That means a solid shape with real padding, a background that separates it from the page, and enough weight to read as an object rather than as a sentence.
A coloured text link can do the same job in a quieter place, such as inside a paragraph. It is the wrong choice for the main action, because it has no shape to find.
Button styles ui kits usually give you three or four variants, and the rules below apply to all of them. Icons are worth a word here. An icon beside the label helps recognition, and an icon on its own asks the visitor to guess, so keep the words.
The test is to squint at a page until the words blur. If you cannot see where to press, neither can anybody else.
Padding is what most home made buttons get wrong. A label pressed tight against the edges reads as a label with a box drawn around it rather than as something built to be pressed.
Give it room on all four sides, and more at the sides than the top. That proportion is what makes a button look like a button.
Shape is the other half of the question people ask. Rounded or square makes little difference to usability, and consistency across the site makes a great deal.

Five Rules for Button Design
In the order they usually need fixing on a site that already exists. Each one is a setting rather than a project, and most of them take minutes.
1. Size it for a thumb
Buttons are pressed by thumbs, on phones, often while the person is walking or holding something else.
The accessibility floor is specific. WCAG 2.2 sets a minimum target of 24 by 24 CSS pixels at level AA, and the enhanced criterion asks for 44 by 44.
The platform guidelines are more generous than the floor. Apple asks for 44 points and Android asks for 48 density independent pixels. That is roughly the pad of a thumb.
Treat the minimum as a legal floor and the platform figures as the design target. A button that only just passes is still annoying to press.
The floor exists for a reason that has nothing to do with compliance. People with tremor, people with large hands, and people holding a baby all press the same button you do.
Spacing matters as much as size. Two correctly sized buttons placed tight together produce the same mis taps as one small button.

2. Make it stand out
Cta button design starts with contrast. Your main action should be the highest contrast element on the screen. If it blends into the design, the design has won an argument it should have lost.
Contrast has measurable rules. Text needs a ratio of at least 4.5 to 1 against its background, and the button shape itself needs at least 3 to 1 against what surrounds it.
That second rule is the one people miss. A pale grey outline button on a white background can have perfectly legible text and still be invisible as a button.
Dark mode catches people out as well. A colour chosen against white can sit at a comfortable contrast there and fail completely on a dark background.
Colour alone is never enough either. Around one in twelve men has some form of colour blindness, so a green save and a red delete must also differ in label, position or shape.
Test it outdoors if you can. A contrast that looks generous on a desktop in a dark office disappears on a phone in daylight.
Pick one accent colour for the primary action and use it for nothing else. A colour that means press this loses its meaning the moment it appears on a heading.

3. One primary action per screen
Three levels is enough for almost any interface. Primary, secondary, tertiary.
The primary is solid and loud, and there is exactly one of it. The secondary is outlined or muted. The tertiary looks like a link and sits out of the way.
Two equally loud buttons side by side create a decision where you wanted an action. The visitor pauses, and some of them pause permanently.
Decide what you most want somebody to do on each page, then make everything else quieter. That is the whole of hierarchy.
The same applies to repeating the primary action down a long page. That is still one decision shown several times. It is different from offering two.
Cancel is the common offender. It usually belongs as a text link rather than as a button with equal weight to the thing you want pressed.

4. Say what happens
Submit is the default label in most form tools and it is the worst word available.
It describes what the software does rather than what the person gets. Get my free quote, Book my slot, Send my enquiry. The verb and the outcome, in that order.
The difference is measurable in how people describe it afterwards. A visitor who pressed Get my free quote knows what they did, and one who pressed Submit does not.
Keep it short. Two to four words fits comfortably on a phone without wrapping, and a wrapped button label looks broken.
Write it in the visitor's voice rather than yours. My quote reads as theirs, your quote reads as a form you are making them fill in.
Avoid words that describe the mechanism. Continue, Next and Proceed all tell somebody that something will happen without telling them what.
Then say what happens next underneath, in small text. Whether a human replies, and roughly when, is the question everybody has at that moment.

5. Build every state
A button has five states and most sites ship two of them.
Normal, hover, focus, pressed and disabled. Each one answers a question somebody is asking with their hand or their keyboard.
Focus is the one that gets deliberately removed, usually because a visible ring was thought ugly. Anyone navigating by keyboard then loses all sense of where they are on the page.
Design a focus ring you like rather than deleting the one you were given. It is the only state some of your visitors will ever see.
Pressed matters on a phone, where there is no hover at all. Without it, a tap on a slow connection feels like nothing happened, and people press again.
Disabled deserves care too. A greyed out button with no explanation reads as a broken site, so say what would make it work.

Common Mistakes
- Too many equal buttons. A screen of equals has no priority.
- Ghost buttons on busy backgrounds. Outline only, and invisible.
- Vague labels. Submit, Continue, Click here, Learn more.
- Targets too small. Correct on a desktop, impossible on a phone.
- No focus ring. Removed for looks, at the cost of keyboard users.
- Low contrast. Legible to the designer, invisible outdoors.
- Buttons too close together. Right sizes, wrong spacing.
Every one of these is visible in a screenshot, which makes them unusually easy to audit. Nothing here needs a testing tool or an analytics setup.
Most of these arrive together, because they share one cause. The button was designed on a large bright screen by somebody who already knew where it was.
The ghost button deserves a particular mention. An outline only button over a photograph is the one combination that can be invisible to some visitors and perfectly clear to others.
Check yours on a phone, outdoors, and with the keyboard alone. Three minutes of that finds more than an hour of discussion.
| What to check | What good looks like |
|---|---|
| Shape | A solid padded box, found at a squint |
| Size | Comfortable for a thumb, not merely legal |
| Spacing | Clear gaps between neighbouring buttons |
| Contrast | Text and shape both pass their ratios |
| Hierarchy | One loud action, everything else quieter |
| Label | A verb and the outcome, in the visitor's words |
| States | All five built, focus included |
Run it on your home page, your contact page and one product or service page. Those three cover most of what visitors actually press.

FAQs
What size should a button be?
WCAG 2.2 sets a minimum target of 24 by 24 CSS pixels at level AA, with 44 by 44 as the enhanced criterion. Apple asks for 44 points and Android for 48 density independent pixels. Treat the platform figures as the design target rather than the floor.
What colour should a call to action button be?
Whichever colour contrasts most with the surrounding page while meeting the ratios. Text needs at least 4.5 to 1 and the button shape at least 3 to 1 against what sits behind it. Reserve that colour for primary actions so it keeps its meaning.
Should I use a button or a text link?
Use a button for the action you most want taken, and a link for quieter navigation inside a paragraph. A link has no shape, so it is not found by somebody scanning. The main action on a page should always be a button.
How many call to action buttons should a page have?
One primary action per screen. The same action may repeat down a long page, since that is still one decision shown twice. Two loud buttons of equal weight create a choice at the exact moment you wanted a click instead.
What button states do I need?
Normal, hover, focus, pressed and disabled. Focus is the one most often removed for appearance, which strands anyone navigating by keyboard. Disabled needs an explanation beside it, otherwise a greyed out button simply reads as a site that is broken.
Conclusion
Good button design is mostly discipline. One loud action, sized for a thumb, labelled with the outcome, and built in every state.
None of it needs a redesign. All of it is reachable in whatever tool built your site.
The button is where every other decision on the page gets tested. Everything above it was persuasion, and this is the part that either works or does not.
Audit the one on your home page first, then work outwards to the rest of the site.
Start with the label on your main button. If it says Submit, you have found the cheapest improvement on the page.
If you would rather hand it over, see how we approach web design.









