A reproducible worked example

How a Sigil pull request lands.

Sigil scans your theme, template, and CSS source, files a real pull request against your own repository, and pairs every finding with the axe-core diagnostic and the WCAG / EN 301 549 criterion map regulators expect. Below is a single, reproducible example — one diff, one diagnostic — driven by the in-repo scanner.

Back to homeSee the methodology →

The shape of every PR

Three steps. One PR. End to end.

  1. 01 · Scan

    The scanner walks your theme, template, and CSS source, applying each WCAG / EN 301 549 rule to every line. Every match becomes a Finding with a deterministic, sha-256-hashed evidence trail.

    See how the scan runs →
  2. 02 · Diff

    Each finding becomes a remediation hunk: the original line and the proposed fix, side by side. The diff is the artifact your team merges — like any other code change.

    Sample diagnostic trace →
  3. 03 · Evidence trail

    axe-core diagnostics, criterion mapping, and the SHA-256 evidence hash are recorded against the commit. Regulators, counsel, and procurement see the same artifact.

    How this maps to VPAT / EAA →

Deeper sister · /methodology

For the citation-grade artifact procurement and counsel read — the reference-table row shape, the axe-core diagnostic format, and the PR / commit-message convention Sigil uses — see /methodology.

Open /methodology →