Bench note
ADA Website Requirements in 2026: What Applies to a Small Business Site
One ADA regime has a technical standard and dated deadlines; the other has neither. Which one your site sits under.
Published 26 October 2026
Jump to a section8 sections
The ADA's website requirements depend on who runs the site. If you are a state or local government, a Department of Justice rule names a technical standard, WCAG 2.1 Level AA, and gives you a compliance date of 26 April 2027 or 26 April 2028 depending on population. If you are a private business open to the public, the ADA still applies to what you offer online, but the Department has published no regulation that fixes a technical web standard for you, and no deadline exists because no rule exists.
That split is the whole answer, and most of the confusion about "the April 2026 deadline" comes from mixing the two. Everything below was read on ada.gov, the Federal Register and the W3C's own pages as of 18 Oct 2026.
Nothing on this page is legal advice. Whether a particular site meets a particular legal obligation is a question for a lawyer who has looked at that site. What follows is what the government has published, and what you can check yourself.
Short answer, by who you are
| Question | Title II | Title III |
|---|---|---|
| Who it covers | State and local governments, including agencies, special districts, public schools and their contractors' work for them | Businesses open to the public, such as shops, banks, hotels, restaurants and medical offices |
| Technical standard in a rule | WCAG 2.1 Level AA | None set by regulation |
| Compliance date | 26 April 2027 (population 50,000 or more); 26 April 2028 (under 50,000, and special districts) | No date |
| Where the obligation comes from | The 2024 final rule, amended by the 2026 interim final rule | The ADA's general nondiscrimination and effective-communication duties |
The two ADA regimes for websites, as stated on ada.gov on 18 Oct 2026
Who it covers
- Title II
- State and local governments, including agencies, special districts, public schools and their contractors' work for them
- Title III
- Businesses open to the public, such as shops, banks, hotels, restaurants and medical offices
Technical standard in a rule
- Title II
- WCAG 2.1 Level AA
- Title III
- None set by regulation
Compliance date
- Title II
- 26 April 2027 (population 50,000 or more); 26 April 2028 (under 50,000, and special districts)
- Title III
- No date
Where the obligation comes from
- Title II
- The 2024 final rule, amended by the 2026 interim final rule
- Title III
- The ADA's general nondiscrimination and effective-communication duties
If you run a small business site on a website builder, you are almost certainly in the right-hand column. If you build sites for a town, a school district or a public library, you are in the left-hand one, and the dates matter.
Title II: the government rule and its extended dates
On 24 April 2024 the Federal Register published the Department of Justice's final rule on the accessibility of web content and mobile apps provided by state and local governments. ada.gov's fact sheet states the requirement plainly: WCAG 2.1 Level AA "is the technical standard for state and local governments' web content and mobile apps."
The original deadlines were never reached. On 20 April 2026 the Department published an interim final rule, effective the same day, extending them. The first compliance date had been 24 April 2026, which is where the "April 2026" in so many search results comes from. As of 18 Oct 2026, ada.gov gives these dates:
- 26 April 2027 where the public entity's total population is at least 50,000;
- 26 April 2028 for public entities with a population under 50,000, and for any special district government.
The Federal Register notice explains the reason in the Department's own words: it "overestimated the capabilities (whether staffing or technology) of covered entities to comply with the rule in the time frames provided." Written comments on the interim rule closed on 22 June 2026. If the Department changes the dates again, ada.gov's fact sheet is where it will show first.
The rule reaches further than a government's own staff. ada.gov's example is a county parks page built and updated by a private web design company: that page must meet WCAG 2.1 Level AA all the same. If you are a designer working for a public body, the standard applies to your work for them.
Title III: private businesses and the absence of a technical standard
Title III covers businesses open to the public. The Department's 2022 guidance on web accessibility, still published on ada.gov with a note that it does not reflect the later Title II rule, sets out its position. It says the Department "has consistently taken the position that the ADA's requirements apply to all the goods, services, privileges, or activities offered by public accommodations, including those offered on the web."
The same page is equally plain about what does not exist: "The Department of Justice does not have a regulation setting out detailed standards." Businesses, it says, "can currently choose how they will ensure" their online offerings are accessible, and it points to WCAG and the federal Section 508 standards as helpful guidance.
Read the two statements together. The obligation is real; the yardstick is not fixed in regulation. That is why anyone selling a product that makes a business site "ADA compliant" is claiming more than the regulatory record supports. There is no published test for the product to pass.
What the Department's guidance does list is a set of practices it expects: sufficient colour contrast, text cues alongside colour, alt text on images, captions on video, labelled forms with clear instructions and error alerts, and navigation that works by keyboard. Those map directly onto checks you can run.
What "ADA compliant" can and cannot mean for a builder site
A website builder gives you an editor, themes and hosting. Your pages, images, forms and embeds supply the rest. No platform can certify the combination, and the platforms say so. Squarespace's own accessibility guide, for example, describes itself as "a resource, but it's not legal advice."
So "ADA compliant website builder" can only sensibly mean a platform that gives you room to build an accessible site without fighting it: themes with visible focus and adequate contrast, an alt text field on every image, form fields with real labels, and nothing that breaks keyboard use. How much room each major builder gives you is what we measure on ADA compliant website builders. It cannot mean the platform has made your site compliant on your behalf.
A practical baseline: WCAG checks you can run
WCAG 2.2 is the current W3C Recommendation, published on 5 October 2023 and updated on 12 December 2024. The W3C says its success criteria are the same as in WCAG 2.1, with nine additions and one earlier criterion now marked obsolete. Working to WCAG 2.2 Level AA therefore covers the 2.1 criteria that the Title II rule names.
You do not need a specialist to find the most common failures. Five checks, each tied to a named criterion:
- Keyboard (2.1.1, Level A). Put the mouse away and press Tab through every page. Every link, button, menu and form field should be reachable and usable. Our keyboard test sets out the full walk.
- Visible focus (2.4.7, Level AA). As you tab, you should always be able to see where you are.
- Contrast (1.4.3, Level AA). Body text needs at least 4.5:1 against its background; large text at least 3:1. Contrast in builder themes covers where themes go wrong.
- Alt text (1.1.1, Level A). Every informative image needs a text alternative; decorative ones should be marked as such. Where builders hide alt text shows where the field lives on each platform.
- Form labels (3.3.2, Level A). Every field needs a label a screen reader can announce, not just placeholder text. The common failures are in forms that fail screen readers.
Automated scanners help with contrast and missing alt attributes. They cannot tell you whether alt text is meaningful or whether the tab order makes sense. That part is a person's job.
Overlays won't settle it
Accessibility overlays are scripts that add a toolbar or widget to your site and are often sold as a route to compliance. The record on them is public. In January 2025 the Federal Trade Commission announced an order requiring accessiBe to pay $1 million over claims that its AI product could make websites compliant with accessibility guidelines. The full account, including what disabled users have said about these products, is on our accessibility overlays page.
An overlay does not change the underlying markup of your pages in a way you control, and no regulator has said that installing one meets an ADA obligation.
Edge cases worth knowing
You build websites for a public body. Content a government publishes through a contractor still counts as the government's content. ada.gov's own example is a county parks page made and updated by a private design company. Your client's compliance date is your deadline for that work.
You run a programme on a government's behalf. ada.gov says state and local governments that contract with others to provide public services must make sure those contractors follow Title II. A nonprofit running a service for a state agency is the example it gives.
A public school district. It is not treated as a special district, so it does not automatically get the later date. ada.gov says it takes its date from a population figure: its city's or county's, or for an independent district, a Census Bureau estimate.
Mobile apps. The Title II rule covers a government's mobile apps as well as its websites, to the same WCAG 2.1 Level AA standard. ada.gov's example is a city parking app that a private company operates.
Customers in the European Union. The ADA is not the only law. EU countries have enforced the European Accessibility Act through their own legislation since 28 June 2025, and it reaches e-commerce services offered to consumers there. It has its own scope and its own exemption for the smallest service businesses.
When to talk to a lawyer
Talk to a lawyer, not a vendor, if any of these apply:
- you are a public entity, or build for one, and need to know which compliance date and exceptions apply to you;
- you have received a demand letter or complaint about your site;
- you sell to customers in the EU as well, where a separate law applies;
- you are being asked to sign a contract that promises compliance.
For everything else, the practical route is the baseline above, a published accessibility statement with a working contact route, and fixing what people tell you about.
Questions from the bench
What are the ADA website requirements?
Was the ADA website compliance deadline extended?
Does the ADA apply to small business websites?
Is there an ADA compliance checker?
Which WCAG version should a small business follow?
Where this is filed
Every note here sits underneath one assessment: ADA-compliant website builders, which is where the platforms are read side by side. Nothing on this site is legal advice, and no builder on that page is sold as a route to compliance.
The recheck notice
When a platform quietly changes what it gives you
Builders move accessibility features without a changelog: a theme restyles its focus ring, a wizard learns a check, a field migrates to another panel. The recheck list is meant to carry one short note whenever a page here has to be corrected. It is not switched on yet, so this form keeps nothing — until it is, the corrected page itself is the record.