Skip to main content
Design-partner cohort open · evidence-backed accessibility operationsApply
Verassaerassa
MethodologyPricing
Sign inBook a demo
Loading…
Verassaerassa

Evidence-backed digital accessibility operations with qualified human review, careful claims, and exportable proof.

Private beta

Apply to evaluate the platform →

Platform

  • Overview
  • How it works
  • Methodology
  • Evidence packages
  • Pricing

Workflows

  • Product and engineering
  • Legal and compliance
  • Accessibility consultancies
  • Ecommerce

Trust

  • Trust Center
  • Security
  • Privacy
  • Claim boundaries

Learn

  • Docs
  • Research
  • Changelog
  • State of Web Accessibility

Company

  • About
  • Contact sales

AI-augmented accessibility evaluation. Findings accelerate audit production but do not replace qualified-reviewer attestation. No scan is a conformance guarantee.

  • Policies
  • Accessibility statement
  • Refused use cases

© 2026 Verassa. Evidence-backed accessibility operations.

Methodology

Download the full methodology

The complete methodology — standards profiles, scan modes, confidence scoring, evidence, reproducibility, and the trust boundary. It is also readable in full on this site.

Read it on the site instead →

Verassa evidence protocol

  1. Evidence

    01

    Screenshot, DOM, replay, and axe baseline captured before decisions.

  2. Judgment

    02

    Reviewer route, rationale, and owner stay attached to lower-confidence work.

  3. Verification

    03

    Re-scan records and disclaimers travel with reportable outputs.

What's in the document

The methodology, in one PDF

Standards profiles & scan modes
Legal Baseline, Core A/AA, Accessibility Excellence, Customer-Selected — and when each fits.
Confidence scoring & expert review
How a finding earns full confidence, and what routes to a reviewer below the gate.
Evidence pipeline & reproducibility
What every finding carries, and how a scan stays re-runnable against the same configuration.
Trust boundary & model routing
What stays in the trust boundary by default, and how a routing decision is policy-enforced and logged.

The same document is readable in full on the site — no email required to evaluate it.