What ADA Means for Your Small Business Website

Most small-business websites in Parker, Lone Tree, and across the South Denver area have at least a few ADA accessibility problems. The owners usually don’t know it. It’s not a conscious choice to exclude anyone. Accessibility is simply not on the standard checklist when a site gets built, and most platforms don’t build it in automatically.

ADA Title III covers places of public accommodation. Courts and Department of Justice guidance have increasingly treated business websites the same way. That applies to a two-person dental office and a 15-seat restaurant the same as it does to a regional chain.

Here is what that actually means in practice.

What the ADA actually requires of a business website

ADA Title III requires that businesses not discriminate against people with disabilities in the access they provide to goods and services. The courts and DOJ guidance that apply this to websites point to WCAG 2.1 Level AA as the operative standard.

WCAG stands for Web Content Accessibility Guidelines, published by the World Wide Web Consortium. Level AA covers a specific set of requirements: text must meet minimum contrast ratios against its background, images must carry descriptive alt text, forms must have visible and correctly associated labels, every interactive element must be reachable and operable by keyboard alone, and focus states must be visible so a user can tell where they are on the page.

None of those requirements are unusual on their own. The difficulty is that they have to be met consistently across every page, every form, every image, every button. A site built on a template with default settings may pass some of them and quietly fail others. A site built on a tight timeline without accessibility review almost certainly fails several.

The standard is not aspirational. It is what courts apply when a complaint is filed.

What the actual exposure looks like

The realistic scenario for most small businesses is a demand letter, not a federal lawsuit.

Serial ADA web litigation works like this: an attorney represents plaintiffs who encounter barriers on websites while using assistive technology. The attorney identifies sites that fail basic accessibility checks, then sends demand letters stating specific barriers and giving a short window to respond. Some of these letters are filed as formal complaints in federal court from the start. Others arrive as pre-litigation demands.

Ignoring the letter, or responding with something that doesn’t resolve the underlying issue, tends to escalate. The cost of resolving a demand letter is meaningful. The cost of defending a case is considerably higher.

The risk is not limited to businesses near a courthouse in a large metro. About 46 percent of Google searches carry local intent, according to local SEO research in 2026. That search traffic includes users who rely on screen readers, keyboard navigation, or voice-control software. A site with barriers is not just a legal risk. It actively blocks a portion of the Centennial, Highlands Ranch, and Parker audience from finding the business, reading about its services, or getting in touch.

The two problems compound: the legal exposure is already there, and the business is losing potential customers at the same time.

What an accessibility audit actually finds

The most common issues on small-business sites are not exotic edge cases. They are the same categories that come up in audit after audit.

Missing or inadequate alt text. Images without alt attributes are invisible to screen readers. A hero image with no alt text, or with “image” as its alt text, tells a screen reader user nothing. The fix is a description that conveys what the image communicates, not just that an image exists.

Form fields without labels. A contact form where placeholder text inside the field is the only indication of what goes there fails WCAG. When the user clicks into the field, the placeholder disappears. A screen reader user has no way to know what to enter. The fix is a proper <label> element associated with each field, not placeholder text standing in for it.

Color contrast failures. Light gray text on a white background, or text overlaid on an image without sufficient contrast, fails WCAG’s minimum ratio requirement. This affects users with low vision and color-vision differences, not just users who are blind. It also affects anyone viewing the site on a phone screen in bright sunlight.

No keyboard navigation. A user who cannot use a mouse should be able to tab through every interactive element in a logical order. Navigation menus, dropdowns, modals, and forms all need to work without a mouse. Many sites break entirely at this point because the focus outline was set to outline: none to clean up the visual appearance. Removing the focus indicator removes the ability to navigate by keyboard.

Missing skip links. Keyboard and screen reader users should be able to skip past the header navigation on each page to reach the main content. Without a skip link, every page load requires tabbing through every navigation item before reaching anything on the page. On a site with an eight-item nav, that is eight tabs just to get started.

These are not advanced issues. They are the baseline. They are also what shows up in the bulk of demand letters filed against small-business websites.

Why an accessibility overlay is not the answer

Several products market themselves as single-line fixes: add a script tag to the site header, and the plugin handles accessibility automatically. They don’t, and this matters both practically and legally.

An overlay runs on top of the rendered page and tries to correct issues it detects in real time. The problem is that screen readers and keyboard navigation software interact with the underlying HTML, not the overlay’s corrected version. When the overlay misses an issue, or when its corrections conflict with the actual document structure, the experience for a user relying on assistive technology can get worse, not better.

Some overlay providers have been specifically named in ADA complaints, not as a defense but as part of the claim. The argument is straightforward: the site still had barriers, the overlay did not remove them, and the business cannot claim good-faith effort when what it purchased does not work for the people it was meant to help.

Building an accessible site from the start, or fixing the underlying HTML and CSS, is the difference between actually reducing the exposure and buying a label that says the work was done. The label shows up in the visual layer; the barriers remain in the code.

What this means if your site runs on a template or builder

Template-based sites and website builders handle accessibility inconsistently. Some have improved their default themes in recent years. Others ship templates with contrast failures built in, interactive elements that cannot be navigated by keyboard, and image components that encourage skipping alt text entirely.

The platform’s defaults are a starting point, not a standard. A site built on a platform that technically supports accessibility can still fail if the implementation choices made during build didn’t account for it. That includes font color choices, image handling, form field configuration, and navigation structure.

This is one reason web design for local businesses done well is different from a site built in an afternoon on a template. The WCAG requirements are not a theme setting. They’re a consequence of how the site is put together. VK is an AWS Certified Solutions Architect, and the sites built by Elements AI are tested against WCAG requirements, not just the platform’s defaults, because the platform’s defaults are not what courts apply when a complaint is filed.

If your current site was built on a platform or by someone who didn’t run accessibility testing, there’s a real chance the issues described in the signs your website is failing extend into accessibility territory you’re not aware of yet.

How accessibility and local search overlap

Accessible design and search-friendly design share more ground than most people expect.

Alt text that describes an image correctly is also the alt text a search crawler indexes. A heading structure that makes logical sense to a screen reader is also the structure that tells Google what a page is about. Form labels that work for keyboard users work better for everyone. The semantic HTML that underlies an accessible page is the same semantic HTML that AI search engines look for when deciding what to recommend.

LocalBusiness schema can add about a 14 percent lift to Google Business Profile click-through, according to schema research in 2026. The same intentionality that produces good schema markup is the same intentionality that produces accessible HTML. Both are a consequence of building the site deliberately, not just building it quickly.

A site that is genuinely accessible tends to perform better in search, load faster, and serve more of the audience that is already searching for the business. Slow websites have measurable costs in lost customers and lower rankings. An inaccessible site has costs that are harder to measure until they show up as a demand letter or as the portion of the local audience that quietly gave up and went somewhere else.

You can see how Elements AI approaches accessibility for this site on the accessibility statement page, which covers our current WCAG 2.1 AA conformance and how to report an issue.

Frequently asked questions

Does the ADA apply to my small business website?

In most cases, yes. ADA Title III covers places of public accommodation, and courts along with DOJ guidance increasingly treat business websites the same way. If your business serves the public, your website is likely covered regardless of business size.

What happens if my site is not ADA accessible?

The most common outcome is a demand letter, not a lawsuit. An attorney sends a letter identifying a specific barrier and a timeframe to fix it. Responding slowly or incorrectly can escalate to litigation. Resolving a demand letter costs far less than defending a case in court.

Does an accessibility overlay plugin fix the problem?

No. Overlay plugins add a widget that patches issues on the surface, but they do not change the underlying code a screen reader or keyboard user actually interacts with. Many accessibility experts consider overlays insufficient to meet WCAG 2.1 Level AA, and some have been named in complaints.

What is WCAG and what level does my site need to meet?

WCAG stands for Web Content Accessibility Guidelines, published by the World Wide Web Consortium. DOJ guidance references WCAG 2.1 Level AA as the standard for business websites. It covers contrast ratios, keyboard navigation, image alt text, form labels, and visible focus states.

How do I know if my site has accessibility problems?

Free automated tools like WAVE or Axe surface the most obvious issues: missing alt text, poor color contrast, unlabeled form fields. Automated checks are a useful starting point but miss many issues that only appear when a real user with assistive technology tries to navigate the page.

---

Most businesses that end up with a demand letter had no idea the gap existed. The issues were there from day one, in the alt text that was never written and the form labels that were never added, built in when the site was first published and never surfaced until someone who uses assistive technology tried to complete a task.

What makes it genuinely complicated is not the list of individual fixes. It’s knowing which ones apply to your site, understanding why an automated scan didn’t catch all of them, and telling the difference between a fix that actually closes the exposure and one that shifts the risk around without resolving it.

That gap between the surface and the underlying code is where the real work lives. If your site serves Parker, Lone Tree, Highlands Ranch, or anywhere across the South Denver metro and you haven’t had an actual accessibility review, the free 30-minute call is a low-cost way to find out where you actually stand before something more expensive arrives.