Is Your Small Business Website ADA Compliant? What Raleigh Businesses Need to Know

Quick Answer

A small business website doesn’t get a legal pass on accessibility just because it’s small. There’s no formal deadline and no size exemption under the ADA, and the safest practical target is building your site to meet WCAG 2.1 Level AA, the standard courts and the Department of Justice point to when a website accessibility complaint comes up. The rest of this article covers what that actually looks like in practice.

Why This Matters Beyond “Doing the Right Thing”

Accessible design is good for every visitor, not just people using screen readers or keyboard navigation. But for a lot of Raleigh and Triangle business owners, the reason this topic lands on their desk isn’t a design conversation. It’s a letter.

Website accessibility lawsuits under ADA Title III have grown steadily, and the Department of Justice’s own guidance confirms that Title III’s requirement to provide “full and equal enjoyment” of goods and services extends to a business’s website, not just its physical location. There is no carve-out in the statute for a five-person shop compared to a national retailer.

That guidance also makes something else clear: private businesses don’t have a fixed compliance deadline the way state and local governments now do. That’s not a loophole. It means there’s no date a business can point to and say “we’re not required to fix this yet.”

What the Standard Actually Is

The ADA itself doesn’t name a specific technical standard for private business websites. In practice, the Web Content Accessibility Guidelines (WCAG), maintained by the W3C, are what courts, settlements, and web professionals treat as the working definition of “accessible.” WCAG 2.1 Level AA is the version most commonly referenced.

WCAG is organized around four principles, often shortened to POUR:

Principle	What it means in practice
Perceivable	Content can be seen or heard in more than one way — alt text for images, captions for video, real contrast between text and background
Operable	Every function works without a mouse — links, menus, and forms can be reached and used with a keyboard alone
Understandable	Navigation is consistent, error messages are clear, and forms tell you what went wrong and how to fix it
Robust	Code is clean enough that assistive technology like screen readers can interpret it correctly

None of this requires exotic technology. It requires a site that was built, or rebuilt, with these principles in mind from the start.

Where Small Business Sites Usually Fail

After looking at accessibility issues across small business websites, a handful of problems show up again and again:

• Missing or lazy alt text — blank alt attributes, or alt text that just repeats the filename instead of describing the image
• Low color contrast — light gray text on white backgrounds, or brand colors used for body copy where they fail contrast ratios
• Forms without labels — a contact form that looks fine visually but has no programmatic label tying each field to its input, which is invisible to a screen reader
• Keyboard traps — dropdown menus, popups, or booking widgets that can be opened with a mouse but never closed or navigated with a keyboard
• No visible focus state — tabbing through the page with a keyboard gives no visual indication of where you are

None of these are visible in a normal glance at the homepage. That’s exactly why they pile up on sites that were designed and approved by looking at them, not by testing how they behave.

A Practical First Pass

A full accessibility audit is a real project, but a business owner can get a useful first read in under an hour:

1. Unplug your mouse and try to reach your main navigation, a form, and your phone number using only the Tab and Enter keys.
2. Run your homepage through a free contrast checker on your body text and buttons.
3. Turn on your phone’s screen reader (VoiceOver on iOS, TalkBack on Android) and listen to how your homepage reads out loud.
4. Check that every image with real content — not decorative backgrounds — has alt text that describes what it shows.
5. Fill out your contact form and see if the browser tells you which field has an error, or just fails silently.

Anything that breaks in that test is worth fixing regardless of legal exposure, because a visitor who can’t complete those actions is a lead you never see in your analytics.

Where Accessibility Fits Into a Website Project

Accessibility works best as part of how a site is built, not a plugin bolted on afterward. Color palettes, font sizes, form structure, and navigation patterns all get decided during design and development — the same phase where a slow, hard-to-use site quietly costs a business customers. Fixing accessibility after launch usually means touching the same templates and components a good Website Design & Development process would have gotten right the first time.

If you’re planning a new website build for a Raleigh or Triangle business, raising accessibility requirements at the start costs far less than retrofitting them into a finished site.

The Bottom Line

Accessibility isn’t a checkbox you clear once. Standards evolve, content gets added, and new pages can reintroduce old problems. Treating WCAG 2.1 AA as an ongoing target, not a one-time fix, is what keeps a site both usable and defensible over time.