Website Accessibility: The Legal Requirement Most Small Businesses Ignore
I'm going to be honest about something uncomfortable: most small business websites I audit fail basic accessibility standards. Not because the owners don't care, but because nobody told them it mattered.
Here's why it matters now more than ever: ADA-related website lawsuits increased 300% between 2018 and 2025. Small businesses aren't exempt. And beyond the legal risk, roughly 26% of American adults have some form of disability. That's a quarter of your potential customers who might not be able to use your website.
The good news? Fixing the most common accessibility issues takes hours, not weeks. And the fixes almost always improve your site for everyone.
What "Website Accessibility" Actually Means
Website accessibility means people with disabilities can perceive, understand, navigate, and interact with your website. This includes people who are:
- Blind or visually impaired — using screen readers that read page content aloud
- Deaf or hard of hearing — needing captions for video and audio content
- Motor impaired — navigating with keyboard only, voice commands, or specialized devices
- Cognitively impaired — needing clear language, consistent navigation, and predictable layouts
The standard everyone references is WCAG 2.1 (Web Content Accessibility Guidelines), maintained by the W3C. It has three levels: A (minimum), AA (recommended for most sites), and AAA (highest). Most legal requirements and best practices target Level AA.
The 5 Most Common Accessibility Failures
After auditing over 100 small business websites, these are the issues I find on nearly every one:
1. Missing Alt Text on Images
The problem: Screen readers can't describe images without alt text. A blind user visiting your site hears "image" or nothing — completely losing the visual context.
The fix: Add descriptive alt text to every meaningful image. Not "IMG_2847.jpg" — describe what the image shows and why it matters.
- Bad:
alt="photo" - Bad:
alt="image of our team" - Good:
alt="Five team members collaborating around a whiteboard in our Orlando office" - Decorative images:
alt=""(empty alt, not missing alt)
Time to fix: 1-2 hours for most sites.
2. Poor Color Contrast
The problem: Light gray text on white backgrounds, or colored text on colored backgrounds, is unreadable for people with low vision — and honestly, it annoys everyone over 40.
The fix: Ensure a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text (18px+ or 14px bold).
Free tool: WebAIM Contrast Checker (webaim.org/resources/contrastchecker). Enter your text and background colors — it tells you instantly if you pass.
Common offenders: Placeholder text in forms (usually too light), footer links, "muted" text, light blue links on white.
3. No Keyboard Navigation
The problem: Many users can't use a mouse. If your site can't be fully operated with Tab, Enter, and arrow keys, those users are locked out.
The test: Put your mouse away. Try to navigate your entire site using only your keyboard. Can you reach every link, button, and form field? Can you see which element is currently focused?
Common failures:
- Dropdown menus that only open on hover
- Custom buttons that aren't real <button> elements
- No visible focus indicator (the outline you see when tabbing through elements)
- Modal dialogs that trap focus or can't be closed with Escape
The fix: Use semantic HTML elements (<button>, <a>, <input>) instead of styled <div> elements. Never remove :focus outlines without providing an alternative.
4. Missing Form Labels
The problem: Screen readers announce form fields by their labels. Without proper <label> elements, a user hears "edit text" instead of "Email address."
The fix: Every form input needs a <label> with a matching for attribute. Placeholder text is NOT a label — placeholders disappear when you start typing.
5. No Skip Navigation Link
The problem: Keyboard users have to Tab through your entire navigation menu on every single page before reaching the main content.
The fix: Add a "Skip to main content" link as the first focusable element on your page. It's invisible until focused, then jumps the user directly to the main content area.
The Legal Side: What ADA Actually Requires
The Americans with Disabilities Act doesn't specifically mention websites. But court rulings since 2017 have consistently interpreted ADA Title III (public accommodations) to include websites, especially for businesses that also have physical locations.
Key legal facts: - There is no "minimum size" exemption. Small businesses have been sued. - Most lawsuits settle for $5,000-$25,000 plus attorney fees. - Having a conformance statement ("we're working on it") provides some legal protection. - WCAG 2.1 Level AA is the most commonly referenced standard in settlements.
My honest take: The legal risk is real but not the main reason to care. Making your site accessible expands your audience and almost always improves SEO, user experience, and conversion rates for everyone.
How to Audit Your Site in 30 Minutes
You don't need an expert for a basic audit. Here's my quick process:
- Run WAVE (wave.webaim.org) — paste your URL and review the errors
- Run Lighthouse — in Chrome DevTools, run an Accessibility audit (aim for 90+)
- Keyboard test — navigate your entire site using only Tab and Enter
- Zoom test — zoom to 200% in your browser. Does the layout still work?
- Check color contrast — use the WebAIM Contrast Checker on your main text colors
What you'll likely find: Missing alt text, some contrast failures, and possibly keyboard navigation issues. These are all fixable in a day.
Frequently Asked Questions
Do I need to make my website 100% WCAG compliant?
Aim for Level AA compliance on your main pages (home, about, contact, key service/product pages). Perfect AAA compliance across every page is unrealistic for most businesses. Focus on the highest-impact issues first.
Will accessibility improvements affect my site's design?
Rarely in a negative way. Better contrast makes text easier to read. Proper heading structure improves scanability. Keyboard navigation is invisible to mouse users. Most accessibility fixes make your site better for everyone.
Can I get sued even if my site is partially accessible?
Technically yes, but demonstrating good-faith efforts significantly reduces risk. Having an accessibility statement, actively fixing issues, and showing progress goes a long way — both legally and ethically.
Does accessibility help SEO?
Absolutely. Alt text helps Google understand images. Semantic HTML improves crawlability. Heading hierarchy helps content structure. Accessibility and SEO share many of the same best practices — fixing one often fixes the other.
Start Here, Today
Don't try to fix everything at once. Here's your priority order:
- Add alt text to all images (biggest impact, easiest fix)
- Fix color contrast on your main text and links
- Add an accessibility statement to your footer (shows good faith)
- Test keyboard navigation and fix any trapped focus issues
- Run WAVE monthly and fix new issues as they appear
Accessibility isn't a one-time project — it's an ongoing practice. But the first pass? That's an afternoon's work that makes your site better for everyone.
Discussion
4 commentsThis scared me into running WAVE on my site immediately. Found 47 errors across 12 pages — almost all missing alt text and contrast issues. Took me about 3 hours to fix everything. Why doesn't anyone teach this in basic web design courses?
47 errors sounds alarming but honestly that's pretty typical — and the fact that you fixed them in 3 hours proves my point that this isn't as overwhelming as people think. Most web design courses focus on making things look good, not making them work for everyone. The industry is slowly catching up, but for now it's on us to educate ourselves. The good news is you're now ahead of roughly 90% of small business sites. — Marcus Reed, High5Expert
I'm a developer and I want to push back slightly on the 'use semantic HTML' advice. Sometimes clients insist on custom-designed buttons that require divs with click handlers. Is there a middle ground?
There's absolutely a middle ground, and it's simpler than most developers think. You can make any element keyboard-accessible with `role='button'`, `tabindex='0'`, and a keydown handler for Enter/Space. But honestly? A styled `<button>` element with CSS is almost always easier than retrofitting a div. The real issue is usually that designers don't know buttons can be styled to look like anything. Show them a `<button>` that looks identical to their mockup and the argument usually ends. — Marcus Reed, High5Expert
We got a demand letter last month about our restaurant website not being accessible. Settled for $8,000 plus remediation costs. This article would have saved us a lot of money and stress if we'd read it six months ago. Please keep writing about this topic — small businesses need to hear it.
I'm sorry that happened, Sandra. $8K is unfortunately on the lower end of what I've seen — some settle for much more. The silver lining is that once you've remediated, you're in a much better position, and the investment in accessibility genuinely improves the experience for all your customers. If you want a quick sanity check on the remediation work, run WAVE again and make sure it comes back clean. And yes, I'll definitely be writing more about this. — Marcus Reed, High5Expert
Does this apply to mobile apps too, or just websites? My business has both and I'm trying to figure out where to focus first.
ADA applies to both, but the legal landscape is clearer for websites right now. I'd prioritize your website first since that's where most lawsuits target, and many of the same principles (contrast, labels, touch targets) apply to mobile apps too. If you're using a framework like React Native or Flutter, there are built-in accessibility APIs that make compliance easier than you might expect. Start with the web, then apply the same thinking to the app. — Marcus Reed, High5Expert