In late 2025, a small flower shop owner received a demand letter alleging her website was not accessible to visitors using screen readers. She had assumed her web developer had handled it. She had not confirmed it. The dispute closed with more than seven thousand dollars in legal fees and settlement costs, for a problem she did not know existed until the letter arrived. Similar letters are now landing in inboxes across Texas at a pace that surprises most business owners, most of whom have never heard the term WCAG before their first warning.
The Legal Reality Behind Website Accessibility
The Americans with Disabilities Act was written in 1990, long before commercial websites existed, but federal courts have consistently applied its public accommodation requirements to the websites of
businesses that serve the public. There is no small business exemption. Recent industry research found that the majority of companies sued over website accessibility had annual revenue well below twenty five million dollars, meaning this is not a large-enterprise problem that smaller Texas businesses can safely set aside.
Federal filings related to website accessibility rose again in the most recent reporting year, and the pattern that plaintiff firms follow is fairly consistent. Automated scanning tools flag common barriers
such as missing alt text, poor color contrast, unlabeled form fields, and keyboard navigation failures, then a demand letter arrives asking for a settlement, typically in the range of several thousand to tens of
thousands of dollars, well before any lawsuit is filed. Most businesses settle because contesting the claim in court costs more than paying it.
There is no single federal regulation that spells out exactly what a private business website must do to comply. Instead, courts and settlement agreements consistently point to the Web Content Accessibility Guidelines, known as WCAG, at what is called Level AA, as the practical benchmark. The Department of Justice has applied this same standard to government websites on a phased timeline, and while that rule does not directly bind private businesses, courts treat it as a clear signal of where the legal expectation is heading.
What WCAG Level AA Actually Requires
WCAG organizes its requirements around four principles, often summarized as POUR: content must be perceivable, operable, understandable, and robust. In practical terms for a small business website, this covers a handful of concrete items that a development team can act on directly.
Alt text on meaningful images helps screen reader users understand what an image conveys, not just that an image exists on the page. Sufficient color contrast between text and its background matters because text that reads fine to someone with strong vision can be unreadable to someone with even mild vision impairment. Full keyboard navigation means every interactive element on a page, menus, forms, buttons, can be reached and used without a mouse. Descriptive form labels let a person using assistive technology understand what each field on a contact or quote request form is actually asking for. Predictable, consistent navigation across the site prevents a new page or design change from silently breaking the experience for someone relying on a familiar pattern.
None of these are exotic requirements. Most are addressable through disciplined web design and development practices rather than specialized tools, which is part of why courts have been unsympathetic to businesses that claim accessibility was too technical to address.
Why Accessibility Overlay Widgets Are Not a Real Fix
A significant share of small businesses that have already been sued had installed a one-click accessibility overlay widget beforehand, the kind of plugin that promises instant compliance for a small monthly fee.
Regulators have taken a dim view of these tools. The Federal Trade Commission fined one major overlay vendor a million dollars in 2025 for misrepresenting its product as a guaranteed compliance solution.
Disability advocacy groups have been even more direct, stating publicly that these widgets often make the experience worse for screen reader users rather than better, since they layer a script on top of code
that remains broken underneath.
Courts and plaintiff attorneys are aware of this pattern too. A website with an overlay installed is not treated as evidence of compliance in litigation, and in a meaningful share of recent cases the presence
of an overlay was noted as a sign the business had been warned about accessibility and chosen a shortcut instead of a fix. Real protection comes from addressing the underlying code, not from a widget
layered on top of it.
Building a Defensible Compliance Position
Texas business owners do not need to become accessibility experts to meaningfully reduce their legal exposure. A defensible position generally includes four elements. First, a genuine WCAG 2.1 or 2.2 Level
AA audit performed by someone who reviews the actual code and site experience, not just an automated scanner report, since automated tools catch only a portion of real barriers. Second, documented remediation of what the audit finds, prioritized by severity. Third, a published accessibility statement that names a contact method for anyone who encounters a barrier, which signals good faith even though it will not by itself stop a determined plaintiff's attorney. Fourth, a plan for ongoing monitoring, since a theme update, a new plugin, or a content change made months after the audit can quietly reintroduce the exact problems that were already fixed once.
Documentation matters more than most business owners expect. When a demand letter does arrive, having audit records, remediation tickets, and training logs on hand has been shown to meaningfully reduce settlement demands, because it demonstrates the business was acting in good faith rather than ignoring a known risk.
The Overlap With SEO and Site Performance
Accessible code and search-friendly code share more overlap than most business owners realize. Descriptive alt text that helps a screen reader user also helps search engines understand image content. Clean heading structure that helps someone navigating by keyboard also helps search engines understand page hierarchy. An SEO services program built on a genuinely accessible foundation tends to perform better in both rankings and usability audits, because many of the same technical disciplines drive both outcomes. Businesses that treat accessibility purely as a legal chore miss this connection and often end up doing the remediation work twice, once for compliance and once for search performance, instead of once for both goals at the same time.
What an Audit Actually Involves
A real accessibility audit combines automated scanning with manual testing, and the manual portion is where most of the value comes from. Automated tools are useful for catching the most obvious issues
quickly and cheaply, things like missing alt attributes or contrast ratios that fall below the required threshold, but they typically surface well under half of actual WCAG violations. Barriers like whether a form's error messages are announced correctly to a screen reader, or whether a dropdown menu traps keyboard focus in a way that prevents someone from continuing past it, require a person actually
navigating the site the way an assistive technology user would.
A useful audit report does more than list problems. It ranks them by how many users a barrier affects and how central that part of the site is to daily use, which gives a business owner a realistic, sequenced path toward compliance rather than an overwhelming list with no clear starting point.
Where to Start
For a Texas business that has never had its website reviewed for accessibility, the starting point is a real audit rather than a guess about where problems might be. From there, addressing the highest-impact
barriers first, typically navigation, forms, and core purchase or booking flows, closes most of the practical risk even before a full remediation plan is complete.
The businesses that come through this current wave of litigation without a costly settlement will not be the ones that got lucky. They will be the ones that treated accessibility as a standard part of running a
website rather than something to worry about only after a letter arrives.
Top comments (0)