Native CI/CD integration.

Block RGAA regressions before production: automatic audit on every pull request, configurable thresholds, 1 line.

The problem solved

One gate, one line, one guarantee.

If the score drops below your threshold, the build fails. Accessibility regressions no longer reach production.

Example · pull request

Required threshold: 90%

  • Build failed · score 84%
  • After fix · score 93%

How it works.

Add the accessibility check to your pipeline in 2 minutes.

  1. Add the check

    One step in your pipeline file.

  2. Set the threshold

    A minimum compliance score per project.

  3. Push code

    Every pull or merge request triggers the audit.

  4. Read the result

    Before/after score and new issues introduced.

Governance.

  • Configurable thresholds

    Set a minimum compliance score.

  • Reports in PRs

    An automatic comment on every pull/merge request with the before/after score and the new issues introduced.

  • Branch comparison

    Compare the accessibility score of your branch with the main branch.

  • Slack/Teams notifications

    Get an alert as soon as a pipeline detects an accessibility regression.

  • 1 line

    of configuration

    To get started.

  • 100%

    of regressions blocked

    Below your threshold.

  • < 2 min

    added to your pipeline

    Setup time.

  • 3

    CI/CD platforms

    GitHub, GitLab, Jenkins.

One config file, that’s all.

.github/workflows/accessibilite.yml
# Accessibility gate · 1 line setup
- name: Accorma audit
  uses: accorma/github-action@v1
  with:
    url: ${{ env.PREVIEW_URL }}
    threshold: 90
    fail-on-regression: true

Your platform is supported.

  • GitHub Actions

    Official action available on the GitHub Marketplace.

  • GitLab CI

    Docker image optimised for your GitLab pipelines.

  • Jenkins

    Official Jenkins plugin with built-in reporting.

Integrate in 5 minutes.

Add the accessibility check to your CI/CD pipeline today.

Book a demo

No-commitment demo