ADA Title III and Your Website: What Small Business Owners Actually Need to Know
You've probably heard that the ADA applies to websites. You may have also heard conflicting things about what that means for your business. Here's a practical read on the actual legal exposure and what triggers it.
If you’ve looked into website accessibility at all, you’ve probably encountered two very different messages. One says your website absolutely must be accessible or you’re at serious legal risk. The other says the whole thing is overblown and that a widget will take care of it.
Neither is quite right.
Here’s a practical read on what Title III of the Americans with Disabilities Act actually covers, what creates real legal exposure for a small service business, and what a measured response looks like.
What Title III Actually Says
The ADA was signed into law in 1990. Title III prohibits discrimination on the basis of disability in places of public accommodation, businesses and services that are open to the general public.
When the ADA passed, websites didn’t exist in any meaningful sense. The law does not explicitly mention them. But over the past fifteen years, federal courts across multiple circuits have consistently held that websites operated by businesses that serve the public are covered under Title III. The logic is straightforward: if a business offers goods or services to the public, those offerings cannot be structured in a way that discriminates against people with disabilities, including through a website that some people cannot use.
The Department of Justice formally codified this interpretation in a rule published in April 2024. For businesses covered by Title III, website accessibility is no longer a gray area. It’s a legal requirement, and WCAG 2.1 Level AA is the technical standard the rule references.
Who Has Actually Been Targeted
Small businesses do get demand letters and lawsuits under Title III. The caseload is not limited to large enterprises.
Healthcare providers, law firms, restaurants, service businesses, and retail operations have all received demand letters citing inaccessible websites. Some of those cases settle quickly. Others proceed to litigation. The costs (legal fees, settlements, remediation) range from a few thousand dollars to significantly more, depending on the complexity of the case and the business’s response.
A few important pieces of context, without sensationalizing: demand letters related to website accessibility number in the thousands per year in the United States. Many target businesses with no prior awareness of the issue. The legal exposure is not theoretical, but it’s also not a certainty for every business, and the appropriate response is measured action, not panic.
The businesses with the highest exposure tend to share a common profile: they have websites with significant functionality (booking, forms, e-commerce, contact), they serve the general public, and their sites have identifiable, remediable barriers. That profile fits a large percentage of service businesses.
What Actually Creates Legal Exposure
The accessibility barriers that appear most frequently in demand letters and litigation are not obscure. They are common issues that appear on a large number of small business websites.
Missing or inadequate alt text on images. Screen readers, assistive technology used by people who are blind or have low vision, rely on alt text to describe images. An image with no alt text, or alt text that says “image123.jpg,” provides no information to a screen reader user. When that image is functional (a button, a logo with meaning, a product photo) the missing description creates a real barrier.
Inaccessible forms. Contact forms, booking widgets, and inquiry forms are critical for service businesses. If form fields are not properly labeled, if error messages don’t clearly indicate what went wrong, or if the form cannot be completed using only a keyboard, a significant portion of users with disabilities cannot complete a core business action.
Keyboard navigation failures. Not every user can operate a mouse. Users with certain motor disabilities navigate entirely by keyboard. A website that traps focus in a dropdown, opens a modal with no way to close it via keyboard, or loses the visual focus indicator makes those users unable to navigate the site at all.
Color contrast failures. Text that doesn’t have sufficient contrast against its background is difficult or impossible to read for users with low vision or color blindness. WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal text. Many service business websites, particularly those with light gray text or branded color combinations chosen for aesthetics, fail this standard.
Videos without captions. Any video with meaningful spoken content needs accurate captions. Auto-generated captions from YouTube or social platforms are frequently inaccurate and do not meet the standard.
These are not edge cases. They are common baseline issues that a competent audit will identify and that a competent developer can fix.
The EU Picture Is Expanding the Scope
For U.S. businesses with any presence in European markets, clients in EU countries, services delivered internationally, or products sold online to European buyers, the European Accessibility Act is now in force.
The EAA, which began enforcement in June 2025, applies to digital products and services offered in EU markets, including websites. The technical standard it references is also WCAG 2.1 AA. This means that businesses serving both U.S. and EU customers are now dealing with overlapping requirements from two separate regulatory frameworks.
Building to WCAG 2.1 AA satisfies both simultaneously. Businesses that operate internationally have a stronger case for prioritizing accessibility than they may have had several years ago.
What Does Not Protect You
Accessibility overlays, the widget-based tools marketed under names like AccessiBe, UserWay, and similar, do not establish compliance and do not stop demand letters.
This is not a controversial opinion. The National Federation of the Blind, the American Council of the Blind, and multiple courts and legal analyses have reached consistent conclusions about overlay tools: they cannot automatically fix the underlying code-level barriers that create legal exposure. A widget that applies a surface-level transformation to a page does not alter the underlying HTML, ARIA attributes, or DOM structure that assistive technology actually interacts with.
Demand letters and complaints have been filed against businesses running overlays. Installing one has not demonstrated, in practice, that it functions as a legal defense. For businesses that have been sold an overlay as a compliance solution, a real audit is the only way to understand what barriers actually exist.
The Practical Response
The goal isn’t to generate anxiety. It is to give you an accurate picture of the situation so you can make a decision.
For most small service businesses, the appropriate starting point is an audit. Not a compliance certification. Not a remediation project costed at tens of thousands of dollars. An audit that tells you specifically what barriers your website has, which ones create the most significant exposure, and what order of operations makes sense for addressing them.
Some barriers take hours to fix. Others require developer involvement and more time. Knowing what you’re dealing with is the prerequisite for deciding what to do about it. The COREaccess™ Accessibility Leadership System covers the full framework — audit, remediate, train, and monitor — for organizations that need documented, standards-based conformance.
COREaccess™ is built around exactly that starting point, not manufacturing urgency, but identifying what’s actually present and building a clear path to address it. If you’re not sure whether your website has barriers that could create legal exposure, a 15-minute conversation is a reasonable place to start.