Is Your Website ADA Compliant? What Rochester Businesses Need to Know

"ADA compliant website" is one of the most common phrases in web design sales pitches, and one of the least precisely used. There is no ADA certification a site can earn, no government seal of approval, and, for a private business, no single federal regulation that spells out exactly which technical checks a website must pass. What exists instead is case law: a steady stream of lawsuits and demand letters, nearly all of them measuring a site against the same technical yardstick. Here's what that yardstick is, why it matters for small businesses, and what to actually do about it.

The law is real, even without a website-specific regulation

Title III of the Americans with Disabilities Act bars discrimination in "places of public accommodation." Federal courts have increasingly read that to include a business's website, on the theory that a site with no keyboard navigation, no alt text, and unreadable color contrast excludes a disabled visitor the same way a step with no ramp would. The Department of Justice's March 2022 web accessibility guidance says the ADA's requirements apply to the goods, services, privileges, and activities of public accommodations, "including those offered on the web." It does not set binding technical rules for private-sector sites; it describes the Web Content Accessibility Guidelines (WCAG) as existing technical standards that offer helpful guidance.

That gap (a law that applies, with no official checklist) is why plaintiffs' firms, defense counsel, and settlement agreements have all converged on the same private-sector standard anyway: WCAG 2.1 Level AA, the Web Content Accessibility Guidelines published by the W3C. It isn't the law by name. It's what "compliant enough to settle" has come to mean in practice.

Why this isn't a big-company problem

Web accessibility lawsuits climbed again in 2025, and there's no small-business carve-out in Title III, so a five-employee shop is exposed the same way a national retailer is. UsableNet's lawsuit tracker, which has published this data for several years, has recorded thousands of federal website-accessibility filings in a single year. Many claims never become public lawsuits at all. They arrive as a letter from a law firm, citing specific pages and specific WCAG failures, and asking for a settlement before litigation.

The pages that usually get cited

Auditors and plaintiffs' firms tend to flag the same handful of issues, over and over, because they are the easiest to detect with automated scanning tools:

• Missing or unhelpful alt text on images, especially product photos, team headshots, and hero images
• Insufficient color contrast between text and its background: light gray text on white is a frequent offender
• Forms without proper labels, such as a contact or quote-request form where a screen reader can't tell what a field is for
• No visible keyboard focus state, which leaves a site usable only with a mouse and excludes anyone who can't use one
• Video or audio with no captions or transcript

None of these require a lawsuit to be worth fixing. They're also, generally, real usability problems for real visitors: an older customer with low vision, someone browsing one-handed with voice control, a visitor with a temporary injury. Accessibility work and better usability overlap more than people expect.

What we build differently

Every site we build is hand-coded, semantic Next.js, not a page-builder theme with div soup standing in for buttons and headings. That starting point matters: proper heading structure, real button and label elements (not styled divs pretending to be interactive), and explicit image dimensions come from the build process itself rather than being bolted on afterward. That reduces risk; it doesn't eliminate it. Nobody can promise a lawsuit will never be filed, and any agency claiming a website can be certified "ADA compliant" is overselling a legal grey area.

If you already got a letter

Don't ignore it, and don't panic-sign a settlement either. A demand letter is a negotiation opener, not a court order. Get it in front of an attorney who handles Title III matters, and separately get a real technical accessibility audit of the specific pages named. Most letters cite specific, fixable issues, and showing a documented remediation effort in progress is meaningful in a negotiation.

Where to start if you haven't been sued

Run your site through a free automated scanner (WAVE or axe DevTools are both free and reputable) to catch the low-hanging fruit, then get a human review for the things automated tools miss, like whether your custom dropdown menu actually works with a keyboard. If you want us to look at yours, our free site audit checks the technical basics; for a full accessibility pass on top of that, get in touch and we'll scope it honestly, including telling you if your current site is close enough that a full rebuild isn't the right answer.