accessibility2026-05-026 min read

The WCAG Compliance Audit Template Your Small Business Actually Needs

A step-by-step WCAG audit template with free tools, prioritization framework, and cost-benefit analysis. Stop guessing what to fix first.

Free tool

Grade your website before you keep reading

Most readers want a quick benchmark first. Start with the free Website Grader, then come back to this article with a clearer sense of what to fix.

Grade My Website →

Most small business owners hear "WCAG compliance" and picture a $20,000 consulting bill and three months of developer time. The reality is more mundane and more within reach than you'd think. An accessibility audit is a structured process, not a mystery. Here's the template we use with small business clients — adapted so you can run most of it yourself.

Phase 1: The 30-Minute Automated Sweep

Before you manually check a single thing, let free tools do the heavy lifting. Run these three tools against every key page on your site:

  • axe DevTools: (browser extension) — scans your page in seconds and flags WCAG violations by severity
  • WAVE Evaluation Tool: (webaim.org/wave) — gives you a visual overlay showing errors, contrast issues, and alt text gaps
  • Lighthouse: (built into Chrome DevTools) — the accessibility score is a decent proxy for general WCAG 2.1 AA compliance
  • Run them on your homepage, your top 3 landing pages, your contact page, and any page with a form. That's maybe 6-8 pages total. Document every finding in a spreadsheet with columns for: page URL, element, violation type (color contrast, missing label, keyboard trap, etc.), severity (critical/serious/moderate), and effort to fix (low/medium/high).

    Most small business sites will surface the same recurring issues: missing alt text on images, low contrast between text and backgrounds, form fields without visible labels, and links that are only distinguishable by color. These aren't edge cases — they account for roughly 70% of automated audit failures.

    Phase 2: Manual Keyboard Testing

    Automated tools catch maybe 30-40% of WCAG issues. The rest require human judgment. Keyboard testing is the single highest-ROI manual check you can do.

    Unplug your mouse. Navigate your entire site using only Tab, Shift+Tab, Enter, Escape, and arrow keys. Specifically watch for:

  • Focus visibility: — can you see which element is currently focused? If not, you've got a violation
  • Tab order: — does focus move through the page in a logical sequence? Jumping around randomly is a common bug, especially on sites built with absolute positioning or CSS grid
  • Interactive elements: — can you activate every button, link, dropdown, and form control without a mouse?
  • Traps: — does focus ever get stuck in a modal, mega menu, or widget with no way to escape?
  • Time-box this to 45 minutes. If you find your site is essentially unusable by keyboard alone, that's a critical finding that goes to the top of your fix list. For a deeper look at why accessibility matters beyond legal compliance, [accessibility is a business superpower](/blog/accessibility-business-superpower) — and keyboard testing is where you'll feel that truth most viscerally.

    Phase 3: Screen Reader Spot-Check

    You don't need to become a screen reader expert. Install VoiceOver (built into macOS), NVDA (free for Windows), or use the screen reader in your phone's accessibility settings. Navigate your homepage and one key conversion page.

    Listen for:

  • Do images without alt text get announced as meaningless file names or just skipped?
  • Are headings announced in a logical hierarchy (h1 → h2 → h3, not h1 → h4 → h2)?
  • Does form validation provide clear, specific error messages ("Please enter a valid email" not just "Error")?
  • Is the page language correctly set? If your site is in English but the lang attribute says something else, screen readers may pronounce everything wrong
  • Phase 4: Prioritize by Effort and Impact

    This is where audits fail or succeed. You've now got a list of issues. Don't try to fix everything at once. Use this framework:

    **Fix immediately (low effort, high impact):**

  • Missing alt text — literally adding text attributes to images
  • Form labels — wrapping inputs with `<label>` elements
  • Focus styles — a single CSS rule to add visible outlines
  • Language attribute — one line in your HTML
  • **Schedule for this month (medium effort, high impact):**

  • Color contrast fixes — adjusting your color palette for WCAG AA ratios
  • Keyboard navigation bugs — fixing tab order and removing focus traps
  • Mobile touch targets — ensuring buttons and links are at least 44×44px
  • ARIA landmarks — adding `role="navigation"`, `role="main"`, etc.
  • **Plan for next quarter (higher effort, still important):**

  • Complex widget accessibility (carousels, accordions, data tables)
  • PDF accessibility remediation
  • Third-party widget compatibility (chat widgets, embedded maps)
  • Comprehensive screen reader testing across devices
  • The Cost-Benefit Reality

    Here's the uncomfortable math. ADA Title III lawsuits against businesses with inaccessible websites have been climbing steadily, with settlements typically ranging from $10,000 to $75,000. But let's set aside the legal risk — that's a motivation, not a benefit.

    The actual business case: roughly 15-20% of your visitors have some form of disability affecting how they use the web. If your site converts at 2% and you fix the accessibility barriers that block those users, you're not gaining 15-20% more traffic — you're removing conversion friction for a segment that's currently bouncing. The ROI on accessibility fixes often exceeds that of paid advertising.

    For a small business site, a thorough self-audit using the process above takes 4-6 hours spread over a week. Fixing the high-priority items typically takes a developer 8-16 hours. Compare that to the cost of a single ADA demand letter, and it's not even close.

    Tools Reference

    | Tool | Cost | What It Covers |

    |------|------|----------------|

    | axe DevTools | Free | Automated WCAG 2.1/2.2 scans |

    | WAVE | Free | Visual overlay + error summary |

    | Lighthouse | Free | Accessibility score + suggestions |

    | Color Contrast Analyzer | Free | Specific contrast ratio checking |

    | VoiceOver / NVDA | Free | Manual screen reader testing |

    For businesses that want professional validation, a third-party [WCAG 2.2 audit](/blog/wcag-2-2-seo-impact) is worth considering after you've addressed the obvious issues yourself. You'll get more value from the audit — and spend less money — when you've already fixed the low-hanging fruit.

    Your Audit Checklist

  • Run automated scans on 6-8 key pages
  • Document all findings in a prioritized spreadsheet
  • Keyboard-test your homepage and contact/conversion pages
  • Spot-check with a screen reader on 2 pages
  • Categorize fixes by effort and impact
  • Fix all low-effort, high-impact issues within one week
  • Schedule medium-effort fixes for the next month
  • Plan quarterly accessibility reviews going forward
  • Consistency beats perfection here. A site that gets a quarterly accessibility check-in is far better off than one that got a perfect audit two years ago and hasn't been touched since. Start this week. The tools are free, the process is defined, and the risk of inaction is real.

    Turn this article into a real benchmark

    Start with the free Website Grader for an instant score, then move to the full AI scan when you want page-level recommendations.

    Open the Free Website Grader →