A WCAG audit that finds 50 failures is a depressing object. It tells you what's broken, sometimes where, but rarely how to fix it in your specific HTML. Teams read the list, get overwhelmed, ship nothing, and circle back three months later with the same 50 failures still there.
The WCAG Fix Generator exists to compress "50 failures → deployable fixes" into one AI round-trip. Paste the audit output, pick your target conformance level, copy the generated prompt plus your page HTML into Claude, get back per-failure patches grouped by file.
What it emits
Three outputs from one click:
1. A per-failure AI remediation prompt. Each WCAG Success Criterion gets a structured brief: the SC number, level (A/AA/AAA), impact (critical/serious/moderate), and a fix pattern describing how to satisfy it. The AI model takes this plus your page HTML and emits specific HTML/CSS/ARIA patches, not generic advice, real code changes grouped by file so you can apply them in one pass per file.
2. A prioritized 30-day roadmap. Critical failures in week 1 (screen-reader-blockers and the highest ADA lawsuit exposure). Serious in weeks 2-3. Moderate in week 4. Each week includes a verify step: re-run the audit, confirm the specific SC numbers drop off the list.
3. Deep-links to re-audit. After the fix ships, one click re-runs /tools/wcag-accessibility-audit/ against the same URL to confirm which failures cleared and which need another pass.
The 45 Success Criteria
The tool covers the full WCAG 2.2 Level A + AA set (and Level AAA when you select the AAA target): 18 Perceivable criteria, 16 Operable, 9 Understandable, 3 strong. Each has a concrete fix pattern distilled from the W3C's ACT rules and common remediation patterns.
Examples of the patterns shipped:
- WCAG 1.4.3 (contrast): body text needs 4.5:1, large text 3:1. Fix pattern includes specifically how warm-gold-on-cream schemes fail and how to push the gold to
#c07400for body text while keeping brighter gold for large headlines. - WCAG 2.4.7 (focus visible):
:focus { outline: none }without a replacement is the most common failure. Fix pattern specifies using:focus-visibleso the ring shows for keyboard users but not on mouse clicks. - WCAG 3.3.1 (error identification):
aria-invalid="true"on failing fields +aria-describedbylinking to the error message. Don't rely on red highlight alone. - WCAG 4.1.2 (name, role, value): custom widgets need ARIA role + state. Fix pattern points at the W3C's ARIA Authoring Practices Guide for every common widget pattern.
Impact weighting
Failures are sorted by impact before being fed to the AI:
- Critical failures block screen-reader users entirely and are the top ADA lawsuit triggers: missing alt text, missing form labels, keyboard-inaccessible widgets, missing focus rings, non-descriptive link text, low-contrast body text. These ship first.
- Serious failures create major barriers for some user groups: missing skip links, missing page titles, broken focus order, timing without extension, missing error suggestions, sticky headers obscuring focus. Ship second.
- Moderate failures are best-practice + UX polish: autocomplete attributes, text-spacing robustness, consistent navigation, single-key shortcut remapping. Ship together in the final sprint.
A roadmap that ships critical first means even if the project gets interrupted, the highest-impact + highest-risk failures are cleared.
Why ADA matters
WCAG 2.2 Level AA is the de facto ADA compliance baseline for Title III (public accommodations). U.S. ADA demand letters and lawsuits against small businesses have grown every year since 2018; ~4,000+ website accessibility lawsuits were filed in federal court in 2024 alone, with most targeting e-commerce, restaurants, and professional services sites. Settlements typically run $10,000-$50,000 plus attorney fees; the "fix it first" defense requires demonstrated remediation effort with documented timestamps.
This tool's 30-day roadmap + the re-audit workflow gives you that documentation. Each week's fix-and-re-audit loop produces timestamped evidence of good-faith remediation.
Input formats
The tool parses WCAG SC codes (1.1.1, 1.4.3, etc.) from whatever format you paste:
- CSV export from
/tools/wcag-accessibility-audit/ - JSON export
- Freetext list ("WCAG 1.1.1, missing alt; WCAG 2.4.4, non-descriptive links")
- Notes copied from axe-core, Lighthouse, WAVE, or any other accessibility tool that emits SC numbers
Or skip the paste, filter by category (Perceivable / Operable / Understandable / strong), select your target level (A / AA / AAA), and manually check the failures from your own observations.
The pair workflow
- Run the WCAG Accessibility Audit on the page
- Copy the CSV or the visible failure list
- Paste into the Fix Generator → auto-select the SC codes
- Click Generate → copy the fix prompt
- Paste the prompt plus your page HTML into Claude (or ChatGPT / Gemini)
- Apply the returned patches by file
- Re-run the audit (the tool gives you a one-click deep-link)
- Repeat until clean
For most SMB sites the critical-only pass (week 1 of the roadmap) is doable in 4-6 hours and clears the ADA risk vector. The serious and moderate tiers can ship incrementally over the following month.
Related reading
- Why the WCAG Audit Exists, Small Business ADA Lawsuit Risk
- How the WCAG Audit Works, 70+ Browser-Side Checks
- Mark N/A Audit Checks, UX Pattern Across All Tools
- The Mega Analyzer's A11y Tab, Quick WCAG Overview Inline
If you run a client agency doing accessibility work, the $20 Dollar Agency walks through the delivery SOP: The $20 Dollar Agency.
Fact-check notes and sources
- WCAG 2.2 Success Criteria and conformance requirements: W3C, WCAG 2.2 specification (accessed 2026-04-20)
- WCAG-ACT rules for automated testing: act-rules.github.io
- WAI-ARIA Authoring Practices (widget patterns): w3.org/WAI/ARIA/apg/patterns/
- ADA Title III web accessibility guidance: ada.gov, Web Accessibility
- U.S. ADA website lawsuit statistics: UsableNet Year End Report — ~4,000+ federal filings in 2024
