Pull Request Audits
Every pull request runs a full WCAG 2.1 AA scan of the changed pages. Reviewers see a structured report inline before they approve.
Run WCAG audits on every commit. Block regressions before they merge. Watch your ACR score climb instead of explaining why it slipped.
Continuous Accessibility plugs The Accessible Org audit engine straight into your CI pipeline. When a developer opens a pull request, we crawl the changed pages against WCAG 2.1 AA, post a summary comment, and gate the merge based on the severity thresholds you set.
No new dashboards. No separate accounts. The check passes or it fails — just like your linter, just like your tests.
Pipeline-friendly outputs. Reviewable diffs. A treatment of accessibility as a first-class build artifact, not an afterthought.
Every pull request runs a full WCAG 2.1 AA scan of the changed pages. Reviewers see a structured report inline before they approve.
Configure severity thresholds. New critical violations fail the check and block the merge. Existing issues are tracked separately so legacy debt does not stall delivery.
Score every build against your ACR baseline. Watch your conformance level rise (or fall) over time with a single dashboard.
Drop the GitHub Action — or any CLI runner — into the workflow you already have. No new dashboards to babysit, no separate accounts to manage.
Drop the workflow below into your repository. Set ACCESSIBLE_API_KEY as a repository secret. Done — every future pull request gets audited.
# .github/workflows/accessibility.yml
name: Accessibility Audit
on: [pull_request]
jobs:
audit:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: theaccessible-org/audit-action@v1
with:
api-key: ${{ secrets.ACCESSIBLE_API_KEY }}
target: https://staging.example.com
fail-on: criticalACCESSIBLE_API_KEY in your repository secrets..github/workflows/accessibility.yml.Stop relying on quarterly audits to catch what your team shipped last month. Make compliance the default — one workflow file away.