Skip to content

Accessibility, caught before your users do.

Accessibility Inspector continuously scans your React, Vue, Svelte, and Angular apps for WCAG barriers — and turns every finding into a clear, prioritized fix.

Accessibility Inspector dashboard: an overall project score, a score trend over time, open issues grouped by severity, and compliance status.

Supported frameworks & libraries.

Works with apps built using any of the following, whether they render on the client or the server.

React
Angular
Vue
Svelte
Next.js
Nuxt
Astro
Gatsby
Preact
SolidJS
Ember.js
and more

Every finding is actionable.

Each issue arrives graded by severity and tied to the exact WCAG rule it relates to — with the page, the element, and a concrete fix. Your team can act on it right away.

Issues view: findings graded by severity, each mapped to a WCAG criterion and level, with the affected page and CSS selector.

Fix a component once, resolve it everywhere.

Connect your design system and Accessibility Inspector audits the components at the source. One inaccessible button gets found a single time — before it ships into a hundred pages.

Components view: design-system components with their accessibility findings grouped at the source.

Test the journeys people actually take.

Check multi-step flows — checkout, onboarding, sign-up — the way real users move through them, so barriers surface exactly where they would block someone.

User flow audit: the steps of a checkout journey with accessibility issues flagged per step.

Audit-ready reports for the standards that matter.

Turn findings into reports mapped to EN 301 549, the BFSG, Section 508 and VPAT 2.5 / ACR — ready for legal and procurement, in the language regulators actually use.

Compliance reports mapping findings to EN 301 549, the BFSG, Section 508 and VPAT.

More in Accessibility Inspector.

Live scans

Start a crawl and watch routes and states get checked in real time, with a streaming log.

Manual audits

Run structured human reviews alongside the automated results, criterion by criterion.

Team & integrations

Roles, API keys and CI hooks put accessibility into the workflow your team already uses.

Questions, answered honestly.

When can I use Accessibility Inspector?

The tool is in private development and not publicly available yet. Waitlist members get access first, in small batches, before any public launch. There's no fixed date — joining the waitlist is the way to hear first.

What will it cost?

Pricing isn't final yet. It will be announced before launch, and early waitlist members will get preferential early-access terms.

Does it replace a manual accessibility audit?

No — and no automated tool honestly can. Automated checks catch a large share of WCAG issues continuously, between releases. For full conformance you still need human review, which is why Accessibility Inspector includes structured manual-audit workflows alongside the automated scans.

Which standards does it cover?

Findings map to individual WCAG success criteria (levels A, AA, AAA), and reports translate them into the frameworks teams are asked about: EN 301 549, the BFSG, Section 508, and VPAT 2.5 / ACR.

How does it handle single-page applications?

It drives a real browser through your routes, states, and interactions — the way a user actually clicks through a React, Vue, Svelte, or Angular app — and audits every rendered view, not just the initial HTML.

Be first in line.

Accessibility Inspector is in private development. Join the waitlist and be among the first to try it when early access opens.

No spam — one email when early access opens, nothing else.