You cannot tell if a website is ADA compliant by looking at it. ADA website compliance is measured against the Web Content Accessibility Guidelines (WCAG), and the only way to verify conformance is through a (manual) accessibility audit conducted by a qualified auditor. Automated checkers flag approximately 25% of issues, so a clean scan score means very little on its own. The strongest signals of a compliant website are a recent WCAG 2.1 AA or 2.2 AA audit report, completed remediation work, validation of fixes, and supporting documentation such as an accessibility statement.
| Signal | What It Tells You |
|---|---|
| Recent WCAG audit report | A (manual) audit against WCAG 2.1 AA or 2.2 AA identifies the issues a site actually has. |
| Completed remediation | Audit issues were fixed by developers and the fixes were validated by the auditor. |
| Accessibility statement | Public documentation of the conformance level, evaluation date, and contact method. |
| Screen reader usability | Pages can be navigated and operated with NVDA, JAWS, or VoiceOver without dead ends. |
| Keyboard operability | Every interactive element is reachable and usable with the keyboard alone. |
What does ADA compliant actually mean for a website?
The ADA itself does not list technical requirements for websites. Courts, the DOJ, and most settlements point to WCAG 2.1 Level AA as the working standard, with WCAG 2.2 AA increasingly requested.
So when someone asks if a website is ADA compliant, the real question is whether it conforms to WCAG at the AA level. Conformance is binary at the criterion level. Either each success criterion is met or it is not.
This is why a glance at a homepage tells you almost nothing. A site can look polished and still fail dozens of criteria that only a trained auditor would catch.
Why automated checkers cannot give you the answer
Free checkers and paid scans are useful for surface-level signals. They identify missing alt text, color contrast issues on static elements, and some structural problems.
What they cannot do is evaluate context. A scan does not know if alt text is meaningful, if a heading structure reflects the actual content hierarchy, or if a custom widget is operable with a screen reader. Scans only flag approximately 25% of issues, which means a perfect checker score and a non-conformant website can be the same website.
If someone tells you their site is ADA compliant because a checker gave them a 100, that is not evidence. That is a screenshot.
The signals that actually mean something
There are a handful of indicators that point to a website being on real footing.
A recent WCAG audit report. The audit should be against WCAG 2.1 AA or 2.2 AA, conducted manually, and dated within the last 12 months.
Evidence of remediation. The audit identifies issues, developers fix them, and the auditor validates the fixes. Without validation, remediation is unverified.
An accessibility statement. A clear statement listing the conformance target, the date of evaluation, and a way to report issues.
Functional usability. The site can be operated with a keyboard. Headings, landmarks, and form labels announce correctly with a screen reader.
Ongoing monitoring. Websites change. A site that was audited two years ago and has shipped new pages since is no longer a known quantity.
How to check a website yourself in a few minutes
You will not be able to confirm conformance this way, but you can quickly tell if a site is clearly not compliant.
Tab through the page using only the keyboard. Watch for visible focus indicators. If focus disappears or you get stuck in a menu, that is an issue. Try to operate the main navigation, a form, and any modal without touching the mouse.
Turn on a screen reader. VoiceOver is built into Mac and iOS. Listen to how the page is announced. If buttons read as “button button” or images read as long file names, the site has not been built with accessibility in mind.
Look for an accessibility statement in the footer. Read it. A vague statement with no audit date or standard reference is not strong evidence of anything.
Why a manual audit is the only definitive answer
A qualified auditor evaluates every relevant WCAG success criterion against the actual content and code of the site. The auditor identifies each issue, points to the location, references the criterion, and documents what needs to change.
That report is the document that tells you, with specificity, whether a site conforms. Without it, every claim of ADA compliance is a guess.
This is also why a website’s compliance status changes over time. Add a new page, swap a template, or push a redesign, and the previous audit no longer reflects the current site. Conformance is a snapshot, not a permanent state.
Frequently Asked Questions
Is there an official ADA certification for websites?
No. There is no government certification for ADA website compliance. The closest equivalent is a recent WCAG audit report from a qualified third party, paired with remediation and validation. Any vendor claiming to issue an official ADA certification is selling something the government does not recognize.
How often should a website be re-evaluated?
At least annually for sites with regular updates, and after any major redesign, template change, or platform migration. Ecommerce sites and content-heavy sites benefit from monitoring between audits to catch regressions early.
Can a scan tell me if a website is ADA compliant?
No. A scan can flag a portion of issues but cannot determine WCAG conformance. Scans miss context-dependent issues, custom components, and anything that requires human judgment. Use scans as a complement to a (manual) audit, never as a replacement.
What if the site has an accessibility statement but no audit?
A statement without a referenced audit is a marketing document. It signals intent but does not verify conformance. Ask for the audit date, the standard evaluated against, and who conducted the work.
The short version: you cannot tell a website is ADA compliant by looking at it, scanning it, or trusting a badge in the footer. You can tell by reading the audit report, confirming remediation was completed, and verifying the site still matches what was evaluated.
Contact me to discuss an audit for your website: Contact.