WCAG 2.2 AA testing — powered by axe-core

Know when your site breaks accessibility.

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

96.3%

Of home pages have WCAG failures

WebAIM 2025

57%

Of issues caught by automated testing

Deque study

8,667

ADA Title III lawsuits filed in 2025

ADA litigation data

< 30s

Full axe-core audit per page

How it works

How it works

Three steps. No SDK. No JavaScript snippet.

01

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.

02

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.

03

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.

Free

No credit card required

$0

  • 25 scans/month
  • WCAG 2.2 AA audit
  • Full violation details
  • Single site
Scan for free

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
Book a 15-min call

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.

Run your first scan in 30 seconds

No signup. No credit card. Just paste a URL.

Try a Free Scan