A few months ago, I was reading through accessibility reports for one of my projects and realized how tedious and inconsistent most a11y tools feel — either too technical for non-specialists or too shallow for developers.
That’s when I started building AccessFix, a developer-first accessibility checker that makes finding (and fixing) accessibility issues as easy as running a linter.
The goal:
Make accessibility scanning fast, actionable, and part of every developer’s normal workflow — not an afterthought.
How It Works
AccessFix runs scans using axe-core, the industry-standard open-source accessibility engine.
You can:
- Upload your HTML file
- Paste a website link
- Or connect your GitHub repository
Once scanned, AccessFix gives you:
- A score (based on detected issues)
- A downloadable report — written in plain English for quick fixes
- An optional GitHub Pull Request — it auto-comments on lines with detected issues so your team can fix them inline
All runs happen in your browser or via GitHub integration — no setup needed.
Key Features:
- axe-core Integration — industry-grade accessibility checks
- Scoring System — quickly gauge overall accessibility health
- Downloadable Reports — shareable summaries in plain English
- GitHub PR Generation — automatic inline comments for issues
- Multi-Input Scanning — upload files, enter URLs, or scan repos
(More features like CI/CD integration, AI integration, color analysis, and advanced scoring are coming soon!)
Sneak Peek
Demo video (30s) AccessFix Demo Video
How Others Can Get Involved
We’re looking for early testers and developers interested in shaping accessibility tools that actually fit into real workflows.
Feedback I’m Looking For
- What would make you actually use AccessFix regularly?
- Any feature you wish existed in accessibility tooling?