Does Your Business Website Need to Be ADA Accessible?

Short answer: probably yes, in the sense that matters for legal risk. Most federal courts that have looked at the question treat a business's website as covered by Title III of the Americans with Disabilities Act (ADA) when the business itself is a "place of public accommodation" — think retail stores, restaurants, hotels, medical and professional offices, gyms, and similar customer-facing businesses. Web-accessibility demand letters and lawsuits against small and mid-size businesses are common and have been rising. At the same time, the law here is genuinely unsettled: there is still no single federal regulation that spells out exactly what a compliant business website has to look like. That gap is exactly why the risk exists — and exactly why cheap, good-faith accessibility steps are worth doing now.

What Title III actually says, and what it doesn't

Title III of the ADA prohibits disability discrimination by "places of public accommodation" — private businesses that are open to the public. The Department of Justice (DOJ), which enforces Title III, has stated publicly that the ADA's requirements apply to the goods, services, and activities a public accommodation offers, "including those offered on the web." That is a real, current position of the federal government, stated on ada.gov.

What DOJ has not done is issue a formal regulation that sets out detailed technical standards for private business websites — for example, DOJ has not adopted a specific version of the Web Content Accessibility Guidelines (WCAG) as a binding rule for Title III the way it has for state and local government websites under Title II. DOJ's own guidance says plainly that it "does not have a regulation setting out detailed standards" for Title III web accessibility, and that businesses have flexibility in how they get there. DOJ confirmed in late 2025 that it is re-examining its ADA Title II and Title III regulations, and a dedicated Title III web-accessibility rulemaking has been paused, so do not expect a bright-line federal web-accessibility rule for private businesses to arrive soon — but that is a policy choice about rulemaking, not a statement that the underlying law doesn't apply.

Separately, in 2024 DOJ finalized a rule requiring state and local government websites and apps to meet WCAG 2.1 Level AA, with phased compliance dates (which DOJ has since moved). That rule is Title II and applies to government entities, not private businesses — but it is the clearest signal of what federal regulators consider the accessibility baseline, and courts and plaintiffs routinely point to it by analogy when a business's site is not accessible.

Why "unsettled" doesn't mean "safe to ignore"

Federal appeals courts disagree with each other on some of the finer legal questions — for instance, whether a website has to connect to a physical store or location to count as a "place of public accommodation," or whether a purely online business can be covered on its own. Because the courts disagree, and the U.S. Supreme Court has not resolved it, businesses in different parts of the country can face different legal exposure for the exact same website. That uncertainty is itself part of the risk: it means a demand letter or lawsuit can be filed and can survive a motion to dismiss in many jurisdictions, even though the ultimate legal theory hasn't been nailed down nationally.

The practical standard courts actually use: WCAG

Even without a binding Title III regulation, WCAG has become the de facto yardstick. In DOJ settlement agreements, consent decrees, and the vast majority of private lawsuits and demand letters, WCAG 2.1 Level AA (or the newer WCAG 2.2 Level AA) is the standard plaintiffs' lawyers cite and the standard businesses agree to meet when they settle. WCAG is developed by the World Wide Web Consortium (W3C) and covers things like whether images have text alternatives, whether color contrast is sufficient for low-vision users, whether every function works with a keyboard alone (not just a mouse), and whether video has captions. Building toward WCAG 2.1 or 2.2 AA is the most defensible, evidence-based way to reduce your risk, even though no law makes it mandatory for every private business yet.

The real litigation risk

Web-accessibility demand letters and "tester" lawsuits — filed by individuals or advocacy organizations, often using automated scanning tools to flag issues like missing alt text or poor contrast — are a well-documented and active area of ADA litigation, and the number of these cases has grown in recent years. A few honest points about this risk:

• It targets businesses of all sizes, including small, local, and online-only sellers — not just large companies.
• A demand letter usually arrives before a lawsuit, often offering to settle for a payment plus a promise to fix the site. Do not ignore it, and do not sign anything or send money without at least a quick read by an attorney familiar with ADA Title III.
• Genuine accessibility problems are common: independent tallies show web-accessibility ADA filings rising year over year, and studies of business homepages consistently find most sites fail basic WCAG checks. This is not a rare "gotcha" niche — it is a widespread, real gap in how small business sites are typically built.
• So-called accessibility "overlay" widgets — the little icon that claims to fix accessibility automatically with one script — have themselves become a target of lawsuits and have been criticized by disability advocates for not actually fixing underlying code problems. An overlay is not a substitute for the steps below.

What to do: cheap, good-faith steps

You do not need a full-scale technical rebuild to meaningfully reduce risk and, more importantly, to make your site usable for real customers with disabilities. A reasonable, documented effort matters both because it helps real people and because it shows good faith if a dispute arises.

1. Add real alt text to images. Every meaningful image (product photos, buttons that are images, your logo) needs a short, accurate text description so screen readers can convey it. Purely decorative images should be marked so screen readers skip them.
2. Check color contrast. Text needs enough contrast against its background to be readable by people with low vision or color blindness. Free browser-based contrast checkers can flag failing text/background combinations in minutes.
3. Make everything keyboard-operable. Try navigating your entire site — menus, forms, checkout, booking widgets — using only the Tab, Enter, and arrow keys, no mouse. If you get stuck or trapped somewhere, a screen-reader user will too.
4. Use real headings and labels. Structure pages with proper heading tags (not just bold text that looks like a heading), and make sure every form field has a visible, programmatically associated label.
5. Caption video and provide transcripts for audio. This helps deaf and hard-of-hearing visitors and also helps your SEO.
6. Run a free automated scan, then fix what it finds. Automated tools only catch a portion of real-world barriers (they can't tell you if your alt text is accurate, for example), but they're a fast, free first pass. Follow up with a manual click-through, or a review by someone who actually uses a screen reader, if your budget allows.
7. Fix your intake and contact forms. Contact and appointment forms are frequently the most-cited barrier — make sure they're keyboard-usable and clearly labeled.
8. Keep records of what you did and when. A dated log of the fixes you made, the tools you used, and any professional audit is your best evidence of good-faith effort if you're ever challenged.
9. Provide a way to report problems. A simple "accessibility feedback" contact method on your site lets a frustrated visitor reach you directly instead of a lawyer first — and gives you a chance to fix a real problem quickly.

If you get a demand letter

Read it, don't panic, and don't sign a settlement or release on your own if you don't fully understand what you're agreeing to. Talk to an attorney who handles ADA Title III matters before you respond — many demand letters are boilerplate sent to hundreds of businesses, but the underlying legal exposure and the right response depend on your specific facts and your circuit's case law. This is general information, not a substitute for that conversation.

A note on employees vs. customers

It's easy to confuse two different parts of the ADA. The employment provisions of the ADA (Title I) generally apply to employers with 15 or more employees and govern how you treat job applicants and your own workforce, including reasonable accommodations. Website accessibility for customers falls under the public-accommodation provisions (Title III), which are not tied to your employee count — a solo freelancer's customer-facing website and a 200-employee retailer's website can both be reached by Title III if the business is a public accommodation. Don't assume that being a small operation with few or no employees puts your website outside the ADA's reach. (For your obligations to your own workers, see our material on the employer's employment-law duties.)

Bottom line

The law on business website accessibility is real, actively enforced through litigation, and still evolving — there is no single federal regulation nailing down every technical requirement for private businesses the way there now is for state and local governments. Building your site toward WCAG 2.1 or 2.2 Level AA, focusing first on alt text, contrast, keyboard access, and clear forms, is the most practical way to lower your legal risk and serve more of your customers well. Check ada.gov's web accessibility guidance directly, since DOJ's position and any future rulemaking can change. For anything significant, a quick conversation with an attorney who handles ADA Title III matters is worth it; free help is also available through the SBA and SCORE.

This is general information, not legal, tax, or financial advice, and reading it does not create an attorney-client relationship.