Paste your URL
We spin up a real Chromium browser, wait for JavaScript to settle, then run axe-core against every WCAG 2.2 Level AA success criterion. Same engine Deque, Microsoft, and Google use.
Live monitoring active.Live · WCAG 2.2 AA · powered by axe-core
alt="image" passes axe-core. It shouldn't.
axe-core finds ~57% of WCAG violations automatically. AccessPulse closes the loop with suggested fixes — deterministic for mechanical rules, computed for contrast, and ML-suggested where the right answer needs human judgment. Review before applying. Free scan, no signup.
Free scan — no signup required
96.3%
of homepages have at least one WCAG 2.2 violation. WebAIM 2025
How it works
Three steps. No SDK. No JavaScript snippet.
Get your report
Every violation includes the exact WCAG criterion it fails, the affected DOM elements with CSS selectors, and a direct link to the remediation technique. No guesswork.
Fail the build
Add AccessPulse/scan@v1 to your GitHub Action — four lines of YAML. Set a score threshold. PRs that introduce regressions get blocked before merge. Your CI pipeline becomes your accessibility gate.
Fits into your existing workflow
One step in your GitHub Actions, GitLab CI, or any pipeline.
.github/workflows/accessibility.yml
name: Accessibility
on:
pull_request:
push:
branches: [main]
jobs:
a11y:
runs-on: ubuntu-latest
steps:
- name: WCAG 2.2 scan
uses: AccessPulse/scan@v1
with:
url: ${{ vars.SITE_URL }}
threshold: 80
api-key: ${{ secrets.ACCESSPULSE_API_KEY }}Overlays don't work. Testing does.
The FTC fined accessiBe $1M for false compliance claims. In 2025, 22.6% of ADA lawsuits targeted sites using overlay widgets. The only path to accessibility is fixing your actual markup.
Overlay widgets
- Don't fix underlying code issues
- $1M+ FTC fines for false compliance claims
- 1,000+ lawsuits against sites using overlays
- Blocked by screen readers, breaking access further
AccessPulse
- Identifies the exact code to fix
- Real WCAG 2.2 AA automated testing
- CI/CD integration catches regressions early
- Complements professional audits, not a shortcut
Simple, transparent pricing
Start free. Upgrade when you need more scans.
Pre-launch:AccessPulse is in Stripe test mode. Real cards won't be charged. Subscriptions you start here won't persist past the public launch. Use Stripe test card 4242 4242 4242 4242 with any future date and CVC if you want to walk through the flow.
Free
No credit card required
$0
- 25 scans/month
- WCAG 2.2 AA audit
- Full violation details
- Single site
Most Popular
Developer
For solo devs and small teams
$29/mo
- 500 scans/month
- Scan history & dashboard
- API key for CI/CD
- Regression detection
Team
For growing engineering teams
$149/mo
- 2,000 scans/month
- Everything in Developer
- Slack & GitHub integration
- Priority support
Agency
For agencies managing multiple clients
$399/mo
- 10,000 scans/month
- Everything in Team
- White-label reports
- Custom integrations
Compare features by tier
Every feature, every cap. The fine print is at the bottom.
| Feature | Free | Developer | Team | Agency |
|---|---|---|---|---|
| Web scans | 25/mo | 500/mo | 2,000/mo | 10,000/mo |
| ML alt text quality scoring* | 5 imgs/scan | 100 imgs/scan | 500 imgs/scan | 2,000 imgs/scan |
| Suggested fixes (deterministic + computed) | ||||
| Suggested fixes (ML-generative)† | ||||
| GitHub Action‡ | anonymous, 25/repo/mo | |||
| API access | — | |||
| API rate limit | — | 50/day | 200/day | 1,000/day |
| Web scan rate limit | 5/day | monthly cap | monthly cap | monthly cap |
| PR-comment posting | — | |||
| Scan history | 7 days | unlimited | unlimited | unlimited |
| Async scanning (large sites)§ | — | — | — | |
| Email support | community | priority | priority | |
| Contract | — | month-to-month | month-to-month | annual or m2m |
- ML alt text scoring caps are subject to revision after May 5 cost analysis with fix suggestions factored in. See the methodology page for current state.
- ML-generative fix suggestions ship conditionally at V1 launch. The feature locks on July 1 based on accuracy hitting our held-out evaluation threshold.
- The GitHub Action runs against your deployed URL on every PR, fails the build below your score threshold, and posts fix suggestions as PR review comments on paid tiers. See the docs.
- Async scanning queues large-site scans (1,000+ pages) and emails results when complete. Available on Agency.
Catch accessibility regressions in CI. With one line.
The AccessPulse/scan@v1 Action runs on every PR — score, fix suggestions, and a fail-the-build threshold.
.github/workflows/a11y.yml
- uses: AccessPulse/scan@v1
with:
url: ${{ steps.deploy.outputs.preview-url }}
threshold: 80Posts fix suggestions as PR review comments— review the fix where you're already reading the diff.
Fails the build below your accessibility score threshold — block regressions before merge.
Free tier signs up in 30 seconds — get an API key, try the Action.
What automated testing can't do
Automated tools like axe-core catch roughly 57% of WCAG violations. The rest — whether alt text is actually meaningful, if the reading order makes sense, whether focus management is logical — requires human judgment. AccessPulse handles the automated layer. For full coverage, pair us with a manual audit.