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.

Standards coverage

WCAG 2.2 A/AA, and the AAA criteria that apply

The platform evaluates against WCAG 2.2 Level A and AA — the courtroom and procurement baseline — plus the AAA criteria applicable to a given surface. Four profiles let you choose the bar.

Book a demoRead the methodology →

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.

The baseline

WCAG 2.2 Level A and AA is the working baseline

WCAG 2.2 Level A and AA is the benchmark that matters in practice. It is the standard referenced by Section 508, by EN 301 549, and by the courts in accessibility litigation. WCAG 2.2 added nine success criteria to 2.1, covering focus appearance, target size, dragging alternatives, consistent help, and redundant entry.

The platform evaluates against WCAG 2.2 A and AA by default, and the 2.2 additions are evaluated, not skipped.

Standards profiles

Four standards profiles

A profile sets which success criteria a scan evaluates against. You choose the bar; the platform does not pick it for you.

  • 01

    Legal Baseline

    WCAG 2.2 Level A and AA only — the criteria used as the benchmark in litigation and in procurement (Section 508, EN 301 549). The narrowest, most defensible scope.

  • 02

    Core A/AA

    The full set of Level A and AA criteria, evaluated thoroughly. The default profile, and the right starting point for most teams.

  • 03

    Accessibility Excellence

    Core A/AA plus the AAA criteria that apply to a given surface, plus established best practice — for teams going past the baseline.

  • 04

    Customer-Selected

    A profile you define: a specific subset of criteria for an internal policy, a contractual requirement, or a procurement standard.

Applicable AAA

Applicable AAA, not blanket AAA

WCAG Level AAA was never designed as a whole-site target. The W3C itself does not recommend AAA conformance as a general policy, because some AAA criteria cannot be satisfied for all content. So the platform evaluates the AAA criteria that apply to a given surface; it does not market full-site AAA conformance.

For the same reason, the platform does not describe a site as compliant or conformant. It reports posture, findings, and evidence. A standard is something a qualified reviewer attests to — not an output a scan can hand you.

Read the methodology →

Choose the right bar for your audit

A demo walks through the standards profiles and how scope is set.

Book a demoView pricing