On a law firm’s contact page we scanned in July, the caption above the message box is wired to a field that doesn’t exist on the page. One word in the code is wrong. A sighted visitor sees “Please Tell Us About Your Concern” and types; a blind visitor’s screen reader reaches the same box and has no idea what it’s for.

That’s the whole category of problem, and it’s why your contact form deserves two minutes of attention.

First, what a screen reader actually needs

A blind visitor doesn’t see your form. Software reads it aloud, one control at a time. For that to work, each box needs a name written into the code — invisible on screen, essential to them. Your web developer writes it once and it keeps working.

The usual way is a <label> tag with a for attribute that points at the box’s ID. Point it at the right ID and the box has a name forever. Point it at the wrong one and the page looks completely normal, while the connection silently doesn’t exist.

What we found

We scanned the websites of law firms whose attorneys filed federal disability-access lawsuits in June 2026 — firms we identified by reading the court dockets ourselves. On Sconzo Law Office’s contact page, scanned 28 July 2026, an automated check flagged two controls with no accessible name. Both rate “critical.” Both break a rule from WCAG 2.0, published in 2008.

The message box. The page serves a real label, correctly written:

<label for="ncf_reason">Please Tell Us About Your Concern: *</label>
<textarea name="Please_Tell_Us_About_Your_Concern" id="ncf_message"></textarea>

Read those two IDs. The label points at ncf_reason. The box is called ncf_message. No element on that page has the ID ncf_reason, so the label points into thin air. Somebody did the work and one word drifted.

A dropdown, elsewhere on the same page. A <select> asking “Are you a new client?” carries that question as its first option and in a data-placeholder attribute. A screen reader announces the current value, so on arrival the visitor does hear the question. Then they choose an answer, the value becomes “Yes, I am a potential new client,” and the question is gone — because the control itself never had a name, only a value.

Both are a few minutes’ work for whoever maintains the site.

The busiest filer’s contact page came back with zero

The cheap version of this story would be that the lawyers bringing these cases have broken websites. Our data says otherwise, and the exception is the useful half.

Reading every federal disability-access docket filed in June 2026 — 149 of them — we confirmed 33 as website-accessibility suits. The attorneys at Gottlieb & Associates in New York appear on 15 of those 33, more than anyone else. We scanned their contact page: zero detected violations. Joseph & Norinsberg returned three. Stein Saks, six.

So this is tractable, and some firms have plainly had someone look. The only way to know which group you’re in is to check.

The accessibility toggle, tested

Sconzo’s site carries its own accessibility feature: a small icon in the page furniture whose alt text and title both read “Switch to ADA Accessible Theme,” linking to the same page with ?enable_wcag=1. We scanned that version too, because we wanted the before-and-after ourselves.

It works on exactly the problems above. Both unnamed controls get names. All nine colour-contrast failures clear. Click it and this article’s two examples stop being examples.

The toggled page also returned twice as many detected issues — 24 against 12, with 14 rated critical against 2. Nineteen are in the navigation menu, where the alternate theme uses menu markup incorrectly. The other five sit on the accessibility toolbar’s own text-size and colour buttons.

Each version has failures the other doesn’t. That’s the practical trouble with treating accessibility as a mode a visitor switches into: you end up maintaining two pages, and the fixes live on only one of them.

The two-minute check on your own form

You don’t need to learn the standard. Ask whoever maintains your site:

  1. Does every field on the contact form have a label connected to it in code? Specifically: does each label’s for value match a real ID on the page? That’s the mistake above, and it survives every visual review because the page looks perfect.
  2. Do the dropdowns have names too? They get missed constantly, because a dropdown that shows its question as the default option reads fine until someone answers it.
  3. Has anyone opened the form with a screen reader? Running a checker is a good start. A checker sees whether a name exists; only a person can tell whether the name makes sense.

Want to know what’s on your own contact page? Run it through our free report — no login, no credit card, no sales call. You get the barriers we can detect automatically and a fixed price to fix them. If you’d rather understand the exposure first, here’s what actually ended one of these lawsuits.

The fine print

  • Five firms’ contact pages on one day — not a rate for anything. We started from 16 attorneys of record on federal disability-access suits filed in June 2026, read by us via CourtListener; nine had a website we could confirm was theirs, four of those wouldn’t load, and five produced a contact page. Worth saying plainly: our data does not show contact pages failing more often than home pages. They carried fewer detected issues, here and in a 20-firm run a day earlier. The contact form is the page that matters most, not the page that fails most.
  • Sconzo is a repeat filer of federal disability-access cases; we have not confirmed its filings are website cases. Gottlieb & Associates, Joseph & Norinsberg and Stein Saks are confirmed on website suits in our June set. Nothing here speaks to the merit of any case any of them filed.
  • A scan is a floor, never a verdict — ours included. Automated testing reaches a minority of the standard’s requirements and produces false positives. Gottlieb’s zero is not a clean bill of health; our own site scores 100 and we don’t claim it either.
  • A detected error is not a legal finding. Everything above is what a scan detected on a named page on a named date. “ADA compliant” is a legal conclusion rather than a measurement — courts reference WCAG rather than adopting it, and whether a website is covered under Title III is still split by circuit.
  • That accessibility theme is not an overlay widget — it’s the site’s own alternate WordPress theme, nothing like the products the FTC has acted against. Different rules fired in each version, so “twice as many” counts what a scanner detected rather than ruling either version more compliant.
  • We sell remediation, and we’re not lawyers. None of this is legal advice.

Sources