Does Your Small Business Website Need to Be ADA Compliant?
What the DOJ says about business websites, who the 2024 web rule and its 2026 extension cover, what overlays cannot do, and a fix-first plan.
- Written by Pixel2Tech Team
- Topic: Web Development
- Published
- 7 min read

This article is general information, not legal advice; if you've received a demand letter or lawsuit, talk to an attorney. Pixel2Tech is a design and development studio in Lahore, Pakistan, and offers the website services discussed here.
Key takeaways
- Title III covers businesses open to the public regardless of size, and the DOJ's position is that this includes what they offer online. There is no small-business exemption.
- There is also no DOJ web regulation for private businesses. The 2024 rule that adopted WCAG 2.1 AA covers state and local governments, and an April 2026 interim final rule moved its deadlines to April 26, 2027 and April 26, 2028.
- WCAG 2.1 or 2.2 Level AA is the practical target for a business site. Content that meets WCAG 2.2 also meets 2.1 and 2.0.
- Overlays don't guarantee compliance. In 2025 the FTC finalized an order requiring accessiBe to pay $1 million over claims that its AI tool could make any website WCAG-compliant.
- If you receive a demand letter, call an attorney first. Then audit, fix templates before content, and keep a dated record of the work.
In this article (11 sections)
Does a small business website need to be ADA compliant?
If your business is open to the public, the Department of Justice's position is that the ADA covers what you offer on your website, and Title III applies regardless of business size. But no DOJ regulation sets a technical web standard for private businesses, so WCAG 2.1 or 2.2 Level AA is the practical target, not a legal checklist.
That answer frustrates people because it isn't a clean yes or no. The practical version: the legal risk is real, the DOJ has told businesses they can choose how to make their sites accessible, and the benchmark almost everyone uses is the Web Content Accessibility Guidelines.
On size, the DOJ's ADA primer for small businesses says nearly all types of businesses that serve the public are covered by Title III, regardless of the size of the business. Size does affect some obligations for physical premises, where the "readily achievable" standard for removing barriers depends on a business's size and resources. It doesn't create an exemption.
Title II vs Title III: who the 2024 DOJ web rule covers
The DOJ's 2024 web accessibility rule applies to state and local governments under Title II, not to private businesses under Title III.
In 2024 the DOJ adopted WCAG 2.1 Level AA as the technical standard for the web content and mobile apps of state and local governments. ADA.gov's summary of the rule says it applies to all state and local governments, including their agencies and departments, as well as special purpose districts, Amtrak and other commuter authorities.
On April 20, 2026, the DOJ published an interim final rule in the Federal Register (document 2026-07663) that moved the compliance dates. As of September 2026, they stand as follows:
| Who | Original date | Date after the April 2026 extension |
|---|---|---|
| State and local governments with a total population of 50,000 or more | April 24, 2026 | April 26, 2027 |
| Public entities with a total population under 50,000, and special district governments | April 26, 2027 | April 26, 2028 |
| Private businesses (Title III) | Not covered by this rule | Not covered by this rule |
Why a private business should still pay attention
The rule shows which standard the DOJ chose when it did write a web regulation: WCAG 2.1 Level AA. If you're deciding what to build to, that's a strong signal. And if you sell to state or local government agencies, their own obligations may shape what they ask of your deliverables.
What the DOJ's 2022 guidance asks of private businesses
The March 2022 guidance says businesses open to the public must make their online goods and services accessible, but leaves the method to them.
The DOJ's guidance on web accessibility and the ADA, dated March 18, 2022, says the Department has consistently taken the position that the ADA's requirements apply to all the goods and services that public accommodations offer, including those offered on the web.
It also says the Department doesn't have a regulation setting out detailed standards, and that businesses can currently choose how they will make their online offerings accessible. It points to existing technical standards, WCAG and the federal Section 508 Standards, as helpful guidance, and it lists the kinds of barriers it has in mind:
- Poor color contrast that makes text hard to read.
- Color used alone to convey information.
- Images without text alternatives (alt text).
- Videos without captions.
- Online forms without proper labels and error indicators.
- Navigation that works only with a mouse, not a keyboard.
Why WCAG 2.1 or 2.2 Level AA is still the practical target
WCAG is the standard the DOJ's guidance points to, and Level AA is the level the DOJ adopted when it wrote its Title II rule.
WCAG defines three conformance levels: A (lowest), AA and AAA (highest). WCAG 2.2 is a W3C Recommendation; its current version is dated 12 December 2024, and content that conforms to WCAG 2.2 also conforms to 2.1 and 2.0. Building to 2.2 AA therefore covers the 2.1 AA standard in the Title II rule, with room to spare.
Two examples of what AA means in practice. Normal-size text needs a contrast ratio of at least 4.5:1 against its background. And under WCAG 2.2's new target size criterion, clickable targets generally need to be at least 24 by 24 CSS pixels, with listed exceptions such as links inside a sentence.
Where small-business sites usually fail
Most accessibility failures on small-business sites come from a handful of template and content issues that a basic review can find.
The W3C's Easy Checks are a good first pass you can run in any browser: page titles, alt text, headings, contrast, text resize, keyboard access and visible focus, forms and errors, moving or flashing content, captions and basic structure. The W3C is clear that a page can pass these checks and still have significant barriers, so treat them as a starting point, not a verdict.
Don't skip the parts other companies built. Booking widgets, chat pop-ups, embedded maps, review carousels and payment forms all appear on your pages, and customers experience them as part of your site. Include them in testing, and ask each vendor for its accessibility documentation before you renew.
| Area | Typical problem | Fix |
|---|---|---|
| Forms | Placeholder text instead of labels; errors shown only in red | Visible labels, error messages in text, a submit button you can reach by keyboard |
| Images | Missing alt text or file names as alt text; words baked into images | Describe meaningful images, mark decorative ones as decorative, use real text |
| Contrast | Light gray text on white; text over busy photos | Meet 4.5:1 for normal text; add an overlay behind text on images |
| Keyboard | Menus, sliders or pop-ups that can't be reached or closed without a mouse | Test every interactive element with Tab, Enter and Escape |
| Video | No captions on explainer or testimonial videos | Add accurate captions and review auto-generated ones before publishing |
| PDFs | Scanned menus, price lists or intake forms | Publish the content as HTML pages, or as tagged, accessible PDFs |
| Headings | Text styled to look like headings but not marked up as headings | Use real heading levels, in order |
Do accessibility widgets make you compliant? What the FTC's accessiBe order means
No widget can guarantee compliance, and the FTC has already acted against a vendor for claiming its AI tool could make any website WCAG-compliant.
Accessibility overlays add a toolbar or script that tries to fix problems automatically. In January 2025 the FTC announced a proposed order requiring accessiBe, which sells a plug-in called accessWidget, to pay $1 million. The FTC alleged that accessiBe falsely claimed its product could make any website compliant with WCAG, and that it formatted third-party articles and reviews to look like independent opinions.
In April 2025 the Commission voted 3-0 to approve the final order. It bars the company from claiming its automated products can make any website WCAG-compliant, or keep it compliant over time, unless it has evidence to support those claims.
The lesson for a business owner: marketing claims about automatic compliance can run well ahead of what a product does. Fix the templates and content of the site itself. If you use a tool, treat it as an extra for some users, not as a legal shield.
Got a demand letter? What to do in the first week
Treat an ADA demand letter as a legal matter first and a website project second. Speak to an attorney before you reply.
A calm first week usually looks like this:
- Don't ignore the letter, and don't reply or pay anything before speaking to an attorney.
- Note any deadline in the letter and share it with your attorney.
- Save a dated record of the site as it is today, such as screenshots of the pages the letter mentions.
- Gather your records: who built the site, the contract, any earlier audits and any accessibility statement.
- Ask your web team for a quick review of the specific barriers the letter describes.
- Don't install an overlay as a quick fix; it's unlikely to resolve the issues the letter lists.
- Check whether your business insurance covers this kind of claim.
- With your attorney, plan remediation you can document.
A reminder on advice
This section is general information. Only an attorney who knows your situation and jurisdiction can advise you on how to respond, what to say, and whether to settle.
A realistic remediation plan: audit, templates, content, monitoring
Fix the parts that repeat first. A template fix corrects every page built on it, while a content fix corrects one page.
Keep a dated record of what you found, what you fixed and when. It helps you track progress, and your attorney may want it.
On cost, one detail is worth a question to your accountant. The DOJ's small-business primer describes a Disabled Access Credit for businesses with 30 or fewer full-time employees or total revenues of $1 million or less in the previous tax year. Whether your website work qualifies is a tax question, so ask before you assume it does.
1. Audit
Combine an automated scan with manual testing by keyboard and screen reader on your key templates and your most important tasks: contacting you, booking, buying or applying. Automated tools can't judge things like whether alt text is meaningful or whether a form's error messages make sense, so the manual part isn't optional.
2. Fix templates and components
Header, navigation, footer, forms, buttons, pop-ups and page templates. These fixes carry across the whole site and give you the most progress per hour.
3. Fix content
Alt text, heading order, link text, captions and PDFs. Train whoever publishes content, so new pages don't bring the same problems back.
4. Monitor
Retest after every design change or new plugin, and review a sample of new content on a regular schedule.
Accessibility statements: what to include and what not to promise
An accessibility statement tells visitors which standard you aim for, what you know isn't working yet, and how to reach you for help.
The W3C's guidance on accessibility statements recommends including:
- A commitment to accessibility for people with disabilities.
- The standard you apply, such as WCAG 2.2.
- Contact information for people who run into problems.
- Known limitations, described in plain language.
- The measures you've taken to support accessibility.
Don't overpromise
Don't claim full compliance unless an audit supports it. "We aim to meet WCAG 2.2 Level AA and are working on the issues listed below" is honest. "This site is 100% ADA compliant" is a promise you may not be able to keep. The DOJ's 2022 guidance also notes that giving the public a way to report accessibility problems helps website owners fix them, so make the contact route easy to find.
Building accessibility into your next redesign or platform choice
Accessibility is cheapest when it's part of the brief. Put WCAG 2.2 AA in your requirements, ask vendors how they test, and include it as a line item. Our guide to website redesign costs shows where it fits in the budget, and our platform comparison covers how WordPress, Webflow and Squarespace affect it. If you sell on Shopify, see our Shopify ADA compliance checklist.
When you compare themes, templates or agencies, ask the same three questions: which WCAG version and level they build to, how they test (automated only, or manual keyboard and screen reader checks too), and what happens when your team adds content after launch. Vague answers to the second question usually mean accessibility hasn't been scoped.
Pixel2Tech's website development team can review your key templates and forms against WCAG 2.2 AA and fix what we find, working alongside your attorney if a letter has already arrived.
Sources and further reading
- ADA.gov: Guidance on Web Accessibility and the ADA (March 2022)
- ADA.gov: Fact sheet on the 2024 Title II web and mobile app rule
- Federal Register: Extension of compliance dates (Interim final rule, April 20, 2026)
- ADA.gov: ADA Update, A Primer for Small Business
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2
- FTC: Final order requiring accessiBe to pay $1 million (April 2025)
Frequently asked questions
Is there an ADA exemption for small business websites?
No. The DOJ's small-business primer says nearly all types of businesses that serve the public are covered by Title III regardless of their size, and its 2022 web guidance says the ADA applies to goods and services offered on the web. What doesn't exist is a DOJ regulation setting a technical web standard for private businesses, which is why WCAG is the working benchmark.
Does the DOJ's 2024 web accessibility rule apply to private businesses?
No. It applies to state and local governments under Title II, including special purpose districts, Amtrak and commuter authorities. An interim final rule published on April 20, 2026 moved its compliance dates to April 26, 2027 for entities with populations of 50,000 or more and April 26, 2028 for smaller entities and special district governments. Private businesses fall under Title III.
What WCAG level should a small business website meet?
Aim for WCAG 2.2 Level AA. Level AA is the level the DOJ adopted, in WCAG 2.1, for state and local governments, and content that conforms to WCAG 2.2 also conforms to 2.1 and 2.0. Level AAA is rarely a realistic target for a whole site. Start with your key templates and the tasks customers most need to complete.
Will an accessibility widget protect my business from an ADA lawsuit?
You shouldn't rely on one. A widget doesn't fix the underlying code and content, and in 2025 the FTC finalized an order requiring accessiBe to pay $1 million after alleging it falsely claimed its tool could make any website WCAG-compliant. Fixing the site itself, and documenting that work, is the approach that actually reduces barriers.
What should I do if I receive an ADA website demand letter?
Contact an attorney before you respond or pay anything, and note any deadline in the letter. Save a dated record of the site, gather your website contract and any past audits, and ask your web team to review the specific barriers the letter describes. Avoid quick fixes like overlays; plan documented remediation with your attorney's guidance.
Is an accessibility statement legally required?
The DOJ's 2022 web guidance for businesses doesn't set a requirement for one, and there's no DOJ web regulation for private businesses. A statement is still useful: the W3C recommends including your standard, known limitations and contact details, and the DOJ notes that a way to report problems helps owners fix them. Ask your attorney about any state or contract requirements.
About the author: Pixel2Tech Team
Pixel2Tech is a Lahore studio for brand, web, video and automation work. We write about problems we see in client projects.
Meet the teamWant to know where your site stands before a letter arrives?
Send us your URL. We'll review your key templates and forms against WCAG 2.2 AA and give you a prioritized fix list you can hand to any developer.
Related articles

Shopify ·
Shopify ADA Compliance: A Practical WCAG Checklist for Stores
A WCAG-based accessibility checklist for Shopify themes, product pages, cart drawers, apps and content, with a three-pass test method and a sensible fix order.

Web Development ·
Website Redesign Cost for Small Businesses: Line-by-Line Budget
What a small business website redesign costs, line by line: design, build, content, SEO migration and accessibility, plus a worksheet to fill in before quotes.

Web Development ·
WordPress vs Webflow vs Squarespace for a Service Business Site
WordPress, Webflow and Squarespace compared for law firms, clinics and contractors: editing, lead capture, exit costs and three-year subscription cost.

Web Development ·
WordPress 7.1.2 Security Fix: What Business Owners Must Do Now
WordPress 7.1.2 fixes CVE-2026-87902, attacked on release day. A 15-minute owner check, safe update steps and signs your site was hit before you patched.
Related Pixel2Tech services
Get new articles by email
Leave your email and we'll send new posts when they're published.