An ADA website checklist small business owners can actually finish does not start with a vendor badge. It starts with three questions: which law covers you, which technical standard that law (or litigation practice) points to, and how much of that standard your site meets today. You will not get a forever certificate from a free scan. You can get a defensible first read in about two hours with a keyboard, a browser, and one honest pass through your key pages.
This guide is a practical WCAG website self check for private service businesses — not legal advice. If you need inclusive patterns baked into a redesign instead of bolted on later, start at web design or contact.
Title II vs Title III: which bar applies to your business
“ADA compliant website” collapses three different regimes into one phrase. Getting the regime wrong means testing against the wrong list.
ADA Title II covers state and local government entities (and special districts, transit authorities, and similar). The Department of Justice’s Title II web and mobile rule names a specific technical standard: WCAG 2.1 Level AA. After an Interim Final Rule published and effective April 20, 2026, the compliance dates are:
| Entity size | Compliance date |
|---|---|
| Population 50,000 or more | April 26, 2027 |
| Population under 50,000, or special district governments | April 26, 2028 |
Those dates and the WCAG 2.1 AA standard are summarized on ADA.gov’s small entity compliance guide. Older posts that still print April 24, 2026 as the big-entity deadline are stale.
ADA Title III covers private businesses open to the public — most local service companies, clinics, retailers, and studios. There is no DOJ-adopted technical checklist that prints “do these WCAG numbers and you are done.” The obligation to provide equal access and effective communication is still real. In practice, settlements, consent decrees, and expert reports keep converging on WCAG 2.1 Level AA as the litigation benchmark. Many teams also test newer WCAG 2.2 Level AA criteria for headroom on new builds; Title II itself still names 2.1 AA.
Section 508 (federal agencies and covered federal procurement) is a third track and names older WCAG 2.0 A/AA. Skip it unless you sell into that market.
If you are a private small business asking “is my website ADA compliant DIY?”, you are almost always in Title III territory: continuous exposure, WCAG AA as the working bar, and no magic government stamp.
ADA website checklist small business owners can run in about two hours
Pick seven pages that represent your templates and critical tasks: home, a listing or services page, a content page with images, a contact or intake form, login or account if you have it, a thank-you or confirmation step, and one page with a table or FAQ accordion. The home page alone is not a sample.
Then run this ADA website checklist for small business — nine checks mapped to WCAG success criteria. Log pass/fail with the page URL and the SC number.
| # | Check | How to run it | WCAG SC | Level |
|---|---|---|---|---|
| 1 | Keyboard only | Unplug the mouse. Tab, Shift+Tab, Enter, Space, arrows — operate every control | 2.1.1 Keyboard | A |
| 2 | Visible focus | While tabbing, you can always see where focus is | 2.4.7 Focus Visible | AA |
| 3 | Meaningful alt text | Read each image alt aloud — does it carry the same information? | 1.1.1 Non-text Content | A |
| 4 | Color contrast | Body text, links, placeholders, text on images vs background | 1.4.3 Contrast (Minimum) | AA |
| 5 | Headings and structure | Heading outline matches the page; not styled bold text pretending to be headings | 1.3.1 Info and Relationships | A |
| 6 | Form labels | Click each visible label — focus lands in the matching field; errors are clear | 3.3.2 Labels or Instructions | A |
| 7 | Zoom and reflow | At ~400% zoom on a desktop viewport, content reflows without forced horizontal scroll or clipped UI | 1.4.10 Reflow | AA |
| 8 | Video captions | Prerecorded marketing or explainer videos have accurate captions | 1.2.2 Captions (Prerecorded) | A |
| 9 | Custom components | Dropdowns, modals, tabs, date pickers work with a screen reader (VoiceOver, NVDA, or TalkBack) | 4.1.2 Name, Role, Value | A |
Contrast numbers to remember: normal text needs at least 4.5:1; large text (about 18pt or 14pt bold) needs at least 3:1.
On the keyboard pass, hunt for traps — components you can Tab into and cannot leave. On alt text, remember alt="image123" passes many scanners and fails the criterion. On forms, unlabeled required fields and error messages that never receive focus end the task for keyboard and screen-reader users even when the rest of the page “looks fine.”
Run the keyboard pass first and the automated scan last. Fifteen minutes of Tab can surface blockers a green Lighthouse Accessibility score will miss.
What automated scanners miss (and why green ≠ accessible)
Automated tools such as axe, WAVE, and Lighthouse are worth running. They are not a verdict.
The WebAIM Million 2026 report (data from February 2026; updated March 30, 2026) found detectable WCAG 2 failures on 95.9% of the top one million home pages — up from 94.8% in 2025 — averaging 56.1 errors per page. Six categories still dominate: low-contrast text (83.9% of pages), missing alternative text (53.1%), missing form labels (51%), empty links (46.3%), empty buttons (30.6%), and missing document language (13.5%). Those six account for about 96% of detected errors.
That means two things for a DIY owner:
- The odds your site is clean without testing are low.
- Fixing contrast, alt text, labels, empty controls, and
langon<html>removes a huge share of detectable issues — and still leaves judgment calls scanners cannot make.
Independent studies disagree on exact coverage percentages because they measure different things (issue volume vs barrier types). A fair operating rule for small teams: tools catch many high-frequency, machine-checkable failures and miss large classes of journey-level and semantic failures. An image with alt="car" on a photo of a classroom can pass automation and fail the criterion. Treat a green score as a partial sensor reading, not a compliance certificate.
Why accessibility overlays are not a compliance strategy
Overlay widgets promise compliance from a script tag. Source-level markup still has to work when the script fails, when a third-party domain loads, or when a plaintiff tests the page without the overlay’s assumptions.
On January 3, 2025, the Federal Trade Commission announced that accessiBe would pay $1 million to settle allegations it deceptively claimed its AI accessibility product could make websites WCAG-compliant. The final order was approved in April 2025. That enforcement action is about marketing claims — and it lines up with what practitioners already know: a runtime layer is not a substitute for fixing name, role, value, contrast, labels, and keyboard behavior in the product itself.
If you already bought an overlay, keep remediating the markup. Do not treat the widget as proof you finished the WCAG website self check.
After the ADA website checklist: DIY fix vs professional remediation
Stay in DIY when:
- Failures are mostly contrast, missing alt, empty buttons/links, missing labels, or missing
lang - You can finish every critical journey with keyboard alone
- Custom widgets are rare or already use native HTML
Bring in a professional audit or a design/development pass when:
- You hit keyboard traps, unlabeled required fields, or journeys you cannot finish
- Modals, filters, booking widgets, or custom dropdowns fail Name/Role/Value
- You need a per-criterion record for a buyer, insurer, or procurement team
- The template or page builder fights semantic structure and you are stacking workarounds
Accessibility work pairs well with performance work — layout stability and readable structure often move together. If you are already auditing field data, our Core Web Vitals guide for small business sites covers the speed side without replacing this checklist.
Building accessibility into your next design project
The cheapest accessibility work is the work you do before launch: semantic HTML, visible focus styles, labeled forms, real headings, captions, and components that work without a mouse. Retrofits cost more because every template and third-party embed becomes a negotiation.
At CD Sportswear INC — a web design, development, branding, and AI automation studio (not an apparel shop) — we treat inclusive patterns as part of the build, not a post-launch badge. When your DIY pass shows structural debt, a scoped web design engagement can remediate and redesign in the same pass. Ready for a fit check? Use contact.
Conclusion
An ADA website checklist small business teams can trust is not a vendor seal. Know whether Title II deadlines or Title III litigation practice applies. Run the nine DIY checks on a real page sample. Use scanners as helpers, not judges. Do not outsource the problem to an overlay. Fix the markup — and when custom components or full journeys need a studio-level pass, start from web design and contact.
This article is educational, not legal advice. Your counsel or a qualified accessibility auditor owns compliance opinions for your facts.