Skip to content

Pillar 1 of 4

Accessibility that doesn't hide behind a green checkmark

We run the same axe-core engine that powers Deque's commercial tooling โ€” and we tell you the truth about what automated testing can and can't find.

Why automated scanning is necessary but not sufficient

Accessibility lawsuits in the US increased every year from 2018 to 2024. The vast majority cited issues that an automated scanner would have caught: missing alt text, contrast failures, form labels, broken focus order. Catching those issues early โ€” and continuously โ€” is non-negotiable. But here's the part most vendors won't tell you: axe-core, the engine behind every credible automated accessibility scanner including ours, catches roughly 50โ€“60% of WCAG issues. The rest require a human. We surface that limit clearly. If a vendor claims 100% coverage or an AAA badge from automated testing alone, walk away.

How findings reach your team

Every violation comes with the rule ID, severity, the offending DOM node's outerHTML, the CSS selector, and a short failure summary that tells your engineer what to change. We link to Deque's rule documentation so the developer doesn't have to context-switch. Findings are stored as JSON. You can export them, diff them between scans, or pipe them into a future GitHub Action that fails the build on regressions.

Score interpretation

Each violation is weighted by axe-core impact: critical = 10, serious = 5, moderate = 2, minor = 1. We subtract the total from 100 for the per-page score, floored at zero. A score of 90+ usually means a small handful of minor issues. 70โ€“89 means a real backlog. Below 70 means the page has structural problems and needs a focused remediation pass.

Example finding

serious

Form elements must have labels

Login form on /signin has an email input without an associated <label> and no aria-label. Screen readers announce the field as 'edit text' with no context, and users with cognitive disabilities relying on placeholder text lose the cue when typing.

<input type="email" placeholder="Email" class="form-input" />

Fix: add <label for="email">Email</label> or aria-label="Email".

Scan your site in 60 seconds

25 free credits. No credit card. Real findings on the page you care about.