Website Accessibility (WCAG) Compliance: A Practical Guide for Business Owners

A visitor who cannot read your menu, fill in your contact form, or navigate past your homepage banner does not file a complaint. They just leave, and they rarely come back. Website accessibility is usually framed as a legal compliance issue, and it is one, but for most business owners the more useful frame is simpler: an inaccessible site is a broken sales funnel for a meaningful share of your traffic, and fixing it is far cheaper than most owners assume.

What “accessibility” actually means for a business website

Accessibility is the practice of building a website so that people with visual, auditory, motor, or cognitive disabilities can use it with the same effectiveness as anyone else. In practice that covers a narrower, more concrete list than most owners expect: enough color contrast to read text, keyboard navigation for people who cannot use a mouse, alt text on images for screen reader users, captions on video, forms that announce errors clearly, and a layout that does not rely on color alone to convey meaning.

The standard almost everyone measures against is the Web Content Accessibility Guidelines (WCAG), currently at version 2.2, published by the W3C Web Accessibility Initiative. WCAG is organized into three conformance levels: A (minimum), AA (the level referenced by most laws and the level most businesses should target), and AAA (a stricter standard rarely required outside specialized sectors).

Why AA, specifically

Level AA is the de facto legal benchmark. It is what the U.S. Department of Justice points to under Title II and Title III of the Americans with Disabilities Act, what the EU’s Web Accessibility Directive and European Accessibility Act reference, and what most settlement agreements in ADA web-access lawsuits require as the remediation target. Building to AA from the start avoids relitigating your whole front end later.

The legal exposure is real, and it is growing

Website accessibility lawsuits in the United States have risen every year for the better part of a decade, and the plaintiffs are not limited to large retailers. Small and mid-size business sites are frequent targets precisely because they are less likely to have addressed the basics. A typical case does not allege that the business intended to discriminate; it alleges that a screen reader user could not complete a purchase or make a reservation because of unlabeled buttons, missing form labels, or a checkout flow that could not be operated by keyboard.

Two things make this different from most compliance risk: there is no minimum company size below which you are automatically safe, and a demand letter is often the first sign of trouble, arriving well before any lawsuit. Outside the US, the picture is similar — the European Accessibility Act’s June 2025 compliance deadline has already pushed enforcement activity higher across EU member states for e-commerce and service sites.

Where most business sites actually fail

Accessibility audits tend to turn up the same handful of problems, in roughly this order of frequency:

1. Images without alt text

Every meaningful image needs a text alternative describing what it conveys, not just what it depicts. A product photo needs alt text describing the product; a purely decorative background graphic needs an empty alt attribute so screen readers skip it rather than reading a meaningless file name aloud.

2. Insufficient color contrast

Light gray text on a white background looks clean in a design mockup and is illegible to a large share of users, not just those with diagnosed low vision. WCAG AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text — a threshold you can check in seconds with a free contrast checker.

3. Forms that don’t announce themselves

A contact or checkout form where fields are marked only by placeholder text (which disappears once you start typing, and which many screen readers skip entirely) leaves users unable to tell what a field is for, or that they made an error, once they’ve submitted something invalid.

4. Keyboard traps and invisible focus

Anyone navigating by keyboard alone (a common accommodation, not just for motor disabilities but for many power users) needs to see, visually, where focus currently sits, and needs to be able to tab through every interactive element including modal dialogs and dropdown menus without getting stuck.

5. Video without captions

Auto-playing hero videos and embedded product demos routinely ship with no captions and no transcript, locking out deaf and hard-of-hearing users and anyone browsing with the sound off, which by some measures is most mobile users in public settings.

Automated scans catch roughly a third of the problem

Tools like WAVE, axe, and Lighthouse’s accessibility audit are genuinely useful and worth running on every page template you have — they’re free, fast, and catch missing alt text, contrast failures, and missing form labels reliably. Their honest limitation, acknowledged by their own creators, is that automated testing can only reliably detect roughly 30-40% of WCAG success criteria. Things like “does this error message actually make sense when read aloud” or “can someone unfamiliar with the page complete checkout using only a keyboard” require a manual pass, ideally by someone who tests with a screen reader (NVDA and VoiceOver are both free) as part of the workflow, not just an automated report.

A pragmatic remediation order

Most businesses cannot fix everything in a week, so prioritize by a mix of impact and effort:

1. Fix the checkout or lead-capture path first. This is where inaccessibility directly costs revenue and where most lawsuits originate.
2. Run a free automated scan sitewide and clear the contrast and missing-label issues; these are usually quick CSS and markup fixes.
3. Add real alt text to every image that carries meaning, and mark purely decorative images as such.
4. Test primary navigation and forms by keyboard alone, tabbing through without touching the mouse.
5. Caption any video that carries information a viewer needs, not just marketing filler.
6. Document what you did and when. An accessibility statement plus a dated remediation log is one of the more effective mitigants if a demand letter arrives, since it shows a good-faith, ongoing effort rather than indifference.

Where this fits into a website project, not bolted on after

Accessibility is dramatically cheaper when it’s a requirement from the first wireframe rather than a retrofit on a finished site — proper heading structure, contrast-aware color palettes, and accessible form components are a normal part of good website development practice, not an add-on. If your site is due for a redesign or a platform migration, that is the moment to fold WCAG AA into the spec rather than treating it as a separate project later. For sites already live, it belongs in the same maintenance cadence as your other technical upkeep — the kind of ongoing review covered under IT maintenance — since new pages and new blocks reintroduce old problems if nobody is checking.

It also intersects with SEO more than most owners expect: proper heading hierarchy, descriptive link text, and alt text are graded by the same crawlers and, increasingly, by the same AI answer engines that decide whether your SEO work translates into visibility. Accessible markup and crawlable markup overlap heavily; you are rarely doing one without helping the other.

Frequently asked questions

Does WCAG compliance apply to small business websites, or just large companies?

US case law does not set a company-size threshold; small businesses are sued regularly, often precisely because their sites are easier targets. Company size affects your risk tolerance and budget, not your legal exposure.

Is there a fast way to check if my site has major problems?

Run your homepage, a product or service page, and your contact/checkout form through a free tool like WAVE or the Lighthouse accessibility audit built into Chrome DevTools. That will surface obvious contrast, alt-text, and label issues in minutes, though it won’t catch everything.

Do accessibility overlay widgets solve this?

Generally no. Widgets that claim to auto-fix accessibility by injecting a script tend to address surface symptoms without fixing underlying markup, and several overlay vendors have themselves been named as co-defendants in accessibility lawsuits. A genuine fix happens in the code.

How much does a real remediation project cost?

It scales with site size and how the site was built. A small brochure site with a handful of templates is a modest, contained project; a large e-commerce catalog with custom components is larger. Fixing the top handful of issues (contrast, alt text, form labels, keyboard traps) is usually inexpensive relative to a full specialist audit, and delivers most of the practical benefit.

Does accessibility work help or hurt SEO?

It generally helps. Alt text, heading structure, and descriptive link text are signals search engines use too, so accessibility remediation and technical SEO cleanup frequently overlap and reinforce each other.

What’s the very first thing to fix if I can only do one thing this month?

Your primary conversion path — contact form, quote request, or checkout. Test it with keyboard-only navigation and fix whatever breaks. That is where inaccessibility most directly costs you business and where legal claims most often originate.

Do I need to hire a specialist, or can a developer just fix this?

A competent developer can fix most code-level issues (contrast, labels, alt text, focus states) without specialized training. A full audit against every WCAG 2.2 AA success criterion, especially for anything involving complex interactive components, benefits from someone with accessibility-specific testing experience.

The Bottom Line

Website accessibility is not a niche legal formality; it is the difference between a site that works for everyone who lands on it and one that quietly turns away a meaningful slice of visitors before they ever reach your contact form. The good news is that the highest-impact fixes — contrast, alt text, form labels, keyboard navigation on your core conversion path — are also the cheapest and fastest to make. Treat WCAG 2.2 AA as the target, run a free automated scan today, fix your checkout or contact form first, and build accessibility into the next redesign rather than treating it as a future cleanup project.