Private beta · Figma Community, September 2026

Checkers tell you.Legibly fixes it.

An accessibility auto-fix for Figma. Scan a selection or a whole page against WCAG 2.2 AA, then repair every violation in one click, using your own design tokens and never an invented color.

Ahead of the Figma Community launch. No newsletter, no pricing surprises.

Legibly · selection audit
Sample under audit — light theme
2.3:1Fails AA · needs 4.5:1Body text measured against the resolved background: four fill layers, 62% opacity, one gradient.


Unreadable design is now a legal risk.

The European Accessibility Act has applied since June 2025, and ADA lawsuits keep climbing. The most common failure in every audit is contrast, and contrast is decided in the design file, months before an engineer can be blamed for it. Legibly moves the fix back to where the mistake was made.


How it works

Scan. Fix. Verify.

  1. 01

    Scan

    Select frames or a whole page. Legibly resolves the real background behind every layer: fill stacks, opacity, gradients, overlapping siblings.

  2. 02

    Fix

    One click swaps every failing value for the nearest passing color in your own token set. Nothing off-system is ever invented, and one undo reverses it.

  3. 03

    Verify

    The same function that flagged the violation re-checks the fix and reports the new ratio. If nothing can pass, it says so instead of guessing.


Flagging is the easy half

A typical checker

Flags dozens of issues, many of them false positives from gradients and overlaps it cannot read. The fixing is still on you, one layer at a time.

Legibly

Flags only what is provably wrong, then fixes the whole page in one click with your tokens and re-verifies every change before it lands. One Cmd-Z undoes it all.


Coverage

Nine checks, one report

Every one of them decided by math rather than opinion, and each one named in the report whether it passed, failed or was left alone.

  1. 01
    The most common failure in every audit

    Text contrast SC 1.4.3

    Measured against the background the text actually sits on, composited through fill stacks, opacity and gradients.

  2. 02

    Line spacing SC 1.4.12

    Line height under 1.5× the type size, where copy stops holding together at reading distance.

  3. 03

    Target size SC 2.5.8 · 2.5.5

    Controls under 24 by 24, or 44 in mobile mode, measured as geometry with the spacing exception included.

  4. 04

    Icon and border contrast SC 1.4.11

    The parts you have to see in order to act: icon strokes, input edges, control borders.

  5. 05

    Image alt text SC 1.1.1

    A presence check on every image, with somewhere to write the description or mark it decorative.

  6. 06

    Color-only links SC 1.4.1

    Links that differ from the body copy by hue alone, with no underline to carry them.

  7. 07

    Clipped text SC 1.4.10

    Copy that overflows its frame and is simply never read by anyone.

  8. 08

    Field labels SC 2.4.6

    Inputs carrying only a placeholder where a visible label is the requirement.

  9. 09

    Focus states SC 2.4.7

    Components given a hover state and no keyboard focus state to match it.

+

And checks 01 and 04 run again on every theme you ship, not only the one on screen. Dark mode is where fixed contrast quietly breaks.

Run all nine at once

Zero false positives is a design constraint here, not a marketing line. Run it and watch two findings survive the fix: one the math cannot read safely, one Legibly never claims to check.

Legibly · page audit1 page · 214 layers

Nothing has been measured yet. Run the nine checks over a sample page and see what comes back.

Next on the roadmap

  • Design-system governance
  • Brand QA
  • An MCP server for Cursor and Claude Code

Built to be trusted

Private by design

The manifest declares zero network access, and Figma enforces it. Nothing about your file can be sent anywhere, to us or to anyone else.

One source of truth

The function that flags a violation is the function that verifies the fix. A report and the canvas cannot physically drift apart.

Proof, not promises

228 unit tests, including a 686-case properly-composited sweep, and a committed fix-never-fails check on every release.

Legibly is made by Glinc. If you want to know who is writing to your file before you install it, write to hello@legibly.design and you will get a person, not a form.


Pricing

Everything is free during the beta, one-click fixes included. The prices below take effect at the September 2026 Community launch.

Free

$0

forever

  • Scan selections or whole pages
  • Three honest verdicts on every layer
  • Pixel-true deep check for composited backgrounds
Recommended

Pro

$10

per month · billed yearly

$120 once for 365 days — 17% off the monthly rate.

  • Everything in Free
  • One-time payment — nothing renews, nothing to cancel
  • One-click and batch auto-fix with a single undo
  • CSV compliance report export
  • Strict mode: on-system tokens only

Questions, answered

Anything else, ask a person: hello@legibly.design

Does it really fix, or just report?

It fixes. Every violation with certain math gets a repaired value written back to the canvas from your token set, then re-measured. A single undo reverses a whole page.

Will it invent colors outside my design system?

No. Strict mode restricts every repair to your published tokens; when nothing in the set can pass, Legibly reports the gap rather than inventing a shade.

What happens with gradients and image backgrounds?

They are measured where the math is safe and marked “needs review” where it is not. You get the range and the worst case, never a confident number that isn’t one.

Is my file private?

Yes, and not as a promise. The plugin declares no network access in its Figma manifest, so nothing about your file can be transmitted anywhere — check the manifest yourself before installing.

Which criteria do you not check?

Anything that needs runtime behaviour or human judgement: focus order, keyboard traps, semantics, motion. The report names each one so silence is never mistaken for a pass.


Be first in line

Legibly is in private beta ahead of its September 2026 Figma Community launch. Leave your email and we will send you access, and nothing else.