How it works
From commit to confidence in three steps.
Drop in the check
Add Clearpath to your pipeline in one line. It runs inside your CI on every commit — no infrastructure to manage, no browsers for you to host.
We diff every deploy
Results are keyed to your commit SHA. Clearpath compares this deploy to the last one on the branch and surfaces exactly what regressed.
Gate the pull request
A Check Run and a PR comment show what got worse. Turn on merge-blocking and accessibility regressions never reach production.
# .github/workflows/accessibility.yml
- name: Clearpath
uses: qashift/clearpath-action@v1
with:
urls: ${{ env.PREVIEW_URL }}
token: ${{ secrets.CLEARPATH_INGEST_TOKEN }}
fail-on: new_or_worsened # block merges on regressionsSlots into the stack you already run.
We're onboarding our first design partners now. No rip-and-replace — Clearpath plugs into your existing CI and Git workflow on day one.
12 free accessibility reports generated and counting.
“Accessibility breaks the same way every other quality gate breaks — silently, one deploy at a time. We built Clearpath so teams catch the regression in the pull request, not in a lawsuit.”
The workflow loop
Not another scanner. The loop around it.
Open-source tools tell you what's wrong, once. Clearpath builds the muscle: deploy-over-deploy diffing, PR gating, trend history, alerts, and badges — the system that keeps accessibility from slipping the moment you stop looking.
Per-deploy regression diffing
The headline. Every report leads with what got worse since your last deploy — not a vanity score you'll learn to ignore.
Pull-request gating
A status check on every commit plus an inline diff comment. Block the merge when new or worsened issues cross your threshold.
Live README badges
A shareable, always-current accessibility badge for your repo. Every embed is proof of commitment — and a backlink.
Trend history
Watch your accessibility posture improve deploy over deploy, with a clean trendline your whole org can rally around.
Anti-overlay detection
We flag sites running accessibility overlay widgets and explain why masking isn't fixing. We fix root cause — overlays don't.
Programmatic reports
Every public scan becomes a clean, shareable, indexable report page — instant credibility for marketing and sales too.
Why Clearpath
Better outcomes. A fraction of the cost.
Overlay widgets rent you a band-aid that's been the subject of hundreds of lawsuits. Per-scan tools meter you into a budgeting nightmare. Clearpath runs in your pipeline, so unlimited usage is sustainable for us — and structurally unmatchable by vendors who run the browsers themselves.
ADA / WCAG compliance status visible to your entire org — not just engineers. Product, legal, and leadership see the same live posture.
| Clearpath | Overlay widgets | Per-scan tools | |
|---|---|---|---|
| Approach | Fixes root cause in your code | Masks issues at runtime | Flags issues, no workflow |
| Pricing | Flat — unlimited scans & pages | Per-domain seat pricing | Metered per page / per scan |
| Runs in your CI | Yes — on every commit | No | Partially |
| Per-deploy regression diff | Yes — the core feature | No | No |
| Blocks risky merges | Yes — configurable | No | No |
| Legal exposure | Reduced — real remediation | Higher — overlays are litigated | Unchanged |
We fix root cause. We don't do overlays.
Accessibility overlays promise a one-line fix and deliver a lawsuit magnet. They sit on top of broken markup and hope nobody notices. Clearpath does the opposite — it pinpoints the underlying issue in your code so your team fixes it once, properly, and it stays fixed. When we detect an overlay on a scanned site, we say so.
Security & privacy
Enterprise-grade trust, by design.
Security teams sign off on Clearpath fast because the architecture is the answer: the heavy work runs in your infrastructure, and we hold as little as possible.
Your code never leaves your pipeline
CI scans run inside your own runner. We never receive your source — only the accessibility results you choose to send. No agent, no repo access required for scanning.
Private by default
Every result is isolated to your organization with database row-level security. Reports and badges are public only when you explicitly opt in — per project.
Compliant & accountable
Built to GDPR and India's DPDP principles, encrypted in transit, OWASP-aware across the stack. Ingest tokens are scoped per project and revocable in one click.
No overlays. No injected scripts.
We never add a third-party widget or script to your site — the approach that's drawn hundreds of lawsuits. Clearpath only reads and reports, so your runtime stays exactly as you shipped it.
Run it in your own CI — unlimited, free of metering.
The recommended path: one line in your pipeline, your compute, zero data shared beyond results.
Pricing
Flat pricing. Unlimited scans.
Checks run in your CI, so unlimited usage is sustainable for us — and unmatchable by vendors who run the browsers themselves.
CI scans: unlimited on every plan.Cloud scans (run on our infrastructure) are metered per plan.
Starter
- Unlimited CI scans
- 10 cloud scans / mo
- 3 projects
- PR bot + badges
Growth
- Unlimited CI scans
- 30 cloud scans / mo
- 10 projects
- Merge-blocking
Scale
- Unlimited CI scans
- 100 cloud scans / mo
- 50 projects
- 365-day history
Questions, answered.
Scanners tell you what's wrong once. Clearpath is the loop around it — it runs on every commit, diffs each deploy against the last, blocks risky merges, tracks the trend, and posts the result in your pull request. You catch the regression when it's introduced, not in an audit months later.
Put accessibility on autopilot for every deploy.
Start free in minutes. Scan any URL right now, or wire Clearpath into your CI and never ship a regression again.