Accessible WordPress Contact Forms: A 15-Minute Check

A contact form looks fine to you. You click the fields, you type, you hit Send. But a blind visitor using a screen reader can hit a radio group and hear “Yes, radio button, 1 of 2” with no idea what the question was. That’s not a made-up case. A Fluent Forms user reported this autumn that radio and checkbox groups “are not announced with their question for screen reader users”, because “the label has no for and wraps no input” (the wp.org thread).

Around the same time a Contact Form 7 user wrote that “screen reader users get no audio feedback after pressing Submit” (thread here). That one turned out to be a bug in the Orca screen reader, not CF7. Which is a useful lesson on its own: you have to test, because guessing goes wrong in both directions.
So this post covers what screen-reader and keyboard users actually need from a form, how to check any form plugin yourself in about 15 minutes, and what the European Accessibility Act means in plain words. No legal advice, just the practical bits.
What a screen-reader user needs from a form
Most of this is old, boring HTML, which is good news: it’s what assistive tech understands best.
Every input has a real label
A <label for="email"> tied to <input id="email">, or a label that wraps the input. When focus lands on the field, the screen reader reads the label. Without that link, the visitor hears “edit text” and has to guess.
No placeholder-only labels
Placeholder text (“First name” in grey inside the box) vanishes the moment someone types. Some screen readers read it, some don’t, and people with memory or attention issues lose track of what the box was for. Placeholders can be hints. They shouldn’t be the only label. Name fields are the usual offender: two boxes side by side with “First” and “Last” as placeholders and nothing else.
Radio and checkbox groups need a group name
This is the Fluent Forms complaint above. Each radio has its own label (“Yes”, “No”), but the question (“Can we call you?”) needs to be attached to the group. The standard way is a <fieldset> around the options with a <legend> holding the question. Then the screen reader says “Can we call you? group, Yes, radio button”.
<fieldset>
<legend>Can we call you?</legend>
<label><input type="radio" name="call" value="yes"> Yes</label>
<label><input type="radio" name="call" value="no"> No</label>
</fieldset>
The same goes for anything made of several inputs: a rating scale, an address block, a name split into two boxes.
Help text is read with the field
“We’ll only use this to reply” under an email box is useless if the screen reader never reaches it. Linking it with aria-describedby makes it get read when the field gets focus.
Errors are tied to the field, and focus moves to them
When a submit fails, a sighted user sees red text. A screen-reader user hears nothing unless the form does something. What helps:
- Each wrong field gets
aria-invalid="true"and its error message linked to it, so tabbing back to it reads the problem. - Focus moves to an error summary at the top that lists what’s wrong, ideally with links to each field.
- The error text says what to do (“Enter an email like [email protected]”), not just “Invalid”.
Colour contrast
Grey placeholder on white, pale borders, red error text on pink. WCAG asks for at least 4.5:1 contrast for normal text and 3:1 for large text and for things like input borders. This one mostly comes from your theme, not the form plugin, so you have to check it on your own site.
Keyboard works everywhere
Tab moves through fields in a sensible order, focus is visible (a ring or outline you can actually see), Space ticks checkboxes, arrow keys move between radios, and nothing traps you. Custom dropdowns and date pickers are where this usually breaks. So are some CAPTCHAs, which is worth thinking about when you pick a spam defence.
Check any form plugin yourself in 15 minutes
You don’t need an audit firm to find the big problems. Put your form on a test page and do these four passes.
1. Automated scan (3 minutes)
Install the free axe DevTools browser extension (Chrome, Edge, Firefox) or WAVE from WebAIM. Open the form page, run the scan. It’ll catch missing labels, bad ARIA and many contrast problems.
Then do it again on a failed submit. Leave required fields empty, click Send, and scan the page in that state. Lots of forms are fine when empty and messy once errors show up.
Automated tools catch a slice of issues, not all of them. Zero violations means “no obvious breakage”, not “accessible”. Anything marked “needs review” is a real to-do for a human.
2. Keyboard-only pass (4 minutes)
Put the mouse away. Tab from the top of the page to the form. Fill every field, tick a checkbox with Space, pick a radio with the arrows, submit with Enter. Can you always see where you are? Did anything skip, trap you, or need a mouse?
3. Screen reader pass (6 minutes)
Free options: NVDA on Windows, VoiceOver on Mac (built in, Cmd+F5 to turn it on). Tab through the form with your eyes closed if you can bear it. Listen for:
- Does every field say what it’s for?
- Do radio and checkbox groups say the question, not just “Yes” and “No”?
- Is the help text read?
- On a failed submit, do you hear that something went wrong, and where?
- On success, do you hear the thank-you message?
4. Contrast spot check (2 minutes)
Use the contrast checker in your browser’s dev tools (inspect the text, the colour swatch shows a ratio) or WebAIM’s contrast checker. Check labels, placeholder text, borders, error text and the button.
| Check | Tool | What it catches |
|---|---|---|
| Automated scan, empty and after a failed submit | axe DevTools or WAVE | Missing labels, bad ARIA, many contrast issues |
| Keyboard only | Your Tab key | Focus order, invisible focus, traps |
| Screen reader | NVDA or VoiceOver | Unnamed groups, silent errors, unread help |
| Contrast | Dev tools or WebAIM checker | Faint text, borders and error colours |
If your current plugin fails
You have a few options before switching anything.
- Check the settings. Some plugins have label position or “hide label” options. Make sure labels aren’t hidden visually in a way that also hides them from assistive tech, and don’t rely on placeholders.
- Use an add-on. For CF7 there’s “Contact Form 7: Accessible Defaults”, which gives new forms better starting markup. It doesn’t fix forms you’ve already built.
- Rewrite markup in your theme. Some plugins expose filters for field HTML. It works, but you’re now maintaining a patch that a plugin update can break.
- Report it. Open a support thread with exact steps and the axe output.
- Switch plugins. Run the same 15-minute check on the candidate before you move. Don’t trust a feature list for this.
Our contact page checklist covers the rest of the page around the form, which matters too.
Where Trinity Forms fits
Full disclosure: Trinity Forms is ours. It’s a free download from our site and needs PHP 8.2 or newer. Here’s what we checked on 12 Nov 2026 with Trinity Forms Free 2.28.0:
- Choice groups (radios, checkboxes, ratings, name, address and survey fields) are a fieldset named by their question in a legend.
- Name fields have real “First” and “Last” labels, not placeholders only.
- Help text is read out with its input.
- On a failed submit, each wrong field is marked invalid for screen readers and tied to its error message, and focus moves to an error summary at the top (“There are some things to fix”) that lists each field.
- We ran axe-core 4.10.2 with the WCAG 2.2 AA rules on a form with every field type, and again on a failed submit: 0 violations.
The limits, plainly. Colour contrast depends on your theme, and axe flagged it as “needs review”, so check it yourself. And we did not test with NVDA or VoiceOver, so please run the screen reader pass above on your own site. We’re not going to call any plugin “fully accessible”, ours included. Your theme, your content and your settings all count. Download Trinity Forms free and put it through the same 15 minutes.
The European Accessibility Act, briefly
The EAA has applied since 28 June 2025. It’s an EU directive that sets accessibility requirements for certain products and services sold to consumers in the EU. Services in scope include e-commerce, consumer banking, e-books, some transport services and electronic communications. If you sell things online to people in the EU, your shop (and the forms in it) is likely in scope, even if your business is based elsewhere.
Microenterprises providing services are exempt: that’s fewer than 10 staff and an annual turnover or balance sheet of no more than 2 million euros. A brochure site for a local plumber probably isn’t covered. A shop with a checkout and a returns form may well be. Each EU country enforces it through its own law, so if you’re unsure, ask someone qualified in that country. Accessibility also overlaps with privacy in forms, and our GDPR forms guide covers that side.
Even if the law doesn’t touch you, a form some people can’t send is lost enquiries.
Frequently asked questions
Is a placeholder enough as a form label?
No. Placeholder text disappears when someone types, isn’t read reliably by every screen reader, and is often too faint to meet contrast rules. Use a visible label tied to the input and keep the placeholder for an example or hint.
Does passing an axe or WAVE scan mean my form is accessible?
No. Automated tools catch a share of problems, like missing labels and many contrast issues. You still need a keyboard-only pass, a screen reader pass with NVDA or VoiceOver, and a manual look at anything marked “needs review”.
Does the European Accessibility Act apply to my WordPress site?
It applies to certain products and services sold to consumers in the EU since 28 June 2025, such as e-commerce. Microenterprises providing services (fewer than 10 staff and no more than 2 million euros turnover or balance sheet) are exempt. If you’re unsure, ask a qualified adviser in the relevant EU country.