The contact form is where an accessibility problem costs you money
Labels that stay put instead of vanishing the moment you type
The phone has been quiet for a week. You keep refreshing the inbox for a form submission that never lands, wondering whether people stopped needing what you sell or the form just stopped working. It's worth checking the form itself before assuming either one.
A common failure hides in plain sight. The field label lives inside the box as placeholder text, and it disappears the second someone starts typing. Get halfway through a phone number and you've lost the label that told you which field this was.
A screen reader user never had that label in the first place. Placeholder text gets announced inconsistently, if at all, depending on the software reading the page.
The fix is a visible label above or beside each field, always there, typed text or not. It costs nothing. It removes an entire category of confusion for every visitor, not just the ones using assistive technology.
This matters more on a phone than on a desktop, since a phone keyboard covers half the screen the moment someone taps into a field. If the label was only ever placeholder text, it's already gone before the keyboard even finishes sliding up.
Error messages that say what's wrong and where
"Something went wrong" does not tell a visitor what to fix. A visitor who mistyped an email address has no way to know which field caused the problem. A screen reader user hears the word "error" with nothing attached to it — no field name, no direction to look.
A working error message names the field and states the fix: "Phone number needs 10 digits." It sits next to the field it describes, not in a banner at the top of the page where the connection has to be guessed.
That single change turns a dead end into a form someone can actually finish. It's a small edit to make. It just needs to happen on every field, not only the obvious ones.
A date field is the classic offender. "Invalid date" says nothing about the format expected, and a visitor can retype the same correct date five times before giving up entirely.
Required fields that don't rely on a red asterisk alone
A red asterisk next to a field name works for exactly one kind of visitor: someone with full color vision, using a screen with a mouse or a finger. Everyone else needs a second signal.
The word "required" printed next to the field does the job the asterisk alone can't. A tag a screen reader will actually announce does the same job in code. Both are simple additions. Neither changes how the form looks to anyone who was already reading it fine.
A screen reader that never announces which fields are required leaves a visitor guessing, submitting, and getting bounced back by an error they had no way to see coming.
Sessions and time limits that expire while someone is still typing
Some contact forms sit behind a login timeout or a security session that quietly expires after a few minutes. Someone reading each field carefully, or filling the form out on a slow connection, can lose everything they typed with no warning at all.
That's a frustrating way to lose an enquiry. If a time limit has to exist, a warning before it expires and a simple way to extend it matters more than the limit itself.
A quote request form is a common place for this to bite. Someone typing out project details on a phone, one-handed, on a job site, needs more than a few quiet minutes before the session gives up on them.
The captcha that filters out customers along with bots
A captcha exists to stop bots. A lot of the common versions also stop some real customers along the way: distorted text a low-vision visitor can't read, a checkbox puzzle that assumes a mouse and a steady hand, an audio fallback nobody remembers exists.
Weigh what the captcha blocks against what it's actually protecting the form from. A honeypot field, invisible to a real visitor and irresistible to a bot, catches nearly all the spam without asking a single customer to prove anything about themselves.
It sits on the page, hidden from view with plain code rather than a visual trick, and any bot filling in every field trips it instantly. A human never even knows it's there.
Confirming to the sender that the message actually went
The last step is one owners forget to check from the visitor's side. After someone submits, does the page actually say so? A form that clears itself and sits there silently reads, to a screen reader user, as if nothing happened at all.
A visible confirmation message closes the loop. So does a redirect to a page that plainly says "message received." Either one turns a moment of doubt into certainty for the person who just wrote to you.
Without that certainty, some visitors submit twice, worried the first attempt failed. Others assume it failed and call instead, which defeats the point of having a form in the first place.
None of this happens by accident, and it doesn't get found by guessing either. Testing the form yourself, step by step, is the fastest way to see where yours currently stands. The type and color choices around the form matter too, and how the form's text actually reads on the page is worth checking at the same time.
If the form is quiet for reasons that have nothing to do with accessibility, what a small business site actually has to do to capture an enquiry is the wider question underneath it. And the form is one piece of a bigger picture — the build questions accessibility sits inside is worth reading in full.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go