---
title: "Prism Wcag Audit"
description: "Prism is a Node.js command-line tool that takes an e-learning package, works out what kind it is, unpacks it, and runs accessibility checks over the HTML inside — producing an HTML, Markdown and JSON report per package and a rollup across a whole library. Underneath it is axe-core, with Playwright for checks that need a rendered page and its own rule modules named after WCAG success criteria. There is also an optional rebuild mode that applies mechanical fixes and writes a patched zip, with the more speculative transforms staged behind an explicit approval step."
canonical_url: "https://scorm-tools.com/tools/prism-wcag-audit"
last_updated: "2026-10-31T10:22:01.205Z"
---

Prism is a Node.js command-line tool that takes an e-learning package, works out what kind it is, unpacks it, and runs accessibility checks over the HTML inside — producing an HTML, Markdown and JSON report per package and a rollup across a whole library. Underneath it is axe-core, with Playwright for checks that need a rendered page and its own rule modules named after WCAG success criteria. There is also an optional rebuild mode that applies mechanical fixes and writes a patched zip, with the more speculative transforms staged behind an explicit approval step.

The idea is sound and the gap is real. Accessibility tooling assumes a URL; e-learning content arrives as a zip full of frames, and auditing a library of a few hundred legacy packages by hand is genuinely expensive. Detecting SCORM 1.2, SCORM 2004, AICC, cmi5 and xAPI packages and iterating their pages is the right shape for that problem.

Judge the maturity honestly, though. The repository was created in April 2026, has around three dozen commits, no stars, no forks and no tagged releases, and its README is written around one firm's consulting workflow — engagement folders, consultant-hour scope estimates, a named house compliance baseline. That is a single-author tool shared publicly, not a community project. The MIT licence is declared in `package.json` rather than a LICENSE file.

Worth reading if you are building your own package auditing; worth trialling on a copy of a real library before you would depend on its numbers.