About AccessPulse

AccessPulse is built by Dylan Grosz, a software engineer who got tired of shipping inaccessible code without knowing.

The accessibility tooling landscape has a gap. On one end, there are free tools like axe-core, Lighthouse, and Pa11y — powerful engines, but you need to wire up your own CI pipeline, build a dashboard, set up alerting, and maintain it all yourself. That takes 10-40 hours of DevOps work that most teams never prioritize.

On the other end, enterprise platforms like Deque, Siteimprove, and Level Access start at $15K/year and require sales calls. They are built for compliance teams at Fortune 500 companies, not for a developer who wants to know if their last deploy broke something.

AccessPulse fills the gap. It runs axe-core — the same engine Google, Microsoft, and the US government use — in a real browser on every URL you submit. You get a structured report with violations grouped by severity, the affected elements, and links to the relevant WCAG success criteria. Add accesspulse/scan@v1 to your GitHub Action and you can fail builds that introduce regressions.

I want to be clear about what this tool is and isn't. Automated testing catches roughly 57% of WCAG violations (per Deque's own research). The remaining 43% — alt text quality, reading order, cognitive load — requires human judgment. AccessPulse handles the automated layer reliably. For full coverage, pair it with periodic manual audits and, ideally, user testing with people who have disabilities.

AccessPulse is not an overlay widget. It does not inject JavaScript into your site. It does not claim to make your site "compliant." It tells you what's broken so you can fix it in your actual code.