Loading…
About Verassa
Verassa exists because accessibility has too often been sold on overlays, vanity scores, and badges that don't survive contact with a real disabled user. We're building the opposite: evidence-backed, human-reviewed, verified accessibility operations — with the receipts behind every finding.
Verassa evidence protocol
Evidence
01Screenshot, DOM, replay, and axe baseline captured before decisions.
Judgment
02Reviewer route, rationale, and owner stay attached to lower-confidence work.
Verification
03Re-scan records and disclaimers travel with reportable outputs.
Why we exist
Overlays promised one-line fixes and made real experiences worse. Scanners hand back a number with nothing behind it. Badges get sold without a disabled person ever opening the product. Every shortcut chips away at trust — and disabled people are left with the broken experience.
Verassa is built on the opposite premise: an accessibility finding is only worth the evidence, the human judgment, and the verification behind it. Everything the platform reports traces back to what was seen, who decided what, and whether a fix was confirmed by a re-scan.
What we believe
Every finding carries its basis — screenshot, DOM, interaction trace — so it can be inspected, reproduced, and trusted.
A model can surface a candidate; a qualified person decides. External-reliance outputs carry a named reviewer, never a model alone.
We publish our claim boundaries and refused use cases. The platform does not promise compliance or protection from litigation, because no honest product can.
Standards exist to serve disabled people, so disabled practitioners hold the product accountable — with real authority, not an honorary title.
Accountability, built in
Verassa's advisory board is composed of disabled accessibility practitioners — certified specialists, advocates, and researchers who do this work and rely on accessible products themselves. They are paid: a monthly retainer and equity, not an honorary title and a thank-you.
The board holds veto authority over product features and over marketing claims. A claim the board vetoes does not ship — this page included. When the board disagrees, the dissent is recorded and protected, not smoothed over. A board that cannot safely dissent is not an accountability mechanism.
Held to it, in public
We would rather be held to a published standard than ask you to take our word for it. Our boundaries, refusals, evaluation method, and data-routing controls are all public — so anyone can check the product against what it says.
Exactly what Verassa will and will not say about accessibility outcomes.
The work we turn down — overlays, badge-selling, and documentation without real remediation.
How diagnostic quality is measured before any finding carries full confidence.
What data is processed where — logged, and reviewable after the fact.
Where we are
Verassa is early. The web and web-app audit core is built and in design-partner use; the broader operating system — native mobile, documents, media, integrations, procurement, and more — is committed and on the roadmap, labeled by what has actually been validated, not by what we hope to ship.
We describe the full vision because that is what we are building. We label each surface's status because that is what honesty requires. Both are true at once.
Book a working session with the founder, or read the methodology and claim boundaries and judge for yourself.