The Lawsuits Are Real, and Small Businesses Are the Target
ADA website accessibility lawsuits have been filed against businesses of every size — including solo operators, local restaurants, and independent service providers. Many of these cases start not with a government agency, but with a demand letter from a plaintiff's attorney citing a handful of specific, easy-to-spot failures on the defendant's website.
The good news: the failures that appear in the vast majority of those letters are not obscure. They are the same four or five issues, repeated across thousands of cases. Fix those, and you have addressed your most meaningful legal exposure. This guide walks you through exactly what those issues are, why they matter legally, and how to prioritize fixing them — without commissioning a $5,000 audit.
What the Law Actually Says About Website Accessibility in 2026
The Americans with Disabilities Act (ADA) does not include a specific section on websites. Courts have consistently extended Title III — which covers "places of public accommodation" — to websites, particularly when the site has a clear connection to a physical business location. In March 2022, the Department of Justice issued guidance confirming that web accessibility is required under the ADA, and in April 2024 the DOJ published a final rule under Title II specifically requiring public entities to meet WCAG 2.1 Level AA. While Title II formally covers state and local governments, the rule reinforced WCAG 2.1 AA as the recognized standard courts and regulators reference when evaluating Title III (private business) compliance as well.
For practical purposes, if you serve customers through your website — whether you sell products, take reservations, publish your menu, or accept contact form submissions — your site is almost certainly covered. WCAG 2.1 Level AA is the benchmark you should be working toward in 2026.
WCAG 2.1 AA: What It Is and What It Is Not
The Web Content Accessibility Guidelines (WCAG) are published by the W3C and organized into four principles: Perceivable, Operable, Understandable, and Robust. Level A is the minimum; Level AA is the legally recognized standard; Level AAA covers edge cases and specialized applications.
You do not need a perfect AAA site. You need a site that does not have Level A or Level AA failures in the areas most likely to affect real users — and most likely to appear in a demand letter.
The High-Risk Failures: Fix These First
These are the issues that appear most frequently in accessibility demand letters targeting small businesses. A developer who knows what to look for can often resolve all of them in a single focused session.
1. Insufficient Color Contrast
WCAG 2.1 Success Criterion 1.4.3 requires a contrast ratio of at least 4.5:1 between text and its background (3:1 for large text). Light gray text on a white background, yellow text on a light-colored button, or faded placeholder text inside form fields are the most common offenders.
This is the single most frequently cited issue in small-business demand letters because it is trivially easy for a plaintiff's attorney to detect with a free browser extension. Fix it by running your site through the WebAIM Contrast Checker and adjusting any failing color combinations in your CSS or design settings.
Developer instruction: "Audit every text color and background color combination sitewide. Replace any combination that fails a 4.5:1 ratio (4:1 for large text ≥ 18pt or bold ≥ 14pt). Pay special attention to form placeholder text, button labels, and footer text."
2. Missing or Empty Alt Text on Images
WCAG 1.1.1 requires that every non-decorative image have a text alternative that conveys the same meaning as the image. Screen readers used by blind and low-vision users read this alt text aloud. An image with no alt attribute — or an alt attribute left as an empty string when the image carries meaning — is a direct failure.
Decorative images (dividers, background textures) should have alt="" so screen readers skip them. Images that convey information — a photo of your team, a picture of a product, a chart — need descriptive alt text.
Developer instruction: "Audit every <img> tag. Confirm meaningful images have descriptive alt attributes. Confirm purely decorative images have alt="". Flag any images where alt is missing entirely."
3. Unlabeled Form Fields
WCAG 1.3.1 and 4.1.2 require that every form input — text fields, dropdowns, checkboxes, radio buttons — be programmatically associated with a visible or accessible label. Using placeholder text alone does not satisfy this requirement, because placeholder text disappears when a user starts typing and is not reliably announced by all screen readers.
Contact forms, newsletter signup boxes, quote request forms, and checkout fields are the most common locations for this failure on small business sites. A plaintiff's attorney can identify missing labels in under a minute using browser developer tools.
Developer instruction: "For every form input, confirm there is a <label> element with a matching for attribute, or that the input uses aria-label or aria-labelledby. Placeholder text alone is not sufficient."
4. Keyboard Navigation Failures
WCAG 2.1.1 and 2.1.2 require that all functionality on the page be operable using a keyboard alone — no mouse required. Users with motor disabilities often navigate entirely by keyboard, using Tab to move between elements and Enter or Space to activate them.
Common failures include: dropdown menus that only open on mouse hover, modals or pop-ups that trap keyboard focus and cannot be closed with Escape, and custom interactive components (sliders, accordions, date pickers) built without keyboard event handlers.
You can test this yourself: close your mouse, press Tab repeatedly, and see if you can reach and activate every link, button, and form field on your site. If you get stuck, you have a failure.
Developer instruction: "Tab through every interactive element on every page. Confirm focus is visible at all times (do not set outline: none on focusable elements without a replacement). Confirm hover-only menus respond to keyboard focus. Confirm modal dialogs trap focus inside and release it on close."
5. Missing Page Titles and Heading Structure
WCAG 2.4.2 requires every page to have a descriptive, unique <title> element. WCAG 1.3.1 requires that heading tags (<h1> through <h6>) be used to communicate structure, not just to change font size. A page where the heading hierarchy skips from <h1> to <h4>, or where headings are simulated using bold paragraph text, creates a navigation problem for screen reader users who jump between headings to orient themselves.
Developer instruction: "Confirm every page has a unique, descriptive <title> tag. Audit heading tags across all pages to confirm logical hierarchy: one <h1> per page, followed by <h2> subsections, <h3> sub-subsections, with no levels skipped."
A Practical Accessibility Checklist You Can Hand to Any Developer
- Color contrast: All text meets 4.5:1 contrast ratio (3:1 for large text). Verified with a contrast checker tool.
- Alt text: All meaningful images have descriptive alt attributes. All decorative images have
alt="". - Form labels: Every input is associated with a visible label via
<label for>,aria-label, oraria-labelledby. - Keyboard navigation: All interactive elements are reachable and operable by keyboard. Focus indicator is always visible.
- Page titles: Every page has a unique, descriptive
<title>tag. - Heading structure: Logical heading hierarchy with no skipped levels and one
<h1>per page. - Link text: No links labeled only "click here" or "read more" — link text describes the destination.
- Error identification: Form validation errors identify which field has the problem and describe how to fix it in text (not color alone).
- Language attribute: The
<html>element has alangattribute (e.g.,lang="en").
What You Can Safely Deprioritize (For Now)
WCAG 2.1 AA includes criteria that are highly relevant for complex web applications — video players with synchronized audio descriptions, real-time communication tools, multi-step authentication flows, and rich data tables. If your small business site is a brochure site, a restaurant with a menu, a service business with a contact form, or a local retailer with a shopping cart, these criteria are unlikely to appear in a demand letter because they do not apply to simple page types.
That said, if you publish video content, confirm you have accurate captions (WCAG 1.2.2). If you use PDFs, those should also be tagged for accessibility — but that is a separate remediation project from your HTML site.
Tools That Help You Find Problems Before a Plaintiff Does
These free tools can identify many of the issues above without any technical expertise:
- WAVE by WebAIM (wave.webaim.org) — browser extension that overlays accessibility errors directly on your page.
- axe DevTools (deque.com/axe) — free browser extension for Chrome and Firefox; widely used by developers.
- Google Lighthouse — built into Chrome DevTools; run an Accessibility audit from the browser without installing anything.
- WebAIM Contrast Checker (webaim.org/resources/contrastchecker/) — paste two hex codes, get your contrast ratio instantly.
Run WAVE or Lighthouse on every page of your site — especially pages with forms, images, or interactive elements. Address every red error before moving to yellow warnings.
Where Your Website Platform Fits In
Some website platforms generate inaccessible HTML by default — unlabeled inputs, missing alt text fields, poor heading structures baked into templates. If your current site was built on a platform that makes it difficult to fix these issues directly, a rebuild on a platform that outputs clean, semantic HTML may be more cost-effective than patching a problematic template.
For example, sites built with SiteGlowUp.ai include LocalBusiness structured data on every generated site, and the platform generates semantic HTML that makes the developer fixes described above straightforward to apply. If you want to see what a cleanly built small business site looks like as a starting point, the Fictional Plumbing Demo shows a service business site with proper heading structure, labeled contact form fields, and clear link text — the exact foundations an accessibility remediation starts from.
The Bottom Line on ADA Website Requirements in 2026
Website accessibility compliance is not an all-or-nothing proposition. The practical goal for a small business in 2026 is to eliminate the specific, high-frequency failures that appear in demand letters: color contrast, alt text, form labels, keyboard navigation, and page structure. A developer with clear instructions and a few hours can address all of these on most small business sites.
You do not need a $5,000 audit. You need the checklist above, a developer who understands it, and the discipline to run a free tool like WAVE before you publish any new page. That combination addresses the overwhelming majority of your legal exposure under current ADA interpretation — and it makes your site more usable for every visitor in the process.