Is My Website ADA Compliant? How to Actually Check in 2026

There is no single test that returns a yes or a no. "ADA compliant" resolves into three questions you have to answer in order: which law covers your organization, which technical standard that law names, and how much of that standard your site meets today. A county government and a private retailer are held to different bars by different rules. You can settle the first two questions in about five minutes. You can get a defensible first read on the third in about two hours with a keyboard, a browser, and a free scanner. This article walks that method end to end.

This is a spoke article in Vervali's accessibility testing cluster. The parent is our complete guide to WCAG 2.2, ADA, Section 508, and EAA compliance, which covers the standards themselves in depth, and a sibling covers how WCAG 3.0 will change accessibility testing when it arrives. This page stays on one job: how you check your own site against the standard that applies to you right now.

The reason the question keeps getting asked is a litigation curve that has not flattened. Seyfarth Shaw's ADA Title III tracker counted 3,117 federal website accessibility lawsuits filed in 2025, a 27% increase over 2024's 2,452, with website cases rising to 36% of all federal ADA Title III filings from 28% a year earlier. Meanwhile the WebAIM Million scan of the top one million home pages in February 2026 found detectable WCAG 2 failures on 95.9% of them, averaging 56.1 errors per page. The odds that your site is clean are low, and the odds that you can prove it without testing are lower.

What You'll Learn

• Which of the three US accessibility regimes applies to you, and which WCAG version each one names

• The current DOJ Title II compliance dates after the April 2026 extension, and why most articles still print the old ones

• A nine-point self-check you can run today, each item mapped to its exact WCAG success criterion

• Where automated scanners stop finding problems, with the numbers from three independent studies

• What a professional audit produces that a scan cannot, and how to decide whether you need one

Why Is There No Single Yes or No Answer to ADA Compliance?

The word "compliant" does most of the damage here, because the standard everyone points to does not use it. W3C's own conformance page describes the WCAG logos as a claim: "Web pages with one of these logos claim conformance to WCAG 2.2 at Level AA." It then adds the line that reframes the whole question: "Claims are not verified by W3C. Content providers are solely responsible for the use of these logos." Conformance is measured against numbered success criteria, on a defined set of pages, at a moment in time, and it is self-declared. Nobody hands out a certificate that settles the matter forever.

The second reason the question has no clean answer is that for most private businesses, no regulation defines the target. The Department of Justice states this plainly in its guidance on web accessibility and the ADA: "The Department of Justice does not have a regulation setting out detailed standards, but the Department's longstanding interpretation of the general nondiscrimination and effective communication provisions applies to web accessibility." DOJ goes further and confirms the flexibility explicitly: "Businesses and state and local governments can currently choose how they will ensure that the programs, services, and goods they provide online are accessible to people with disabilities." The obligation is real. The checklist is not published.

Key Finding: "Claims are not verified by W3C. Content providers are solely responsible for the use of these logos." Every WCAG conformance claim on the web is a statement the site owner made about their own testing, which is why the evidence behind the claim matters more than the claim. Source: W3C WAI.

The third reason is that the target moves. DOJ's rulemaking on web accessibility ran through an advance notice in 2010, a supplemental notice in 2016, a full withdrawal of both in 2017, a fresh proposal in 2023, and a final rule in 2024, before the compliance dates in that final rule were pushed back again in April 2026. A site that conformed to WCAG 2.0 Level AA in 2019 is measured against a longer list today if it falls under Title II. So the honest version of "is my website ADA compliant" is three narrower questions, and the first one is the one almost nobody answers correctly.

Which ADA Rule Actually Applies to Your Website?

Three separate regimes get collapsed into the phrase "ADA compliance," and they name three different technical standards. Getting this wrong means testing against the wrong list.

ADA Title II covers state and local government entities. DOJ's 2024 final rule adopted a specific standard, stated on the department's own fact sheet: "The Web Content Accessibility Guidelines (WCAG) Version 2.1, Level AA is the technical standard for state and local governments' web content and mobile apps." This regime has hard dates, and those dates changed recently. An Interim Final Rule, Federal Register document 2026-07663, was published and took effect on April 20, 2026, extending both compliance dates by exactly one year. Entities with a total population of 50,000 or more moved from April 24, 2026 to April 26, 2027. Entities under 50,000 population, and any special district government regardless of size, moved from April 26, 2027 to April 26, 2028. The technical standard did not change. Only the clock did.

ADA Title III covers private businesses open to the public. There is no DOJ-adopted technical standard here at all, which is the single fact most competing articles on this question get wrong. WCAG 2.1 Level AA operates as the working benchmark because that is what consent decrees, settlements and expert reports keep converging on, and courts have accepted that websites fall within Title III's reach. The Supreme Court declined to review Robles v. Domino's Pizza on October 7, 2019, leaving the Ninth Circuit's nexus holding in place. Practically, a private business testing against WCAG 2.1 Level AA is testing against the bar that plaintiffs' experts will apply, while knowing it is a litigation benchmark rather than a codified rule.

Section 508 covers federal agencies and covered federal procurement, and it names an older standard. The US Access Board's revised standards at 36 CFR Part 1194, issued January 18, 2017, state it directly: "Electronic content shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0." That is WCAG 2.0, not 2.1 and not 2.2. If you sell software into the federal market, the conformance report a contracting officer asks for is scored against WCAG 2.0 A and AA. Our explainer on what Section 508 compliance testing means covers that standard in more detail.

The European Accessibility Act sits alongside these for anyone selling into the EU, and the complete standards guide covers it properly. Accessibility is also one regulatory bar among several most products have to clear, alongside the data-security regimes covered by Vervali's compliance testing services. For the accessibility bar specifically, Vervali's accessibility testing services scope engagements to whichever of these three regimes applies before any testing starts.

Watch Out: If an article, a vendor deck or an internal memo tells you the Title II deadline is April 24, 2026, it was written before April 20, 2026 and has not been updated. That date was superseded by the Interim Final Rule and is no longer a live obligation. Planning remediation against a date that has moved by a year distorts every downstream decision about scope and budget.

How Do You Check Your Own Website in the Next Two Hours?

Start by choosing what to test, because the home page alone tells you almost nothing about a site. W3C's evaluation methodology begins with defining scope and selecting a representative sample, and the same logic holds at small scale. Pick seven pages covering your distinct templates and critical tasks: the home page, a listing or search-results page, a content page with images and video, a form, the login or registration flow, the checkout or submission step, and one page with a data table. Those seven carry most of the markup patterns a site ships.

Then run these nine checks. Each one maps to a specific WCAG success criterion, so a failure gives you a number to log rather than a feeling.

A few of these need more than one line to run properly. On the keyboard pass, the failure to hunt for is a component you can Tab into and cannot Tab out of, which strands a keyboard user on the page. On focus, the common cause is a CSS reset that removed the browser outline and never replaced it. On alt text, remember that a scanner only checks whether the attribute exists: alt="image123" on a product photo passes every automated tool and fails the criterion outright. On contrast, standard text needs a ratio of at least 4.5:1 and large text at 18 point or 14 point bold needs at least 3:1, with logos and incidental text excepted. On reflow, 400% zoom at 1280px is equivalent to a 320 CSS pixel wide screen, and content must land in a single column with nothing clipped or overlapping.

For the ninth check you need an actual screen reader, and every operating system ships one. VoiceOver is built into macOS and iOS, TalkBack into Android, and NVDA is free on Windows. Turn one on and try to complete one real task end to end, such as adding an item and reaching the confirmation screen. Custom widgets built from generic elements are where this usually breaks, because a dropdown made of div elements has no role, no state and no accessible name unless someone added them deliberately.

Pro Tip: Run the keyboard pass first and the automated scan last. The keyboard pass takes fifteen minutes, needs no tooling, and surfaces the failures that most reliably block a real user from finishing a task. Starting with a scan report anchors the whole exercise to whatever the tool happened to detect, which is a fraction of what is there.

Where Do Automated Accessibility Scanners Stop Finding Problems?

Run a free scanner across your sample now. Axe, WAVE and Lighthouse are fast, free and worth running. What matters is reading the output with a correct sense of its coverage, and three good studies address exactly that. They disagree, and the reason they disagree is the most useful thing about them.

Deque Systems published the largest of the three in March 2021, covering more than 2,000 audits, 13,000 first-time-assessed pages and roughly 300,000 issues. Its headline finding was that automated testing identified 57% of digital accessibility issues. Deque attached its own caveat: that number counts total volume of issues, not the share of WCAG success criteria a tool can evaluate, and volume is dominated by a handful of highly automatable, highly frequent issue types. Which is exactly what the WebAIM data shows. Six error types account for 96% of all detected failures across the top million home pages: low contrast text on 83.9% of pages, missing alt text on 53.1%, missing form input labels on 51%, empty links on 46.3%, empty buttons on 30.6% and missing document language on 13.5%.

The UK Government Digital Service measured something different and got a lower number. Its team built a page with deliberately injected, known accessibility barriers and ran automated tools against it, which tests detection against ground truth rather than against issue volume. In the published blog round, ten tools were run against 143 injected barriers: the tools picked up 71% of the barriers between them, and 42 of the 143 were missed by every single tool tested. The companion audit data, covering thirteen tools against 142 barriers, reports the per-tool picture: the best performer caught 40% on a strict pass or fail basis and the weakest caught 13%. A third government source, the UK Department for Education's own testing guidance, lands independently in the same band and states that tools "only identify around 30% to 40% of issues."

Those numbers measure different things and all of them are correct. Automation catches a large share of issues by count, because contrast and missing labels are both very common and very machine-checkable. It catches a much smaller share of distinct barrier types, because judgment-dependent failures are invisible to a parser. The UK Department for Education gives the clearest illustration: an image of a classroom carrying alt="car" passes the automated test and fails the criterion, because a tool can confirm an attribute exists and cannot confirm it is true. The same guidance notes the reverse failure, where a logo's low contrast is flagged even though logos are excepted, which is why scanner counts need triage before they become a work plan.

Key Finding: "While the tools picked up the majority of the accessibility barriers we created, 71%, there was a large minority that would only have been picked up by manual checking." Of the 143 barriers the UK Government Digital Service injected, 42 were missed by all ten tools tested. Source: UK Government Digital Service, 2017.

One further wrinkle shows up the moment you run two scanners. Accessibility practitioner Sheri Byrne-Haber documented running the same public government page through different commercial vendors and getting contradictory verdicts, one reporting a perfect health score and another rating the page only semi-compliant, with no visibility into which tests either vendor ran. A single tool's green result is a statement about that tool's rule set.

How Do You Run a Structured Manual Assessment Across a Whole Site?

The two-hour pass tells you whether you have a problem. A structured manual assessment tells you how big it is, and it is a one-time deep pass a small team can run in one to two weeks. The scope is the full conformance list rather than nine highlights. WCAG 2.1 carries 50 success criteria across Levels A and AA combined, and that is the list Title II entities are measured against. WCAG 2.2, published as a W3C Recommendation on 5 October 2023, adds nine further success criteria on top of 2.1 and is worth testing against if you want headroom, though it is not the standard DOJ adopted for Title II.

Expand the page sample first, because six to eight pages is a smoke test. A real assessment covers every distinct template, every multi-step journey, the pages carrying the most traffic or revenue, and every state a component can be in. States matter more than people expect: an error message, a loading state, a modal over a modal, a disabled control that becomes enabled, and a filtered results view are all separate things to evaluate, and none of them show up in a crawl of static URLs.

Then test the journeys as well as the pages. Automation evaluates documents, so it cannot register, log in, add an item, hit a validation error, correct it and complete a purchase. That sequence is where failures compound, because one unlabeled field or an error message that never receives focus ends the task no matter how cleanly the rest of the page scores. Walk each critical journey once with the keyboard alone and once with a screen reader, and record where it stops.

Then label severity by consequence rather than by criterion level. Critical means a user cannot complete the task at all: keyboard traps, unlabeled required fields, error messages that are never announced, controls with no accessible name. Major means the task is completable with significant difficulty, such as an illogical reading order or a focus order that jumps around the page. Minor means the barrier is real and the task still succeeds, such as slightly-under-ratio contrast on secondary text. Log every finding with the page URL, the success criterion number, what happened, what should have happened, and a screenshot or a short recording.

Pro Tip: Give every finding a success criterion number the moment you log it. A defect that reads "the filter dropdown is hard to use with a screen reader" gets argued about. A defect that reads "filter dropdown fails SC 4.1.2 Name, Role, Value, Level A: the control exposes no role and no expanded state" gets fixed.

What Does a Professional Accessibility Audit Add That You Cannot Do Yourself?

The honest answer is scale, defensibility and documentation. W3C publishes its own Website Accessibility Conformance Evaluation Methodology, and its five steps describe what separates an audit from a scan: define the evaluation scope, explore the target website, select a representative sample, evaluate the selected sample, and report the findings. The third step is the one an internal team rarely has time to do rigorously. On an estate of a few thousand URLs, a sample that is truly representative of every template, journey and content type is what makes the conclusion hold for pages nobody opened.

Vervali's process maps onto that methodology across six steps. Scoping fixes the applicable standard and the target user needs. Automated scanning runs alongside expert manual review rather than ahead of it. Assistive technology compatibility is validated on real devices with screen readers and alternative input. Findings are categorized by WCAG level and business impact so that remediation has an order. Remediation guidance is written for the developers who have to implement it, with the criterion and the fix stated together. Re-testing then verifies the fixes and establishes an ongoing cadence, because conformance is a point-in-time result on a codebase that keeps changing.

The artifact a real audit produces is worth naming, because "we ran a scan" and "we have an ACR" carry different weight in a procurement conversation. The Voluntary Product Accessibility Template is a free template from the Information Technology Industry Council that, in ITI's words, "translates accessibility requirements and standards into actionable testing criteria." Filled in with real test results it becomes an Accessibility Conformance Report, declaring criterion by criterion whether the product supports, partially supports, does not support, or is not applicable to each requirement. That per-criterion record is what a federal contracting officer or an enterprise procurement team asks for, and a scanner output cannot substitute for it.

Scale is where this becomes concrete. Vervali audited NEOGOV, a US HR software provider serving more than 6,000 public-sector and education organizations, against Section 508 and its WCAG 2.0 Level AA success criteria and conformance requirements. The engagement covered more than 2,000 URLs. It surfaced and remediated more than 5,000 accessibility gaps, and during the work an additional product that sat outside the original scope was found to be non-compliant and was brought into remediation rather than left for a later cycle. The HR technology provider's submission went in inside the committed 90-day window, and certification was achieved on the first attempt. First-attempt certification at that scope is a methodology outcome: it means the sample was representative enough that the findings held across everything the sample stood for. That is what Vervali's accessibility testing methodology is built to produce.

Why Does an Accessibility Overlay Widget Not Answer This Question?

Overlay widgets promise to resolve this question with a script tag, and the regulatory record on that promise is now specific. On January 3, 2025 the Federal Trade Commission ordered accessiBe to pay $1 million over deceptive claims that its AI product could make websites compliant with accessibility guidelines. The FTC found the company's advertising that its automated product would make any website WCAG compliant to be false, misleading or unsubstantiated, and the order bars the company from repeating such representations without evidence to support them. That is a government enforcement action about a specific marketing claim, and it lines up with the coverage research: a runtime script sits on top of the same markup an audit would have to fix, and it cannot judge whether an image description is accurate or whether a checkout can be completed.

The litigation data points the same way. UsableNet's mid-2026 tracker reports that federal filings are on track to surpass 6,000 in 2026, close to 20% above 2025, and states that lawsuits against companies already using accessibility widgets continue to rise, with the presence of a widget failing to prove a meaningful deterrent. Treat that as a vendor-produced tracker rather than government data, and it still points in one direction: an overlay is not a legal shield.

Watch Out: An unactioned scan report can become evidence against you. Sheri Byrne-Haber's framing is worth quoting exactly: plaintiffs' attorneys will characterize the pattern of receiving a report and not remediating it as "willful disregard, your organization had the report, and anything short of complete remediation means you disregarded the report." If you commission a scan or an audit, commission the remediation plan in the same breath.

The alternative is not complicated. Fix the markup. Every one of the six error categories that make up 96% of detected failures is a source-level fix: a contrast value, an alt attribute, a <label> element, a link with text in it, a button with an accessible name, a lang attribute on the <html> element. Those changes hold across every browser, every assistive technology and every future scan, and they do not depend on a third-party script loading correctly.

What Should You Do With What You Found?

Match the finding to the next action rather than treating every result the same way.

You found nothing in the two-hour pass. Against a 95.9% baseline failure rate on scanned home pages, a clean result usually means the check missed something rather than that the site is clean. Re-run check 1 and check 9 specifically, since keyboard operation and custom component semantics are where a quick pass most often gives a false all-clear, and expand the sample to include a form and a multi-step journey.

You found one or two minor issues and nothing critical. Fix them, re-test the specific criterion, and put the nine-point check into your release routine so new templates get the same pass before they ship.

You found a keyboard trap, an unlabeled required field, or a journey you could not finish. Treat those as critical and fix them before the next release, because anything that stops a user completing a task carries both the highest user impact and the highest legal exposure.

You are a Title II entity. You have a dated obligation, so work backwards from April 26, 2027 or April 26, 2028 depending on your population tier. Audit, remediate, re-test and document, in that order, and leave room for the re-test.

You need documentation for a buyer or a procurement team. An Accessibility Conformance Report needs a real per-criterion evaluation behind it, which means a scoped audit rather than a scan.

Your real question is about one specific flow. If the concern is a checkout, a payment page or a billing portal rather than a whole site, our companion piece on ADA compliance for billing and payment portals covers the criteria that carry the most weight in transactional flows. For everything wider than accessibility, Vervali's full testing and QA services cover the other quality gates a release has to clear.

How Does Vervali Approach ADA Compliance Checking?

Two details of how Vervali runs the six stages above are worth spelling out, because they are where most engagements are won or lost. Automated scanning with Axe, WAVE and Lighthouse runs together with expert manual review rather than ahead of it, so the tools handle the machine-checkable categories and reviewers handle the judgment calls. Assistive technology compatibility is then validated on real devices, including TalkBack on Android and VoiceOver on iOS and macOS, because emulators do not reproduce how a screen reader announces a live component.

The scope covers WCAG 2.1 at Levels A, AA and AAA, ADA Title II and Title III, and Section 508, across web and mobile. Vervali holds ISO/IEC 17025:2017, CMMI Maturity Level 3, ISO 9001:2015 and ISO/IEC 27001, which govern how testing evidence is produced and handled. One structural advantage is worth stating plainly: Vervali runs a development practice alongside QA, so remediation guidance can be implemented as well as specified, and the build and the verification sit under one roof rather than across a vendor boundary.

TL;DR:

• "ADA compliant" is three questions: which law covers you, which WCAG version it names, and how much of it you meet today.

• Title II is WCAG 2.1 Level AA with deadlines now at April 26, 2027 and April 26, 2028 after the April 2026 extension. Title III has no DOJ-adopted standard. Section 508 is WCAG 2.0 Level A and AA.

• Run the nine-point self-check on six to eight representative pages before you buy anything.

• Automated tools catch 57% of issues by volume in Deque's study and between 13% and 40% of injected barriers in the UK government's, which is a floor rather than a verdict.

• An audit produces a per-criterion Accessibility Conformance Report. A scan produces a list. Procurement asks for the first one.

Ready to Find Out Where Your Site Actually Stands?

A two-hour self-check tells you whether you have a problem. A scoped audit tells you exactly which success criteria you fail, on which pages, with what severity, and produces the conformance record a buyer or a regulator will ask for. Vervali's accessibility testing experts audit web and mobile products against WCAG 2.1, ADA Title II and Title III, and Section 508, with remediation guidance written for the team that has to ship the fix.

Sources

Neutral authorities are linked directly. Vendor-published and practitioner sources are named and dated in full without a link.

1. U.S. Department of Justice (2026). "Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities," Interim Final Rule, Federal Register document 2026-07663, published April 20, 2026. federalregister.gov

2. ADA.gov (2026). "Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments." ada.gov

3. ADA.gov. "Guidance on Web Accessibility and the ADA." ada.gov

4. U.S. Access Board (2017). "Revised 508 Standards and 255 Guidelines," 36 CFR Part 1194, final rule January 18, 2017. access-board.gov

5. W3C Web Accessibility Initiative. "WCAG 2 AA Conformance." w3.org

6. W3C Web Accessibility Initiative. "Website Accessibility Conformance Evaluation Methodology (WCAG-EM)." w3.org

7. W3C (2023). "Web Content Accessibility Guidelines (WCAG) 2.2 is now a W3C Recommendation," 5 October 2023. w3.org

8. W3C (2018). "Web Content Accessibility Guidelines (WCAG) 2.1 is now a W3C Recommendation," 5 June 2018. w3.org

9. W3C Web Accessibility Initiative. WCAG 2.1 Understanding documents for SC 1.1.1, 1.2.2, 1.3.1, 1.4.3, 1.4.10, 2.1.1, 2.4.7, 3.3.2 and 4.1.2. w3.org

10. WebAIM (2026). "The WebAIM Million: The 2026 report on the accessibility of the top 1,000,000 home pages," data collected February 2026. webaim.org

11. UK Government Digital Service (2017). "What we found when we tested tools on 'the world's least accessible webpage'," 24 February 2017. accessibility.blog.gov.uk

12. UK Government Digital Service. "Accessibility tools audit results." alphagov.github.io

13. UK Department for Education. "False positives (and false assurance) in accessibility testing tools." accessibility.education.gov.uk

14. Federal Trade Commission (2025). "FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims that its AI Product Could Make Websites Compliant with Accessibility Guidelines," January 3, 2025. ftc.gov

15. Information Technology Industry Council. "Voluntary Product Accessibility Template (VPAT)." itic.org

16. Section508.gov, U.S. General Services Administration. "ACR/VPAT FAQ." section508.gov

17. Seyfarth Shaw LLP (2026). "Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025," ADA Title III blog, March 2026. adatitleiii.com

18. Bryan Cave Leighton Paisner (2019). "Supreme Court Denies Review in Website Accessibility Case Against Domino's Pizza," certiorari denied October 7, 2019. bclplaw.com

19. Deque Systems (2021). Dylan Barrell and Preety Kumar, "Automated Testing Identifies 57% of Digital Accessibility Issues," March 10, 2021.

20. UsableNet (2026). "Inside the 2026 Midyear Numbers: The ADA Continues to Be the Only True Enforcement Around," July 8, 2026.

21. Sheri Byrne-Haber (2023). "Why doing an instant ADA website compliance review is a terrible idea," August 17, 2023.