Fixable-a11y-PR

Who it's for

Small agencies, freelancers, and indie SMBs who today run Lighthouse/accessibility audits manually or hand-edit CMS templates (WordPress/Shopify/Netlify/hosted Git repos) to patch issues.

The problem

Time and money: engineers or designers spend days hunting failures and producing risky manual patches; legal/compliance risk for businesses facing accessibility complaints (demand letters) increases exposure and remediation cost.

How to build it

A web UI + GitHub/Bitbucket/GitLab OAuth that crawls the live site and the repo, proposes branch+commits, and opens PRs with code changes and Playwright tests; also supports manual ZIP/patch upload for non-git sites.

How it makes money

Who pays: site owners or agencies (not end users). Price: $149 one-off per site for the automated PR bundle or $29/month per site for ongoing scanning+PR credits; why they pay: reduces billable dev-hours, provides auditable remediation tickets and tests used in legal defense; why not free: competing free linters only detect problems and don't produce verified fixes or tests—customers pay to convert detection to safe, reviewable code that reduces external contractor time and legal risk.

Why it doesn't exist yet

Large accessibility tools focus on detection (Lighthouse, axe) not safe automated remediation because fixes often require contextual judgment; CMS plugin ecosystem fears false positives and breaking layouts; incumbents avoid shipping auto-PRs due to liability. An indie can target the low-risk, high-frequency subset of fixes (semantic elements, missing labels, color-contrast, keyboard-focus, alt text placeholders, form label ties) with conservative, reversible edits plus tests and opt-out comments to keep risk minimal and defensible.

First users

1) Agencies want fast deliverables to bill; 2) Shopify/WordPress shops with legal threats want quick remediation; 3) freelancers can upsell a 'fix PR' service; 4) accessibility consultants will use it to convert audits into billable PRs; 5) early adopters from Lighthouse/axe communities will try automated, tested fixes; initial outreach via agency Slack communities, WP/Shopify dev forums, and Product Hunt will bring the first 10.

Build size

2 people x 8–10 weeks: includes crawler + rule engine for 25 conservative fix patterns, Git integration (OAuth PR creation), Playwright test generator, small web UI, and a rollback/preview system. Excludes universal CMS plugin authors (full WP plugin with all themes) and complex layout rewrites or JS-framework-specific design system changes.

Biggest risk

A major platform (GitHub, Netlify, Shopify) shipping native 'auto-fix accessibility PRs with tests' or an established accessibility vendor adding safe auto-PR capability would collapse the niche.

Conditions for a hit (all 3 required)

• Produces 1–5 Git branches with concrete code diffs (HTML/CSS/templating edits) per site and opens verified PRs within 30 minutes for a site under 100 pages.
• Each PR includes an auto-generated Playwright accessibility test that reproduces the original failing Lighthouse/axe rule and shows it passing after the PR merge (test file + run log).
• Provides an HTML 'preview diff' and a one-click rollback that reverts all created branches and removes generated assets within 5 minutes of request.

How it's judged (in 6 months)

Product Hunt daily top 5 or GitHub repo reaching 1,000 stars (either qualifies)(judgment date 2027-02-15)

AI self-confidence 55/100 — self-reported likelihood of meeting the criterion, not a business success rate