FixProof

How it works

From URL to verified fix in six steps

The same workflow for one website or two hundred.

  1. 1

    Add a client and website

    Create a client, add its public website and confirm you are authorised to test it. FixProof validates the domain and blocks internal addresses.

  2. 2

    Run the scan

    A background worker opens the site three times in an isolated Chromium browser — without interacting with the banner, after rejecting and after accepting — and runs the accessibility and legal-page checks. Progress is shown live.

  3. 3

    Review findings

    Findings land in one inbox with severity, evidence and a label: technical finding, potential risk, or needs legal review.

  4. 4

    Fix with guidance

    Open a finding for a plain-language explanation and a stack-specific fix. Assign it to a developer and track its status.

  5. 5

    Verify

    Trigger a rescan. If the issue is gone, the finding moves to “verified” with the scan that proves it. If it returns later, it is reopened.

  6. 6

    Report

    Generate a branded PDF in German or English with the methodology, findings, tracker inventory and verified fixes.

What automation cannot do. Automated accessibility testing finds only part of WCAG issues, and whether a tracker needs consent can depend on configuration and purpose. FixProof shows the evidence and flags what needs human or legal review rather than guessing.
Start free scan