Do I Have to Make My Website ADA Compliant?

A plain-English answer for business owners: who actually has to comply, what "ADA compliant" really means for a website, why there is no official certification, and how to get there without falling for overlay marketing.

In practice, yes — if your business serves the public in the United States, your website should meet accessibility standards. Most courts treat a business website as a "place of public accommodation" under Title III of the Americans with Disabilities Act, so it's expected to be usable by people with disabilities. There is no government form to file and no official "ADA-certified" stamp; compliance means your site actually meets the Web Content Accessibility Guidelines (WCAG) 2.1/2.2 Level AA — the standard courts and regulators use.

That is the short version. The rest of this page explains who is covered, what the standard involves, what happens if you ignore it, and how to actually get compliant instead of buying a badge. You can also scan your site free to see where you stand right now.

Who has to comply

The ADA's Title III applies to businesses that are "places of public accommodation" — a broad category that includes retailers, restaurants, hotels, medical and dental offices, salons, gyms, banks, entertainment venues, and most professional services open to the general public. When those businesses operate a website, most federal courts have held that the site is a service of the business and therefore falls under the same expectation of accessibility.

A few practical points:

• Small businesses are not exempt for being small. Title III has no small-business carve-out based on revenue or employee count. Small firms receive accessibility demand letters routinely.
• Public-facing is the key test. If customers can find you, browse products, book appointments, or buy from you online, assume the site needs to be accessible.
• There is genuine nuance at the edges. Purely internal tools, private membership organizations, and businesses with no public-facing services can sit in grayer areas, and courts across different regions have not ruled identically. This is one reason a documented, good-faith effort matters more than a yes/no label.
• State and international laws raise the stakes. California's Unruh Civil Rights Act can attach statutory damages to an accessibility failure, and businesses that sell into the European Union face the European Accessibility Act (EAA), which took effect in 2025. Your exposure is often broader than the federal ADA alone.

What "ADA compliant" actually means for a website

The ADA itself does not contain technical web specifications. It does not say "use alt text" or "meet a 4.5:1 contrast ratio." So how does anyone measure compliance? Through the Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium (W3C). WCAG is the de-facto technical standard that courts, regulators, and plaintiff attorneys use as the benchmark.

The relevant target is WCAG 2.1 Level AA, with WCAG 2.2 Level AA being the newer, backward-compatible version. Meeting 2.2 AA also satisfies 2.1 AA, so aiming for 2.2 AA keeps you current. The U.S. Department of Justice adopted WCAG 2.1 AA in its 2024 rule for state and local government websites, which further cemented it as the reference point in private-sector matters as well.

WCAG organizes its requirements around four principles, often abbreviated POUR:

• Perceivable — content can be seen or heard (for example, images have text alternatives, video has captions, contrast is sufficient).
• Operable — the site works with a keyboard alone, has visible focus, and doesn't trap users.
• Understandable — text is readable, forms have clear labels, and behavior is predictable.
• Robust — the code works with assistive technologies like screen readers now and as they evolve.

Crucially, there is no official ADA "certification." Compliance is a factual state of your website measured against WCAG — not a certificate, seal, or license anyone issues. You can and should keep your own records of conformance, but that is documentation you maintain, not a stamp from a regulator.

What happens if I don't

The most common consequence is a demand letter from a plaintiff's attorney, alleging that your site is inaccessible to users of screen readers, keyboard navigation, or other assistive technology. These letters typically reference WCAG 2.1 AA, ask for remediation, and often request a monetary settlement. Some matters escalate into a filed lawsuit.

Beyond the federal ADA, state laws can add teeth — California's Unruh Act attaches statutory damages per violation, which is one reason California sees so much accessibility litigation. If you sell into the EU, the European Accessibility Act adds a separate compliance obligation with its own enforcement.

If you want the detail on legal risk specifically, see our companion answer: Can I be sued if my website isn't ADA accessible? The short version is that the strongest position is a documented, good-faith remediation effort completed before — not after — a letter arrives.

Is there an official ADA website certification?

No. This is worth repeating because the misconception drives a lot of wasted money. No U.S. government agency certifies, approves, or "blesses" a website as ADA compliant, and no official seal exists.

Treat the following as red flags:

• Any vendor that claims to "certify" or "guarantee" ADA or WCAG compliance.
• Any product that says installing a script or overlay widget makes you compliant. Overlays do not reliably produce WCAG conformance, courts have continued to hear cases against sites that use them, and overlays can introduce new barriers for assistive-technology users.
• Any "compliance badge" sold as legal protection.

The overlay problem isn't just theory. In 2025 the U.S. Federal Trade Commission announced a $1,000,000 settlement with the accessibility overlay vendor accessiBe over its accessibility claims. If overlays actually created compliance, that action wouldn't have happened. Real compliance comes from fixing the underlying code.

How to actually comply

Getting to WCAG 2.2 AA is a process, not a purchase. A realistic path looks like this:

1. Scan for real WCAG barriers. Start with an automated audit to find the concrete issues — missing alt text, low color contrast, unlabeled form fields, keyboard traps, missing focus indicators, and broken heading structure. This gives you a prioritized, dated baseline. You can run a free scan to begin.
2. Fix the code. Work through issues by severity. Automated tools catch a large share of problems; the remainder needs manual review, because things like meaningful alt text and logical reading order require human judgment.
3. Verify with assistive technology. Re-scan after fixes, and test key flows (navigation, forms, checkout) with a keyboard and a screen reader to confirm the experience is genuinely usable.
4. Keep a good-faith record. Save your audit reports, note what you found and fixed, and log dates. If a letter ever arrives, this documentation is one of your best assets.
5. Maintain it. Accessibility is ongoing. New pages, new plugins, and redesigns can reintroduce barriers, so re-scan on a schedule.

If you want a concrete, business-friendly checklist to work from, see our WCAG 2.2 AA checklist for small businesses.

Do very small or brochure sites have to comply?

Here's the honest nuance: not every website carries an identical obligation, and anyone who tells you the rules are perfectly black-and-white is overselling. That said, the safe assumption for almost any public-facing business is that the site should be accessible.

A simple one-page "brochure" site for a business open to the public is still a service of that business, and plaintiffs have targeted small brochure sites — a small footprint is not a shield. Where genuine gray areas exist — a truly private site, an internal-only portal, a members-only organization with no public services, or a jurisdiction whose courts have ruled differently — the right move is to talk to counsel rather than guess. And because accessibility also expands your actual customer base and improves usability for everyone, meeting WCAG 2.2 AA is worthwhile even where the legal line is fuzzy.

This page is general information, not legal advice. For guidance on your specific situation, consult a qualified attorney.

Frequently asked questions

Is ADA compliance legally required for websites?

For most public-facing U.S. businesses, effectively yes. The ADA does not contain a line that says "websites must be accessible," but most federal courts treat the website of a business open to the public as a service of a "place of public accommodation" under Title III. That means it is expected to be usable by people with disabilities. There is no form to file and no license to obtain—compliance is measured by whether your site actually meets recognized accessibility standards, in practice WCAG 2.1/2.2 Level AA.

Is there an official ADA certification for websites?

No. There is no government body that certifies, approves, or stamps a website as "ADA compliant," and no official seal exists. Any vendor that claims to "certify" or "guarantee" ADA compliance—or that says a widget makes you compliant—should be treated as a red flag. Compliance is a factual state of your code measured against WCAG, not a badge you buy. You can document your own good-faith conformance, but that is a record you keep, not a certificate anyone issues.

Does my small business site count?

Usually yes if you serve the public. Restaurants, retailers, clinics, salons, contractors, hotels, and professional services with a website are the most common targets of accessibility demand letters, and small businesses are not exempt simply for being small. There is some legal nuance—obligations can differ for purely internal sites, private membership organizations, and businesses with no public-facing services—but if customers can find, browse, or transact with you online, you should assume the site needs to be accessible.

What standard do I need—WCAG 2.1 or 2.2?

WCAG 2.1 Level AA is the widely referenced benchmark used by courts, regulators, and plaintiff attorneys, and the U.S. Department of Justice adopted WCAG 2.1 AA in its 2024 rule for state and local government websites. WCAG 2.2 AA is the newer version, is backward-compatible, and adds a handful of criteria; meeting 2.2 AA also satisfies 2.1 AA. A practical target for most businesses is to aim for WCAG 2.2 AA, which keeps you current.

Do overlays make me compliant?

No. Accessibility overlay widgets—scripts that promise to automatically fix a site—do not reliably produce WCAG conformance, and courts have continued to hear cases against sites that used them. In 2025 the Federal Trade Commission announced a $1,000,000 settlement with accessibility overlay vendor accessiBe. Overlays can also introduce new barriers for assistive-technology users. Real compliance comes from fixing the underlying code, not layering a script on top of it.

What happens if my website is not accessible?

The most common consequence is a demand letter from a plaintiff attorney alleging your site is inaccessible under Title III, often requesting remediation plus a monetary settlement. Some matters escalate to a filed lawsuit. State laws such as California's Unruh Civil Rights Act can add statutory damages, and businesses selling into the EU face the European Accessibility Act. A documented, good-faith remediation effort is one of the strongest positions you can be in.

How do I actually make my website ADA compliant?

Scan your site for real WCAG barriers, fix them in the code (alt text, color contrast, labeled form fields, keyboard operability, heading structure, captions), verify with a re-scan and manual assistive-technology testing, and keep a dated record of what you found and fixed. Treat accessibility as ongoing maintenance rather than a one-time project, because content and features change over time.