If you run a small business in Philadelphia and you’ve heard about ADA website lawsuits, or worse, you’ve already received a demand letter, you’re not alone. Accessibility litigation targeting business websites has become one of the fastest-growing legal risks for small and mid-sized companies, and Pennsylvania has real, documented filing activity in federal court. This page walks through what the law actually requires, who’s getting targeted, and what an honest fix looks like, without the scare tactics or the overlay-widget sales pitch.
What ADA Website Compliance Actually Means in 2026
The Americans with Disabilities Act was written before the modern web existed, so there’s no single line in the statute that says “your website must do X.” Title III of the ADA covers “places of public accommodation,” and for years courts have argued over whether a website counts. Increasingly, federal courts, including courts that hear Pennsylvania cases, are ruling that it does, especially when a business has a physical location, sells products online, or offers services through its site.
Separately, the Department of Justice has issued a rule requiring WCAG 2.1 AA compliance for state and local government websites under Title II. That rule is specific to government entities, not private businesses. But here’s the part that trips up a lot of business owners: even though there’s no codified federal regulation forcing private companies to meet WCAG 2.1 AA, courts and settlement agreements already treat it as the de facto standard in private lawsuits. Plaintiffs’ attorneys cite WCAG 2.1 AA success criteria in demand letters and complaints, and businesses that fall short end up settling or defending against exactly those citations. In practice, the standard applies to you whether or not a law technically requires it yet.
Why Lawsuit Volume Is Rising, and What It Looks Like in Pennsylvania
Website accessibility litigation has grown steadily for several years, and a relatively small number of law firms and serial plaintiffs file a large share of the cases nationwide. Pennsylvania, including the Eastern District that covers Philadelphia, has real, ongoing filing volume, so this isn’t a coastal or big-city-only problem happening somewhere else.
The typical pattern looks like this: a firm runs an automated accessibility scan against thousands of small business sites, flags common WCAG failures, and sends a demand letter citing specific violations, missing alt text, unlabeled form fields, poor color contrast, along with a settlement offer to avoid a federal lawsuit. Some firms skip the letter entirely and file directly. Either way, the letters and complaints are rarely random. They point to specific, checkable problems on your site, which means specific, checkable problems are also how you defend against them.
Which Philadelphia Businesses Are Most at Risk
Not every business faces the same exposure. Three categories show up disproportionately in accessibility litigation:
- E-commerce and retail sites. Online checkout flows, product image galleries, and filtering tools are packed with the exact elements, forms, images, interactive controls, that fail accessibility audits most often.
- Restaurants. PDF menus, embedded reservation widgets, and third-party delivery integrations are frequently inaccessible to screen readers, and many restaurant sites are built quickly with heavy image use and little attention to alt text.
- Template and DIY-built sites. Sites thrown together fast on a page builder, without anyone checking contrast ratios, heading structure, or keyboard navigation, tend to accumulate the same handful of WCAG failures that show up on every automated scan.
If any of that describes your site, it’s worth reading through our guide on signs your Philadelphia website needs a redesign, since accessibility gaps often show up alongside other structural problems that are worth fixing at the same time.
Why Overlay Widgets Don’t Provide Real Legal Protection
A lot of business owners get pitched a one-line JavaScript overlay that promises instant ADA compliance for a monthly fee. These widgets sit on top of your existing site and try to patch accessibility problems on the fly, adjusting contrast, adding a menu of display options, sometimes claiming to auto-generate alt text with AI.
The problem is that overlays don’t fix the underlying code. Screen readers and other assistive technology often interact poorly with them, and in some documented cases, the overlay itself interferes with a user’s existing accessibility software, making the site harder to use than if nothing had been installed at all. Plaintiffs’ firms have caught on to this too. Because overlay widgets are a recognizable, easily identifiable product, some firms specifically target sites that use them, treating the widget as evidence that a business knew it had a problem and chose the cheapest possible patch instead of an actual fix. Real compliance happens in the site’s code, structure, and content, not in a bolt-on script.
A Practical WCAG 2.1 AA Self-Check
You don’t need to be a developer to spot the most common failures. Walk through these on your own site:
- Alt text. Every meaningful image should have a text description a screen reader can announce. Decorative images should be marked so they’re skipped.
- Color contrast. Text needs sufficient contrast against its background. Light gray text on a white button is a classic failure point.
- Keyboard navigation. Try tabbing through your entire site without touching a mouse. If you can’t reach the menu, forms, or checkout, neither can a keyboard-only user.
- Form labels. Every input field needs a programmatically associated label, not just placeholder text that disappears when someone starts typing.
- Video captions. Any video with spoken content needs accurate captions, not just an auto-generated transcript buried on another page.
Finding one or two issues doesn’t mean you’re facing a lawsuit tomorrow. Finding several, especially on your product pages, checkout flow, or contact forms, means it’s time for a proper audit rather than a guess.
What a Real Remediation Plan Costs vs. a Lawsuit Settlement
Every remediation project is different depending on how the site was built and how many pages, templates, and third-party tools are involved. A site built on a modern, well-structured platform might need a focused round of fixes to markup, alt text, contrast, and form labeling. An older or heavily templated site may need a deeper rebuild of specific components, like a checkout flow or a reservation widget, before it can pass a real audit.
What matters is the comparison: a professional remediation project is a one-time investment in an asset you keep. A lawsuit settlement is money spent to make a single case go away, with no guarantee the next demand letter doesn’t arrive six months later if the underlying site hasn’t actually changed. If you’re weighing that investment against a broader site rebuild anyway, our guide on how much a website costs in Philadelphia is a useful starting point for understanding where accessibility work fits into an overall project budget.
How Media Proper Builds and Audits for Accessibility
We don’t treat accessibility as an add-on service or a widget you install after launch. When we build a site through our Philadelphia web design and development process, accessibility considerations, semantic markup, proper heading structure, labeled forms, keyboard-navigable menus, are part of how the site gets built in the first place, not a punch list we get to later.
This matters even more for online stores, where checkout flows, product filters, and payment forms are exactly the components that show up most often in accessibility complaints. Our e-commerce web development work is built with those components in mind from the start, rather than retrofitted after a demand letter arrives. If you want a look at how we approach projects end to end, A Year of Building walks through our process and the kind of work we take on.
Next Steps: Request an Accessibility Audit Before a Demand Letter Arrives
The businesses that come out ahead on this issue aren’t the ones with the biggest legal budgets. They’re the ones who checked their site before a law firm did it for them. If you’ve read through the self-check above and found problems, or if you simply don’t know where your site stands, the right move is a real audit, not an automated scan and not an overlay subscription.
Reach out to Media Proper for an accessibility review of your Philadelphia business site. We’ll tell you plainly what’s actually a risk, what’s a minor fix, and what a real remediation plan looks like, before you’re staring at a demand letter instead of a checklist.