Know your design system passes — before anyone asks.

What it changes

• Catch it before it ships.

  Every PR gets a check: new accessibility blockers fail the build.

  A dev opens a PR, the check goes red: Button — focus not visible (WCAG 2.4.7). They fix it in ten minutes, before review, before release.

  Shipping day stops being the day you find out.

• Fix once, fixed everywhere.

  Findings map to components, not pages.

  One fix in Input clears the finding from every screen that uses it — you watch the number drop across the whole product.

  Your design system finally works the way you promised it would.

• An answer, not an archaeology project.

  One click: current EAA readiness report, mapped WCAG → EN 301 549 → EAA.

  Legal asks on Tuesday. You export the report on Tuesday. It’s dated this morning.

  The compliance question stops being scary. It’s just a button.

This site passes its own scan

EAA enforcement, so far

1. Apr 2019

   The European Accessibility Act is adopted as EU Directive 2019/882.

   EUR-Lex (opens in a new tab)

2. Jun 28, 2025

   The EAA applies. Products and services placed on the EU market must be accessible.

   European Commission (opens in a new tab)

3. Jun 4, 2026

   A French court orders Carrefour to make its site and app accessible within six months — €500 per day past the deadline.

   Law Office of Lainey Feingold (opens in a new tab)

4. H2 2026

   The Dutch regulator ACM moves from monitoring to formal enforcement of the EAA for e-commerce.

   Deque (opens in a new tab)

Included with every plan

• The EAA Readiness Checklist

  A two-page PDF that maps EAA requirements to decisions your team can actually make.

  Included because without it, you don’t even know what to ask.

• The CTO One-Pager

  A ready-made business case with numbers: audit cost vs. subscription vs. the risk of fines.

  Included because your boss won’t buy a link to a landing page — one page can convince them.

• The Component Fix Playbook

  The ten most common component failures, each with a ready fix pattern — in code.

  Included because a finding without a fix is just a guilty conscience.

The honest part

“Of the 55 WCAG 2.2 AA criteria, 4 can be verified by a machine end to end. 25 more can be checked in part. The remaining 26 need a human — so anyone promising 100% automated compliance is lying to you. Passa11y automates what can be automated, brutally well — every component, every commit — and gives your team guided checklists for the rest. You always see both numbers: what’s verified by machine, what needs a human. An absence of findings is never presented as proof of conformance. That’s what an honest compliance tool looks like.”

FAQ

1. We already tried an accessibility scanner and drowned in false positives.

   Every finding is machine-verified, not guessed — that’s the whole point of showing you both numbers instead of one score. Between scans you only see what’s new, never the same 400 issues again: baseline & diff between scans, not a wall of shame every Monday. At launch, npx passa11y scan will run locally, free, no signup — try it on your own code before you pay anything. Waitlist members get there first.

2. We don’t have capacity to fix what you find.

   Findings don’t arrive as a bare list. The Component Fix Playbook gives the ten most common component failures, each with a ready fix pattern in code, and findings are ranked by compliance impact — not alphabetically — so the order to fix things in is already decided. What machines can’t check doesn’t get ignored either: guided manual-review checklists give it an owner and a date, not a footnote.

3. Is this enough for EAA compliance?

   About half of the 55 WCAG 2.2 AA criteria can be checked by machine — 4 fully, 25 in part. The other 26 need a human, so anyone promising 100% automated compliance is lying to you. Passa11y automates what can be automated and gives your team guided checklists for the rest — every finding is labeled verified by machine or needs human review, never blended into one score, and an absence of findings is never presented as proof of conformance. The report is a readiness report, not a certificate — it tells you where you stand, not whether a court would agree, and it isn’t legal advice.

4. We use Vue / web components / old Storybook.

   Passa11y is built for product teams with a design system in Storybook (v7+). No Storybook yet? Then we’re honestly not a fit — Passa11y scans your Storybook build.

5. Security won’t let a scanner near our code.

   Open-source CLI · results-only upload · EU-hosted. Passa11y scans the static Storybook build inside your own CI — your code never leaves your infrastructure, only the results do. Security won’t block this purchase.

6. When can I get it? What does early access mean?

   There’s no public launch date yet — Passa11y is being tested privately with real design systems first. Joining the waitlist means you get access before anyone else, at founding price, the moment that private testing wraps. We never promise a date we don’t have.

7. What counts as a component?

   A unique component in your Storybook (by title path). Stories and variants don’t count separately — a Button with 12 stories is one component. If you go over your limit, nothing breaks: scans keep running, you get 30 days to upgrade.