What Does ADA Website Compliance Mean for a New York Business?

If you run a business in New York and a law firm has emailed you about your website, you are not alone, and you are not imagining that it happens here more than elsewhere.

The short answer: ADA website compliance in New York means your site can be used by people with disabilities, including people who rely on screen readers, keyboards or magnification. There is no official checklist written into the ADA itself, so courts and settlements almost always measure sites against WCAG 2.1 or 2.2 at level AA. New York is the busiest state in the country for these lawsuits, so the practical goal is to fix the issues plaintiffs test for first, document your work, and keep the site accessible as it changes.

This post is general information, not legal advice. If you have received a demand letter or a complaint, talk to an attorney before you reply.

Why do so many New York businesses get accessibility demand letters?

Because New York federal courts are where most of these cases are filed. Seyfarth Shaw's annual count found 3,117 federal website accessibility lawsuits in 2025, up 27% from 2024, and 1,021 of them (about a third) were filed in New York. Florida and Illinois were next. Those figures cover federal court only, so state court suits and demand letters that settle before anything is filed come on top.

2026 is running hotter. Equidox, summarizing UsableNet's tracking through mid-June, reported that digital accessibility lawsuits are on track to surpass 6,000 in 2026, roughly 20% above 2025.

A few reasons New York draws so many cases:

• Federal courts here have generally been willing to treat websites as covered by the ADA, even for businesses without a strong physical presence.
• New York's own state and city human rights laws let plaintiffs add claims on top of the federal one.
• Many letters come from firms that file in volume, using automated scans to find sites with obvious errors.

That last point matters most for you. Many letters are not the result of someone carefully reviewing your site. They come from a scan that flagged missing image descriptions, unlabeled form fields or poor contrast. Those are exactly the issues you can find and fix.

What does WCAG 2.1 or 2.2 AA actually ask for?

WCAG (Web Content Accessibility Guidelines) asks that people can perceive, operate and understand your content, and that it works with assistive technology. Level AA is the middle tier courts and settlements usually reference. WCAG 2.2 adds a few criteria on top of 2.1, mostly about focus visibility, touch target size and not making people re-enter information.

In plain terms, AA asks that:

• Images have text alternatives. Meaningful images get a short description in the alt attribute. Decorative ones get an empty alt so screen readers skip them.
• Everything works with a keyboard. Menus, sliders, booking widgets and pop-ups can be reached and used with Tab, Enter and the arrow keys, and you can always see where the focus is.
• Text has enough contrast. Body text needs a contrast ratio of at least 4.5 to 1 against its background. Light gray on white usually fails.
• Forms are labeled. Every field has a real label a screen reader can announce, and errors are explained in text, not only with a red border.
• Structure is real. Headings use proper heading tags in order, links say where they go ("View pricing", not "Click here"), and the page language is set.
• Media is accessible. Videos have captions and audio has a transcript.
• The site works zoomed in. Content reflows at 200% zoom and on small screens without text getting cut off.

None of this is exotic. Most of it is ordinary good web development that got skipped under deadline. How hard it is to fix depends on how your site was built: a themed WordPress site and a custom build each have their own trade-offs, which we compare in WordPress vs a custom website.

Do accessibility overlays protect you from lawsuits?

No. Overlays are the widgets that add a little accessibility icon to your site and promise compliance with one line of code. They can change font size or contrast on request, but they cannot reliably fix the underlying code that screen readers and keyboards depend on.

The clearest signal came from the Federal Trade Commission. In April 2025 it finalized an order requiring accessiBe, one of the best known overlay vendors, to pay $1 million over claims its accessWidget product could make any site WCAG compliant. The order bars the company from making that claim without evidence to back it up.

An overlay sits on top of the same broken code, so a scan or a screen reader user still runs into the same unlabeled buttons and inaccessible forms underneath. If you are paying a monthly fee for an overlay as your compliance plan, that money is better spent fixing the site itself.

What should you fix first?

You do not need to fix everything at once. Start where users and plaintiffs both start: the pages and paths that matter most.

1. Your money paths. The homepage, main service pages, contact form, booking or checkout flow. If a blind user cannot request a quote, that is the core of most complaints.
2. Forms. Add proper labels, clear error messages and keyboard access. This is often the highest value fix per hour.
3. Images and icons. Write alt text for meaningful images and icon buttons (a magnifying glass button needs a name like "Search").
4. Keyboard and focus. Tab through your site. If you get stuck in a menu or cannot see where you are, fix the focus styles and the trap.
5. Color contrast. Adjust brand colors for text and buttons where they fail. Usually a slightly darker shade solves it.
6. Third-party embeds. Chat widgets, schedulers and payment forms count as part of your site. Check them, and ask vendors for their accessibility conformance report.
7. PDFs and documents. Menus, price sheets and forms posted as PDFs are frequently overlooked and are often inaccessible.

Then publish an accessibility statement that says what standard you aim for, what you are working on, and how someone can reach you if they hit a barrier. It shows good faith and gives users a route other than a lawyer.

How should you approach an accessibility audit?

A useful audit combines three things, because each catches what the others miss.

Automated scanning. Free tools like axe DevTools, WAVE or Lighthouse catch a meaningful share of issues fast: missing alt text, contrast failures, unlabeled fields. Run them on your key templates, not just the homepage. Automated tools cannot judge whether alt text is accurate or whether a flow makes sense, so they are a starting point only.

Manual keyboard and screen reader testing. Someone walks through your main tasks using only a keyboard, then with a screen reader (VoiceOver on Mac, NVDA on Windows). This finds the problems that block real people: a date picker you cannot operate, a modal that traps focus, a button announced as "button, button."

A written report with priorities. Each issue should be tied to a WCAG criterion, a page, a severity and a fix. That report becomes your roadmap and your record of good faith.

After fixing, build accessibility into how the site changes. New pages, new plugins and redesigns are where sites slip back. Add a quick accessibility check to every release, the same way you would check that links work. If a redesign is on the table anyway, it is the cheapest moment to get this right, and the website redesign SEO checklist covers the other things not to break during that move.

Accessibility work also overlaps heavily with search work: clean headings, descriptive links, alt text and fast pages help both. It is one reason we keep development and SEO under one roof, so the fixes land once instead of being argued over by two vendors.

Quick answers

Does the ADA apply to my small business website in New York?

Very likely, if you serve the public. New York federal courts have generally treated business websites as covered, and businesses of all sizes receive letters. Ask an attorney about your specific situation.

Is there an official ADA website standard?

The ADA does not spell out a technical standard for private business websites. In practice, WCAG 2.1 or 2.2 level AA is the benchmark used in settlements, court orders and audits.

Will an accessibility widget make my site compliant?

No. Overlays cannot fix the underlying code, and the FTC fined a major overlay vendor $1 million over compliance claims. Fix the site itself.

How long does it take to make a website accessible?

It depends on the size of the site and how it was built. As our own rule of thumb, a small brochure site can often be brought close to AA in a few weeks of focused work, while a large site with custom tools takes longer and is usually done in phases, money paths first.

What should I do if I get an ADA demand letter?

Do not ignore it, and do not reply on your own. Contact an attorney, and in parallel get an audit so you know what is actually wrong with the site and can start fixing it.

Next step

If you want to know where your site stands before a letter arrives, we can audit your key pages, fix what we find and keep it accessible as the site grows. Book a free call and we will send you a written recommendation within a few days.