Do Garage Door Companies Get Sued Over Website Accessibility?

You got a demand letter, or a vendor called and told you your site is a lawsuit waiting to happen, or you just read something online and now you’re worried. This article is for a garage door company owner trying to figure out what is actually true: whether the ADA requires your website to meet a specific technical standard, what a real demand letter looks like, and what is worth fixing regardless of the legal question. We sell websites, not legal advice, so treat everything below as background, not a legal opinion. If a letter has actually arrived, that goes to a lawyer who handles ADA cases, not to us and not to your web guy.

The quick answer

There is no federal regulation that spells out a specific technical standard your garage door company’s website must meet under Title III of the ADA, the part of the law that covers private businesses. There is one that does that for state and local government websites, published in 2024, but it does not apply to you. What does apply to you is the general requirement that your business be accessible, and in practice, courts, plaintiffs’ firms, and demand letters treat WCAG 2.1 Level AA as the benchmark anyway. So the honest position is neither “you must be WCAG compliant by law” nor “this doesn’t apply to me.” It’s closer to: nobody can hand you a checklist and call it the law, but the checklist people actually use is real, and a chunk of it is worth doing on its own merits.

What the DOJ actually says

Start with the source instead of a vendor’s summary of it. The Department of Justice’s own web accessibility guidance states plainly that it “does not have a regulation setting out detailed standards” for how a public accommodation’s website has to comply with Title III (checked 2026-08-28). The same page says businesses and state and local governments “can currently choose how they will ensure that the programs, services, and goods they provide online are accessible to people with disabilities.” That is not a loophole we’re pointing you toward. It’s the actual current legal position, stated by the agency that enforces the ADA.

The same guidance names the Web Content Accessibility Guidelines, WCAG, as one existing technical standard that “provides helpful guidance” on how to make a site accessible. Helpful guidance is a specific choice of words. It’s not “the required standard.” Anyone telling you otherwise is speaking more confidently than the DOJ’s own page does.

Title II versus Title III, the distinction almost every vendor collapses

Here’s where the pitch usually goes wrong. In April 2024, DOJ did publish a codified rule requiring WCAG 2.1 Level AA conformance, with real compliance deadlines: April 26, 2027 for larger jurisdictions, April 26, 2028 for smaller ones (checked 2026-08-28). That rule is real, it’s specific, and it names a version and a level.

It applies to Title II. Title II covers state and local government: city websites, county services, public transit authorities, Amtrak. It does not cover a private garage door company. A vendor who cites this 2024 rule while pitching your business is either confused about which title it falls under or is hoping you won’t check. Either way, the rule they’re waving at you was written for city hall, not for you.

So why does everyone cite WCAG 2.1 AA anyway

Because in practice, de facto and required end up looking similar even though they are not the same thing. Without a codified Title III standard, courts have needed something to point to when a website accessibility case actually gets litigated or settled, and WCAG 2.1 AA has become that reference point by repeated use, not by statute. Demand letters cite it because it’s specific and it’s what shows up in settlement agreements. Plaintiffs’ firms cite it because judges have accepted it as a reasonable measure of accessibility in past cases.

Both halves of that sentence matter equally. WCAG 2.1 AA is the practical benchmark everyone in this space uses. It is also not a law Congress or DOJ wrote requiring your specific business to hit it. Treat it as the standard worth aiming for on the merits, and stop treating “it’s not codified for Title III” as either an excuse to ignore accessibility or as proof nobody could ever come after you over it.

Your actual risk profile as a service-area contractor

Here’s the part that’s genuinely reassuring, and also the part vendors have the least incentive to tell you: your site’s shape matters. A garage door company’s site is a marketing and lead-capture site. No shopping cart, no account login, no online checkout, no stored payment methods. The demand-letter and lawsuit activity that dominates this space concentrates heavily on e-commerce, where a blind or low-vision customer is trying to complete a purchase and physically cannot. That’s a materially different fact pattern than a homeowner trying to find your phone number and read your service area.

That does not mean zero risk. Any public-facing business website is technically within reach of Title III. A form field with no label, a phone number buried in an image with no alt text, navigation that only works with a mouse: those are real accessibility failures regardless of what your site sells, and a determined firm sending template letters doesn’t necessarily check your business type before mailing one. Lower exposure than an online store is a fair, accurate thing to say. Lower is not the same as immune.

The demand-letter numbers, and why we’re not repeating them as fact

You’ll run into specific figures in this space: a certain number of demand letters sent last year, a year-over-year percentage jump in web-accessibility lawsuits, a share of cases aimed at e-commerce specifically. Those numbers get quoted constantly in accessibility-vendor marketing and law-firm client alerts, and directionally they’re probably not wrong: letters are real, and the volume has trended up for years. But we went looking for a primary source, a government tally or an audited report, and did not find one behind the numbers commonly repeated online. They trace back to industry surveys compiled by accessibility vendors and law firms with an obvious interest in the answer.

So we’re not going to hand you a specific count and act like it’s settled. What we can tell you with a straight face, sourced to DOJ and W3C directly: letters and suits happen, the WCAG 2.1 AA benchmark is what most of them reference, and e-commerce is where plaintiffs’ firms have concentrated their attention. If a vendor quotes you an exact number with no citation attached, that’s worth noticing.

Six things worth doing regardless of the legal question

Set the lawsuit question aside for a second, because a chunk of accessibility work is just good practice for a service-area contractor site, whether or not a letter ever arrives. These six are cheap, they help real people using your site, and none of them require a monthly subscription to fix:

• Readable contrast. Light gray text on a white background looks clean in a mockup and is genuinely hard to read in a sunny driveway, not just for someone with low vision. If you can’t read your own site squinting on your phone outside at noon, neither can a customer.
• Alt text on photos. Every real photo of your trucks, crew, and finished installs should have a short text description behind it. It’s how a screen reader user knows what’s there, and it’s a page or two of work, not a redesign.
• Labeled form fields. Every input on your quote form needs a real label a screen reader can announce, not just placeholder text that vanishes once someone starts typing. If your site runs an online booking or estimate request tool for scheduling, the fields inside that tool need the same treatment. That’s a Lead Engine feature, our sister brand that handles the booking and follow-up side of things, and their guide to online booking and estimate appointments walks through what a usable scheduling flow looks like if you’re running one.
• Keyboard-reachable navigation. Someone who can’t use a mouse should be able to tab through your menu, your forms, and your phone link and reach everything a mouse user can. Test it yourself: unplug the mouse for five minutes and tab through your own homepage.
• Real text instead of text baked into images. A phone number or address rendered as a picture is invisible to a screen reader and to Google. Type it as actual text.
• Captions on any video. If you’ve got a truck-wrap promo video or a testimonial clip on the site, captions make it usable for someone who’s deaf or hard of hearing, and for the far larger group of people scrolling with the sound off.

None of these fix everything WCAG 2.1 AA covers. They’re the highest-value fraction of it for a site your size, and they’re the fraction a small shop can actually knock out in an afternoon or two with a developer, rather than a specialist audit.

Why an overlay widget is not the shortcut it looks like

This is the product every owner reaches for first, because it’s a script tag and a monthly fee instead of a project. accessiBe and UserWay are the two names you’ll hear most. Install a line of code, the widget adds an on-page menu for adjusting contrast, font size, and a few other display settings, and the pitch is that you’re now covered.

Here’s the mechanism problem, argued on how the thing actually works rather than on any legal claim about outcomes. An overlay sits on top of your page and tries to patch accessibility issues on the fly, in the visitor’s browser, after the page has already loaded with whatever problems it has. It does not go back and fix the missing alt text, the unlabeled form field, or the div that should have been a button, in your site’s actual code. For a sighted visitor adjusting contrast or font size, the widget genuinely helps. For someone using their own screen reader, the tool they already rely on and have configured for years, an overlay frequently gets in the way instead of fixing anything, because it’s a second layer of scripted behavior competing with assistive technology that expects to read clean, correctly structured code underneath. That’s the actual complaint accessibility practitioners have with this category of product, and it’s a complaint about mechanism, not a claim about anyone’s legal exposure.

If your site also runs a chat widget for lead capture, that’s a related case worth flagging while we’re on injected third-party scripts. A chat widget needs to be operable by keyboard and readable by a screen reader too, the same basics as everything else on the page. That’s also Lead Engine territory rather than ours; their guide on chat widgets and lead qualification is the place to look if you’re evaluating one.

The three real paths, compared honestly

Option	Published price	Best for	Where it gets hard
accessiBe / UserWay overlay widget	accessiBe: $59 to $479 per month by traffic tier (checked 2026-08-28). UserWay: not published on their pricing page as fetched (checked 2026-08-28); requires contacting sales.	A shop that wants something visible and live today, and mainly wants the display-adjustment features for sighted visitors.	Does not rewrite your underlying page code, so the specific problems a screen reader user hits (unlabeled forms, missing alt text, broken navigation) often remain. Ongoing subscription, not a one-time fix.
Manual WCAG 2.1 AA remediation	No single published price; a developer engagement, priced against your page count and current condition. Not invented here, and neither should it be guessed by whoever quotes you.	A shop that wants the actual underlying issues fixed, which holds up better if a letter ever does arrive.	Takes real time and costs more upfront than flipping on a widget. How long depends on how many pages and forms you have and how broken they currently are; get that timeline from whoever is doing the work rather than a rule of thumb.
Doing nothing	$0	A shop with a small, simple site that already handles contrast, labels, and photo alt text reasonably well, and has decided the residual risk is acceptable.	If real WCAG issues exist and go unaddressed, a letter, if one comes, arrives with none of the easy fixes already done, which is the worst version of this situation to be in.

What usually goes wrong

The most common mistake is panic-buying an overlay widget the same day the letter arrives, without reading the letter closely enough to know what it actually alleges. The second most common is the opposite: deciding the whole thing is a scam because a demand letter is often a template, and ignoring genuinely broken form fields and missing alt text that would help real customers regardless of any legal question. A distant third, but a real one: a well-meaning shop owner spends money on a full accessibility audit for a five-page marketing site that never needed one, when the six basics above would have covered most of the practical exposure at a fraction of the cost.

If a letter actually arrives

In order: don’t reply to it yourself, don’t call the sender, and don’t sign anything. Forward it to a lawyer who has handled ADA web accessibility matters specifically, not necessarily your general business attorney, since this has become enough of its own niche that experience matters. Do not install an overlay widget and consider the letter handled; it doesn’t change what the letter alleges about your actual page. Once you have a lawyer’s read on the specific claims, that’s the point where fixing the underlying issues on the site becomes a concrete, scoped project instead of a guess.

How to tell you got it right

You’ve got it right when the six basics above are actually true on your live site, not just on a punch list somewhere. Pull up your own homepage, tab through it with the mouse unplugged, and see if you can reach the phone number and the quote form. Check that your real photos have alt text and your form fields have labels a screen reader would announce. None of that requires a subscription or an audit to verify; it takes twenty minutes and your own attention. If you’ve never run a basic pass over your site for the fundamentals, our garage door company website checklist covers the broader set, and the same logic about substance over decoration that shows up there applies here too. The home service website design piece covers how this plays out across other trades, if you’re curious whether garage doors are unusual here. They generally aren’t.

Common questions

Is WCAG 2.1 AA legally required for my garage door company’s website?

Not by a codified federal regulation specific to Title III, as of the date at the top of this page. It is the standard most demand letters and settlements reference in practice, which is a different thing than a binding legal requirement, and both facts are true at once.

Does an accessibility overlay widget protect me from a lawsuit?

No product can promise that, and treating a widget as legal insurance misreads what it does. It adjusts display settings for sighted visitors; it does not rewrite your page’s underlying code, which is what a screen reader actually interacts with. Some plaintiffs’ firms and disability advocates have specifically criticized this category of product for exactly that gap.

My site has no shopping cart. Am I safe?

Meaningfully lower risk than an e-commerce site, based on where litigation and demand-letter activity have concentrated. Not zero risk, since Title III technically covers any public-facing business website. Lower and zero are different words for a reason.

Should I just do nothing until something happens?

For the six basics in this article, no. They cost little, they help real visitors using screen readers or navigating by keyboard today, and they leave you in a better position if anything ever does arrive. A full paid audit or remediation engagement before you have any specific reason to think you need one is a different question, and for most small service-area sites, not the first move.

What if I already got a letter?

Send it to a lawyer with ADA web accessibility experience before you do anything else, including before you talk to any vendor who calls you about it. This article, and any web company’s opinion including ours, is background, not the advice that letter actually needs answered.