Website Accessibility for Small Business: What 2026 Changed
The DOJ pushed its web accessibility deadlines back a year in April 2026, but lawsuits against private businesses hit a record. What that means for a small business site.
Two things happened this year that look like they contradict each other. In April the Justice Department pushed its web accessibility deadlines back by a full year. Over roughly the same stretch, website accessibility lawsuits against private businesses climbed to a record.
Most of the coverage led with the extension. For a small business owner that is the less useful of the two facts, because the extended deadline was never yours to begin with. Here is what actually changed, which rule applies to you, and what to do about it in an afternoon instead of a quarter.
What the April extension changed
On April 20, 2026 the Justice Department published an interim final rule extending the compliance dates for the Title II web accessibility rule it adopted in 2024. Entities with a total population of 50,000 or more moved from April 24, 2026 to April 26, 2027. Smaller entities and special district governments moved from April 26, 2027 to April 26, 2028.
What did not change is the destination. WCAG 2.1 Level AA is still the technical standard, and the scope of covered content is the same, as the DOJ fact sheet on the web rule sets out. The extension bought time, not a different requirement.
What also did not change is who the rule covers. Title II is state and local government: cities, counties, school districts, public colleges, libraries, transit agencies. If you are a private business, this rule was never about you. That is why leading with the extension was misleading for most readers.
The rule that is actually yours
Private businesses open to the public fall under Title III, which works differently in a way that trips almost everyone up.
There is no compliance date, because there is no regulation with a date in it. DOJ's own guidance on web accessibility states plainly that the Department "does not have a regulation setting out detailed standards" and that businesses have flexibility in how they comply with the ADA's general requirements.
Then it finishes the sentence. Businesses still must ensure that the programs, services, and goods they provide to the public, including those provided online, are accessible to people with disabilities.
Flexibility about how. Nothing at all about whether. The absence of a deadline is not the absence of an obligation, and in practice the gap left by regulators has been filled by plaintiffs.
The number that functions as your deadline
The law firm Seyfarth Shaw tracks these filings from federal court records. Its count found 3,117 federal website accessibility lawsuits in 2025, up from 2,452 in 2024. That is a 27 percent increase, and those cases made up 36 percent of all federal ADA Title III filings, compared with 28 percent the year before.
Be precise about what that number is and is not. It counts federal filings only, so it undercounts: state court cases and pre-suit demand letters never show up in it. It is also concentrated in a few states and among a small number of plaintiffs' firms. It is not evidence that a random plumber in Sandy is about to be served.
What it is evidence of is a working business model, and business models expand into new territory when the old territory saturates. The demand letter is the product here, not the trial. Most of these matters resolve long before a courtroom, which is exactly why the volume can grow the way it has.
What this means in Utah specifically
Two groups of Utah businesses should pay closer attention than average.
The first is anyone who sells to a public entity. The Title II obligation does not stay with the city or the school district. It flows down the contract to whoever builds and maintains the thing. Along the Wasatch Front, the larger cities and the populous counties land in the 2027 group. Most of Utah's smaller towns, and the state's long list of special districts, land in the 2028 group. Either way, the shop delivering the website inherits WCAG 2.1 AA as a deliverable, and that shop is usually small. If you want that work, being able to speak to conformance is now part of qualifying for it.
The second is any business whose customers arrive from search and then leave without calling. Accessibility failures and conversion failures are very often the same failure wearing a different label. A form that cannot be completed with a keyboard is not only legal exposure. It is a lead you already paid to acquire and then dropped on the floor. That overlap is why I file this under websites rather than under legal, and why the same fixes show up in the landing page quality discussion in our post on Google Ads vs SEO.
Where small business sites actually fail
In my experience rebuilding small business sites, the failures cluster in four places, and the missing alt attribute everyone worries about is rarely the worst one.
Contrast on secondary text. The muted gray that design tools hand you by default, something in the neighborhood of #9ca3af, measures roughly 2.5 to 1 against white. WCAG success criterion 1.4.3 asks for 4.5 to 1 on normal text and 3 to 1 on large text. So the headline passes and the caption under every photo, the form placeholder, and the fine print all fail. Run your own body text through any contrast checker and you will usually find this within a minute.
Forms built on placeholders. Placeholder text used as the label instead of a real label. The moment someone types, the only description of the field disappears. Assistive technology has nothing useful to announce, and the validation error points at a field the user can no longer identify.
Focus that was removed because it looked untidy. Someone turns off the focus outline in CSS during design polish. Now a person navigating by keyboard has no idea where they are on the page. This one is free to test: unplug the mouse, load your homepage, and press Tab from the top. If you lose track of your position, so does every keyboard user.
Interactive things that are not really interactive elements. The hamburger menu built as a div with a click handler. The button that is a styled span. It looks and behaves correctly with a mouse and it is close to invisible to a screen reader. This is the most common structural problem I find on otherwise attractive small business sites.
An audit you can run this afternoon
None of the following requires a specialist or a budget. Work in this order.
- Unplug the mouse and press Tab through your homepage and your contact page. Note every place you cannot see where you are or cannot reach something.
- Complete your own contact form using only the keyboard, including the submit. This is where most sites break.
- Run your body text and your muted text through a contrast checker against their real backgrounds. Fix anything under 4.5 to 1.
- Check that every form field has a visible label that stays visible after typing.
- Turn images off in your browser and read the page. What is missing tells you which alt text actually carries meaning.
- Build to WCAG 2.2 Level AA rather than 2.1 where you can. It is the current W3C recommendation and it is backward compatible with the 2.1 AA that Title II names.
Anything left after those six steps is worth paying someone for. Most of what those six steps surface, you or your developer can fix in a day.
Frequently asked questions
Does the ADA apply to my site if I have no physical location? Courts have split on this and I am not a lawyer, so treat that honestly rather than as a settled answer. What is not in dispute is that DOJ's published position covers services provided online by businesses open to the public, and that plaintiffs file regardless of how the question is resolved in your circuit. Deciding your risk on a circuit split is a worse plan than fixing the four failures above.
Is WCAG 2.1 or 2.2 the right target? Title II names 2.1 Level AA specifically. WCAG 2.2 is the current W3C recommendation and adds criteria on top of 2.1 rather than replacing them, so a site built to 2.2 AA also satisfies a 2.1 AA requirement. If you are starting now, start at 2.2.
My site is on a hosted platform. Does that cover me? No. The platform gives you accessible building blocks at best. Almost every failure listed above comes from theme choices, content, and custom sections, not from the platform core. The obligation follows the published page, not the tool that produced it.
When is the cheapest time to fix this? During a rebuild, by a wide margin. Retrofitting contrast, focus states, semantics, and form structure into a finished site means touching nearly every template. Deciding those things once in a design system costs close to nothing extra. If a redesign is already on your list this year, fold it in rather than scheduling it separately.
The deadline that moved was never the one aimed at private businesses. The one aimed at you has no date on it, which is a harder problem, not an easier one. Start with the keyboard test, because it takes ten minutes and it usually finds the thing that is also costing you leads. If you want a second set of eyes on what it turns up, or you are quoting work for a Utah public entity and need to speak to conformance, we can look at it with you. Local visibility work that leads people to a page they cannot use is covered in our post on Salt Lake City local SEO, and the same principle applies: get the page usable first.