Website Accessibility for Small Businesses: Practical ADA Basics

Website accessibility is one of those topics small business owners hear about mostly through fear — usually a story about a demand letter from a law firm over a website a blind visitor couldn't use. The fear isn't baseless: accessibility lawsuits and demand letters overwhelmingly target small companies, not the Fortune 500. But fear is a bad teacher, because it makes accessibility sound like a legal tax instead of what it mostly is: a set of fixable website-quality problems that also lock out real customers.

Roughly speaking, accessibility means people with disabilities — vision, hearing, motor, cognitive — can actually use your site: read it with a screen reader, navigate it by keyboard, distinguish its text, complete its forms. Most small business sites fail at this not by intent but by default, through the same half-dozen errors repeated on nearly every page.

This guide covers the practical basics: what the legal exposure really looks like, the six fixes that address the vast majority of violations, how to test your own site for free, and why the "one-click compliance" widgets are a trap. One caveat up front: this is practical marketing guidance, not legal advice — for an actual dispute, talk to an attorney.

Why Website Accessibility Matters Beyond Lawsuits

Accessibility is a market-size issue before it's a compliance issue: a meaningful share of your potential customers has some disability affecting how they use the web — aging eyes that can't read gray-on-white text, hands that navigate by keyboard, screen readers that speak pages aloud. A site that fails them doesn't offend them; it simply loses them to the competitor whose site works, without either of you knowing.

The overlap with everything else you want from a website is nearly total. The practices that make a site accessible — real text instead of text baked into images, descriptive headings in logical order, labeled forms, sufficient contrast, alt text on images — are the same practices that help search engines parse your pages and help every visitor on a sunlit phone screen. Accessibility work is website-quality work wearing a different name, which is why it pairs naturally with SEO rather than competing with it for budget.

And yes, the legal exposure is real, which is worth understanding calmly rather than through a demand letter's framing — so here's the landscape.

The Legal Landscape in Plain English

The Americans with Disabilities Act's Title III covers businesses open to the public, and courts have widely treated websites as part of that public accommodation — with no small business exemption. In practice, plaintiffs' firms reference WCAG (the Web Content Accessibility Guidelines, version 2.1 level AA) as the de facto standard, even though no federal rule formally mandates it for private businesses.

The volume is not theoretical: thousands of website accessibility lawsuits are filed in federal and state courts each year — federal web accessibility suits rose about 27% in 2025 to over three thousand — and the demand letters that precede or replace lawsuits are estimated in the tens of thousands annually, typically settling around five thousand dollars. Most digital accessibility actions target companies under $25 million in revenue; small, visible, local businesses with obviously non-compliant sites are the easy cases, which is exactly why they're chosen.

Two clarifications keep this in proportion. First, the Department of Justice's recent accessibility rule with hard deadlines (2027–2028) applies to state and local governments — Title II — not to private businesses; your exposure comes from litigation trends, not a new statute. Second, the practical goal for a small business isn't certified perfection; it's eliminating the obvious, scanner-detectable failures that make you a target, and showing a genuine, ongoing effort — which happens to be the same work that makes the site better for everyone.

The Six Fixes That Cover Most Violations

Accessibility scans of millions of pages find the same handful of errors behind roughly 96% of detected failures. Fix these six and you've addressed the bulk of both your risk and your real-world usability problems.

Low-contrast text — the most common failure by far, found on more than four in five pages: light gray body text, white text over busy photos, brand colors that fail arithmetic. Contrast is measurable (4.5:1 for normal text under WCAG AA); free checkers tell you instantly whether your palette passes. Missing alt text — over half of pages: every meaningful image needs a short written description a screen reader can speak ("technician replacing HVAC condenser coil," not "IMG_4032"), while purely decorative images should be marked so screen readers skip them. Unlabeled form fields — also over half of pages: placeholder text that vanishes when typing begins is not a label; every field needs a real one, or a screen reader user meets a row of anonymous boxes standing between them and contacting you.

Empty links and buttons — icon links and image buttons with no accessible name, so assistive tech announces "link" with no clue where it goes. Missing document language — a one-line site setting that tells screen readers how to pronounce your pages. Keyboard navigation — the structural one: every menu, form, and button must be reachable and operable by Tab and Enter alone, with a visible focus indicator showing where you are. Most website platforms handle this until a fancy menu or popup breaks it — which is why you test.

Testing Your Site in an Afternoon, Free

You can find most of your accessibility problems yourself, with free tools and one slightly humbling exercise. Do four checks.

Run an automated scanner — the WAVE browser extension or the Lighthouse audit built into Chrome — on your five most important pages: home, services, contact, and your top-traffic pages from analytics. These catch the measurable failures (contrast, alt text, labels, empty links) and point to the exact elements. Automated tools catch only a portion of real-world barriers, but that portion includes nearly everything demand letters cite.

Then unplug your mouse and navigate the site by keyboard alone: Tab through the header, open the menu, reach every page, complete the contact form, submit it. Anywhere you get stuck or lose track of where you are, a motor-impaired visitor is stuck too. Next, try a screen reader for fifteen minutes — VoiceOver is already on every Mac and iPhone, Narrator on Windows, NVDA free to download — and listen to your homepage. Hearing your site read aloud makes abstract errors uncomfortably concrete. Finally, view the site at strong zoom and on a phone in bright light; text and tap targets that fail there fail accessibility arithmetic too.

Log what you find, fix in order of traffic and severity, and re-scan. For a typical small business site on a mainstream platform, the first pass is days of work, not months.

The Overlay Widget Trap

There's a category of product that promises one-line-of-code compliance — an accessibility widget or "overlay" that adds a toolbar and claims to fix your site automatically. The pitch is exactly what a busy owner wants to hear, and the record says the opposite: overlays don't repair the underlying code, many actively interfere with the screen readers and keyboard workflows real users rely on, and hundreds of businesses running overlays have been sued anyway — some suits now cite the overlay itself as a barrier. Disability advocates have been blunt on the subject, and plaintiff firms treat an overlay badge less as a shield than as a signal.

The honest version of "quick" is the six fixes above: they're real repairs, most are content-level changes an owner or webmaster can make in a mainstream platform without engineering, and they reduce the actual thing lawsuits cite. Money budgeted for an overlay subscription is better spent on an afternoon of fixes and, where needed, a professional audit of the genuinely technical items like focus management in custom menus and popups.

Making Accessibility Stick

Accessibility decays without habits, because every new page, post, and plugin can reintroduce old errors. Three light-weight practices keep a site clean after the first cleanup.

Bake it into content workflow: alt text written when images are uploaded, headings used in order (one h1, h2s for sections) rather than styled text, link text that says where it goes ("see our pricing," never "click here"), and new colors checked for contrast before they ship. Re-scan quarterly and after any redesign, new template, or new form tool — redesigns are where accessibility regressions concentrate, which is one more reason accessibility requirements belong in the project brief, as we've argued about website redesigns generally. And put a short accessibility statement on the site with a contact path for barriers — it's genuinely useful to visitors, and it documents the ongoing good-faith effort that matters if a complaint ever arrives.

When to bring in help: an e-commerce checkout, a booking system, custom interactive features, or an actual demand letter are all past the DIY line — a professional audit against WCAG 2.1 AA with a remediation list, or an accessibility-literate web development partner, is the right tool there. For most small business sites, though, the honest summary is encouraging: the majority of what's wrong is a finite list of unglamorous fixes, most of them content-level, all of them improvements your human visitors feel too.