Website Accessibility for Texas Small Businesses: What WCAG Asks For, in Plain English, Before a Demand Letter Asks First

A Letter Arrives

Website accessibility rarely makes a small business owner's to-do list until a letter arrives. A law firm, often from out of state, says your website is not usable by blind visitors and violates the Americans with Disabilities Act. It suggests a settlement. You had not thought about your site's accessibility since launch day, if then.

This article is not legal advice. If you receive a demand letter or a lawsuit, call an attorney before you call anyone else, including us. What follows is the practical side: what the accessibility standard asks for, why small businesses end up receiving these letters, and what to fix so your site works for every customer who visits.

Why This Keeps Happening

Title III of the ADA covers places of public accommodation, which includes most businesses open to the public. The law dates from 1990, before business websites existed, and it does not spell out a technical standard for them. Courts have reached different conclusions about when and how it applies online. The Department of Justice has said businesses open to the public should make their websites accessible, and it points to the Web Content Accessibility Guidelines (WCAG) as helpful guidance.

That ambiguity creates a market. Automated scanners can find common errors on thousands of sites in an afternoon. Missing image descriptions and unlabeled form fields are easy to detect and common on small business sites. A letter costs little to send. Settling often looks cheaper than fighting. So the letters go out.

The cynical summary: you were not singled out. You were found by software. The useful summary: the same errors that attract letters also turn away real customers.

WCAG in Plain English

WCAG is published by the World Wide Web Consortium, the body that sets web standards. Most businesses aim for version 2.1 or 2.2 at the "AA" level. The guidelines run long, but they rest on four ideas, abbreviated POUR:

• Perceivable. People can take in the content whatever their senses. Images have text descriptions. Videos have captions. Text contrasts enough with its background to read.
• Operable. People can use the site without a mouse. Every button, menu, and form works from the keyboard, and nothing traps the cursor.
• Understandable. Pages behave predictably. Form errors explain what went wrong. Language is clear.
• Robust. The code is clean enough that screen readers and other assistive technology interpret it correctly.

The Usual Suspects on Small Business Sites

Most small business sites stumble in the same handful of places.

1. Images without alt text. A screen reader announces "image" or reads a file name like "IMG_4471.jpg." Write a short description of what matters in the photo. Purely decorative images get an empty alt attribute so they are skipped.
2. Low-contrast text. Light gray on white looks elegant in a design review and unreadable on a phone in the sun. WCAG sets a minimum contrast ratio of 4.5 to 1 for normal body text.
3. Unlabeled form fields. Placeholder text that vanishes when you type is not a label. Every field needs a real label assistive technology can read.
4. Keyboard traps and invisible focus. Tab through your site. If you cannot see where you are, or you get stuck in a pop-up, so does every keyboard user.
5. Links that say nothing. Five links that all say "Click here" make no sense when a screen reader lists them out of context.
6. Missing captions. Video testimonials and explainer clips need captions. Auto-generated ones need a human pass.
7. Headings used for decoration. Headings should outline the page in order, not choose a font size. Screen reader users navigate by them.
8. Menus and forms as image PDFs. A scanned PDF is a picture of text. Nobody using a screen reader can read a photo of your menu, a common problem for restaurants.

About Those One-Line Widgets

You will be offered an accessibility overlay: a script that adds a toolbar to your site and promises compliance for a monthly fee. The pitch is appealing. Paste one line of code, stop worrying.

The mechanism explains the limits. An overlay runs on top of your existing code and tries to patch problems as the page loads. It cannot write a meaningful description of a photo of your crew. It cannot rebuild a form that was built wrong. Many people who rely on screen readers already have their own tools configured and find overlays get in the way. Fixing the underlying code is the durable answer. Ask your attorney before treating any product as a legal shield.

A Practical Order of Operations

You do not need perfection by Friday. You need a plan and visible progress.

1. Run a free automated check. Tools built into modern browsers flag missing labels, contrast failures, and empty links. Automated checks catch only part of the problem, but it is the easiest part.
2. Test with a keyboard. Put the mouse in a drawer and try to request a quote. It takes ten minutes and teaches more than any report.
3. Try a screen reader. Phones and computers ship with one built in. Listen to your homepage. It is humbling.
4. Fix the money paths first. Contact forms, booking, checkout, phone links, and the pages your ads point to.
5. Publish an accessibility statement. Say what standard you aim for, what you are working on, and how someone can reach you if they hit a barrier. Ours lives on our accessibility page.
6. Build it into the process. Every new page, photo, and form gets checked before it goes live. Accessibility added at the end costs more than accessibility designed in.

Why It Pays, Lawsuits Aside

Accessible sites tend to be better sites. Clear labels reduce form abandonment, the same ground conversion optimization covers. Good contrast helps everyone squinting at a phone outside a job site. Clean heading structure helps search engines understand the page, which is why accessibility work overlaps with technical SEO. Captions help the many people who watch video with the sound off.

And some of your customers have a disability. A veteran with a service-connected vision impairment. A retiree with arthritis who struggles with tiny tap targets. A parent holding a toddler in one arm and a phone in the other. They have money, and they will spend it with someone whose site works.

Where We Come In

We build sites with accessibility designed in from the first wireframe: semantic code, labeled forms, keyboard support, and contrast that passes. That is how our web design process works by default. If your current site has problems, a website redesign or a targeted website maintenance plan can fix them in order of importance. The free website grader gives a quick read on speed and basic site health.

Medical and dental practices have extra reason to care, since patients book and fill out forms online. Our medical practice marketing guide covers the rest of that picture.

Frequently Asked Questions

Does the ADA apply to small business websites in Texas?

It may, depending on the facts, and only an attorney can tell you how it applies to your business. Title III of the ADA covers businesses open to the public, and the Department of Justice has said those businesses should make their websites accessible. Courts have reached different conclusions about websites, which is why demand letters are common and outcomes vary.

What should I do if I get an ADA website demand letter?

Contact an attorney before responding, paying, or making public statements. A lawyer can assess the claim and your options. Separately, document the accessibility work you have done and plan to do, and start fixing the most important barriers, such as forms, navigation, and missing image descriptions, so customers with disabilities can use your site.

Will an accessibility overlay plugin make my website ADA compliant?

An overlay alone is unlikely to fix the underlying problems. Overlays run on top of existing code and cannot write meaningful image descriptions or rebuild broken forms, and many screen reader users prefer their own tools. Fixing the site's code is the durable approach, and an attorney can advise you on legal risk.

What WCAG level should a small business website meet?

Most businesses aim for WCAG 2.1 or 2.2 at the AA level, the level most commonly referenced in accessibility guidance. AA covers the important basics, including text alternatives, keyboard access, color contrast, form labels, and captions. Reaching it is practical for a typical small business site, especially when it is designed in from the start.

Want to know where your site stands before a letter tells you? We will check your forms, navigation, and key pages for common accessibility barriers and send a free written plan you keep whether or not you hire us. Request your free plan or call (210) 346-0848.