Calls to action
The call to action, and why so many of them quietly fail.
Every page is asking for something. The only question is whether it asks clearly enough that a distracted person on a phone can tell what happens if they tap.
What is a call to action on a website?
A call to action is the specific next step a page asks someone to take, expressed as a link or a button whose words say what will happen when it is used.
It matters because a page with no obvious next step, or with six competing ones, hands the decision back to the visitor at the exact moment they are least willing to make it.
The ones that work are concrete and low risk: they name the thing, they match what the page has just promised, and they are reachable by keyboard and readable by a screen reader, which a surprising share of buttons on the web are not.
What a call to action actually is
It is not a button colour and it is not a slogan. It is the moment a page stops explaining and starts asking, and the quality of the ask is mostly about clarity and risk rather than persuasion.
Two things decide whether someone acts. First, whether they can tell what happens next. Second, whether that next thing feels small enough to do right now. A button that says Submit fails the first test. A button that says Book a consultation fails the second for someone who only wanted a price.
This is why calls to action cannot be written in isolation from the page above them. The ask has to match the state of mind the page has just created. If the page has answered a question, the natural next step is another answer. If the page has made a case, the natural next step is contact.
It is also why one page can reasonably carry more than one call to action, as long as they are the same ask expressed in the places a person might be ready: at the top for the already convinced, again after the proof, and again at the end.
What a good one does
None of this is about clever copywriting. It is about removing the reasons someone would hesitate.
- It names the action and the outcome, so the words on the button describe what the next screen will contain.
- It matches the page. A page about emergency appointments should not end by offering a newsletter.
- It is honest about what follows. Telling someone the form takes a minute, or that you reply by email rather than by phone, removes a real hesitation at no cost.
- It sets the commitment level correctly. Somebody comparing three providers is not ready to book, but they will accept a price list or a question answered.
- It is visible without hunting on a phone, and repeated where a person would reasonably have become convinced rather than only at the very bottom.
See the full checklist: What a good one doesHide the full checklist: What a good one does
- It is a real link or button, not a styled image or a div with a click handler, so that keyboard users and screen reader users can reach and understand it.
- Its text makes sense read alone. Screen reader users routinely navigate by listing every link on a page, and a list of six identical entries reading Read more is useless.
- It stays reachable. A sticky bar, a chat bubble and a cookie banner stacked on a small screen can cover the very thing they were added to promote.
How often the button itself is broken
WebAIM's 2026 automated analysis of one million home pages counted the most common detected accessibility failures. Three of them are calls to action that cannot be used or understood.
SourceWebAIM Million 2026 (automated analysis of 1,000,000 home pages)
WebAIM notes that real conformance is worse than these figures suggest, because only automatically detectable failures can be counted. A scanner cannot judge whether a button labelled Go is meaningful. What the numbers do establish is that the most common accessibility failures on the web are concentrated in exactly the elements a business most wants people to use.
The call to action is one link in a chain
A call to action cannot rescue a page that has not made a case, and it cannot survive a form that fails afterwards.
If the page above has not answered the visitor's question, a better button will not help. If the form below is twelve fields long, a better button only moves the drop-off one step later.
So diagnose in order: did they get far enough to see it, did they understand it, did they act, and did the thing that followed work. Most teams rewrite the button when the failure was at one of the other three points.
Vague against specific
The pattern is consistent: replace an instruction to the visitor with a description of what they get.
| Instead of | Try | Why it works |
|---|---|---|
| Submit | Send my enquiry | It describes the outcome rather than commanding an operation |
| Learn more | See what the treatment involves | It survives being read on its own, out of context |
| Click here | Download the price list | The link text names the destination, which keyboard and screen reader users depend on |
| Contact us | Ask a question by email | It sets the channel and the effort involved |
| Get started | Request a callback | It names a small, concrete step instead of an open ended commitment |
| Read more | Read the full accessibility checklist | A list of links read aloud stays useful |
None of these are clever. They are just specific, and specific consistently beats energetic. Note that the right hand column is also better for accessibility, which is the usual pattern: the accessible version and the persuasive version are the same version.
The failures we see most
Too many asks. A page offering a call, a form, a chat, a download and a newsletter has not given the visitor five chances. It has given them a decision they did not want to make.
The ask that does not match the moment. Asking a first time visitor who arrived from a broad search to book a paid appointment is asking for a commitment the page has not earned yet.
Read the full breakdown: The failures we see mostHide the full breakdown: The failures we see most
Hiding the phone number. On a phone, for many local businesses, calling is the action people actually want, and burying the number behind a contact page is a self inflicted loss.
A button that is a picture. Text baked into an image cannot be resized, read aloud, translated or searched, and it goes blank if the image fails to load.
A form that punishes mistakes. Error messages that appear only at the top, clear the fields, or do not say which field is wrong will lose people who were entirely willing to be customers.
No tracking. If the button is not recorded as a conversion, nobody can tell which version performed better, and every subsequent argument about wording becomes a matter of opinion.
Changing everything at once. Rewriting the headline, the button, the form and the layout in one release produces a result nobody can attribute to anything.
You cannot improve what nobody recorded
Before rewriting anything, make sure every route a person can take to reach you is being counted, including the one that does not touch a form.
For most local businesses the largest single call to action is the phone number, and it is the one most often missing from reporting. A site that counts only form submissions will conclude its calls to action are failing when they are working fine.
Record which page the enquiry came from as well as which channel. Otherwise the reporting can tell you that search is working without telling you which page made the case.
Read next
Where the call to action fits with everything around it.
What a landing page is
The page type built entirely around a single action, and when you need one.
What a landing page isConversion rate optimisation explained
How to test a change properly instead of rewriting on instinct.
Conversion rate optimisation explainedTracking where leads come from
Counting calls as well as forms, so the reporting reflects reality.
Tracking where leads come fromWhat counts as a sales lead
Defining the thing your call to action is supposed to produce.
What counts as a sales leadThe web design guide
How pages get planned and built so the action is obvious by default.
The web design guideNot sure which of your pages is losing people
A free audit reports the pages with no clear next step, the buttons a screen reader cannot announce, and the forms that fail on a phone.
Straight answers.
How many calls to action should a page have?
One ask, repeated where it is useful. Placing the same action at the top, after the proof and at the end is not clutter, because a visitor becomes ready at different points.
What causes trouble is several different asks competing, because that turns a decision about your service into a decision about your website.
Does button colour affect conversions?
Far less than contrast, position, wording and what the page said beforehand. A button needs to be visibly a button and to meet contrast requirements against its background.
Beyond that, colour is one of the last things worth arguing about and one of the first things people argue about.
Should the call to action be above the fold?
There should be one there for the people who arrived already convinced, particularly a phone number on mobile.
It should not be the only one. Someone who needed the whole page to be persuaded should not have to scroll back up to act.
Why do my buttons get lots of clicks but few enquiries?
Usually what follows the button rather than the button itself. Long forms, required fields nobody expected, error handling that clears entries, or a page load between tap and form.
Compare form starts against form completions. A big gap between those two points at the form, not the call to action.
Is a phone number a call to action?
Yes, and for many local businesses it is the most important one. It needs to be a tappable link on mobile rather than plain text.
It also needs to be tracked, or your reporting will credit the form for everything and quietly under-count the channel people actually used.
What makes a call to action accessible?
Use a real link or button element, give it text that makes sense read on its own, keep visible focus so keyboard users can see where they are, and meet contrast requirements.
Avoid text baked into images, and make sure any icon-only control carries an accessible name.
Where this comes from.
Primary documentation and published research behind the guidance on this page.
- W3C: Web Content Accessibility Guidelines (WCAG) 2.1 (opens in a new tab)
- W3C Web Accessibility Initiative: Introduction to web accessibility (opens in a new tab)
- Google Ads Help: About conversion measurement (opens in a new tab)
- Google Analytics Help: Engagement rate and bounce rate in GA4 (opens in a new tab)GA4 defines bounce rate as the inverse of engagement rate, not as a single-page visit.
Talk to the team
A short call, a look at how the business currently shows up, and a straight answer on what we would do first.