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

Live in Figma today · free, no account

Accessibility that starts in the frame.
Graded A–F, before code exists.

Catch issues in Figma and grade every screen — before a single line of code inherits the problem.

Scan your first frame freeSee how it grades
example reportWCAG 2.2 · AAA
38 / 100
scanning…
Demonstration of Aulys scoring: an example accessibility grade rising from F to A as you scroll.
contrast ratio3.1 : 1
below AAAAA 7:1
Contrast 1.4.6
7.4 : 1
Touch target 2.5.8
44 px
Focus visible 2.4.13
3 px ring
Headings 1.3.1
h1 → h3

0 / 13 checks · audited with Aulys

The gap between design and code is where accessibility dies.

Designers check in one tool, developers lint in another, QA scans with no memory of the original intent. Nothing carries the thread — so issues fall through it.

You don't pass or fail. You raise your grade.

Aulys scores every frame A–F and explains the why. WCAG is the floor — we show you the ceiling.

Aulys grades run from F, the lowest, to A, the highest.

Color contrast

WCAG 1.4.6 · Level AAA
What
Text needs a 7:1 contrast ratio against its background to meet AAA — 4.5:1 for AA.
Why it matters
Low contrast is the most common barrier on the web. It shuts out people with low vision.

  • In the frame

    Issues get caught in Figma, where the decision is made — not three sprints later in a ticket queue.

  • A grade, not a verdict

    Pass/fail tells you nothing about how close you are. A–F shows the distance to great — and the path.

  • Explains the why

    Every check teaches the rule behind it, so the same mistake doesn't ship twice.

Why now

The European Accessibility Act is no longer a deadline. It’s the law.

Enforcement began June 2025; the first lawsuits followed within months. Retrofitting accessibility under a court order costs weeks. Catching it in the frame costs seconds.

EAA enforcement began across the EU
Jun 2025
First lawsuits filed in France
Nov 2025
of barriers caught by scanners alone — the rest starts in design
~30–40%

Where this is going

One issue, tracked from the first frame to production.

The Figma plugin is where the loop starts — live today. Each surface below joins it as it ships, honestly labelled until then.

  1. Figma pluginCatch issues while you designLive
  2. Code extensionInline WCAG linting in your editorLive
  3. Browser extensionAudit any live site, in the browserIn development
  4. Web ScannerScan staging and productionComing
  5. DashboardOne grade, one history, one teamComing
  6. APIWire the loop into CIComing

We hold ourselves to the grade we sell.

No logos yet, no testimonials — we're early, and we won't fake either. What we can show you is our own work, audited in public.

  • 100 / 100

    Real Lighthouse accessibility score on this site — re-audited every release.

  • WCAG 2.2 AAA

    The standard this site is built to. AA is the legal bar; we design past it.

  • Open method

    Every check we run is documented, with the rule and the reasoning behind it.

Read the accessibility statement · browse the WCAG checks

Know your grade before you ship.

Start in Figma in under a minute. Free, no account — the loop grows from there.

Scan your first frame freeSee pricing