// accessibility testing
Catch accessibility regressions before they ship.
axe-core on every page, severity-ranked, mapped to the exact selector and WCAG criterion — running on every deploy. Optional VPAT export for procurement.
// sample report
What a scan finds on a typical SaaS dashboard.
40 findings across 12 pages · all mapped to WCAG 2.1 AA · 18 have one-click fixes
// what we cover
Beyond axe-core: the full a11y story.
axe-core on every page
WCAG 2.1 A & AA on every scan. Each finding mapped to the exact selector + WCAG criterion.
Severity-ranked report
Critical / serious / moderate / minor. Filter by what blocks your audit, ignore the noise.
Concrete code fixes
Most findings ship with a copy-pasteable fix — corrected ARIA label, suggested contrast value, role attribute.
Keyboard + focus trap check
We crawl using a keyboard, not just a mouse — catches focus-trap bugs and unreachable interactive elements.
Re-runs on every deploy
New regressions caught the moment they ship. Auto-tickets to Jira / GitHub Issues with the WCAG ref attached.
Exportable findings
Export the full findings list (CSV / HTML / PDF) — per-page issues, severity and WCAG criterion — for audits and procurement reviews.
// faq
Frequently asked
Is axe-core enough for WCAG compliance?
axe-core catches roughly 50–55% of WCAG issues automatically — anything pattern-based. The remaining 45% is judgement (e.g. "is this alt text descriptive enough?") and requires manual review. AegisRunner runs the axe-core 55% on every deploy so manual auditors can focus on the qualitative bits.
Does this cover Section 508 / EAA?
Largely — WCAG 2.1 AA is the technical basis for both Section 508 (US federal) and the EAA (EU European Accessibility Act), so the axe-core findings map directly onto the criteria those standards reference. AegisRunner reports against WCAG 2.1 A/AA; formal 508/EAA conformance still needs the manual-review portion that no automated tool covers.
Can I export evidence for compliance audits?
Yes. Export the full findings — per-page issues with severity, the exact selector, screenshots and the WCAG criterion — as CSV, HTML or PDF from any run. It gives auditors and procurement a concrete evidence trail to work from.
Do you test dynamic / SPA content?
The crawler is a real browser — it follows redirects, executes JS, waits for hydration, and runs axe-core on the fully-rendered DOM. Single-page apps (React / Vue / Angular) are tested the same as server-rendered.
Is the mobile experience tested too?
The a11y audit runs against the fully-rendered page, and responsive testing exercises your site at mobile viewports so mobile-web regressions surface as well. For native iOS/Android apps, AegisRunner does functional testing on real devices today — native-app accessibility audits are on the roadmap.
Run an a11y audit on your site — free
First scan in under a minute. You get the full axe-core report with severity ranking + WCAG citations.