A business owner reviewing their website on a laptop screen showing accessibility testing results

Website Accessibility: What Small Businesses Need to Know in 2026

Max Jacobson Mar 19, 2026

Last year, over 5,000 ADA website accessibility lawsuits were filed in U.S. courts. Most of them targeted small and mid-sized businesses. And the typical settlement? Somewhere between $5,000 and $25,000 before you even factor in legal fees.

If you've been ignoring website accessibility because you thought it was only a problem for big corporations, this is the part where I tell you it's not.

But here's the thing: the legal risk is only part of the picture. Accessibility is about making your website work for everyone who visits it. Around 26% of American adults have some form of disability. That's roughly one in four people. If your site doesn't work for them, you're turning away customers and you probably don't even know it.

Let me break down what website accessibility actually means, what the law says, and what you can do about it without spending a fortune.

What Website Accessibility Actually Means

Website accessibility means building your site so that people with disabilities can use it. That includes people who are blind and use screen readers, people with motor impairments who can't use a mouse, people who are deaf and need captions on video content, and people with cognitive disabilities who need clear, simple layouts.

The technical standard everyone references is called WCAG, which stands for Web Content Accessibility Guidelines. The current version most courts and regulators point to is WCAG 2.1, Level AA. That's the benchmark.

WCAG is built around four principles. Your site needs to be:

  • Perceivable - Can people see or hear your content? (alt text on images, captions on videos, sufficient color contrast)
  • Operable - Can people navigate without a mouse? (keyboard navigation, no flashing content, clear focus indicators)
  • Understandable - Can people figure out how your site works? (readable text, predictable navigation, clear error messages)
  • Robust - Does your site work with assistive technology? (valid HTML, proper ARIA labels, semantic structure)

None of this is rocket science. Most of it is just building a website correctly in the first place.

The Legal Side: What the ADA Requires

The Americans with Disabilities Act was written in 1990, before the internet was a thing. But courts have consistently ruled that websites count as "places of public accommodation" under Title III. That means if you run a business that serves the public, your website needs to be accessible.

There's no official ADA standard for websites (the DOJ has been dragging its feet on formal rulemaking for years), but courts use WCAG 2.1 AA as the de facto standard. Starting April 24, 2026, public sector websites and apps must meet defined accessibility standards, and the private sector is watching closely.

The lawsuit numbers tell the story. Over 4,000 ADA website cases were filed in 2024. That number climbed to roughly 5,000 in 2025. Plaintiffs' attorneys have figured out that website accessibility violations are easy to find, easy to prove, and most businesses settle quickly.

Small businesses are targets because they're less likely to fight back in court. A plaintiff's attorney can run an automated scan on your site, find violations in minutes, and file a demand letter the same day.

I'm not saying this to scare you. I'm saying it because ignoring it is the most expensive option.

The Most Common Website Accessibility Problems

WebAIM's annual analysis of the top one million websites found that 95.9% fail basic WCAG compliance. The violations that show up most often are surprisingly simple to fix:

Missing alt text on images. Every image on your site needs descriptive alt text that explains what the image shows. Decorative images (like background patterns) get an empty alt attribute. This is the single most common violation, and it takes minutes to fix.

Low color contrast. If your text doesn't have enough contrast against the background, people with low vision can't read it. WCAG requires a contrast ratio of at least 4.5:1 for normal text. There are free tools that check this in seconds. Google "WebAIM contrast checker" and test your color combinations.

Missing form labels. If your contact form has input fields without proper labels, screen readers can't tell users what information goes where. Every input needs a <label> element connected to it.

Empty links and buttons. Links that just say "click here" or buttons with no text (like icon-only buttons without labels) are useless to screen reader users. Every interactive element needs a descriptive label.

Missing page language. Your HTML needs a lang attribute so screen readers know what language to use. One line of code. Takes five seconds.

No keyboard navigation. If someone can't tab through your site and use it without a mouse, you've got a problem. This usually happens when developers use <div> elements instead of proper <button> and <a> elements.

Quick Wins You Can Handle Today

You don't need to hire an accessibility consultant to get started. Here's where to begin:

  1. Run a free scan. Go to wave.webaim.org, plug in your URL, and see what it finds. It won't catch everything, but it'll catch the obvious stuff.
  2. Add alt text to every image. Go through your site page by page. If an image shows something relevant, describe it. If it's decorative, use alt="".
  3. Check your color contrast. Use the WebAIM contrast checker on your text and background colors. Fix anything below 4.5:1.
  4. Label your forms. Make sure every input field has a connected label. Your developer can do this in an hour or two.
  5. Test keyboard navigation. Open your site and try to use it with just the Tab key, Enter, and arrow keys. If you get stuck anywhere, that's a problem.
  6. Add a skip-to-content link. This lets keyboard users jump past your navigation menu to the main content. Standard practice, easy to implement.

These six items will fix the majority of common violations. They won't make your site perfectly accessible, but they'll put you ahead of 95% of websites out there.

The Business Case Beyond Lawsuits

Legal risk gets the headlines, but there's a business argument here that most people overlook.

That 26% of Americans with disabilities represents real purchasing power. Globally, people with disabilities and their families control an estimated $13 trillion in spending. If your website is hard to use for someone with a visual impairment, they're going to your competitor whose site works with their screen reader. And as we covered in our post on warning signs your website is losing customers, most business owners never realize it's happening.

There's also the SEO angle. Many accessibility best practices overlap directly with what Google rewards. Alt text helps Google understand your images. Semantic HTML helps Google understand your page structure. Fast, clean code (which accessibility encourages) improves your Core Web Vitals scores.

And then there's the demographic reality. Your customers are getting older. Baby boomers are in their 60s, 70s, and 80s. Vision loss, hearing loss, and motor impairments increase with age. Building an accessible website isn't just the right thing to do today. It's preparing for your customer base tomorrow.

What About Those Accessibility Overlay Widgets?

You've probably seen those little accessibility icons that float in the corner of websites. Products like accessiBe, UserWay, and AudioEye promise to make your site accessible by adding a JavaScript widget. Click a button, pick your settings, done.

I'll be direct: these don't work the way they promise.

The National Federation of the Blind has publicly opposed overlay products. Over 800 accessibility professionals signed an open letter calling them "worse than doing nothing." Multiple lawsuits have been filed against companies using overlays, with courts ruling that the overlays didn't actually make the sites accessible.

The problems are fundamental. An overlay can't fix bad HTML structure. It can't add meaningful alt text to images (AI-generated descriptions are often wrong or useless). It can't restructure your navigation to be keyboard-friendly. And it can actually interfere with the assistive technology that disabled users already have.

If someone is pitching you a $50/month overlay widget as your accessibility solution, save your money. Fix the actual code instead.

The Tax Credit Most Small Businesses Don't Know About

If your business has fewer than 30 employees or less than $1 million in revenue, you may qualify for the Disabled Access Credit (IRS Form 8826). It covers 50% of eligible accessibility expenditures between $250 and $10,250, for a maximum credit of $5,000 per year.

That means if you spend $5,000 making your website accessible, you could get $2,375 back as a tax credit. Not a deduction. A credit, which is dollar-for-dollar off your tax bill.

Most small business owners have no idea this exists. Talk to your accountant about it before you start any accessibility work so you can document your expenses properly.

How Red Rock Approaches Website Accessibility

Full transparency: this is the part where I talk about what we do. Skip it if you want.

Every site we build at Red Rock is hand-coded from scratch. The code is ours, top to bottom: no WordPress, no templates, no page builders. That matters for accessibility because we control every line of HTML.

Our standard build includes semantic HTML structure, proper heading hierarchy, alt text on all images, labeled form fields, keyboard navigation, skip-to-content links, and sufficient color contrast. These aren't add-ons. They're part of how we build sites.

Our maintenance plans ($150/month, everything included) cover ongoing accessibility monitoring. When standards update or new issues surface, we fix them as part of your plan.

When we're not the right fit: If you already have a WordPress site with hundreds of pages, we're probably not going to rebuild the whole thing. In that case, you'd want an accessibility specialist who works within WordPress. We can point you in the right direction.

If you're building a new site or replacing one that's giving you problems, reach out and let's talk about it.

Frequently Asked Questions

Is my small business website legally required to be accessible?

If your business is open to the public (which includes most businesses with a website), courts have consistently ruled that the ADA applies to your website. There's no formal exemption for small businesses. The practical risk depends on your industry and visibility, but the legal exposure is real. Over 5,000 lawsuits were filed in 2025 alone, and many targeted businesses with fewer than 50 employees.

How much does it cost to make a website accessible?

It depends on the current state of your site. If you have a clean, well-built site with a few violations, fixing them might take a developer 5-10 hours. If your site was built with a page builder and has deep structural problems, it could cost significantly more. Professional accessibility audits typically start around $3,000-$5,000, but you can catch most common issues yourself using free tools like WAVE. And don't forget the Disabled Access Credit, which can offset up to $5,000 of your costs.

Can I just add an accessibility widget to my site and be compliant?

No. Overlay widgets like accessiBe and UserWay have been widely criticized by the accessibility community, and courts have ruled that they don't satisfy ADA requirements. The National Federation of the Blind has specifically opposed them. These tools can't fix structural HTML problems, can't add accurate alt text, and sometimes interfere with actual assistive technology. Fix the underlying code instead.

What's WCAG, and which version do I need to follow?

WCAG stands for Web Content Accessibility Guidelines, published by the W3C (the organization that sets web standards). WCAG 2.1 Level AA is the version most courts and regulators reference as the standard for ADA compliance. It covers things like color contrast ratios, keyboard navigation, alt text, form labels, and video captions. You can read the full guidelines at w3.org/WAI/WCAG21/quickref, but the quick wins I listed above cover the most common violations.

How do I test my website for accessibility issues?

Start with WAVE, a free tool from WebAIM. Plug in your URL and it'll flag common violations with explanations of what's wrong and how to fix it. For a more thorough check, try navigating your entire site using only your keyboard (Tab, Enter, arrow keys). If you get stuck or can't tell where you are on the page, that's a real problem. Google Lighthouse (built into Chrome DevTools) also includes an accessibility score. None of these tools catch everything, but together they'll surface the issues that matter most.

Your website should work for everyone who visits it. That's good business, good ethics, and increasingly, it's what the law requires. If you're not sure where your site stands, run a free scan and start with the quick wins. And if you want a site built right from the start, let's talk.