CASOONOpen Source
Accessibility inspection where the page actually runs.
One script tag on your own site, and findings appear on the affected element — in the page's real state, after every script, embed and client-side render has had its say.
npm install @casoon/liveaudit
- gzipped JavaScript, layer included
- 18.8 kB
- gzipped WebAssembly, the whole rule set
- 80.9 kB
- states a finding can have — never a score
- 4
- attributes written to the inspected page
- 0
The inspector on a real page
Captured on 2026-10-14 on the demo page, which deliberately contains a fragment with known defects.


What makes it different
Findings on the element, not beside it
A report tells you that an image on some page has no alt text. The inspector layer puts the finding on that image, in the state the page is actually in — after hydration, after the third-party embed loaded, after the cookie banner appeared.
Two axes, never a percentage
Outcome says how certain the statement is: FAIL proven, REVIEW suspected, PASS passed, UNTESTED not decidable by machine. Severity says how much it weighs. A single number would hide exactly that difference, so there is none.
"Not testable" is not "passed"
A contrast rule without rendering access reads like a passed check in most tools. Here it is listed as not run, with the reason. Where it runs but cannot decide — text on a gradient has no single background colour to measure — it reports UNTESTED instead of a verdict.
It inspects. It does not repair.
No data attributes, no inline styles, no rewritten markup: the layer lives in its own host element and positions itself from measurements it reads. This is deliberately not an accessibility overlay: it makes no claim to repair anything.
One rule set, three surfaces
The rules live in the shared Rust core in barrierlab, which also drives astro-post-audit at build time and auditmysite in CI. A finding carries the same rule id in all three. That reuse — not speed — is why the core is Rust.
Quickstart
LiveAudit is self-hosted: you install it, copy two files into your own project and serve them from your own domain. A centrally hosted script would make someone else's domain a permanent dependency of your site.
- Install it:
npm install @casoon/liveaudit— the package holdsinspector.jsanda11y_wasm_bg.wasm, built and ready. - Copy both files next to each other into your own site and add the script tag. The module loads its WebAssembly from beside itself.
- Open the page with
?liveaudit. Without the flag the script registers nothing, creates no global and loads no WebAssembly. - Call
LiveAudit.show()from the console or from your own toolbar.
<!-- your own copy, on your own domain -->
<script
type="module"
src="/vendor/liveaudit/inspector.js"
></script>On npm, still self-hosted
@casoon/liveaudit carries the two built files, not the sources. Copy them from node_modules into your public directory at build time; updating is an ordinary dependency update, and nothing is loaded from anyone else's domain.
If your site has a strict Content Security Policy
Instantiating WebAssembly needs wasm-unsafe-eval inscript-src. Without it the inspector fails with an error that names the missing directive instead of failing silently.
New in v0.2.1
Changelog →- Releases: the package is published from a release workflow with npm Trusted Publishing (provenance, no stored token), after approval in the
npmenvironment.
Frequently asked questions
Is LiveAudit an accessibility overlay?
No. It inspects; it does not repair. Nothing about the page is modified — no data attributes for element identification and no inline styles on the target, just an in-memory mapping to a shadow-root layer drawn on top.
Can I load it from a CDN?
No, deliberately not. LiveAudit is self-hosted: you serve inspector.js and a11y_wasm_bg.wasm from your own domain, so a centrally hosted script never becomes a permanent dependency of every site that embeds it.
Why isn't contrast checked by default?
Contrast needs a second, rendering-aware pass that costs 1.9x to 4.6x the plain collector, so it stays opt-in via scan(root, { rendering: true }). Without it, contrast rules are recorded as not run, never as a silent PASS.
What happens with things no rule can decide, like alt text quality?
They become a checklist, not silence: criteria such as captions, alt text quality or time limits appear once per page as UNTESTED under manual/* whenever the page contains something they apply to.