LiveAudit

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
MITself-hostedRust → WebAssemblyno runtime framework
Screenshot of the LiveAudit demo page with the inspector layer open, 42 findings. Numbered markers sit on the defective elements of a reservation form: an image without alt text, two inputs without labels, a duplicated id, a heading that skips a level, a table without headers. The dark sidebar counts 16 FAIL, 4 REVIEW, 22 UNTESTED and 0 PASS over 209 scanned nodes and 56 rules.
The demo page with the inspector layer open: markers on the elements, the sidebar with the four states.
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.

LiveAudit demo: numbered markers on faulty elements of a form fragment, on the right the sidebar with 16 FAIL, 4 REVIEW and 21 UNTESTED, 56 rules ran
Markers on the element, the sidebar beside it. Demo page of the documentation, version 0.2.0.
LiveAudit demo: sidebar with counts per state and the manual checklist, with items such as alternative texts and colour as the only cue
What cannot be decided automatically appears as UNTESTED on the manual checklist.

What makes it different

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.

  1. Install it: npm install @casoon/liveaudit — the package holds inspector.js and a11y_wasm_bg.wasm, built and ready.
  2. Copy both files next to each other into your own site and add the script tag. The module loads its WebAssembly from beside itself.
  3. Open the page with ?liveaudit. Without the flag the script registers nothing, creates no global and loads no WebAssembly.
  4. Call LiveAudit.show() from the console or from your own toolbar.
index.htmlhtml
<!-- 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 →

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.