Preflight / Quick Scan

Find the likely friction before the browser goes deep.

Quick Scan is a lightweight preflight for structural and accessibility-oriented signals. Its findings are leads for verification, not proof that a user-facing defect exists.

Structural first pass

Use a compact preflight to surface page structure, obvious interaction, and accessibility-oriented leads.

Leads, not verdicts

Each lead should be independently verified in the browser before becoming a confirmed finding.

Handoff into the run

Relevant leads can be carried into a bounded browser mission with their source and status visible.

A faster investigation start

Use the signal to choose where to look next instead of asking one browser run to inspect everything blindly.

The workflow

From one URL to evidence you can act on.

  1. 01

    Run the preflight

    Point Quick Scan at an authorized target and collect structural or accessibility-oriented observations.

  2. 02

    Select useful leads

    Prioritize signals that match the mission and discard noise before browser verification.

  3. 03

    Verify with evidence

    Use Quick Smoke or Standard Adaptive to reproduce the behavior and attach observed evidence.

Quick Scan and browser testing have different jobs

A preflight can identify clues quickly, but it may not know whether a control is reachable through the actual journey, whether an error is announced, or whether a responsive state breaks under interaction. Browser verification supplies the user-visible context.

Learn when to use Quick Smoke and when to expand into Standard Adaptive.

Keep the handoff honest

Quick Scan leads should retain their source, title, and verification status. A lead marked unverified is not a customer-facing defect until the browser observes the relevant behavior or another authorized review confirms it.

That distinction supports evidence-based triage and prevents a fast preflight from inflating the finding count.

A practical path for Free users

Free users can use the Quick Scan-oriented preflight and Quick Smoke path while Standard Adaptive remains a visible upgrade option. The pricing page keeps the upgrade path explicit instead of hiding capabilities from the Free experience.

Compare Free and Starter access and understand how measured usage works.

Questions teams ask
Does Quick Scan prove a bug?

No. It provides structural or accessibility-oriented leads that should be verified through the browser or an appropriate manual review.

Can Quick Scan replace Quick Smoke?

No. Quick Scan is a preflight; Quick Smoke observes a bounded authorized browser journey. They answer different questions.

Are Quick Scan leads charged as confirmed findings?

No. The handoff preserves an unverified state until the relevant behavior is independently observed or reviewed.

Turn your next deploy into a proof, not a guess.

Start with one authorized URL. Matrix QA walks the journey and returns the evidence your team needs to decide what ships.