# ADA Website Rules and Your Business

> The 2024 ADA web rule covers state and local government, not private business. Here is what the DOJ requires of you, and the widget claim the FTC fined.

[Home](https://seoagencynaples.com/) / [Blog](https://seoagencynaples.com/blog/) / Technical SEO Site Protection
# The New ADA Website Rule Is Real, and It Is Probably Not About Your Business
A Naples business owner gets an email warning that a new federal rule makes their website illegal, with a deadline and a link to a widget that fixes it. The rule is real. Almost nothing else in the email is.

By [Jamie Kloncz](https://seoagencynaples.com/jamie-kloncz/), Founder and CEO, SEO Elite Agency ** 16 min read ** Published August 25, 2026

Three claims circulate about the ADA and small business websites, and two of them are wrong in opposite directions. The first is that a specific technical standard is now legally required of you. The second, usually a reaction to discovering the first is shaky, is that none of this reaches your website at all. Both are answered directly in Department of Justice guidance.
The Department states that it does not have a regulation setting out detailed standards, and that businesses can currently choose how they will ensure the goods and services they provide online are accessible [1](#ref-1). It also states that since 1996 it has consistently taken the position that the ADA applies to web content [1](#ref-1). Those two sentences are both true, and quoting either one alone produces a misleading article.
This guide separates what applies to a private business from the April 2024 rule that applies to state and local government, corrects a set of compliance dates that quietly moved in 2026, and covers the accessibility widget whose vendor paid the Federal Trade Commission a million dollars over its compliance claim. It is a description of published federal material, not legal advice about your situation.

## Two halves of the ADA, and which one you are in
Title II covers state and local government. Title III covers businesses open to the public, which the ADA also calls public accommodations. A Naples restaurant, clinic or contractor is Title III, and almost every article circulating about a new website rule is describing Title II.
The distinction does all the work here, and it is the one thing consistently dropped from coverage. The Department of Justice sets it out simply: the ADA applies to state and local governments under Title II, and to businesses that are open to the public under Title III [1](#ref-1). Title III language calls those businesses public accommodations, and the examples are ordinary ones: restaurants, retailers, medical offices, hotels.
What Title III requires is stated in terms of outcomes rather than specifications. The Department describes it as requiring that businesses open to the public provide full and equal enjoyment of their goods, services, facilities, privileges, advantages or accommodations to people with disabilities, and take steps to provide appropriate communication aids and services where necessary to communicate effectively.
Read that against how a website actually fails somebody. The Department draws the comparison itself, noting that the way a website is designed can create unnecessary barriers making it difficult or impossible for people with disabilities to use it, just as physical barriers like steps can prevent some people from entering a building [1](#ref-1). A quote form nobody can complete with a keyboard is a step at the door.
One practical note before going further. This post describes what two federal agencies have published about their own rules and their own enforcement. It is not legal advice, it takes no position on any particular business situation, and if you have received a demand letter the correct next call is to a lawyer rather than to a web agency.
Title II Title III
Who it covers State and local government Businesses open to the public
Examples Courts, police, elections, benefits offices Restaurants, clinics, retailers, contractors
Technical standard WCAG 2.1 Level AA, adopted April 2024 None adopted
Compliance deadline 26 April 2027 or 26 April 2028 by population No rule-based deadline
Does the ADA still apply? Yes Yes

## There is no standard for you, and that is not the good news it sounds like
The Department of Justice says it has no regulation setting detailed standards for private businesses, and that businesses can currently choose how they comply. The same guidance says they must still comply. Flexibility in method is not an exemption from the obligation.
Here is the sentence that settles the first claim. The Department of Justice does not have a regulation setting out detailed standards, but its longstanding interpretation of the general nondiscrimination and effective communication provisions applies to web accessibility [1](#ref-1). There is no adopted technical standard for a private business, so nobody can accurately tell you that a particular WCAG version is your legal requirement.
The Department goes further and says businesses can currently choose how they will ensure that the programs, services and goods they provide online are accessible to people with disabilities [1](#ref-1). It points to WCAG and the Section 508 standards as existing technical standards that provide helpful guidance, which is a meaningfully different status from a rule you are bound by.
Now the half that makes the first half safe to publish. The same guidance says businesses have flexibility in how they comply with the general requirements of nondiscrimination and effective communication, but that they must comply with the ADA requirements [1](#ref-1). Flexibility describes the method, not the obligation, and an article that quotes only the flexibility is as misleading as one that invents a deadline.
The practical position this leaves a small business in is genuinely awkward, and pretending otherwise helps nobody. There is an obligation with no specification attached, which means the question is not whether you passed an audit but whether somebody can actually use your site to do business with you. WCAG is the most widely used way of answering that question, and using it as a working guide is sensible precisely because it is not the law.

Source: Department of Justice web guidance, the DOJ fact sheet on the 2024 Title II rule, and an FTC enforcement action Download SVG

## The 2024 rule is real, it is about governments, and its dates moved
The final rule published on 24 April 2024 updates Title II and sets WCAG 2.1 Level AA for state and local government web content. An Interim Final Rule in April 2026 pushed the deadlines to April 2027 and April 2028, which most articles still have wrong.
This is the rule behind the emails. On 24 April 2024 the Federal Register published the Department of Justice final rule updating its regulations for Title II of the ADA, with specific requirements about how to ensure web content and mobile apps are accessible [2](#ref-2). The technical standard it sets is the Web Content Accessibility Guidelines Version 2.1, Level AA [2](#ref-2).
It applies to state and local governments, which the fact sheet illustrates with offices providing benefits and social services, police departments, courts and elections offices. If your business is a med spa in Naples or a roofing contractor in Bonita Springs, this rule is not addressed to you. That does not make the marketing email a lie exactly. It makes it a real rule pointed at the wrong reader.
The deadlines have also changed, and this is where even careful articles are now out of date. An Interim Final Rule published in the Federal Register on 20 April 2026 extended the compliance date for state and local government entities with a total population of 50,000 or more to 26 April 2027, and for entities under 50,000 or any special district government to 26 April 2028 [2](#ref-2).
Two things follow from that for a business owner. If somebody is quoting you an April 2026 deadline, their material predates the extension and is worth discounting generally. And if you do work with a city, county or school district as a client or vendor, those dates are the ones that matter to them, which makes accessibility a commercial question for you even though the rule does not bind your own site.

## The widget that promised compliance, and the million dollar order
The FTC required accessiBe to pay one million dollars over claims that its automated tool could make any website WCAG compliant, stating the product did not do so and the claims were false, misleading or unsubstantiated. The order bars repeating the claim without evidence.
A specific product category deserves naming here, because the sales pitch is aimed precisely at owners who have just been frightened by one of those emails. The Federal Trade Commission required software provider accessiBe to pay one million dollars to settle allegations that it misrepresented the ability of its AI-powered web accessibility tool to make any website compliant with WCAG [3](#ref-3).
The complaint is quite specific about the mechanism of the problem. Despite the company claims, the FTC stated, accessWidget did not make all user websites WCAG-compliant, and these claims were therefore false, misleading, or unsubstantiated, in violation of the FTC Act [3](#ref-3). The order bars the company from representing that its automated products can make any website WCAG-compliant, or ensure continued compliance over time, unless it has evidence to support the claim [3](#ref-3).
There is a second allegation worth knowing about, because it explains why the product looked so well reviewed. The FTC alleged that the company deceptively formatted articles on third-party websites to appear as if they were independent opinions by impartial authors, and failed to disclose its material connections to the supposedly objective reviewers. The favorable coverage a worried owner would find was, in part, the vendor.
None of this makes every overlay product worthless, and the honest framing is narrower than the internet reaction to this case. What it establishes is that a single script promising to make your site compliant is a claim a federal agency has already treated as unsupported. Treat that promise the same way you would treat any vendor claiming a guarantee, which is to ask what specifically it does and what evidence exists that it does it.

- No script makes a website compliant on its own.
- The FTC order targets the compliance claim, not accessibility tooling in general.
- Some of the positive coverage of that product was placed by the vendor.
- Ask any vendor what their product does, not what it promises.
- We are not going to claim we make a site compliant either.

## What actually helps, given there is nothing to pass
Use WCAG as a working guide rather than a legal test, fix the things that block a transaction first, and treat accessibility as part of how the site is built rather than a layer added afterwards. Most of what matters is unglamorous and permanent.
Start where a failure actually costs somebody something. The Department names captions on video as an example, noting that people with hearing disabilities may not be able to understand information in a video without them [1](#ref-1), and describes barriers that make a site difficult or impossible to use. In practice the highest-value fixes are the ones standing between a person and a transaction: the contact form, the booking flow, the phone number, the menu.
Use WCAG deliberately and describe it accurately. It is, in the Department own framing, an existing technical standard that provides helpful guidance [1](#ref-1), and it is the standard the government adopted for itself under Title II. Working to WCAG 2.1 Level AA is a defensible, well-documented way to answer the question of whether your site is usable. Just do not let anybody tell you, or let yourself tell a customer, that it is the law for a private business.
The structural point is that accessibility survives better when it is part of how a site is built than when it is added as a layer. Keyboard navigation, real text rather than text baked into images, sensible heading order, labeled form fields and adequate color contrast are all decisions made during the build. They also overlap heavily with the things that make a site legible to a machine, which we cover in [how site quality relates to rankings](https://seoagencynaples.com/blog/core-web-vitals-speed-rankings/).
And the boundary on what we will claim. We build and maintain sites with these things in mind, and that is a different sentence from saying we make a site compliant. Nobody should offer you that, for the reason the FTC just spent a million dollars establishing [3](#ref-3). If you want to know how your current site behaves, our [free SEO audit](https://seoagencynaples.com/free-seo-audit/) covers the machine-readability side, and a genuine accessibility review is a separate and more manual piece of work.

- **Work out which title applies to you.** A business open to the public is Title III. The 2024 rule is Title II and is not addressed to you.
- **Ignore any April 2026 deadline you are quoted.** The dates moved to April 2027 and April 2028, and only for governments.
- **Fix what blocks a transaction first.** Contact form, booking, phone number, menu. Start where a failure costs somebody something.
- **Use WCAG 2.1 AA as a working guide.** Helpful guidance and a documented target, not a legal test for a private business.
- **Be skeptical of one-script fixes.** The compliance claim attached to that category has already drawn a federal enforcement action.
- **Call a lawyer, not an agency, about a demand letter.** Nothing in this article is legal advice and no web vendor should be your first call.

Test yourself
## Which ADA claims survive checking?
Five questions from Department of Justice guidance and an FTC enforcement action, all linked in this guide.

- 1 Is a private business legally required to meet WCAG 2.1 Level AA? Yes, since April 2024 No, the DOJ has no regulation setting detailed standards Yes, since 1996 Only in Florida **Answer:** No, the DOJ has no regulation setting detailed standards The Department of Justice states plainly that it does not have a regulation setting out detailed standards, and that businesses can currently choose how they ensure what they provide online is accessible. WCAG is described as helpful guidance rather than a binding technical standard for private businesses. Anyone telling a Naples business that a specific WCAG version is the legal requirement is describing a rule that has not been adopted for them.
- 2 So does the ADA reach your website at all? No, only physical premises Yes, the DOJ has taken that position since 1996 Only for businesses over fifty staff Only if you sell online **Answer:** Yes, the DOJ has taken that position since 1996 This is the half that people who read the first answer tend to miss. The Department states that since 1996 it has consistently taken the position that the ADA applies to web content, and that while businesses have flexibility in how they comply, they must still comply with the ADA requirements. Flexibility in how is not permission to do nothing, and the two facts are only honest together.
- 3 Who does the April 2024 ADA web rule actually bind? All businesses State and local governments Federal agencies Healthcare providers **Answer:** State and local governments The final rule published in the Federal Register on 24 April 2024 updates the regulations for Title II of the ADA, which covers state and local governments. It sets WCAG 2.1 Level AA as the technical standard for their web content and mobile apps. It is a real rule with real deadlines, and it is the one being cited in marketing emails sent to private businesses that it does not cover.
- 4 When must covered governments comply with that rule? April 2026 and April 2027 April 2027 and April 2028 Immediately No date has been set **Answer:** April 2027 and April 2028 The dates moved and most published articles have not caught up. An Interim Final Rule published in the Federal Register on 20 April 2026 extended the compliance date to 26 April 2027 for entities with a total population of 50,000 or more, and to 26 April 2028 for entities under 50,000 and for any special district government. If you read the older dates somewhere, that article predates the extension.
- 5 What happened to the vendor selling an accessibility widget as a compliance fix? Nothing The FTC required it to pay $1 million It was certified by the DOJ It won a court case **Answer:** The FTC required it to pay $1 million The Federal Trade Commission required accessiBe to pay one million dollars to settle allegations that it misrepresented the ability of its tool to make any website WCAG compliant. The complaint stated the product did not make all user websites compliant and that the claims were false, misleading or unsubstantiated. The order bars the company from repeating the claim without evidence to support it.
Honest self-check. There is no sign-up, and nothing is stored.

Questions answered
## Straight answers to the common questions
The questions readers ask about this topic, answered directly. **No forms, no sales pitch.**

JAMIE KLONCZ · SEO AGENCY NAPLES ************** ONLINE
Pick a question on the left, or search above. You will get the direct answer, the way an answer engine would give it.

← PREV NEXT → [FREE AUDIT →](https://seoagencynaples.com/free-seo-audit/)

- **Is my business website legally required to meet WCAG 2.1 Level AA?** Not as a rule-based requirement, if you are a private business. The Department of Justice states that it does not have a regulation setting out detailed standards, and that businesses can currently choose how they will ensure the goods and services they provide online are accessible to people with disabilities. WCAG is described as an existing technical standard that provides helpful guidance rather than an adopted requirement for Title III businesses. That is a genuine difference and it is worth knowing, but it is not the same as being off the hook, because the Department also says the ADA applies to web content and that businesses must comply with its requirements.
- **Does the ADA apply to websites at all?** Yes, according to the agency that enforces it. The Department of Justice states that since 1996 it has consistently taken the position that the ADA applies to web content, and its guidance describes how businesses open to the public should make their websites accessible. What is absent is a detailed technical specification for private businesses, not the underlying obligation. The Department frames it as flexibility in how you comply with the general requirements of nondiscrimination and effective communication, while still having to comply. Anybody quoting the absence of a standard as proof the ADA does not reach websites has read half the page.
- **What is the April 2024 ADA website rule I keep getting emails about?** It is a real final rule, published in the Federal Register on 24 April 2024, updating the Department of Justice regulations for Title II of the ADA. Title II covers state and local governments, so the rule binds courts, police departments, elections offices, benefits agencies and similar public entities. It sets WCAG 2.1 Level AA as the technical standard for their web content and mobile apps. If you run a private business, that rule is not addressed to you. This is the single most common confusion in the marketing sent to small businesses on this subject, and the rule being real is what makes the pitch persuasive.
- **When is the compliance deadline for that rule?** The dates were extended in 2026 and a great many published articles still carry the old ones. An Interim Final Rule published in the Federal Register on 20 April 2026 extended the compliance date to 26 April 2027 for state and local government entities with a total population of 50,000 or more, and to 26 April 2028 for public entities with a total population under 50,000 or any special district government. If an article or a sales email quotes you an April 2026 deadline, it predates that extension, which is a reasonable signal about how current the rest of its information is.
- **Do accessibility overlay widgets make a site compliant?** A federal agency has already addressed that specific claim. The Federal Trade Commission required accessiBe to pay one million dollars to settle allegations that it misrepresented the ability of its AI-powered tool to make any website WCAG compliant, stating that the product did not make all user websites compliant and that the claims were false, misleading or unsubstantiated. The resulting order bars the company from claiming its automated products can make any website compliant, or maintain compliance over time, without evidence to support it. The FTC also alleged the company placed third-party articles formatted to look like independent reviews.
- **Where should a small business actually start?** With the paths that stand between a person and doing business with you, rather than with a compliance score. If somebody using a keyboard or a screen reader cannot complete your contact form, book an appointment, find your phone number or read your menu, those are the failures that cost both of you something today. The Department of Justice gives examples in the same spirit, such as video without captions leaving people with hearing disabilities unable to understand the content. Working to WCAG 2.1 Level AA is a sensible documented target. Building accessibility into the site is more durable than adding a layer afterwards.
- **I received a demand letter about my website. What should I do?** Speak to a lawyer, and treat that as the first call rather than a later one. Nothing in this article is legal advice, it takes no position on any particular situation, and a web agency is not the right party to assess a legal claim against you. What an agency can usefully do is work alongside your lawyer on the technical remediation once you understand what is being asserted. Be particularly wary at this moment of anybody selling a fast fix, because the urgency created by a demand letter is exactly the condition the compliance-guarantee pitch is designed for.

## References

- U.S. Department of Justice. Guidance on Web Accessibility and the ADA. accessed 25 August 2026. [https://www.ada.gov/resources/web-guidance/](https://www.ada.gov/resources/web-guidance/)
- U.S. Department of Justice. Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments. accessed 25 August 2026. [https://www.ada.gov/resources/2024-03-08-web-rule/](https://www.ada.gov/resources/2024-03-08-web-rule/)
- Federal Trade Commission. FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims that its AI Product Could Make Websites Compliant with Accessibility Guidelines. January 2025. [https://www.ftc.gov/news-events/news/press-releases/2025/01/ftc-order-requires-online-marketer-pay-1-million-deceptive-claims-its-ai-product-could-make-websites](https://www.ftc.gov/news-events/news/press-releases/2025/01/ftc-order-requires-online-marketer-pay-1-million-deceptive-claims-its-ai-product-could-make-websites)

Written by
## [Jamie Kloncz](https://seoagencynaples.com/jamie-kloncz/)
Founder and CEO, SEO Elite Agency
Jamie Kloncz is the founder and CEO of SEO Elite Agency, the firm behind SEO Agency Naples. An engineer who scaled his own plumbing business to 3 million dollars in revenue and led growth for over 200 teams, he built this agency on one principle: every SEO action must connect directly to revenue, not vanity metrics.
[More about Jamie →](https://seoagencynaples.com/jamie-kloncz/)

Free · No pressure
## See where your business actually stands
Start with a free audit of your rankings, Google Business Profile, technical health, and AI-search visibility, with a prioritized plan and an honest quote for your situation.
[Get your free audit](https://seoagencynaples.com/free-seo-audit/)

Keep reading
## Related guides
[Technical SEO Why Your Quotes Land in Spam When You Only Send Forty Emails a Day Read guide →](https://seoagencynaples.com/blog/business-email-going-to-spam-spf-dkim/)[Technical SEO Who Actually Controls Your Domain Name, and the 60-Day Trap Most Owners Find Too Late Read guide →](https://seoagencynaples.com/blog/who-owns-your-domain-name/)[Technical SEO Website Speed and Core Web Vitals: Why They Decide Rankings Read guide →](https://seoagencynaples.com/blog/core-web-vitals-speed-rankings/)