Web accessibility demand letters are a live risk for small businesses with a public website, residential contractors included. The pattern is well known: a site gets scanned for accessibility violations using automated tooling, and a demand letter follows. We are not going to quote you a filing count or a settlement range, because the numbers that circulate in this space come from firms selling remediation and we have not found a primary source that supports them. What we can source is what the law actually says, which is more useful anyway. The legal exposure is structural and avoidable, the technical fixes are achievable, and the third-party “accessibility overlay” widgets that promise instant compliance often make the exposure worse, not better.
What ADA web accessibility actually requires
The Americans with Disabilities Act doesn't name websites specifically, it predates the modern web. The Department of Justice's own web guidance states that title III prohibits discrimination by businesses open to the public and that the Department has consistently taken the position that the Act's requirements apply to all the goods and services a public accommodation offers, including those offered on the web.
Here is the part most contractor-facing articles get wrong. For a private business there is no federal regulation setting out a detailed technical standard. The Department says businesses have flexibility in how they comply but must comply, and it points to the Web Content Accessibility Guidelines as helpful guidance rather than as a binding rule. The 2024 Department of Justice web rule that does adopt WCAG 2.1 Level AA as a technical standard applies to title II, meaning state and local governments, with compliance dates in April 2027 and April 2028 depending on population. It is not a rule for private businesses. So treat WCAG 2.1 Level AA as the practical target a plaintiff and a court will measure you against, not as a regulation you can point at and claim literal compliance with.
WCAG 2.1 is built on 4 principles, and defines three conformance levels, A, AA, and AAA:
- Perceivable. Information and user interface components must be presentable to users in ways they can perceive. Text alternatives for images, captions for video, sufficient color contrast.
- Operable. User interface components and navigation must be operable. Keyboard, screen reader, voice control. No content that flashes or requires precise mouse control without alternatives.
- Understandable. Information and the operation of the user interface must be understandable. Labels on form inputs, error messages identifying problems clearly.
- Robust. Content must work with current and future assistive technologies and user agents. Valid HTML, proper semantic structure, accessible names on interactive elements.
The lawsuit-target profile
The accessibility-overlay trap
A common contractor temptation is to install a third-party accessibility overlay that promises “ADA compliance in one line of code.” Don't.
The problems with overlays:
- They don't actually fix the underlying accessibility violations, they layer a UI on top of the broken markup.
- An overlay is a script that runs after your markup loads. It cannot supply the semantic information that was never in the markup, which is what assistive technology actually reads.
- Installing one does not put you inside any safe harbour, because for a private business there is no federal regulation defining one. A vendor promising compliance is promising something no regulator has defined for you.
- Screen-reader users report that overlays interfere with the assistive technology they have already configured. A tool that fights the user's own software makes the underlying experience worse while appearing to fix it.
The honest path is fixing the underlying markup. Slower and more work, but durably effective and legally defensible.
The practical compliance checklist
For a residential contractor website, the practical accessibility audit:
Images
- Every image with informational content has alt text.
- Decorative images marked with empty alt (alt="") so screen readers skip them.
- Logo alt text identifies the business.
- Project photos describe the type of work shown.
Forms
- Every input has a visible label associated via for/id or wrapping label tag.
- Required fields marked accessibly (not just visually).
- Error messages identify the field and the problem.
- Form submission produces clear success/error feedback accessible to screen readers.
Color contrast
- Body text contrast ratio at least 4.5:1 against background. That is success criterion 1.4.3 at Level AA, verbatim.
- Large-scale text at least 3:1. WCAG defines large-scale as at least 18 point, or 14 point bold.
- Interactive elements (buttons, links) clearly distinguishable from surrounding text.
Keyboard navigation
- All interactive elements reachable via Tab key.
- Visible focus indicators on focused elements.
- Skip-to-content link as the first focusable element.
- No keyboard traps where focus gets stuck.
Semantic structure
- Proper heading hierarchy (H1 → H2 → H3, not H1 → H4).
- Landmark roles (header, nav, main, footer) used.
- Lists marked up as actual list elements.
- Buttons used for buttons, links for links (not divs with onclick).
Media
- Videos have captions.
- Audio has transcripts.
- Auto-playing media can be paused.
The audit process
How to actually run the audit:
- Automated scan first. A browser accessibility extension or your build tool's accessibility audit will catch the machine-checkable failures: missing alt attributes, missing labels, insufficient contrast, bad heading order. It cannot tell you whether your alt text is meaningful or your focus order makes sense, which is why the manual steps below are not optional. Start here anyway; it is free and fast.
- Manual keyboard test. Tab through every page using only the keyboard. Confirm everything interactive is reachable and visible.
- Screen reader test. Run the screen reader built into your operating system, or a free one, over key pages. Confirm content reads logically.
- Color contrast check. Run a contrast checker on every text and background pair against the 4.5:1 and 3:1 thresholds above.
- Form test. Submit forms with errors, confirm error states are accessible.
- Document the audit. Maintain a record showing the date and scope of each audit. It will not make a claim go away, but a dated record of deliberate effort is a materially better position than nothing at all.
The accessibility statement
The cost-of-compliance math
Cost categories:
- Initial audit and remediation: $2,000 to $8,000 depending on site complexity, on the scoping ranges we use.
- Ongoing maintenance: a few hundred to a couple of thousand a year for periodic re-audits and remediation as content changes.
- Annual third-party manual audit, worth it for larger sites: comparable to the initial audit.
Those are our scoping assumptions, not market rates, and you should get quotes. The comparison that matters is not against a settlement figure somebody made up; it is that remediation is a known, bounded, one-time cost you control, and a demand letter is an unbounded one you don't.
The proactive accessibility menu (different from overlays)
A self-coded accessibility menu (font size adjustment, contrast toggles, motion reduction) on top of an underlying WCAG-compliant site is meaningfully different from a third-party overlay covering an inaccessible site. The first is a usability enhancement; the second is a legal-exposure-magnet. The Limitless site uses the former approach, the accessibility menu in the bottom-right corner is built on top of properly-structured markup.
4.5:1
The minimum contrast ratio WCAG 2.1 requires for body text at Level AA, with 3:1 for large-scale text of at least 18 point or 14 point bold. It is the single most commonly failed criterion on contractor websites and the cheapest one to fix.
Sources
- U.S. Department of Justice, guidance on web accessibility and the Americans with Disabilities Act, the source for title III applying to goods and services offered on the web, for businesses having flexibility in how they comply, and for the statement that the Department does not have a regulation setting out detailed standards.
- U.S. Department of Justice, 2024 rule on web and mobile app accessibility, which adopts WCAG 2.1 Level AA as the technical standard for state and local governments under title II, with compliance dates of 26 April 2027 and 26 April 2028 depending on population, and which does not apply to private businesses.
- Web Content Accessibility Guidelines 2.1, World Wide Web Consortium, the source for the four principles, the A, AA, and AAA conformance levels, and success criterion 1.4.3 requiring a contrast ratio of at least 4.5:1 for text and 3:1 for large-scale text of at least 18 point or 14 point bold.
Ready to talk numbers on your own pipeline?
On the strategy call, we'll lay out the plan we'd run for your business and talk through how it fits your market.
Final thought
Web accessibility is one of the most-overlooked legal exposures in the small-business world, and the discovery process against you is automated while your remediation is not. The path is simple in principle: build accessibly, audit regularly, document what you did, maintain an accessibility statement with a working contact route, and avoid third-party overlays. The technical fixes are achievable and they make the site better for every visitor, which is the part worth remembering when the legal framing gets tiresome.
This article is for informational purposes only and is not legal advice. For specific compliance questions about your business, consult qualified counsel.
Tagged