If you read that the federal website accessibility deadline was pushed back, it is easy to conclude that you have more time. For a private business, that reading does not hold. The rule that moved covers state and local governments under title II of the ADA, and the DOJ says its title III regulations, the part that covers businesses open to the public, were not addressed. This post covers what the DOJ said, what the lawsuit data shows, and what a widget can and cannot do. If you want the fix rather than the background, our website accessibility and ADA compliance work starts with an audit that tests your pages by hand as well as with automated tools. This is general information, not legal advice. Talk to an attorney about your own situation.
What did the DOJ change, and who does it cover?
The DOJ moved the compliance dates of its web accessibility rule for state and local governments, and nobody else. Its own ADA.gov guidance says: "In April 2026, the Department published an Interim Final Rule (IFR) extending the compliance date for State and local government entities with a total population of 50,000 or more to April 26, 2027." The same page lists April 26, 2028 for entities with smaller populations and for special districts.
The standard those governments must meet is WCAG 2.1 Level AA, the same technical guideline GrossiWeb's audits test against. The rule text is just as clear about its reach: "This IFR only pertains to the Department's regulations implementing title II; the Department's regulations implementing title III, found at 28 CFR part 36, are not addressed in this rulemaking." The interim final rule, AG Order No. 6742-2026, was published in the Federal Register on April 20, 2026 (91 FR 20902) and took effect that day. It moved the dates from April 24, 2026 and April 26, 2027 to April 26, 2027 and April 26, 2028.
Does the delay mean a private business is off the hook?
No. The rule that moved was written for state and local governments under title II, and as quoted above, the DOJ says its title III regulations were not addressed. Title III is the part that reaches businesses: the DOJ's 2022 guidance on web accessibility, which ADA.gov still publishes, says "Title III prohibits discrimination against people with disabilities by businesses open to the public."
The same guidance says the DOJ "does not have a regulation setting out detailed standards" for web accessibility, and that businesses "have flexibility in how they comply with the ADA's general requirements of nondiscrimination and effective communication. But they must comply with the ADA's requirements." So there was never a federal website date for a private business to wait for. What that means for your own site is a question for your attorney, not for a government calendar.
What does the lawsuit data say?
Website accessibility lawsuits are rising, according to UsableNet, which tracks the filings every month. UsableNet reported on July 8, 2026 that, based on filings through June 14, lawsuits were on track to surpass 6,000 in 2026, "a historic high and a nearly 20% increase over 2025." UsableNet sells accessibility testing software and a managed accessibility service, so treat its numbers as coming from an interested party, and note that 6,000 is a projection, not a final count.
The same publisher's January 2026 analysis reported more than 5,000 digital accessibility lawsuits by the end of 2025 and found that 64 percent of the companies sued made less than $25 million a year, the figures our accessibility page already cites. The July report added that 79 percent of the 2026 filings it tracked through mid-June were against ecommerce businesses. If you run an online store, start with our ecommerce industry page.
Do accessibility widgets protect you from a lawsuit?
UsableNet's monthly tracker shows that a widget did not keep 134 businesses out of court in a single month. It reports that in August 2026 plaintiffs filed 432 new ADA web accessibility lawsuits, and 134 defendants "were sued despite using a third-party accessibility widget on their sites at the time," about three in ten by our own division.
Read that number carefully. It counts defendants. It does not say how often sites with a widget are sued compared with sites without one, so it cannot prove a widget makes things worse. UsableNet's July report says the same in plain words: "the presence of a widget has not proven to be a meaningful deterrent, legally or practically."
The Federal Trade Commission has also acted against one widget maker's compliance claims. On April 22, 2025 it approved a final consent order against accessiBe, after a complaint that alleged its accessWidget plug-in "did not make all user websites WCAG-compliant" and that the company's claims were "false, misleading, or unsubstantiated." The order requires accessiBe to pay $1 million and bars it from representing that its automated products can make any website WCAG-compliant "unless it has the evidence to support such claims." That is one settlement with one company, not a ruling on every widget, but it is a good reason to ask any vendor for evidence before you believe a compliance promise.
What did Missouri change?
Missouri's Act Against Abusive Website or Web Content Access Litigation took effect on August 28, 2026. In its own words: "A defendant who receives written notice of an alleged website or web content access violation and in good faith initiates substantial steps to correct it within ninety days shall have a rebuttable presumption that any subsequent claim for a website or web content access violation is abusive." The presumption does not apply if the violation "is not corrected, as determined by the court, within ninety days after being provided written notice or being served a petition or complaint with sufficient detail to identify and correct the alleged access violation." This is one state's law, and whether it or anything like it covers your business is a question for an attorney licensed where you operate.
What can you do this week?
You can learn where you stand in a few days without spending anything, and you can decide who fixes what. None of the steps below is legal advice, and none of them guarantees you will never receive a demand letter.
- Find out whether your site runs a widget or overlay. Ask whoever built or maintains it, and write down the product name.
- Run a free automated scan on your home page, contact page, top service or product page and checkout. Treat the result as a starting point, not a verdict.
- Put your mouse away and tab through those pages. Can you open the menu, fill in and submit a form, and finish checkout? Can you always see where the keyboard focus is?
- Check the basics by eye: images that carry meaning have alt text, every form field has a label, and text has enough color contrast against its background.
- Keep a dated record of what you find and what you fix. If a letter ever arrives, that record is the first thing to hand your attorney.
- If a demand letter or complaint arrives, do not ignore it. Contact an attorney first, then bring in the person who will fix the code.
Accessibility drifts as you add pages, plugins and content, which is one more reason a site is a business system you maintain, not a project you finish. If you are planning a new site, build it in from the start with web design that checks against WCAG 2.1 AA. For an existing site, put recurring checks into your maintenance and support routine so new problems are caught when they appear, not when a letter arrives.