Technology

Two systems. One writes, the other proves.

One guarantee shapes the architecture: no result is marked verified by the system that produced it.

A tall concrete pillar lit from the side, its edge a clean line between light and shadow.

  1. Crawler

    An edge crawler that sees what users see

    Discovers templates, components and interactive states from the sitemap, the router and scripted navigation. Runs close to the customer’s site, respects robots rules and rate limits, and captures the rendered DOM and accessibility tree rather than raw HTML.

  2. Producer

    Constrained drafting, reviewed by engineers

    Language models draft changes inside a rule set written per defect class: what may change, what must not, and which requirement the change must satisfy. Drafts are reviewed by an engineer before they leave the system. Models are hosted in the customer’s chosen region, and no customer code is used to train any model.

  3. Verifier

    Independent checks, three ways

    Deterministic rules on the rendered page; recorded runs with real assistive technology in a controlled browser farm; and keyboard-only runs. Vision models, run as batched GPU inference, analyse screenshots for contrast on complex backgrounds and flag image alternatives for human review. The verifier has no access to the producer’s reasoning, only to the result.

  4. Evidence store

    Every claim linked to its proof

    Each result stores the method, the artefact (recording, data table or annotated screenshot), the reviewer decision where one was needed, and the version it was tested against. Reports are generated from the store, so they can be reissued for any date, and reviewer rulings feed back into the rules without touching customer code.

Standards

Tested against the standards buyers and regulators cite.

What we test and how we report it is defined by public standards, so a customer, an auditor or a court can repeat our checks.

WCAG 2.2
The W3C guidelines at levels A and AA; the assessment target for every accessibility result.
EN 301 549
The European standard behind the European Accessibility Act and public procurement in the EU.
WCAG-EM
The W3C evaluation methodology: how scope, sampling and reporting are done, so results are comparable.
VPAT / ACR
The conformance report templates US and international buyers ask for, filled from the evidence store rather than by hand.

Security and data

Nothing runs on our customers’ visitors.

  • No script tag, overlay or runtime agent on the customer’s site; products work on code and on crawls of pages
  • Read-only repository access is enough to start; write access is limited to opening pull requests
  • Test accounts, recordings and crawl data are deleted on request; recordings never include real end-customer data when a staging environment is provided
  • Crawls and verification run in the EU or the US, at the customer’s choice; models never train on customer code

Start with Suretto.

Pilot partners get one user journey fixed in their own code and verified separately, at no cost.

Visit Suretto Talk to us