Some Chicago small businesses have opened a letter from a law firm claiming their website violates the Americans with Disabilities Act. The letter typically demands a settlement, threatens litigation, and cites specific technical failures: missing alt text on images, a contact form that can't be completed with a keyboard, low-contrast text that's hard to read. Owners who spent years thinking about physical accessibility (ramps, doorway widths, accessible restrooms) are often surprised that a website can create the same legal exposure.
This guide explains what website accessibility means in practice, why small businesses receive these letters, and how to fix the most common problems without an enterprise-sized budget.
Why Website Accessibility Became a Legal Issue
The ADA was signed in 1990, before the modern web existed, so it never mentions websites. For years that left real legal ambiguity about whether the law applied online at all. Federal courts still disagree on exactly when a website is covered, but the U.S. Department of Justice has stated its position plainly: in its 2022 web accessibility guidance, it says Title III of the ADA applies to the goods and services that businesses open to the public offer on the web. For a business with a storefront, office or customers it serves in person, the safe assumption is that its website is covered too.
The DOJ has no regulation setting a technical standard for private businesses, and its guidance points to the Web Content Accessibility Guidelines (WCAG), a set of testable criteria published by the W3C. For state and local governments, the DOJ's 2024 Title II rule adopts WCAG 2.1 Level AA, and that level is also what settlements and audits commonly use. WCAG 2.2, published in 2023 and updated in December 2024, adds a few criteria on top of 2.1. For a Chicago small business, the practical target is WCAG 2.1 or 2.2 Level AA: a documented technical standard, not a judgment call.
Why Small Businesses Get Demand Letters
ADA website litigation isn't spread evenly across the country. Plaintiffs' firms that specialize in it tend to file where courts have been receptive, and they often aim at small and mid-size companies in retail, restaurants, healthcare, professional services and e-commerce, because those businesses are less likely to have addressed accessibility and less likely to have in-house lawyers.
A typical demand letter cites a handful of technical violations found by an automated scanner, asks for a settlement and sets a short deadline to respond. Many businesses settle because even a modest legal defense can cost more than the demand, whatever the merits. That makes small businesses an economically attractive target, and it's why fixing accessibility in advance is so much cheaper than defending a claim.
The Most Common Accessibility Problems on Small Business Websites
A handful of issues come up again and again in demand letters and audits. The table maps each to the WCAG 2.2 criterion it fails.
| Problem | WCAG 2.2 success criterion | Level | Typical fix |
|---|---|---|---|
| Missing or useless alt text | 1.1.1 Non-text Content | A | Describe what each meaningful image shows; mark decorative images with empty alt |
| Low-contrast text | 1.4.3 Contrast (Minimum) | AA | At least 4.5:1 for body text and 3:1 for large text; adjust brand grays |
| Unlabeled form fields | 1.3.1 Info and Relationships; 3.3.2 Labels or Instructions | A | Tie each visible label to its input; explain required formats |
| Mouse-only menus and widgets | 2.1.1 Keyboard; 2.4.7 Focus Visible | A / AA | Make every control work with Tab, Enter and arrow keys, with a visible focus outline |
| Videos without captions | 1.2.2 Captions (Prerecorded) | A | Upload edited captions, not unreviewed auto-captions |
| Tiny tap targets | 2.5.8 Target Size (Minimum), new in 2.2 | AA | Buttons and links at least 24 by 24 CSS pixels, or spaced apart |
Missing or unhelpful image alt text tops the list. Screen readers rely on alt text to describe images to people who can't see them, and a missing or generic "image123.jpg" alt attribute leaves those users with nothing, even when the image is essential, like a product photo or an infographic with pricing. Insufficient color contrast between text and background is close behind, particularly on sites with fashionable light-gray text or brand colors that look elegant but fail objective contrast ratio tests.
Forms are another frequent failure. When the input fields on a contact form, quote request, or online ordering form aren't properly associated with their visible labels, screen reader users can't tell what belongs in each field. Keyboard navigation gaps show up constantly too: many sites depend on mouse-only interactions such as hover menus or custom dropdowns that don't work for people who navigate only by keyboard because of a motor disability. Videos without captions and PDFs that aren't tagged with proper reading order and alt text round out the most common findings, and both are especially common on Chicago small business sites that post promotional videos or downloadable brochures and spec sheets.
Why Popular Website Builders Don't Solve This Automatically
Many owners assume that a modern, professionally designed template or a popular platform like Squarespace, Wix, or WordPress produces an accessible site automatically. It doesn't. These platforms provide the tools to build an accessible page (proper heading structure, alt text fields, label associations), but they don't enforce them, and most business owners and many web designers don't fill them in correctly because accessibility wasn't part of the original brief. A visually polished Chicago restaurant or law firm website can still fail a WCAG audit badly if alt text was left blank, contrast wasn't checked, and the navigation menu doesn't respond properly to keyboard input.
That's also why a redesign is the best moment to build accessibility in from the start instead of treating it as a separate project later. Retrofitting an existing site's HTML structure, color palette, and interactive elements is almost always more expensive and slower than designing for accessibility the first time, particularly for e-commerce sites or sites with complex booking and scheduling tools.
What an Accessibility Audit and Remediation Process Looks Like
A proper accessibility review combines automated scanning with manual testing. Automated tools quickly flag objective, measurable issues across a whole site, such as missing alt attributes, insufficient contrast ratios, and missing form labels, and they're a reasonable first pass for a Chicago small business trying to understand its exposure. On their own, though, they miss many real-world issues, and the DOJ's guidance warns that a clean automated report does not mean a site is accessible. Some of the most important problems, like whether a screen reader announces content in a logical order or whether a custom dropdown can be operated by keyboard, need a human tester, often using real assistive technology such as a screen reader.
Remediation after the audit is usually prioritized by severity and effort. Quick wins like adding alt text and fixing color contrast can often be done in days, while structural issues like an inaccessible custom navigation menu or a booking widget built without keyboard support may need more substantial development. Publishing a written accessibility statement on the site, along with a documented remediation plan and timeline, also shows good faith, which matters for usability and for how a business is perceived if it does receive a legal demand.
Why Overlay Widgets Are Not a Shortcut
A category of products markets itself as an instant ADA fix: a line of JavaScript added to your site that claims to make it fully accessible for a modest monthly subscription. These overlay widgets are controversial in the disability advocacy and legal communities, with good reason. Instead of fixing a site's underlying HTML, color contrast, and structure, they try to patch problems on top of the existing code as the page loads, and they often conflict with the screen readers and assistive technologies they claim to support. In 2025 the Federal Trade Commission ordered one overlay vendor, accessiBe, to pay $1 million and barred it from claiming its automated product could make any website WCAG-compliant without evidence, and disability advocates have long warned businesses not to rely on overlays in place of real remediation. For a Chicago small business, paying for an overlay without fixing the underlying code usually buys a false sense of security, not legal protection.
Building Accessibility Into Ongoing Website Maintenance
Accessibility doesn't stay fixed. Every new blog post, product listing, or landing page can introduce new issues if the person creating it hasn't been trained on the basics. A short accessibility checklist in your publishing process (alt text on every image, a contrast check on new brand colors, a keyboard test on new forms) costs almost nothing and keeps the problems an audit fixed from creeping back. Periodic re-scans, especially after a redesign or a new e-commerce feature, catch regressions before they show up in the next demand letter.
Working With an IT Partner on Accessibility Compliance
For most Chicagoland small businesses, the fastest and most cost-effective route to WCAG compliance is a technology partner who understands both the technical requirements and the legal pressure behind them. 312 IT Consulting helps small businesses run an accessibility audit that combines automated scanning and manual testing, prioritize and implement fixes (in most cases without a ground-up rebuild), and set up a maintenance process so new content doesn't bring the same problems back. Addressing accessibility early usually costs less than responding to a demand letter, and it makes your site usable for customers who rely on assistive technology.
Frequently Asked Questions
Is website accessibility legally required for small businesses?
The U.S. Department of Justice says the Americans with Disabilities Act (ADA) applies to the web content of businesses open to the public, and many federal courts agree, even though the ADA doesn't mention websites and federal courts still disagree on the details. There's no technical standard written into the law for private businesses. In practice, settlements and audits commonly use WCAG 2.1 Level AA as the benchmark. Small businesses aren't exempt because of their size.
What is WCAG and what level of compliance should a small business target?
WCAG (Web Content Accessibility Guidelines) is the internationally recognized technical standard for making web content usable by people with visual, auditory, motor, and cognitive disabilities. It has three conformance levels: A (minimum), AA (mid-range), and AAA (highest). Level AA is the level the DOJ adopted for state and local government websites (WCAG 2.1 AA) and the level most accessibility policies use, which makes WCAG 2.1 or 2.2 Level AA the practical target for Chicago small businesses rather than the harder-to-achieve AAA level.
What are the most common website accessibility problems for small business sites?
The most frequent issues are images missing descriptive alt text, insufficient color contrast between text and background, forms without properly associated labels, videos without captions, websites that can't be fully navigated using only a keyboard, and PDF documents that aren't tagged for screen readers. These problems are common because most small business websites were built by designers focused on looks without accessibility testing, and popular website builders don't enforce accessible defaults.
How much does it cost to fix website accessibility issues?
Cost varies widely depending on how the site was built, how many pages and templates it has, and how many issues an audit finds. Quick fixes like alt text and contrast are inexpensive; rebuilding an inaccessible booking widget or navigation menu costs more. Fixing problems before a demand letter arrives is almost always cheaper than responding to one, and building accessibility into a redesign is typically the most cost-effective path for Chicago small businesses.
Do overlay widgets or plugins make a website ADA compliant?
Accessibility overlay widgets that promise instant compliance for a monthly fee are generally not a reliable solution, and in 2025 the FTC ordered one overlay vendor to pay $1 million over claims that its product made websites WCAG-compliant. Overlays try to patch accessibility problems with JavaScript instead of fixing the underlying code, and they often interfere with the assistive technology they claim to support. Real compliance requires fixing the site's HTML, contrast, and structure, ideally verified with both automated scanning tools and manual testing with real screen readers.