Every finding, proven.

§ 01 · The deadline

A compliance deadline with a budget attached.

§ 02 · Why probe

For a bank, AI usually means risk. probe is built the other way.

An AI that invents a legal artifact is a liability. One that proves every claim it makes is the opposite — the tool you can hand to compliance, to legal, to an auditor. probe is built to be shown, not trusted on faith.

§ 03 · The method

Scan. Reproduce. Prove.

1. 01

   Scan

   Automated checks across accessibility, SEO, Core Web Vitals, layout integrity, and consent — for a whole target.

2. 02

   Reproduce

   A headful browser re-runs each failure on the live page, desktop and mobile, and records it.

3. 03

   Prove

   Video walk-through, screenshots, the DOM, and the execution trace, captured and bound to the finding.

4. 04

   Report

   Prioritized findings, exportable to SQL. VPAT / ACR to EN 301 549 on request.

• Accessibility — WCAG 2.1 AA
• SEO — crawl & index health
• Core Web Vitals
• Layout integrity
• Consent & cookies

§ 04 · The use cases

One engine. Every pass a person would make.

Each of these is the same scan, reproduced and proved the same way. What changes is what we look for, and who reads the result.

1. 01

   Accessibility & compliance

   The audit banks need on file: EU under the Accessibility Act and EN 301 549, US under the ADA. Every failure reproduced, with a VPAT / ACR you keep.

   Public sites · apps · portals

2. 02

   Manual QA, run by machine

   The pass a tester does by hand each release — every screen, every state, desktop and mobile — replayed on demand, with a recording of each step.

   Before every release

3. 03

   Automated testing

   Recorded flows become suites that keep running. When one breaks, the failure arrives with the video, the DOM and the trace attached.

   In your pipeline

4. 04

   Design & layout analysis

   Layout integrity across breakpoints: overflow, collision, contrast, spacing that has drifted from the design system.

   Every breakpoint

5. 05

   User-experience research

   Where real flows stall — focus traps, dead ends, forms that reject without saying why — shown as a walk-through, not a heatmap.

   Whole journeys

6. 06

   Security surface

   The exposure visible from the browser: headers, consent and cookies, mixed content, data left in the DOM. Your properties, with your authorization.

   Your own estate

§ 05 · The index

The bank accessibility index.

We are auditing the public estates of the largest retail banks in the EU and the US against the same standard, with the same evidence we hand a client — and publishing the result by vertical. Each position will carry the bundle that proves it. No such ranking exists today.

In progress. Tell us which peer set you want first. Ask for the index →

§ 06 · The limits

What automated scanning can’t catch.

Automated scanning catches a fraction of accessibility issues — roughly a quarter to a third. probe is built as evidence plus prioritized findings, with expert review where defensibility demands it. It is an audit, not an overlay or a quick-fix widget. The difference is that you can prove every line.

probe runs against properties you own, or that you are authorized to audit, and it reads what any browser can see. It does not circumvent access controls, defeat protections, or collect anything from behind a login it was not given. An audit you could not show the other side is not an audit.