The only reliable way to know if a website is ADA compliant is to conduct a (manual) WCAG 2.1 AA audit. The ADA does not publish a technical standard for websites, so courts, regulators, and demand letters point to WCAG as the benchmark. A scan or accessibility checker can flag some issues, but scans only flag approximately 25% of issues and cannot determine conformance. A trained auditor evaluates the site against each success criterion and identifies what passes, what fails, and what needs remediation. The resulting audit report is the documented evidence of where the site stands.
| Step | What It Tells You |
|---|---|
| Use an accessibility checker | Surface-level signal only. Catches roughly 25% of issues. |
| Conduct a (manual) WCAG audit | Evaluates the full site against WCAG 2.1 AA success criteria. |
| Review the audit report | Identifies every issue, severity, and location for remediation. |
| Remediate and validate | Fixes are applied, then re-evaluated to confirm conformance. |
| Publish an accessibility statement | Documents the standard met and provides a contact method. |
What Does ADA Compliance Mean for a Website?
The ADA itself does not list technical website requirements. Courts and the Department of Justice have pointed to WCAG, with WCAG 2.1 AA serving as the practical standard most plaintiffs, defense attorneys, and regulators reference.
So when someone asks if a website is ADA compliant, the real question is whether it conforms to WCAG 2.1 AA. That is the bar to evaluate against.
Why You Cannot Tell from a Checker Alone
Free accessibility checkers and browser extensions can return a score in seconds. The score feels concrete, but it is incomplete.
Automated tools detect roughly a quarter of WCAG issues. They catch missing alt attributes, empty form labels, and certain contrast ratios. They cannot evaluate whether alt text is meaningful, whether keyboard focus order makes sense, whether ARIA is implemented correctly, or whether a custom component behaves as a screen reader user expects.
A score of 95 or even 100 on a checker does not mean the site is ADA compliant. It means the scanner did not flag anything it knows how to flag.
How a (Manual) WCAG Audit Confirms Conformance
A (manual) accessibility audit is the only way to determine WCAG conformance. A trained auditor reviews each page against the applicable success criteria, using screen readers, keyboard-only navigation, color contrast tools, and code inspection.
The auditor evaluates representative templates across the site, mobile and desktop where relevant, and produces a report that identifies each issue, the WCAG criterion it relates to, the location, and guidance for remediation.
Accessible.org audits are always fully manual. The output is a working document the development team can act on, not a list of automated flags filtered into a PDF.
More on how audits work is covered in this short video.
Signs a Website Likely Is Not ADA Compliant
Even without an audit, certain patterns are clear signals of nonconformance. If any of the following apply, the site has work ahead of it:
Images that lack meaningful alt text or use filenames as alt are a common indicator. Keyboard users who cannot reach or operate menus, forms, or modals point to significant access gaps. Hidden or removed focus indicators in CSS, text contrast below 4.5:1 for body copy, form fields without programmatic labels, videos without captions and transcripts, headings used for styling rather than structure, and custom components such as carousels, dropdowns, and tabs that do not announce state to screen readers all signal nonconformance.
These patterns appear in nearly every ADA website lawsuit and demand letter.
What Documentation Confirms Compliance Posture
Two documents carry weight: the audit report and the accessibility statement.
The audit report from a qualified provider is the technical record of conformance against WCAG 2.1 AA. After remediation and validation, it serves as evidence of the work completed.
The accessibility statement, published on the site, names the standard the site conforms to and offers a contact method for accessibility issues. It is not a legal shield, but it signals intent and provides a path for users who encounter issues.
How Often Should You Re-evaluate?
Websites change. New pages, templates, plugins, and design refreshes can introduce issues that did not exist at the time of the last audit.
A reasonable cadence is an annual (manual) audit, with smaller scoped re-evaluations after major releases. Between full audits, scan-based monitoring can flag regressions on the issues automated tools catch, which keeps the lower-hanging items from piling up.
Frequently Asked Questions
How do I get a definitive answer on whether my website is ADA compliant?
Conduct a (manual) WCAG 2.1 AA audit with a qualified provider. The audit report identifies every issue against the standard, and once those issues are remediated and validated, you have documented conformance. That is the closest thing to a definitive answer the current legal environment offers.
Can an accessibility checker tell me if my site is ADA compliant?
No. Checkers detect approximately 25% of issues and cannot evaluate context, intent, or assistive technology behavior. A clean checker score is not the same as WCAG conformance.
Is WCAG 2.1 AA or WCAG 2.2 AA the right standard to evaluate against?
WCAG 2.1 AA remains the most widely referenced standard for ADA website compliance. WCAG 2.2 AA is gaining traction, especially for newer audits, and is a sound choice if your team wants to evaluate against the most current criteria. Either is defensible.
Does a (manual) audit cover the entire site?
An audit covers representative templates and key user flows rather than every single page. For a typical site, evaluating the homepage, primary templates, key forms, and checkout or conversion paths captures the issues that exist across the codebase.
Knowing where a website stands against WCAG 2.1 AA is a matter of evaluation, not estimation. A scan gives a hint. An audit gives an answer.
Contact the Accessible.org team to request a WCAG audit for your website.
