Before you go
Know What’s Costing Your Business Leads.
Get a practical Growth Plan that shows where your visibility, website and lead response may be limiting results—and which improvements deserve attention first.
No obligationNo shared leadsNo generic plan
U.S. small-business playbook: prioritized website fixes, simple audit steps, and low-cost monitoring to cut ADA lawsuit risk and improve conversions.
Target WCAG 2.1 or 2.2 Level AA as your working benchmark. It’s the standard DOJ/ADA guidance points to, and the one courts and consent decrees actually cite. Start with an accessibility audit that combines an automated scan with manual testing, then fix your highest-traffic pages first: navigation, forms, and checkout or booking flows.
TL;DR:
- Small-business websites with online booking, checkout, or forms are most at risk and should prioritize fixing missing labels, poor contrast, and inaccessible forms.
- Treat WCAG 2.1 Level AA as a practical compliance benchmark, as it is repeatedly reinforced by lawsuits, settlements, and regulatory guidance.
- Automated tools identify common issues but must be combined with manual testing, including keyboard navigation and assistive technology use, to catch hidden problems.
- Ongoing monitoring, regular re-tests after updates, and a clear remediation plan greatly reduce legal exposure and improve long-term accessibility.
- Choosing a qualified vendor involves verifying manual testing practices, reference to WCAG AA, and demand for a prioritized, actionable remediation plan over vague compliance claims.
Almost certainly yes, if you’re open to the public. Title III of the ADA covers “public accommodations,” which the DOJ interprets to include businesses that serve customers online, not just brick-and-mortar locations. Title II, by contrast, governs state and local government entities and carries its own WCAG AA mandate with compliance expectations. If you run a private business, Title III is your concern, not Title II.
Here’s the part that trips people up: there’s no single federal regulation spelling out exactly what a private business website must do. Courts have split on how much a website needs to connect to a physical location, sometimes called the “nexus” test, and that split varies by federal circuit.
Waiting for total legal clarity is a bad bet. Fix what you can now.
WCAG AA didn’t become the default by accident. The DOJ’s Title II final rule for public entities adopted WCAG 2.1 Level AA with hard compliance timelines, and that same standard shows up repeatedly in private-sector settlements and consent decrees. No DOJ rule forces private businesses to hit AA specifically, but when regulators, courts, and plaintiffs’ attorneys all point to the same benchmark, that benchmark becomes the safest target regardless of what the letter of the law technically requires.
WCAG AA organizes requirements around four principles:
Hit those four categories at the AA level and you’ve covered the overwhelming majority of what shows up in demand letters.
Most small-business sites fail on a short, predictable list of issues, not on exotic edge cases.
<label> elements is often unusable with a screen reader, and it’s frequently the single biggest revenue leak on a site.Fixing the form and checkout issues alone tends to move the needle on conversions for every visitor, not just those using assistive technology.
Run this in order. Skipping steps or jumping straight to remediation without a real audit is how businesses spend money fixing the wrong things.
Step 1: Scope and scan. Identify your core user journeys, the paths that generate revenue or handle essential information, and run an automated scanner like WAVE or axe against them. Automated tools catch a meaningful share of issues (missing alt attributes, contrast failures, missing form labels) but they miss context-dependent problems entirely.
Step 2: Manual and user testing. Unplug your mouse and try to complete a purchase or fill out a contact form using only Tab, Shift+Tab, and Enter. Then run the same test with a screen reader like NVDA or VoiceOver. Where budget allows, have someone who actually uses assistive technology daily test your core tasks; automated scans plus code review still miss things a real user catches in seconds.
Step 3: Prioritize by impact, not by ease. Fix navigation and forms before you touch decorative image alt text. A prioritized remediation plan that targets core transactions first, booking, checkout, contact, reduces both user friction and legal exposure faster than working through a flat punch list top to bottom.
Step 4: Fix code, not just appearance. Accessibility overlay widgets that promise instant compliance are worth skepticism. They layer a separate experience on top of broken code rather than fixing it, and plaintiffs have specifically targeted sites relying on them.
Step 5: Publish and monitor. Post an accessibility statement naming your target standard, disclosing known limitations, and giving visitors a way to report problems. Set a monitoring cadence, monthly automated scans at minimum, and if you work with a vendor, put a remediation SLA in the contract.
Pro Tip: Bookmark your checkout and booking pages and re-test them by hand after every plugin update or theme change. That’s where regressions hide, and it’s the one habit that catches problems before a customer, or a plaintiff’s attorney, does.
Accessibility isn’t a one-time project. Every new blog post, product page, or embedded video is a chance to reintroduce the same problems you just paid to fix.
Building this into your regular website audit cycle, rather than treating it as a separate legal project, is usually the cheapest way to stay compliant long term.
Don’t panic, and don’t ignore it either. A large share of web accessibility suits follow a recognizable pattern: high-volume, sometimes serial filings from a small number of plaintiffs’ firms, often aimed at settling quickly rather than going to trial. That pattern cuts both ways. It means many small businesses do resolve these fast and relatively cheaply, but it also means moving slowly or dismissing the letter tends to cost more the longer it drags on.
First moves, in order:
Once you have an audit, a written remediation plan with dates, and (ideally) a published accessibility statement already in place, you have real negotiating leverage. Attorneys and courts tend to view an active, documented remediation effort more favorably than a business that did nothing until served.
Not really, and this is where a lot of business owners get bad advice. The ADA’s employment provisions under Title I exempt businesses with fewer employees, but that threshold applies to hiring practices, not to Title III’s public accommodations requirements that cover your website. There’s no parallel small-business headcount exemption written into Title III itself.
That said, practical enforcement isn’t uniform. Plaintiffs’ firms tend to target businesses with meaningful web traffic, e-commerce functionality, or online booking systems, since those sites present clearer “denial of access” arguments than a static one-page brochure site with a phone number. A five-employee auto shop with a simple contact form faces different practical risk than a fifty-employee retailer running full online checkout, even though neither is formally exempt.
Some states layer additional accessibility requirements on top of the federal baseline, and a handful of state laws (California’s Unruh Act is the most cited example) create their own private right of action with statutory damages, which changes the settlement math in ways that vary by state. If you operate in North Carolina or South Carolina, the practical exposure runs primarily through Title III and general negligence-style claims rather than a state-specific accessibility statute.
The honest bottom line: don’t rely on business size to avoid this issue. Build your compliance posture based on your site’s actual functionality, checkout, booking, account creation, not on employee count.
Costs vary enormously depending on your platform, site size, and how broken things currently are, but the general pattern holds: fixing issues proactively is almost always cheaper than fixing them after a demand letter arrives.
A few cost drivers worth budgeting around:
Emergency remediation under legal pressure, after a demand letter, with an attorney’s clock running, almost always costs more than the same work done on your own timeline. That’s the real budgeting lesson here: the cheapest version of ADA compliance is the one you start before anyone forces you to.
Not every accessibility “expert” you’ll find online is qualified, and small businesses are an easy target for vendors selling overpriced audits or overlay widgets that don’t actually fix anything.
Look for a few concrete signals before you hire anyone:
For most owner-operated businesses, the right move is folding accessibility into a broader website audit rather than treating it as a standalone legal purchase. That way the same review that catches accessibility gaps also catches conversion and SEO issues sitting on the same pages.
Accessible sites tend to load cleaner, structure content more logically, and convert better, three things Google’s crawlers and your customers both reward. At Wayofmarketing, a local North Carolina agency, we treat accessibility checks as a standard part of any website audit, not an optional add-on, because the fixes that satisfy WCAG AA usually overlap with the fixes that reduce bounce rate and improve form completion.
— Jason
Most small-business owners don’t have time to become ADA compliance experts, and hiring a specialized accessibility law firm for a routine audit is overkill for a five-page contractor site. Wayofmarketing folds accessibility review into the same website design and conversion optimization work we already do for contractors and service businesses across the Carolinas, so you’re not paying for two separate vendors to look at the same pages.
The process is simple: request an audit of your core pages (home, contact, booking, checkout), get a prioritized remediation plan back with specific fixes and timelines, and decide whether you want us to implement the code-level changes or hand them to your own developer. Pricing runs through our standard service packages, starting with the Foundation plan at $49 per month, up through the full W.A.Y. Growth System™ for businesses that want ongoing monitoring bundled with SEO and lead generation. Browse the full solutions overview or reach out to get your audit scheduled.
For the legal baseline, start with ADA.gov’s web guidance and the accompanying PDF checklist, both straight from the DOJ. For litigation patterns and settlement trends, Accessible.org’s lawsuit tracker documents actual filing activity. For a deeper dive on how WCAG AA intersects with search visibility, see this accessibility and SEO breakdown.
This article is general information, not a substitute for advice from a qualified lawyer. Consult a qualified legal professional about your own circumstances before acting on anything here.
If your business is open to the public, Title III of the ADA almost certainly applies to your website, though the exact technical requirements aren’t spelled out in a single federal rule. Treat WCAG 2.1 AA as your practical standard regardless.
Yes. The ADA’s small-business exemptions under Title I apply only to employment rules for businesses with fewer than a certain number of employees, not to Title III’s public accommodations requirements that cover your website.
Any website operated by a business open to the public falls under Title III, with the strongest legal exposure on sites offering online booking, checkout, or account creation. State and local government sites fall under Title II, which has its own WCAG AA mandate and deadlines.
Yes, and many of these suits follow a high-volume pattern where plaintiffs’ firms file repeatedly and push for quick settlements rather than trial. A documented audit and remediation plan, done before a demand letter arrives, is your strongest practical protection.
