WCAG Audit for Small Businesses: What to Check and How to Fix It
Published January 22, 2025 · 10 min read
Around 61 million adults in the United States live with a disability — about 26% of the adult population. A significant share rely on assistive technology to browse the web: screen readers, keyboard-only navigation, magnification software, or voice control. If your website has accessibility barriers, you are turning away a meaningful portion of potential customers.
Under Title III of the ADA, places of public accommodation — a category many courts have extended to commercial websites — must provide equal access to people with disabilities. WCAG 2.1 Level AA is the technical standard used by courts and the DOJ to evaluate compliance.
This guide walks you through what a WCAG audit covers, what issues to look for first, and how to fix the most common problems — without hiring an expensive consultant.
What Is a WCAG Audit?
A WCAG audit is a systematic review of your website against the W3C's Web Content Accessibility Guidelines. It identifies barriers that prevent users with disabilities from accessing your content. Audits typically have two phases:
Automated scanning
Tools like AccessCheckup or axe DevTools analyze your HTML and flag violations they can detect programmatically. Fast, cheap, and catches 30–40% of issues. Good first step.
Manual testing
A human tester navigates your site using a keyboard and screen reader, checking for logical reading order, meaningful link text, and interactive elements that work correctly. Required for full WCAG conformance.
The 5 Most Common WCAG Failures in Small Business Websites
These issues appear in the vast majority of small business sites we audit. Fixing these five alone will have the biggest impact on accessibility.
Images missing alt text
WCAG 1.1.1 Non-text Content (Level A)
Every meaningful image must have an alt attribute describing its content. Decorative images should have alt="" so screen readers skip them. Missing alt text is the single most common WCAG violation in small business sites.
How to fix it
Add descriptive alt attributes to all <img> tags. Be specific: 'alt="Dentist performing a teeth cleaning procedure"' not 'alt="photo"'.
Form inputs without labels
WCAG 1.3.1 Info and Relationships / 4.1.2 Name, Role, Value (Level A)
Every form field — text inputs, checkboxes, dropdowns, date pickers — needs a programmatic label. Placeholder text alone is not sufficient because it disappears when the user starts typing.
How to fix it
Use <label for="fieldId"> or aria-label on each input. Never rely solely on placeholder.
Insufficient color contrast
WCAG 1.4.3 Contrast (Minimum) (Level AA)
Normal text (under 18pt / 14pt bold) needs a contrast ratio of at least 4.5:1 against its background. Large text needs 3:1. Many brand color palettes fail this requirement, particularly light gray text on white or low-saturation combinations.
How to fix it
Check contrast ratios with a tool like the W3C contrast checker. If your brand gray is #888 on white (#FFF), the ratio is 3.54:1 — failing AA. Darken the text to at least #767676 for a 4.54:1 ratio.
Links and buttons without accessible names
WCAG 4.1.2 Name, Role, Value (Level A)
An icon-only button (hamburger menu, close button, social media icon link) has no visible text, so a screen reader user hears "button" or "link" with no context. They cannot tell what it does.
How to fix it
Add aria-label="Close menu" or visually hidden text inside the element. For linked icons, aria-label on the <a> tag is sufficient.
Missing or incorrect heading hierarchy
WCAG 1.3.1 Info and Relationships (Level A)
Screen reader users navigate by headings to understand page structure. Skipping heading levels (jumping from H1 to H4) or using headings for visual styling rather than structure breaks this navigation pattern.
How to fix it
Use headings in logical order: one H1 per page (the main topic), then H2 for sections, H3 for subsections. Never skip a level.
How to Audit Your Site in 4 Steps
- 1Run an automated scan
Start with AccessCheckup or install the axe DevTools browser extension. Run it on your homepage, a contact page, and any page with a form. Note every failure — these are your definite issues.
- 2Test keyboard navigation
Put your mouse aside. Press Tab to move through the page. Every interactive element should be reachable and have a visible focus indicator. You should be able to complete any form or purchase without touching the mouse.
- 3Check color contrast
Use the W3C's contrast checker or the Colour Contrast Analyser app to test your body text, link text, and button text against their backgrounds. Record every combination that fails 4.5:1.
- 4Review with a screen reader
On Mac, press Cmd+F5 to activate VoiceOver. On Windows, download NVDA (free). Navigate your key pages and listen for: missing alt text, unlabeled form fields, confusing link text, and any element that is skipped entirely.
How to Prioritize Fixes
You may find 20, 50, or even 100 issues. Do not try to fix everything at once. Use this priority order:
- 1.Level A violations first — these are the most severe and most legally risky
- 2.Issues on your highest-traffic pages (homepage, contact, checkout)
- 3.Issues that block a user from completing a transaction or getting information
- 4.Level AA violations
- 5.Issues on lower-traffic pages
Frequently Asked Questions
Does my small business have to comply with WCAG?
There is no single federal law that explicitly requires private small businesses to follow WCAG, but under Title III of the ADA, places of public accommodation (which many courts have extended to websites) must not discriminate against people with disabilities. WCAG 2.1 Level AA is the standard most courts and the DOJ use to measure compliance. ADA lawsuits against websites have increased significantly since 2018, and small businesses are frequently targeted.
What is the difference between a Level A, AA, and AAA audit?
WCAG 2.1 has three conformance levels. Level A is the minimum — if your site fails Level A, it is largely unusable for many disabled users. Level AA (the standard required by law and DOJ guidance) addresses the most common barriers. Level AAA is the most stringent and is not required by any law, but may be appropriate for highly specialized accessibility contexts. Most audits target Level AA.
Can I do a WCAG audit myself?
Yes, partially. Automated tools like AccessCheckup (powered by axe-core) can identify 30–40% of WCAG 2.1 violations quickly with no technical knowledge required. For a full conformance audit, you also need manual testing: keyboard-only navigation, screen reader testing (using NVDA or VoiceOver), and checking color contrast with a dedicated tool. A complete audit of a 10–20 page site typically takes 4–8 hours of manual review in addition to automated scanning.
What are the most common WCAG failures found in small business sites?
In our experience, the five most frequent issues are: (1) images missing alt text, (2) form inputs without associated labels, (3) color contrast below the 4.5:1 ratio for normal text, (4) links and buttons without accessible names, and (5) missing or skipped heading levels. These five issues alone can block users who rely on screen readers or keyboard navigation.
How long does it take to remediate a small business website?
For a 10–20 page site, focused remediation of the top WCAG issues typically takes a developer 1–3 days if the site is built on a standard CMS like WordPress, Squarespace, or Webflow. Complex or custom-built sites may take longer. The biggest variable is color contrast: if the brand color palette has insufficient contrast, a design decision is required before development can begin.
Sources & Further Reading
Get your plain-English accessibility report
AccessCheckup scans up to 25 pages, flags WCAG violations with screenshots, and tells you exactly what to fix — in plain English. Free scan, no account needed.
Start free scan →