Lake Wylie Web Co.WEB CO.
Writing / What WCAG compliance means for a small business website

What WCAG compliance means for a small business website

WCAG is the rulebook for accessible websites. Here is what it actually requires, why it matters for a small business, and what an ADA lawsuit risk looks like in practical terms.


If you have heard the term WCAG in the context of websites and assumed it was a concern for large corporations, that is a common and increasingly expensive assumption. WCAG is the set of guidelines that courts and regulators point to when deciding whether a website is accessible to people with disabilities, and small business sites are the ones most commonly out of compliance.

What WCAG actually is

WCAG stands for Web Content Accessibility Guidelines. It is maintained by the World Wide Web Consortium (W3C), the same body that defines the standards the web itself runs on. The guidelines cover four principles: a site must be perceivable (content can be seen or heard), operable (navigation works with keyboard, voice, or other means), understandable (content and interface are clear), and robust (the site works with assistive technologies like screen readers).

There are three conformance levels: A (the minimum), AA (the target most organizations aim for, and the level referenced in ADA legal cases), and AAA (the highest, which is not required and not always achievable for every page). Most legal and regulatory frameworks point to Level AA as the standard a website should meet.

Why it matters for a small business

The practical risk is legal. Title III of the Americans with Disabilities Act prohibits discrimination on the basis of disability in places of public accommodation, and courts have increasingly held that websites count as places of public accommodation. The Department of Justice issued guidance in 2024 confirming that the ADA applies to websites, and WCAG is the standard they reference.

The majority of ADA web accessibility lawsuits filed in recent years target small and mid-sized businesses, not Fortune 500 companies. A single demand letter from a law firm specializing in these cases typically asks for a settlement in the range of $5,000 to $25,000, plus the cost of remediation. The cost of building an accessible site from the start is a fraction of that.

What an accessible site actually does

The most common WCAG failures on small business sites are straightforward to fix if they are addressed during the build, and expensive to fix after the fact. They include:

  • Missing alt text on images — a screen reader user has no way of knowing what a photo of your storefront shows.
  • Insufficient color contrast — text that is too light against its background, which affects the 1 in 12 people with some form of color vision deficiency.
  • No keyboard navigation — a person who cannot use a mouse (a significant portion of users with motor disabilities) cannot get past the homepage.
  • Unlabeled form fields — a contact form where the fields are identified only by placeholder text, which disappears when a user starts typing and is not announced by screen readers.
  • Missing page titles and headings — assistive technology relies on these to navigate a page, and their absence makes a site unusable for a screen reader user.

An accessible site is not a different kind of site. It is the same site, built with attention to a set of rules that happen to make it usable by more people. The same alt text that helps a screen reader user also helps Google understand your images. The same heading structure that helps a keyboard user also helps your search ranking.

How compliance is measured

Accessibility is measured with automated tools and manual review. The automated tool I use is axe-core, which is the same engine that powers the accessibility audits in Chrome DevTools and Microsoft's tools. It scans a page and reports specific WCAG violations — which rule failed, how many elements are affected, and what the fix is. Automated testing catches roughly 30-40% of WCAG issues; the rest requires manual review, which is why an audit is a process, not a single button.

Every site I build is checked with axe-core against the WCAG 2.1 AA standard, and the results are visible. Zero critical violations is the baseline, not the goal. If you already have a site, the free audit will run the same check on it and show you exactly what it finds.

The bottom line

WCAG compliance is not a moral argument or a nice-to-have. It is a legal standard, it applies to your website, and the cost of ignoring it is higher than the cost of meeting it. If your site was built without accessibility in mind — and most small business sites were — there is a reasonable chance it has violations. Finding out is free.