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.
WCAG 2.2 AA testing — powered by axe-core
axe-core finds up to 57% of WCAG violations automatically. AccessPulse runs it on every deploy so regressions never reach production. Not an overlay. Not a badge. Actual testing.
Free scan — no signup required
Three steps. No SDK. No JavaScript snippet.
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.
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.
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.
One step in your GitHub Actions, GitLab CI, or any pipeline.
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 }}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.
Start free. Upgrade when you need more scans.
No credit card required
$0
Most Popular
For solo devs and small teams
$29/mo
For growing engineering teams
$149/mo
For agencies managing multiple clients
$399/mo
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.