Accessibility Is Not a Plugin. It Lives in the Source.
Vigil runs a nightly axe-core scan for WCAG 2.2 Level A and AA on live Forged Sites. Coverage is partial. Staff review the results at least monthly. A clear scan is not a compliance certificate.
Before launch, a staging check targets zero failed Lighthouse accessibility audits and zero axe WCAG 2.2 A/AA violations, plus a human review of what scanners cannot judge.
Meet Vigil
The nightly accessibility scan, the monthly staff review, and the check we do before our own changes publish.
Accessibility Is Easy to Get Wrong
Broken contrast, missing alt text, and skipped headings still ship. An overlay widget can sit on top of that markup and leave it broken. A scanner can clear the rules it knows while manual criteria stay unassessed. Vigil is the accessibility work we actually run, and a green scan is not a legal certificate.
What Most Businesses Are Dealing With:
An accessibility overlay that sits on broken markup and does not repair the source underneath
Contrast, alt text, labels, and heading order left for later, then forgotten after launch
A green automated score treated as if every manual criterion had been judged
A client design choice that conflicts with WCAG, then described as if the page still conformed
Vigil's Promise: Live Forged Sites get a nightly axe-core scan for WCAG 2.2 Level A and AA, with partial coverage, and a staff review at least monthly. Before launch we run a staging check and a human review. Failures in our own work are fixed free. If a client design choice conflicts with WCAG, we record an exception and we never call that choice conforming. Vigil does not certify compliance.
A Nightly Scan. A Monthly Review.
Vigil checks accessibility. The scan runs at about 01:15 ET. The usual sample is home, contact, the shallowest pages, and the newest post. It is not a publish gate, and a clear scan is not a compliance certificate.
Accessibility (WCAG 2.2 A and AA)
Nightly axe-core scan for WCAG 2.2 Level A and AA on every live Forged Site
About 8 pages per site, on desktop and mobile, with partial coverage
Assets served from other domains are not scanned
Pre-launch staging check with a human review of what scanners cannot judge
Accessibility review of our own changes before they publish
DraftDash remediation pass for alt text, heading order, link text, inline contrast, and table headers
Staff review at least monthly
Free fixes for failures in our own work. Recorded exceptions when a client design choice conflicts with WCAG
Them vs. Us
An overlay widget compared with the accessibility work Vigil actually does.
| Capability | Overlay Plugins | Vigil |
|---|---|---|
| Accessibility | JavaScript overlay on top of broken source | We fix accessibility in the source. We do not add an overlay widget. |
| Ongoing Verification | Overlay remains a script on top of the page | Nightly axe-core scan, staff review at least monthly |
| What a Clear Scan Means | A script layered on the existing page | Automated rules on the pages tested. Manual criteria can remain open. |
How Vigil Works
Checked before launch, scanned each night, and reviewed before our own changes publish.
Before Launch
Before a Forged Site launches, we run a staging check to zero failed Lighthouse accessibility audits and zero axe WCAG 2.2 A/AA violations. A person reviews what the scanners cannot judge.
After Launch
Every night, around 01:15 ET, Vigil scans every live Forged Site with axe-core. About 8 pages are checked, on desktop and mobile. Coverage is partial. Staff review the results at least monthly.
Our Own Changes
Changes we make are reviewed for accessibility before they publish. DraftDash posts get a remediation pass for alt text, heading order, link text, inline contrast, and table headers. Failures in our own work are fixed free. A client design choice that conflicts with WCAG is recorded as an exception and is never called conforming.