Web Accessibility Is a Legal Issue, Not Just a Design Choice

Most small business owners think of website accessibility — making sites usable by people with disabilities — as a feature you add if you want to be thoughtful or inclusive. That framing misses something important: accessibility is also a legal requirement in many circumstances, and lawsuits against small businesses for inaccessible websites have become increasingly common.

The Americans with Disabilities Act was passed in 1990, well before the commercial internet existed. But courts and the Department of Justice have consistently extended ADA protections to websites and digital services as these have become essential to participating in commerce and public life. If your website is the digital front door to your business, the argument goes, it needs to be as accessible as your physical front door.

The Legal Landscape: What the Law Actually Says

The ADA doesn’t include specific technical standards for websites — it’s principle-based, prohibiting discrimination against people with disabilities in places of public accommodation. Courts have interpreted websites as places of public accommodation, which means ADA applies. The technical standard that courts and regulators point to is the Web Content Accessibility Guidelines, commonly abbreviated WCAG, published by the World Wide Web Consortium.

WCAG 2.1 Level AA is the current de facto compliance target. In April 2024, the DOJ issued a final rule formally requiring state and local government websites to meet WCAG 2.1 AA. While this rule directly applies to government entities, it sets a clear standard that courts use when evaluating private sector ADA claims as well.

Section 508 of the Rehabilitation Act applies to federal agencies and organizations that receive federal funding — if your business has government contracts or receives certain types of federal grants, Section 508 applies directly to you. Many state governments have their own accessibility statutes that can apply to businesses in their jurisdictions.

The Rise of Small Business Accessibility Lawsuits

This isn’t theoretical. Web accessibility lawsuits have been filed against businesses of every size, including small businesses, restaurants, and local service providers. Many of these lawsuits are filed by plaintiffs’ attorneys who use automated tools to scan websites for accessibility violations, then send demand letters or file suits in bulk.

The demand letters typically offer to settle for a few thousand dollars plus a commitment to fix the issues — which sounds manageable until you realize the alternative is federal litigation. The businesses most commonly targeted are those with enough web presence to be found but not large enough to have legal teams watching for these issues.

The best defense is a website that genuinely meets accessibility standards — not because you’re trying to avoid lawsuits, but because it’s the right thing to do and it happens to also protect you legally. A website with documented accessibility improvements and good-faith compliance efforts is in a much stronger position than one that has never been reviewed.

What Web Accessibility Actually Means in Practice

WCAG 2.1 AA is organized around four core principles: perceivable, operable, understandable, and robust. In plain terms, these translate to a set of concrete requirements that aren’t as daunting as they might sound.

Images need descriptive alternative text so screen readers can convey what’s shown to visually impaired users. Video content needs captions for deaf or hard-of-hearing users. Your website needs to be fully navigable using only a keyboard, for users who can’t use a mouse. Text needs sufficient color contrast — a minimum ratio of 4.5:1 for normal text — so it’s readable by people with low vision or color blindness. Form fields need visible labels, not just placeholder text that disappears when you start typing. Error messages need to be clear and specific. And your site should work correctly with common assistive technologies like screen readers.

None of these requirements are technically exotic. They’re mostly things that any well-built website should do anyway, for the simple reason that they make the site clearer and easier to use for everyone — not just people with disabilities.

How to Check Your Website’s Accessibility

Several free tools make it easy to run a basic accessibility audit. Google’s Lighthouse tool, built into Chrome’s developer tools, includes an accessibility audit that scores your site and lists specific violations. WAVE (Web Accessibility Evaluation Tool) from WebAIM is another widely-used free option that provides visual, in-browser feedback on accessibility issues. Both tools catch the most common issues: missing alt text, poor color contrast, form label problems, and keyboard navigation failures.

These automated tools are useful but not complete. They catch perhaps 30 to 40 percent of real accessibility issues — the rest require human review, particularly testing with actual screen reader software like NVDA (free) or JAWS. If accessibility compliance is important to your business — whether for legal reasons or because you serve a customer base that includes people with disabilities — investing in a professional accessibility audit periodically is worthwhile.

For ongoing monitoring, tools like accessiBe and UserWay offer automated remediation widgets that apply some accessibility fixes automatically. These are controversial in the accessibility community — they catch some issues but miss others, and they’ve been named in accessibility lawsuits. They’re not a substitute for building an accessible website, but they can help with specific, remediable issues while you work on a more comprehensive approach.

Building Accessibility In From the Start

Like most aspects of web compliance, accessibility is much easier to build into a website from the beginning than to retrofit after the fact. If you’re building a new site or doing a significant rebuild, making accessibility a requirement from day one adds relatively little cost and avoids significant rework later.

Practically speaking, this means choosing an accessible theme or page builder as your foundation, establishing color palette choices that meet contrast requirements, requiring alt text as part of your content workflow, and testing keyboard navigation as part of your QA process before launch. For WordPress sites, plugins like WP Accessibility Helper can assist with common issues. For any platform, the most important step is making sure the developers and designers you work with understand WCAG requirements and build to them.

Accessibility also connects directly to SEO. Many accessibility best practices — descriptive alt text, clear heading structure, logical page organization, fast load times — overlap with what Google rewards in search rankings. An accessible website is, in many respects, a better-optimized website. The business case goes in the same direction as the legal case and the ethical one.

If you’re not sure whether your website meets accessibility standards, Manson Bay Digital can help you find out and fix what needs fixing. We build websites for small businesses that are designed to work for every visitor — and to hold up to legal scrutiny. Reach out at mansonbaydigital.com/contact/ or call (509) 800-7735.