Sued Over a Contact Form? The Free-Theme Accessibility Sweep You Can Do Before Lunch
Photo: InclusiveGameLab, CC BY-SA 4.0, via Wikimedia Commons
If you run a small business website, the letter doesn't arrive from a government agency. It arrives from a law firm, often in New York, Florida, California, or Texas, and it usually says something like: our client, a screen reader user, could not complete your contact form. Then it asks for money.
Several thousand web accessibility lawsuits get filed in US federal courts each year, and the pattern has held for a decade: the targets are overwhelmingly small and mid-sized businesses, not the giants. A restaurant with a menu PDF. A dental practice with an online booking widget. A consultant with a page builder site on a free hosting plan.
That last one is you, maybe. And here's the annoying part — the free template is often the reason.
Why free themes fail more often, not less
Paid themes have customers who complain. Free themes have customers who don't. Accessibility bugs — unlabeled inputs, keyboard traps, low-contrast buttons — don't show up in a screenshot, so they never generate a support ticket. They just sit there for years.
The good news: the failures are predictable. You'll see the same five problems on almost every free theme and page builder out there.
Failure 1: Images with no alt text (or worse, wrong alt text)
Screen readers announce the filename when alt text is missing — hero-image-final-v3.jpg read aloud, character by character. Decorative images should have an empty alt="" so they're skipped entirely. Informative images need a short description of what they convey, not what they are.
The fix: In WordPress, open the Media Library and fill the Alt Text field for everything in use. In a page builder, click the image block and look for the alt/description field. Ten minutes, tops. If an image is purely decorative, mark it as such or leave alt blank.
Failure 2: Form fields with no labels
Placeholder text is not a label. It disappears the moment someone starts typing, and many screen readers skip it. Every input needs a real <label> tied to it — for attribute matching the input's id.
The fix: Most form plugins have a 'label' field separate from the placeholder. Fill it in. If you're hand-coding, wrap the input in a <label> element. For the free-host crowd: check that your contact form isn't just a mailto link, because those are inaccessible and unreliable in equal measure.
Failure 3: Contrast that looks moody and reads like mud
Light gray text on white, white text on a pastel hero image, thin fonts at 12px — free themes love all three. The threshold most courts and standards reference is a 4.5:1 contrast ratio for normal text and 3:1 for large text (roughly 18pt, or 14pt bold).
The fix: Run your text and background hex codes through the WebAIM Contrast Checker (free, no account). Then override the theme colors. If your host gives you a custom CSS box — most free plans do — a few lines will fix it without touching the template:
body { color: #1a1a1a; }
.btn { background: #0b5ed7; color: #ffffff; }
If you can't reach the CSS, switch themes. It's faster than fighting it.
Failure 4: Keyboard traps and invisible focus
Unplug your mouse. Now tab through your whole site. Can you reach the menu? Can you see where you are? Can you get out of the popup?
Free page builders are notorious for focus outlines set to outline: none — the developer thought the glow looked ugly. Others have modals you can tab into but never tab out of. That's a keyboard trap, and it's one of the clearest violations you can have.
The fix: Never remove focus outlines without replacing them. Add this if your theme stripped them:
:focus-visible { outline: 3px solid #0b5ed7; outline-offset: 2px; }
Then tab through and note anything you can't escape. Remove autoplay carousels — they're a focus and motion problem in one package.
Failure 5: Heading soup and 'click here' links
Skipping from an H2 to an H5 because the font size looked better is a real habit. So is a page with eleven H1s. Screen reader users navigate by heading level; a broken hierarchy is a broken map.
Link text matters too. A screen reader can pull up a list of every link on the page, and if that list says click here, click here, read more, click here, the page is unusable.
The fix: One H1 per page, then H2s, then H3s, in order. Use descriptive link text: 'download the 2026 price list' beats 'click here.' Both fixes take minutes and cost nothing.
Your 20-minute test, using only free tools
- WAVE (wave.webaim.org) — paste your URL, get a visual report. Free, no login.
- Lighthouse — built into Chrome DevTools under the Lighthouse tab. Run the accessibility audit.
- The keyboard test — unplug the mouse. Tab everywhere. Escape every overlay.
- The zoom test — hit Ctrl+plus until you're at 200%. Does anything overlap or vanish?
- The screen reader spot check — VoiceOver on a Mac (Cmd+F5) or Narrator on Windows (Win+Ctrl+Enter). Listen to your homepage for two minutes. It's humbling.
Fixes that survive a free-hosting plan
Free plans usually won't let you install arbitrary plugins or edit PHP. That rules out some automated remediation tools. But everything in this list is achievable within those limits:
- Alt text and labels live in your content, not your server.
- Contrast and focus styles live in a custom CSS box.
- Headings and link text live in the editor.
- Captions for video come free from YouTube's auto-captioning — just edit them, because raw auto-captions are rough.
If a demand letter does show up
Don't ignore it, and don't pay it in a panic. Talk to a lawyer — some legal aid organizations and state bar referral services offer low-cost consultations for small businesses. And document what you fix and when. A dated record of remediation is worth a lot more than a promise to do better.
Start with the contact form and the keyboard. Those two account for a startling share of the complaints, and neither one costs a dime to fix.