Skip to content
Accessibility testing tool

Make your producteveryone can use

DeepSpectrum Accessibility Inspector is a research preview. Submit your business interest to get notified.

Accessibility Inspector dashboard: quick access shortcuts, open issues by severity, a list of projects with their scores, and a score trend chart.

For accessibility engineers, and everyone who wants to become one

Made in Europe

Human-led, not just automated

Built by VU Amsterdam alumni

From finding to fix

Trace every issue to the component that caused it, test it across the flows people actually use, and turn it into a report you can hand off.

A score per project

Every project gets scanned continuously and scored on a 0-100 scale, so you can see accessibility improve or slip week over week instead of finding out at the next audit.

Projects overview: each project scanned continuously with an accessibility score and its trend over time.

Findings mapped to WCAG

Each issue arrives graded by severity and tied to the exact WCAG rule it relates to, with the page and element it occurs on. Assign it to a teammate and track it from open to resolved, right alongside the rest of your team's work.

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

Component-level fixes

Connect your design system - a private npm registry, components/ui, shadcn - and every component gets its own pass/fail status, occurrence count, and fix guide. 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.

User flow testing

Check multi-step flows - checkout, onboarding, sign-up - step by step, on a schedule or on every deploy. When a step fails, like a modal that doesn't trap focus, you see exactly which step and why.

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

Compliance reports

Set a conformance target - WCAG 2.1 AA, for example - and track criteria met against it. Generate the report someone actually asked for - EN 301 549, VPAT 2.5/ACR, Section 508, AODA - and check statement readiness before you send it.

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

Structured manual review

Work through every WCAG criterion one by one, marked passed, failed, N/A, or still to review, with an overall percent reviewed. Automation catches a large share of issues, but full conformance still needs this kind of human judgment - and it feeds into the same findings and reports as the automated scans.

Manual audit view: a structured human review of WCAG criteria alongside the automated findings.

Works with your stack

Runs against apps built with any of the following frameworks, and connects to the tools your team already uses.

React
Angular
Vue
Svelte
Next.js
Nuxt
Astro
Gatsby
Storybook
GitHub
GitLab
Bitbucket
CI/CD
Jira
Linear

Questions

When can I use Accessibility Inspector?

Accessibility Inspector is currently a research preview and not publicly available yet. There's no fixed launch date - joining the waitlist just means we'll email you as soon as you can sign up.

What will it cost?

Pricing isn't final yet. It will be announced before launch - waitlist members will simply be the first to hear when it is.

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, Section 508, VPAT 2.5 / ACR, and AODA.

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.

How is this different from a tool like axe-core?

Axe-core and similar scanners check the first render of a page. Accessibility Inspector drives a real browser through your actual routes and states, tests components at the design-system level so a fix applies everywhere at once, and covers multi-step user flows like checkout - on top of the same rule-based checks.

Submit your business interest

Accessibility Inspector is currently a research preview. Leave your email and we'll let you know the moment it opens up.

One email when it's ready - no spam.