ADA website compliance for a small business means building and maintaining your site to the Web Content Accessibility Guidelines (WCAG) 2.1 or 2.2 at Level AA, because the Department of Justice treats websites as covered by Title III of the Americans with Disabilities Act even though it has never issued a specific technical rule for private businesses. There is no exemption based on size, revenue, or employee count. Nearly 4,000 ADA website accessibility lawsuits were filed in 2025, up from 132 in 2016, and most begin with a demand letter to a small business, not a government enforcement action.
Is Your Small Business Website Actually Covered
Title III of the ADA prohibits discrimination “in the full and equal enjoyment of the goods, services, facilities, privileges, advantages, or accommodations of any place of public accommodation.”1Office of the Law Revision Counsel. 42 USC 12182 – Prohibition of Discrimination by Public Accommodations The statute was written in 1990 and doesn’t mention websites, but ADA.gov states plainly that “almost all types of businesses that serve the public, regardless of their size or the age of their buildings, must follow the ADA.”2ADA.gov. Businesses That Are Open to the Public
The DOJ’s position is that existing nondiscrimination and effective communication requirements already reach websites, and its guidance points to WCAG as “helpful guidance” while telling businesses they “can currently choose how they will ensure that the programs, services, and goods they provide online are accessible to people with disabilities.”3ADA.gov. Guidance on Web Accessibility and the ADA For state and local governments, the DOJ finalized a 2024 rule that explicitly requires WCAG 2.1 Level AA. That rule does not apply to private businesses, and reading it as if it does is a common misstep.
Federal appeals courts are split on whether a website is itself a place of public accommodation. In Robles v. Domino’s Pizza (2019), the Ninth Circuit held that Domino’s website and app were covered because they connected to physical restaurants, reasoning that the ADA applies to “the services of a place of public accommodation, not services in a place of public accommodation.”4United States Court of Appeals for the Ninth Circuit. Robles v Dominos Pizza LLC In Gil v. Winn-Dixie (2021), the Eleventh Circuit went the other way, concluding that “public accommodations are limited to actual, physical places.”5United States Court of Appeals for the Eleventh Circuit. Gil v Winn-Dixie Stores Inc Businesses in California, Oregon, Washington, and Arizona face the tightest exposure; those in Florida, Georgia, and Alabama face a higher bar for plaintiffs. Most accessibility attorneys recommend treating your site as covered regardless of where you sit, because plaintiffs shop for favorable venues and because state laws in places like California allow statutory damages that federal law does not.
The Standard to Build To: WCAG 2.1 or 2.2 Level AA
WCAG, published by the World Wide Web Consortium, is the measuring stick that shows up in settlement agreements, court orders, and the DOJ’s own guidance. Level AA is the target. Level A misses too many real-world barriers, and Level AAA sets a bar that isn’t practical to apply to an entire site. The guidelines organize around four principles known as POUR:
- Perceivable. Content is presented in ways all users can detect, including text alternatives for images, captions for video, and sufficient color contrast.
- Operable. Navigation and interactive features work for people using only a keyboard, voice commands, or other assistive input.
- Understandable. The interface behaves predictably, with clear labels on form fields and readable text.
- Robust. The underlying code works reliably with current and future assistive technologies like screen readers.
Concrete requirements at Level AA include a minimum 4.5:1 color contrast ratio for normal text (3:1 for large text) and the ability to resize text up to 200% without losing functionality. WCAG 2.2, published in 2023, added criteria that matter for common small business features: minimum touch target sizes on mobile, keyboard focus indicators that aren’t hidden behind other elements, no drag-only interactions, and authentication that doesn’t rely on cognitive tests like CAPTCHAs.6World Wide Web Consortium. Web Content Accessibility Guidelines (WCAG) 2.2 If your site has a booking widget, shopping cart, or login, those newer criteria apply directly.
Running an Accessibility Audit
Start by listing every unique page and every interactive element, including embedded maps, payment processors, chatbots, and social feeds. Anything that loads on your domain counts as part of your site for audit purposes.
Automated scanners like WAVE and Axe DevTools catch common technical failures quickly, flagging insufficient contrast, missing alt text, poor heading structure, and unlabeled form fields.7WAVE Web Accessibility Evaluation Tools. WAVE Web Accessibility Evaluation Tools They typically catch 30 to 40 percent of accessibility issues. The rest require a human.
Manual testing means navigating the entire site with only a keyboard, then again with a screen reader. NVDA (free, Windows) and VoiceOver (built into macOS and iOS) work for small businesses without a testing budget. JAWS is the paid industry standard. Focus on whether every interactive element receives keyboard focus in a logical order, whether error messages get announced, and whether any information is conveyed only through color or visual position.
Compile findings into a remediation report that lists each error, its location, and the WCAG criterion it violates. That document becomes your technical roadmap and, if a demand letter ever arrives, evidence of good-faith effort. A professional manual audit for a small business site typically runs $1,500 to $7,000 depending on size and complexity.
The Fixes That Come Up Most Often
Most remediation involves HTML, CSS, or CMS settings, not deep engineering. The recurring problems on small business sites are predictable.
Image alt text. Every image that carries information needs a concise description in the alt attribute. Purely decorative images should use an empty alt (alt="") so screen readers skip them. Describe what the image communicates, not just what it depicts. “Team photo at our downtown storefront” beats “IMG_3847.jpg.”
Color contrast. Body text needs at least 4.5:1 against its background; large text (18pt, or 14pt bold) needs 3:1. Light gray on white is the single most common contrast failure on small business sites.6World Wide Web Consortium. Web Content Accessibility Guidelines (WCAG) 2.2
Heading structure. H1 through H6 should follow a logical hierarchy without skipping levels. Screen reader users navigate by jumping between headings, so a page that goes H1, H3, H2 is disorienting. Most content management systems set heading levels in the editor without touching code.
Keyboard navigation. Every link, button, form field, and interactive element must be reachable and operable using only Tab, Enter, and arrow keys. Custom dropdowns and modal pop-ups are the usual traps. Walk through your entire contact and checkout flow with only a keyboard after any redesign.
Rerun the automated scan after fixes to confirm you resolved the flagged issues without creating new ones.
Why Overlay Widgets Are Not a Solution
Automated overlay tools that promise instant ADA compliance through a single line of JavaScript are heavily marketed to small businesses. They don’t work, and they can make your legal situation worse.
In January 2025, the FTC fined overlay provider accessiBe $1 million for deceptive claims, finding that the company misrepresented its AI tool’s ability to make websites WCAG-compliant.8Federal Trade Commission. FTC Order Requires Online Marketer to Pay 1 Million for Deceptive Claims Its AI Product Could Make Websites Accessible The order bars the company from claiming its automated product achieves or maintains WCAG compliance without evidence.
The technical problem is that overlays can’t restructure your underlying HTML, can’t create proper form label associations, and can’t fix keyboard navigation inside custom JavaScript components. Screen readers often parse the source before the overlay’s script loads, so the assistive technology reads the original, non-compliant code. Settlement agreements now routinely require overlay removal and source-code remediation instead. Paying for an overlay and assuming you’re protected leaves you with the overlay bill and the same legal exposure.
Third-Party Widgets Are Your Problem Too
If a third-party tool loads on your domain, its accessibility problems are your accessibility problems. Booking engines, chat plugins, social feeds, and embedded payment forms are part of the experience you control, and users encountering barriers won’t distinguish between your code and a vendor’s. When the user leaves your domain to complete a transaction on the vendor’s site, direct liability generally ends at the handoff, but the intake widget on your site still has to be accessible.
Before integrating any third-party tool, ask the vendor for a Voluntary Product Accessibility Template (VPAT) documenting conformance with WCAG 2.2 Level AA. If they can’t produce one, that’s a signal. For new vendor contracts, require WCAG 2.2 Level AA conformance for the life of the engagement, treat accessibility defects as bugs rather than change orders, require an updated conformance report with major releases, and include an indemnification clause covering costs if you’re sued because of the vendor’s product.
If a Demand Letter Arrives
Most small businesses first meet ADA web accessibility through a demand letter from a plaintiff’s attorney. These letters allege specific barriers and demand a settlement plus a remediation commitment. Settlements typically range from $3,000 to $25,000, with federal-only cases at the lower end because Title III limits private plaintiffs to injunctive relief and attorney’s fees.
That limit is worth understanding. When a private individual sues under Title III, a court can order you to fix barriers and can award the plaintiff’s attorney’s fees, but it cannot award the plaintiff monetary damages.9Office of the Law Revision Counsel. 42 USC 12188 – Enforcement The money in settlements goes primarily to the lawyer. DOJ enforcement is different: the Attorney General can seek damages for affected individuals and civil penalties up to $75,000 for a first violation and $150,000 for subsequent violations.10ADA.gov. Americans with Disabilities Act Title III Regulations Some state laws also allow statutory damages, which is why California cases settle higher.
Engage an attorney who handles digital accessibility cases specifically. Don’t admit liability, and don’t ignore the letter. Commission an audit immediately and put a written remediation plan on paper with timelines. Documented good-faith effort matters, because courts weigh whether a business tried to fix problems when evaluating claims of willful neglect. A measured response that acknowledges the issue and outlines steps often keeps a demand from escalating into a federal lawsuit.
Tax Credits and Deductions That Offset the Cost
Two federal tax incentives help pay for accessibility work, and a small business can use both in the same year.
The Disabled Access Credit under IRC Section 44 is built for small businesses. If your business had gross receipts under $1 million or fewer than 30 full-time employees in the prior tax year, you qualify. The credit covers 50% of eligible accessibility expenditures between $250 and $10,250, producing a maximum annual credit of $5,000.11Office of the Law Revision Counsel. 26 USC 44 – Expenditures to Provide Access to Disabled Individuals Website remediation, accessibility audits, and assistive technology testing are eligible.
The Architectural Barrier Removal Deduction under IRC Section 190 lets any business, regardless of size, deduct up to $15,000 per year for removing accessibility barriers.12Office of the Law Revision Counsel. 26 US Code 190 – Expenditures to Remove Architectural and Transportation Barriers to the Handicapped and Elderly Spending above $15,000 must be capitalized and depreciated. A business that spends $12,000 on remediation could claim a $5,000 credit under Section 44 and deduct the remainder under Section 190.
Keeping the Site Compliant Over Time
Every new blog post, product listing, image, or plugin update can introduce a new barrier. The businesses that avoid repeat lawsuits build accessibility into their content workflow rather than treating it as an annual project.
Publish an accessibility statement linked from your site footer. It should name the standard you target (WCAG 2.1 or 2.2 Level AA), acknowledge known limitations, and give users a dedicated way to report access issues.13World Wide Web Consortium. Developing an Accessibility Statement A working feedback channel catches problems before they become lawsuits and shows good faith if a complaint is filed.
Assign someone to check that new content meets your accessibility standards before it publishes. That person doesn’t need to be a developer. Writing usable alt text, using headings correctly, keeping link text descriptive, and checking contrast with a free browser extension covers most content-side issues. Run a full automated scan quarterly and a manual screen reader review at least twice a year. The cost of maintaining accessibility is a fraction of the cost of remediating from scratch after a demand letter arrives.