Contests with captcha-protected voting: helping people through one extra check

What is a captcha on a voting form checking?

It checks that a person is behind the click. The contest wants each vote to come from someone present, and a challenge that people pass easily but automated programs struggle with is the organizer's tool for that.

A captcha does not check who the voter is, and it does not limit how often they vote. Those jobs belong to other protections, such as email verification, IP and device limits or daily limits. A contest with only a captcha might let the same person vote again straight away, and a contest with every protection may still show a captcha on each attempt. Your own test vote reveals the combination.

From the supporter's side, the check sits between the vote button and the counted vote. It adds a few seconds when it works and a lot of irritation when it does not. That asymmetry is why this guide spends more time on failure than on success: the supporters you lose here are people who wanted to vote, saw a puzzle they could not complete, and gave up.

Our job is to prepare them for the puzzle, help them through it and watch what the counter does.

Which forms does a captcha take, and what trips supporters up on each?

You will meet a handful of forms, and each has its own trouble spots.

How to use the table

Find the form on your own test and write the matching help line into your ask. Some people are shown more challenges than others, and you cannot see why from outside, so prepare supporters for either experience: no puzzle at all, or several in a row.

If the form gives no accessible alternative, that is worth raising with the organizer in writing. Contests that rely on public votes depend on everyone being able to cast one.

Why do willing supporters fail a captcha?

Usually for ordinary reasons that have nothing to do with intent.

• Screen size: tiny tiles on a small phone invite mis-taps.
• Vision and hearing: image and audio puzzles are harder for some people.
• Privacy tools: ad blockers and tracking protection can stop a challenge from loading at all, so the vote button seems to do nothing.
• Built-in browsers: links opened inside other apps sometimes load challenges badly.
• Slow connections: a challenge can time out before the page finishes loading.
• Impatience: pressing the vote button before the challenge has completed.

What this means for your campaign

A supporter who fails once usually tries again. A supporter who fails twice often stops. So the real lever is the first impression: a calm sentence in your ask that the check exists, takes a moment and can be repeated without penalty. People who are told that a puzzle is normal treat it as a small chore. People who meet it unannounced treat it as a sign that something is wrong with the page.

For contests reached through paid ads, expect a wider gap between clicks and counted votes than on a one-tap form, and plan the ad budget around finished votes.

How do you mention the captcha without making voting sound hard?

Call it one quick check, put it last in the sequence, and put the help line directly under the ask.

For friends, family and customers:

Could you vote for my entry? [entry link]. Press vote, then complete the quick check that appears, and you are done. If the check will not load, tell me and I will help you sort it out.

For a cold audience reached by ads, put a line on the landing message: Voting includes one short check that you are a person.

For supporters who have already failed once, send a different message:

The check can be fussy. Try once more in your phone's main browser, and if it still fails, send me a screenshot.

What we leave out

We never describe the check as something to beat or avoid, and we never promise that it will not appear. Honest wording keeps trust with the people you most want to keep. More ask variants are in the templates for asking people to vote, and the creative and copy service writes the landing line and the help message in your voice.

What do you tell supporters when the check keeps failing?

Give them a short ladder, in this order, and stop at the first step that works.

1. Wait a moment, reload the page and let the challenge finish loading before pressing vote.
2. Read the instruction again and go slowly; fast taps are the commonest cause of repeated rounds.
3. Open the link in the phone's main browser, not inside a chat or social app.
4. If a privacy extension is installed, check whether it is blocking the challenge on this page, and decide for yourself whether to allow it.
5. Try a different connection, such as home Wi-Fi instead of mobile data, or the other way round.
6. Try again later. Challenges that fail repeatedly sometimes pass when the page is reloaded fresh.
7. Write to the organizer with a screenshot, and ask about an accessible option if the form is the problem.

Three things we will never do

We do not use captcha-solving services. We do not install automation to click through forms. And we do not ask anyone to complete the check on behalf of a supporter. Each of those defeats the purpose of the check and risks the entry being removed. The line is spelled out in our no-bots policy.

How do you measure completion when the captcha hides the drop-off?

By triangulation, because the failures happen on a screen you cannot see.

What you can observe:

• Tracked visits per audience group.
• The entry counter, written down before and after each wave.
• Stuck reports, which are replies saying the check failed.

What you cannot observe is the number of people who met the check and left without saying anything. The gap between visits and counter movement includes them, mixed with everyone else who changed their mind.

Test circle

To separate the two, recruit a handful of volunteers on different devices and connections, and ask each to vote once and report what they saw. If several of them struggle, the check is the problem and the wording needs work. If they all pass, the leak is somewhere else, in the message or the audience.

We report all of this as it is, and we label any estimate as an estimate. Where an organizer shows no figures at all, we say so in the report. How we read results explains the format.

How do you pace asks, and where do the limits of this protection sit?

Pace in steady waves. A captcha exists to blunt sudden floods of automated votes, and a campaign that brings people in steadily over days looks like what it is: people.

The organizer controls everything about the check itself: which form appears, how strict it is, whether an accessible alternative exists. We cannot change it and we cannot see how it scores a visitor. When it blocks genuine supporters, our work is to collect screenshots and send them to the organizer, not to find a way round it.

The next step is simple. Send the contest link, your entry, the deadline and a screenshot of the check as it appears for you through the free contest analysis. We reply with the rules read, the wording for the ask and a help message, and a plan for the waves. If your contest has more than one check, the overview of voting protection types shows how they combine.

How it works

1. Test the form on three kinds of deviceUse a phone, a tablet or laptop, and a second browser, and screenshot the check each time.
2. Write the one-line help messageDescribe the check as quick and give the first two fixes, so supporters can retry alone.
3. Launch to a small test circleAsk a handful of volunteers on different connections to vote once and report what they saw.
4. Collect and sort stuck reportsGroup failures by cause, such as loading, tiles or built-in browsers, and fix the wording.
5. Widen in steady wavesCompare visits with the counter after each wave and send the organizer any accessibility issues.