Website accessibility is not a nice-to-have. It is a legal requirement, a business obligation, and a practical way to make sure every visitor can use your site. For small businesses, the risk is not theoretical. ADA lawsuits over inaccessible websites are filed every day, and they target small companies as often as large ones.

The short answer

WCAG 2.2 AA is the standard most accessibility laws point to. It means your site works with a keyboard, has text alternatives for images, uses sufficient color contrast, labels every form field, and lets users skip to main content. The most common failures are missing alt text, low contrast, no keyboard navigation, unlabeled forms, and no skip link. You can catch most of these with three free tests: keyboard-only navigation, a screen reader pass, and a contrast checker.

What WCAG 2.2 AA means

WCAG stands for Web Content Accessibility Guidelines. Version 2.2 is the current standard, published in October 2023. The "AA" level is the middle tier and the one most laws reference, including the ADA and Section 508.

WCAG is organized around four principles. Content must be:

  • Perceivable: Users can see or hear it. Images need alt text, videos need captions, content needs sufficient contrast.
  • Operable: Users can navigate it. Keyboard access, no keyboard traps, enough time to read content.
  • Understandable: Users can comprehend it. Clear language, predictable navigation, error prevention on forms.
  • Robust: It works with assistive technology. Proper HTML, ARIA where needed, compatible with screen readers.

You do not need to memorize all 86 success criteria. You need to fix the ones that fail most often.

The criteria that matter most for small businesses

If you focus on the handful of criteria that fail most often on small business sites, you cover the majority of real-world risk:

  • 1.1.1 Non-text Content — every image has alt text (or empty alt if decorative). This is the single most cited failure in ADA lawsuits.
  • 1.4.3 Contrast (Minimum) — text meets 4.5:1 contrast against its background. Light gray on white is the usual offender.
  • 1.4.11 Non-text Contrast — form borders, focus indicators, and icons need 3:1 contrast against adjacent colors. Most sites miss this one entirely.
  • 2.1.1 Keyboard — every interactive element works with a keyboard. No mouse required.
  • 2.1.2 No Keyboard Trap — focus can move in and out of any component without getting stuck.
  • 2.4.1 Bypass Blocks — a skip link or landmark lets keyboard users jump past repeated navigation.
  • 2.4.7 Focus Visible — the focused element has a visible focus indicator. Removing outline without a replacement is a failure.
  • 3.3.2 Labels or Instructions — every form field has a programmatic label, not just a placeholder.
  • 4.1.3 Status Messages — success and error messages are announced to assistive technology without moving focus.

These nine criteria are where most small business sites break. Fix them first and you have addressed the bulk of what plaintiffs' attorneys scan for.

The most common accessibility failures

1. Missing alt text

Every image that conveys information needs an alt attribute that describes what the image shows. Decorative images should have empty alt text (alt="") so screen readers skip them.

The failure: images with no alt attribute at all, or alt text that says "image" or "photo" or the filename. That tells a screen reader user nothing.

The fix: write alt text that describes the content and function of the image. "Team meeting at Durand office" is good alt text. "IMG_4821.jpg" is not.

2. Low color contrast

Text needs enough contrast against its background to be readable. WCAG 2.2 AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (18pt or 14pt bold).

The failure: light gray text on a white background, or colored text that looks fine to someone with full color vision but is invisible to someone with color blindness.

The fix: use a contrast checker (WebAIM's is free and browser-based). Test every text and background combination. If the ratio is below 4.5:1, darken the text or lighten the background.

3. No keyboard navigation

Not everyone uses a mouse. Some users navigate with a keyboard alone (Tab, Shift+Tab, Enter, Space). Every interactive element (links, buttons, form fields) must be reachable and operable with a keyboard.

The failure: custom JavaScript widgets that trap focus, links that only work on click, dropdown menus that do not open with keyboard, and no visible focus indicator (the outline that shows which element is selected).

The fix: tab through your site without touching the mouse. If you get stuck, that is a keyboard trap. If you cannot tell which element is focused, the focus indicator is missing or removed.

4. Unlabeled form fields

Every form input needs a label. Not a placeholder. A placeholder disappears the moment you start typing, and screen readers often do not announce placeholders at all.

The failure: forms that use placeholders instead of labels, or labels that are not programmatically connected to their inputs.

The fix: use a <label> element with a for attribute that matches the input's id. Every field should have a visible, persistent label.

5. Missing skip link

A skip link is a hidden link at the top of the page that lets keyboard users jump directly to the main content. Without it, a keyboard user has to tab through your entire header and navigation on every page.

The failure: no skip link, or a skip link that is not visible when focused.

The fix: add a "Skip to main content" link as the first element in the body. It should be visually hidden until focused, then appear when a keyboard user tabs to it.

A before and after: fixing color contrast

Here is the kind of fix I make on almost every small business site I audit. A site has a contact button styled like this:

Before:

<a href="/contact/" style="color: #999; background: #fff;">
  Contact Us
</a>

That gray on white has a contrast ratio of about 2.85:1. It fails 1.4.3 (minimum is 4.5:1). It looks fine to the designer, but it is unreadable for anyone with low vision or in bright ambient light, and it is one of the first things an automated scanner flags.

After:

<a href="/contact/" style="color: #4a4a4a; background: #fff;">
  Contact Us
</a>

#4a4a4a on white is roughly 9.2:1. It passes AAA. The change is a single hex value, it still looks clean, and it resolves a criteria failure that shows up in every audit tool. This is the kind of fix that takes five minutes and eliminates a real legal exposure.

The legal risk

ADA Title III applies to websites. Courts have ruled repeatedly that websites are places of public accommodation. You do not need to be a Fortune 500 company to get sued. Plaintiffs' firms file hundreds of these lawsuits per year, many against small businesses, restaurants, and local services.

A typical ADA web accessibility lawsuit costs between $5,000 and $25,000 to settle, plus your own legal fees. The cost of fixing the accessibility issues is almost always lower than the cost of a single settlement.

According to the 2023 UsableNet ADA Digital Lawsuit Report, over 4,500 ADA web accessibility lawsuits were filed in federal court in 2023, and the majority targeted small and mid-size businesses. Plaintiffs' firms use automated scanners to find sites with contrast and alt text failures, then file in bulk. You do not need to be a target on purpose. You just need to be on the list of sites that fail a scan.

How accessibility helps your SEO

Accessibility and SEO overlap more than most people realize. Search engines read your site the way a screen reader does: they rely on structure, not visual design. When you fix accessibility issues, you usually improve your search rankings at the same time.

  • Semantic HTML helps both. Using <nav>, <main>, <article>, and <button> instead of generic <div> tags gives screen readers and crawlers the same context. A <div onclick> is invisible to a screen reader and ambiguous to Google.
  • Heading structure matters. A single <h1> followed by <h2> and <h3> in order helps screen reader users navigate and helps Google understand your content hierarchy. Skipped levels or multiple <h1> tags confuse both.
  • Alt text is indexable. Image alt text is how Google understands what an image shows. Good alt text improves image search traffic and reinforces the page's topic.
  • Fast, keyboard-friendly pages tend to rank better. Core Web Vitals reward the same lean, well-structured markup that accessibility demands.

If you need a reason to prioritize accessibility beyond the legal one, the SEO upside is real and measurable.

How to test your site

You do not need expensive tools. Three free tests catch most problems:

  1. Keyboard-only test: Unplug your mouse. Try to navigate your site using only Tab, Shift+Tab, Enter, Space, and arrow keys. If you get stuck or cannot reach something, that is a failure.
  2. Screen reader test: Install NVDA (free, Windows) or VoiceOver (built into macOS). Close your eyes and try to use your site. If you cannot tell what is on the page or what each element does, your screen reader users cannot either.
  3. Contrast checker: Run your site through WebAIM's Contrast Checker or the WAVE accessibility extension. It flags every contrast failure automatically.

For a broader audit, use the WAVE browser extension. It scans a page and reports structural issues, missing labels, alt text problems, and contrast failures in one pass.

The tools I actually use

  • axe DevTools — a browser extension (Chrome, Firefox, Edge) that runs the same axe engine used in automated CI testing. It flags violations by WCAG criteria number, tells you which element failed, and suggests the fix. This is the first tool I run on any audit.
  • WAVE — WebAIM's accessibility evaluation tool. Available as a web form and a browser extension. It gives you a visual overlay of errors, contrast failures, and structural issues directly on the page. Good for a quick pass on a single page.
  • Lighthouse accessibility audit — built into Chrome DevTools under the Lighthouse tab. It runs axe under the hood and scores the page 0-100. The score is not the point, but the list of failed checks is useful, and it packages accessibility alongside performance and SEO so you see the overlap.

Run axe DevTools and WAVE on every page. They will not catch everything (no automated tool catches more than about 30-40% of issues), but they catch the mechanical failures that get sites sued.

When to get help

The basics (alt text, contrast, labels, skip links) you can fix yourself if you are comfortable editing content. Structural issues (keyboard traps, ARIA implementation, custom widgets) usually need a developer.

I help small businesses make their sites accessible and compliant. If you want an audit or remediation work, check my website accessibility service or reach out directly.

The bottom line

Accessibility is not about checking a box. It is about making sure every person who visits your site can actually use it. The legal risk is real, but the bigger reason is simpler: if someone cannot use your site, they cannot be your customer. Run the three free tests, fix what you find, and you will have handled the majority of accessibility problems on most small business sites.