Is Your Website ADA Compliant? What Las Vegas Small Businesses Need to Know

An ADA compliant website is one a person can use without a mouse, without sight, or without hearing, and the law expects yours to be one. The way most Las Vegas business owners find this out is a letter. It comes from a law firm you have never heard of, on behalf of a plaintiff who has never walked into your shop, and it says a screen reader could not get through your online menu or your booking form. It asks for a settlement and a promise to fix the site. That letter is a form letter, and thousands of them went out last year.

I'm a web designer, not a lawyer, so what follows is the practical side: what the courts have said, what the lawsuits point at, how to test your own site this afternoon, and what it costs to fix. If you get a demand letter, call an attorney. If you want to avoid one, keep reading.

Does the ADA apply to my website?

The Americans with Disabilities Act was signed in 1990, before most businesses had a website, so the statute never mentions one. Title III bans discrimination in "places of public accommodation," which covers restaurants, salons, clinics, gyms, retail stores, and most other businesses that serve the public. The question courts have argued over for a decade is whether a website counts as one of those places.

For Nevada, that argument is settled enough to plan around. Nevada is in the Ninth Circuit, and in Robles v. Domino's Pizza (2019) the Ninth Circuit held that the ADA applies to a website and app that connect customers to a physical business. Domino's argued that it was unfair to be sued when no regulation spelled out a technical standard. The court rejected that, and the Supreme Court declined to hear the appeal. If you have a storefront, an office, or a clinic in Las Vegas and a website that takes orders, bookings, or inquiries for it, you are inside that ruling.

Since there is no regulation for private websites, the yardstick everyone uses is WCAG. The Department of Justice's own web accessibility guidance points businesses to it, the DOJ's 2024 rule for state and local government websites adopts WCAG 2.1 Level AA outright, and settlement agreements name it. Build to WCAG 2.2 AA (the current version) and you are meeting the standard a court would reach for.

What do the website lawsuits look like?

Seyfarth Shaw, a law firm that tracks these cases, counted 3,117 website accessibility lawsuits filed in federal court in 2025, up from 2,452 in 2024. That count leaves out state court filings and the demand letters that settle before anyone files, so the true number is higher. Online stores draw the largest share, followed by restaurants, clinics, hotels, and service businesses. A national chain is a bigger prize, but a small business with a broken booking form settles faster, and plaintiff firms know it.

The pattern is consistent. A plaintiff who uses a screen reader visits the site, hits a barrier, and a firm files or sends a letter. The complaint lists the specific failures, and the list is almost always drawn from the same short set of errors. That set is worth knowing, because it is the same list you can check yourself.

What makes a website ADA compliant, in practice?

WCAG 2.2 has dozens of criteria, and a full audit walks through all of them. In the real world, a handful of failures do nearly all the damage. WebAIM, the accessibility research group at Utah State University, scans the top one million home pages every year. In the 2026 WebAIM Million report, 95.9% of home pages failed at least one WCAG 2 check, and six error types made up 96% of everything detected:

• Low-contrast text (83.9% of home pages). Light gray on white, thin text on a photo. If someone with reduced vision cannot read your hours, they cannot visit. WCAG AA requires a 4.5:1 contrast ratio for body text.
• Images without alt text (53.1%). A screen reader announces "image" and moves on. If your menu, your price list, or your "Book now" button is a picture with no description, it does not exist for that visitor.
• Form fields without labels (51%). A screen reader reads "edit text" for a field with no label. The user has no idea whether it wants a name, a phone number, or a date. This is the failure that shows up most in complaints about booking and contact forms.
• Empty links (46.3%). A link that contains only an icon or an image with no text. "Link" is all the user hears.
• Empty buttons (30.6%). Same problem, on buttons. The hamburger menu on a lot of template sites is an empty button.
• Missing page language (13.5%). A one-word attribute on the page's opening tag. Without it, a screen reader can pick the wrong voice and pronunciation for the whole page.

Every one of these is a line of code. None of them is a design decision that costs you anything visual. That is the part I want business owners to hear: the fixes that eliminate most of the legal exposure are mechanical, and a competent developer can do them in an afternoon.

How to check your website for accessibility in 15 minutes

You do not need a developer for a first pass. These four checks catch most of what a plaintiff's firm would list.

1. Put the mouse down. Open your home page and press Tab, over and over. You should see a visible outline move from link to link, in a sensible order. Try to open the menu, reach the phone number, and submit the contact form with Tab, Enter, and the arrow keys only. If you get stuck, or you lose track of where you are, that is a failure a keyboard or screen reader user hits every time.
2. Run WAVE. Go to wave.webaim.org, paste in your home page, then your contact page, then your menu or services page. Red icons are errors. Look for the six items above: contrast errors, missing alternative text, missing form labels, empty links, empty buttons, and missing language. The tool is free and takes ten seconds a page.
3. Zoom to 200%. Press Ctrl and plus (Cmd and plus on a Mac) until the browser says 200%. Text should reflow, nothing should overlap, and you should not have to scroll sideways to read a sentence.
4. Find the pictures of text. Menus, price lists, flyers, and event posters uploaded as images are invisible to a screen reader and cannot be zoomed cleanly. If the only place your prices live is inside a JPG, that is the first thing to change.

If you clear all four, you are ahead of most of the businesses on your street. If you fail two or more, keep reading and then send me the URL; a quick look is free.

Should you install an accessibility overlay widget?

You have seen the ads: paste one line of code, a little icon appears in the corner, and your site is "ADA compliant." The pitch is aimed at business owners who want the problem to go away for a subscription fee, and it does not deliver. An overlay is a script that sits on top of your page. It can enlarge text or change colors for a visitor who clicks its toolbar, but it does not add the alt text, labels, or button names that a screen reader needs. Those live in the code, and the code is unchanged.

In April 2025 the Federal Trade Commission finalized a $1 million order against accessiBe, the largest overlay vendor, for claiming its widget could make any website WCAG compliant. The order bars the company from making that claim without evidence. Plaintiff firms, for their part, treat the icon as a signal that the owner cares about compliance and has not done the work. Skip the widget and spend the money on the code.

What does it cost to fix?

Two different situations, two different answers.

You have a hand-coded site or a WordPress site you control. The six failures above are an afternoon of work for a developer who knows what to look for. Contrast is a color value. Alt text is a sentence per image, which you can write yourself. Form labels are one tag per field. Empty links and buttons need a name, and page language is one attribute. Budget a few hundred dollars for a cleanup pass and a WAVE report showing zero errors when it is done. Ask for that report; it is your evidence.

You have a template site from a page builder, an agency you can no longer reach, or a site older than five years. The problems are usually baked into the theme, and patching them one page at a time costs more than starting over. In that case the honest number is the price of a new site, which for most Las Vegas small businesses is far less than the agency quotes make it sound. If your site is also failing the tests in five signs your website is costing you customers, a rebuild solves both problems at once.

How I handle accessibility

Every site I build is coded to WCAG 2.2 Level AA from the first line, at the published flat price, with no "accessibility package" upsell. Real text instead of pictures of text, labeled forms, visible keyboard focus, 4.5:1 contrast checked against the actual colors, captions on video, and an accessibility statement page you can point to if anyone asks. I test with the same tools a plaintiff's expert would use (WAVE, axe, and a keyboard) before launch, and I hand over the report with the source files. My own accessibility statement lists the exact checks and the known gaps, because a page that claims perfection is the first thing an expert witness picks apart.

Accessible code has a side benefit worth naming: the same alt text, headings, and labels that help a screen reader are what Google and the AI search engines read to understand your page. Accessibility and what makes a website good in 2026 are mostly the same list. The sites on my work page were built that way, and none of their owners has had to think about this article.