ADA Compliant Website: Why No Badge or Certificate Exists

The Americans with Disabilities Act was signed in 1990, years before the modern web. It bans discrimination on the basis of disability in places of public accommodation, and courts have increasingly treated business websites as part of that. What the statute does not do is say what an accessible website looks like. There is no section listing required alt text, contrast ratios, or keyboard behavior.

So “ADA compliant” is shorthand, not a defined status. In practice people use it to mean a site that people with disabilities can use, measured against the Web Content Accessibility Guidelines (WCAG) (opens in new tab), usually Level AA. Our explainer on the difference between WCAG and the ADA goes deeper on how the two fit together.

No. The Department of Justice does not certify websites, does not run an approval program, and does not issue seals. No government agency will hand you a document that says your site is ADA compliant, and no such document would bind a court or a plaintiff if you had one.

That matters because a lot of marketing says otherwise. If a vendor sells you a “certified ADA compliant” badge, ask who certifies it and against what. Usually the answer is the vendor itself. A badge is a claim about your site, not proof, and a claim that overreaches can make things worse. The FTC fined one overlay vendor $1 million over its automatic compliance marketing, which we cover in our post on accessiBe alternatives after the FTC fine.

Third parties can audit your site and write a report. A VPAT documents how a product measures against a standard. Those are useful records. They are still descriptions of a moment in time, not certificates of legal compliance.

For private businesses (ADA Title III), there is still no regulation that names a web standard. In practice, settlements, consent decrees, and DOJ statements keep landing on WCAG 2.1 or 2.2 at Level AA. WCAG 2.2 is the current version and is backward compatible with 2.1, so building to it covers the older target too. Our WCAG 2.2 explainer lists what was added.

State and local governments are different. The DOJ published a 2024 rule under ADA Title II that names WCAG 2.1 Level AA for their web content and mobile apps, with phased deadlines. If you build sites for a city, county, school district, or public university, check the DOJ web guidance (opens in new tab) for the current dates. Federal agencies and their contractors have their own rules under Section 508.

None of this is legal advice. Which rules apply to you depends on who you are and where you operate, and a lawyer who handles accessibility law is the right person to ask.

Conformance is judged page by page, against the rendered result, and it changes every time someone publishes a new page, swaps a theme, or adds a widget. A site that passed last quarter can fail today without anyone touching the accessibility work.

It is also not fully automatable. Automated scanners, ours included, catch a real and valuable slice of problems, but the industry consensus is that automation covers roughly 30 to 40 percent of WCAG success criteria. CompliaScan runs axe-core plus 9 custom checks on top of it. The rest, such as whether alt text is meaningful, whether focus order makes sense, or whether an error message is understandable, needs a person. We break down that split in automated vs manual accessibility testing.

So a tool that promises your site will be fully compliant after you paste in one line of code is promising something no tool can deliver. We explain why in do accessibility overlays work.

UsableNet counted 3,117 federal ADA web lawsuits in 2025. Plaintiffs do not check for badges. They look for concrete barriers: unlabeled form fields, images without alt text, low contrast, menus a keyboard cannot operate. Small businesses are named routinely, not just large brands. Read ADA website lawsuits in 2026 for the pattern.

The practical takeaway is that you cannot buy your way to a safe status. What you can do is reduce the barriers a plaintiff would find, and keep evidence that you are working on the rest.

Since there is nothing to certify, aim for the next best thing: a site that is measurably better than it was, plus a paper trail that shows steady effort. This is not a legal guarantee, but it is the position an accessibility-minded business wants to be in.

1. Pick WCAG 2.2 Level AA as your target. It is the standard everyone else is measuring against.
2. Scan your key pages. Start with the home page, contact and checkout or booking flows, and your top landing pages. Our free WCAG checker gives you a list of automated findings in minutes.
3. Fix the high-impact issues first. Missing form labels, missing alt text, low contrast, and broken keyboard access account for most of what shows up in complaints. See the most common WCAG failures.
4. Test by hand what scanners cannot. Tab through your pages with a keyboard, try a screen reader on one key flow, and zoom to 200 percent. Our keyboard accessibility guide shows how.
5. Publish an accessibility statement. State your target, known gaps, and a real contact for feedback. Our statement generator drafts one, and the how-to guide explains what to include. Only claim what is true.
6. Re-scan on a schedule. Monitoring catches regressions after redesigns and content updates. See accessibility monitoring.
7. Keep dated records. Save scan reports, fix logs, and the statement history. If someone ever raises a complaint, a timeline of good-faith work is worth having.

Talk to a lawyer before you do anything else. This article is general information, not legal advice, and how to respond to a specific claim is a legal question. For a plain description of what these letters usually contain and how the timeline tends to run, see what happens in the first 14 days.

Can I get an ADA compliance certificate? Not from any government body. Private audit reports and VPATs exist, but they are documents about a point in time.

Does an accessibility badge protect me? No. A badge is a claim, and an inaccurate one can hurt your credibility.

Does passing an automated scan mean I am compliant? No. It means the issues automation can detect were not found. Manual review covers the rest.

Which level should I target? WCAG 2.2 Level AA. Our plans include scheduled scans if you want ongoing monitoring, and the WCAG checklist helps with manual review.

An ADA compliant website is not a status you receive, it is a condition you maintain: a site people with disabilities can actually use, built to a recognized standard, checked regularly, and honestly documented. Skip anyone selling a shortcut. Start by scanning your site to see where you stand, then work through the list above one fix at a time.