Skip to content
aulys.app · accessibility 100read the statement
Aulys

APIComing

Put the grade in your pipeline.

The same engine behind the plugin and the scanner, exposed as an API. Score a build, gate a pull request, or fail CI on a new regression — accessibility becomes a check that runs, not a hope that someone remembers.

🚧 On the roadmap — not built yet. The Figma plugin is live today and is where the loop starts.

  1. Figma
  2. Code
  3. Scan
  4. Monitor

What it does

  • Score anything programmatically

    Send a URL or build artifact, get back a structured grade with every failing rule and element. JSON in, evidence out.

  • Gate pull requests

    Add Aulys as a PR check. Block merges that introduce new WCAG failures, the same way you'd block a failing test.

  • Regression budgets

    Set the floor your team can't drop below. Aulys fails the build when the grade slips, not just when something is technically wrong.

How it connects

The loop is the point. The same issue follows the thread into the neighbouring phase — one score, one history.

Started in Figma

By the time it reaches CI, the issue was already visible in design.

Reports to the Dashboard

Every CI run feeds the team's single grade and history.

JSON API · PR checks · regression budgets · same engine

Start with what's live today.

Start free in FigmaGet notified