Open-source accessibility checks for your CI and your coding agent
Equall runs multiple accessibility engines on your source code, locally or in CI, and combines the results into one clear WCAG report. Every issue is deduplicated and fingerprinted, creating an audit trail of when it appeared, when it was fixed, and what each change introduced.
Example output of equall scan: 3 WCAG violations (1 critical, 2 serious), 1 best-practice recommendation, score 78.4 out of 100, 23 criteria supported, 3 not supported, 29 not evaluated.
An accessibility audit tells you where you stand at one point in time. But every release can introduce new issues or bring old ones back. Equall brings accessibility testing into the development workflow, with support for standards including WCAG 2.1, WCAG 2.2 and EN 301 549, so teams can catch regressions as the product evolves.
Follow accessibility through every change
An accessibility audit tells you where you stand today. Equall helps you keep accessibility on track as your product changes.
Scan
Run multiple accessibility engines and combine their findings into one clear report across WCAG and accessibility standards.
- CI gate
- Exits 1 below your minimum score
- Multiple engines
- One report across WCAG and accessibility standards
Review
See what was tested automatically, what changed since the last scan, and what still requires human judgement.
- One verdict per criterion
- Tested, failing, or needs a human
- Since the last scan
- What changed, what still needs review
Fix
Focus on accessibility issues introduced by the change you are working on, instead of resurfacing the entire existing backlog.
- New issues
- Introduced by this change
- Legacy issues
- Already at main, not yours today
- Not statically testable
- Run the rendered check
Track
Follow every issue across scans, releases and fixes, with a consistent fingerprint that keeps its history intact.
- Fingerprint
- Survives reformats
- Events
- Detected, fixed, reopened
Know what changed between scans
Equall gives every issue a stable fingerprint, so the same finding can be identified across code changes. Export scan results to JSON and use them in CI to see what was tested, what failed and what still needs manual review.
Changelog
- Write the JSON report to a file, keeping the normal output
- A path that does not exist now exits 2
- CI can now fail only on what a change introduces
- Same content as 0.3.0, with one change to how axe-core is injected (below). Both versions install identically; 0.3.1 is the recommended one. Everything listed under 0.3.0 below ships in 0.3.1