ZiraDocs Evidence
The linter is the sensor. This is the product: compliance evidence, aggregated over time, that you can hand an auditor.
A red build in CI doesn't close a contract. Whoever signs the annual deal is the person who answers for what the organization publishes — and they need evidence, not a stderr log. Under Apache-2.0 the format and the linter are forkable forever. A service isn't.
What's in the MVP
Compliance evidence, over time In progress
Every finding aggregated per standard — WCAG 2.2 AA, EAA, Section 508 — with the trend an auditor actually asks about: did it get better?
Waivers with an owner and an expiry In progress
Request, approve, record, sign. A waiver's state lives outside the document — it's irreproducible locally, and it's half of what a waiver is worth.
Runs behind your firewall In progress
One signed binary, zero egress. The portal ingests only the report, never the document — over HTTP for connected teams, or by file import for airgapped ones.
Evidence you can hand an auditor In progress
Export as PDF, CSV, or JSON. An artifact that's recovered, not just generated.
Which standards, and on whose authority: the Document Accessibility Compliance Crosswalk maps each check to the clause that backs it — across ADA, the EAA, Section 508, PDF/UA, Brazil, Colombia, and Mexico — quoted verbatim, with the cells we could not defend left empty and explained.
On-prem first, not SaaS with an on-prem option
The buyer with the most at stake can't send documents out of their network. CFR Part 11, pharma, defense, banking — that constraint comes first, so it's what the portal is built around: one signed binary, zero egress, and only the report crosses the boundary.
The accessibility tooling that exists checks a finished artifact after it's been produced — it inspects the output and tells you what's wrong with it. ZiraDocs validates the source before the artifact exists, because underneath there's a format and an AST: what ships can be diffed, versioned semantically, searched by structure, and checked against a declared rule. That's the difference between finding a problem and being able to prove there wasn't one.
For the report formats, waiver schema, and rulepack protocol the portal ingests, see the Evidence Pipeline & Linting docs.
Talk to us
We don't publish pricing until we've closed our first few contracts. If your org needs to prove what it ships is compliant — not just detect where it isn't — tell us about your setup.
hello@ziradocs.com →