01 ·
Real pull requests
A branch, a diff, a code review. Your team merges the fix on the same cadence they merge everything else — no exceptions, no overlay, no widget.
developer-grade
What Sigil isn't
Not a runtime overlay. Not a widget. No client-side patch.
The defenceless 2025 ADA Title III records — and the new EAA window — don't reward a script that hides barriers. They reward remediation at the source. Sigil fixes the underlying markup, in your repo, like any other code change.
accessiBe et al.
widget
Overlay widgets
Inject a runtime script that rewrites the DOM and overlays an accessibility UI on top of — and over — the original barrier.
no source-level fix
audit-grade code change
code change
Sigil
Identifies WCAG / EN failures in your theme, template, and CSS source. Files a real PR with the diff, evidence, and a criterion-mapped rationale.
merged in your repo
The three pillars
What ships with every PR Sigil opens.
02 ·
VPAT 2.x ACR
A versioned Accessibility Conformance Report, signed and reissued on every deploy. The same artifact procurement and counsel hand to regulators on demand.
audit-grade
03 ·
Evidence trail
axe-core diagnostics, criterion mapping, DOM and AT trace — hashed and stored. When a regulator asks "why is this WCAG pass valid?", the trail is the answer.
tamper-evident
A diagnostic, not a score
Every finding ships an axe-core diagnostic,
a criterion-mapped rationale, and a trace.
When the diff lands, the developer sees the WCAG clause, the offending selector, the computed contrast, and a proposed fix — the same shape as any other inline review comment in your repo.
- axe-core rule with a 1.4.11-mapping citation
- DOM snapshot + assistive-tech trace
- Evidence hash recorded in the VPAT ACR
PR #4471 · commit f1c4…0a92audit-2025-09-14
WCAG 2.2 · 1.4.11 (Non-text Contrast)· axe-core · color-contrastButton uses #6B7280 on #FFFFFF (3.49 : 1).Computed contrast is 3.49 — below 4.5 for text.Suggested fix: bg-[#374151] ⇒ 8.49 : 1
merged
hash 0xC4F0…92A1A code-review cadence
The same four-step shape your team already runs.
No new tool to learn, no new dashboard to host — just PRs your developers review like any other engineering work, with the audit trail attached.
- 01 · SCAN
Theme, template, CSS source — diffed against WCAG 2.2 & EN 301 549.
- 02 · DIFF
One failing criterion at a time, with a proposed change.
- 03 · STAGE
AT trace, axe diagnostics, and a 1.4.11-mapping rationale attached.
- 04 · PR
A branch, a code review, the same cadence your team already uses.
Mapped to a real standard
Compliance, by clause — not by guesswork.
Every PR is recorded under the actual criterion it satisfies. Sigil doesn't ask whether the page is accessible; it cites which axe-core rule, which WCAG clause, which EN 301 549 clause was satisfied, on which commit, by whom.
WCAG 2.2
mappedW3C recommendation · Level A/AA
Every criterion cited per finding, mapped to a precise axe-core rule.
EN 301 549
mappedEU harmonized standard
Mappings carried through to the VPAT — so procurement and counsel can quote the same line.
EAA · ETA
mappedEuropean Accessibility Act · since Jun 2025
Re-issued on every deploy; old versions remain retrievable for an audit window.
VPAT 2.x
mappedSection 508 + ACR
Versioned, re-signed, and downloadable on demand — the artifact regulators expect.
Brief us on the audit
Tell us the standard you need to pass.
WCAG 2.2 conformance, EN 301 549, the EAA, an ADA Title III defence — bring the standard, the deadline, and the regulator. We'll ship a Sigil pilot and an evidence-ledger preview scoped to your stack.