Does my small business website need to be ADA compliant?

What does the law require of private businesses?

Private businesses fall under Title III of the Americans with Disabilities Act, which covers businesses open to the public. In March 2022 the Department of Justice published guidance on web accessibility stating that the ADA’s requirements apply to “all the goods, services, privileges, or activities offered by public accommodations, including those offered on the web.”

The same guidance is candid about the gaps. The DOJ “does not have a regulation setting out detailed standards” for business websites, and businesses “have flexibility in how they comply.” It points to the Web Content Accessibility Guidelines (WCAG) as helpful technical guidance, and the page notes that DOJ guidance has no legally binding effect on its own.

Three points matter for a small business:

• There’s no size exemption. The DOJ’s Title III technical assistance manual asks whether there is any grace period for small business, and answers “No.”
• Private lawsuits seek fixes and fees. Under Title III, a private plaintiff can get a court order but “not compensatory or punitive money damages,” per the same manual. A winning plaintiff can also recover attorney’s fees.
• No rule doesn’t mean no risk. Without a set standard, WCAG AA is the yardstick: it’s what the DOJ points to, and what its own rule for governments adopted.

Does the DOJ’s 2024 web accessibility rule apply to my business?

No, not directly. The rule published on April 24, 2024 is a Title II rule. It covers state and local governments and their agencies, and it makes WCAG 2.1 Level AA the required standard for their websites and mobile apps. It does not apply to private businesses.

Its deadlines have moved. An interim final rule published April 20, 2026 extended compliance to April 26, 2027 for governments serving 50,000 or more people, and to April 26, 2028 for smaller governments and special districts. One exception worth knowing: governments must make sure contractors who provide public services on their behalf follow Title II, so a business doing that work can be pulled in.

Why is New York a hotspot for website accessibility lawsuits?

New York leads both of the main lawsuit trackers. The latest numbers:

Seyfarth counts federal cases only. UsableNet also tracks New York and California state courts, so its totals are higher. Seyfarth notes that stricter standing rulings in federal court have pushed many plaintiffs into New York and New Jersey state courts.

What do WCAG 2.1 and 2.2 AA mean in plain terms?

WCAG is published by the W3C. It has three levels: A (the minimum), AA (the usual target) and AAA (the strictest). WCAG 2.2, published in October 2023, adds criteria to 2.1, and a site that meets 2.2 also meets 2.1. Aim for 2.2 AA. In practice, AA means:

• Everything works with a keyboard, with a visible focus outline that isn’t hidden behind sticky headers or pop-ups.
• Images have text alternatives that describe what matters, and decorative images are marked as decorative.
• Text has enough contrast: at least 4.5:1 for normal text.
• Color isn’t the only signal, for example on form errors or required fields.
• Forms have labels and explain errors in words.
• Videos have captions.
• Pages still work zoomed in, without content getting cut off.
• Tap targets are big enough: at least 24 by 24 CSS pixels, or spaced apart.
• Headings and structure are real, so screen reader users can navigate by them.

Why accessibility overlays are not a fix

Overlays are the widgets that add an accessibility icon and promise instant compliance. The record is poor. In January 2025 the FTC announced that overlay vendor accessiBe would pay $1 million to settle allegations that it misrepresented its AI tool’s ability to make any website WCAG-compliant; the order became final in April 2025. The W3C says evaluation tools “can not determine accessibility, they can only assist.” And UsableNet found no meaningful drop in lawsuits against sites using widgets in 2025. Barriers live in the site’s code, so that’s where they get fixed.

A practical accessibility checklist

1. Run a free automated scan (WAVE, axe or Lighthouse). It finds only part of the problems, but it’s a fast start.
2. Unplug the mouse. Tab through the home page, a service page and the contact form. Can you reach and use everything, and always see where you are?
3. Zoom to 200% on desktop and check nothing overlaps or disappears.
4. Try a screen reader (VoiceOver on Mac and iPhone, NVDA on Windows) on your contact form.
5. Fix templates first. A header, footer or form fixed once is fixed on every page.
6. Check PDFs, menus and embedded booking tools. Third-party widgets are still part of your site to a visitor.
7. Publish an accessibility statement with a phone number and email for reporting problems.
8. Retest after changes. New content and redesigns bring new barriers; build checks into ongoing maintenance.

What does a website accessibility audit cost?

These are market ranges from published provider pricing, not East End Web prices.

Ranges from Accessible.org and thefrontkit published pricing and cost guides, 2026.

Where East End Web fits

The cheapest time to get accessibility right is when a site is built or rebuilt, not after a demand letter. If you’re planning a new site or a redesign, ask for WCAG 2.2 AA in writing, whoever builds it. That’s the standard we’d scope a build to. For build costs, see what a website costs on Long Island. See how we build websites.