axe-core under the hood
Findings come from the open-source rule engine your developers already trust. No vendor scanner; no false-positive arguments; the same output as `axe.run()` from a unit test.
For engineering teams
Accessibility your engineers won’t ignore.
AccessGlade runs the same engine your developers already use locally, ships findings in a standard format, and pushes them into the queue you already triage from. No proprietary detector. No new place to babysit. No PDF.
You've seen this movie before
PDFs don’t fix bugs.
You inherit a 47-page accessibility audit from a consultancy. It lists 312 issues across 208 pages — most of which are the same broken header repeated. Your team gets handed a CSV, files a few tickets, and the rest evaporates. The score on the dashboard stays at 87% forever; the 13% never moves.
What you get
The bits that matter for your role.
EARL JSON-LD output
Findings persist as W3C‑standard EARL assertions. Audit history is yours, not ours; export anytime; portable to any compliance workflow.
Linear-style queue
j/k to move, x to select, e/r/i to set status, ↵ to open. Bulk-resolve 50 issues in 5 seconds. Saved views you can share via URL. Built like the bug tracker you actually use.
Push to Jira / Linear / GitHub
One-way push from a finding to your tracker so the fix happens where engineers already work. Jira, Linear, and GitHub today; more on request.
API + Chrome extension
POST EARL findings to /api/ingest from your CI, scheduled jobs, or scanners we don’t natively support. The Chrome extension uses the same API — sign in, audit any page, sync.
Per-tenant Row-Level Security
Tenant isolation enforced at the PostgreSQL layer, not in app code. A finding from org A is mathematically unable to surface in a query from org B. Verified with integration tests, not promises.
Coverage
- WCAG 2.1 / 2.2 AA + best-practice rules
- EU-West data residency by default
- Headless Chromium (real DOM, JS executed)
- Component rollup across pages