Make your producteveryone can use
Continuous accessibility testing for modern web apps. A research preview — request access to get notified.
For accessibility engineers, and everyone who wants to become one
Made in Europe
Human-led, not just automated
Built by VU Amsterdam alumni
Everything from scan to report
Find issues, trace them to the component, test real user flows, and generate the compliance report you need.
A score per project
Every project is scanned continuously and scored 0–100, so regressions show up week to week.
Findings mapped to WCAG
Each issue is graded by severity and tied to the exact WCAG criterion, page, and element.
Component-level fixes
Connect your design system so a broken component is caught once, not on every page.
User flow testing
Test multi-step flows like checkout and onboarding on a schedule or every deploy.
Compliance reports
Track a target like WCAG 2.1 AA and generate EN 301 549, VPAT, or Section 508 reports.
Structured manual review
Work through every WCAG criterion by hand, feeding the same findings and reports.
Works with your stack
Runs against apps built with any major framework, and connects to the tools your team already uses.
Runs against
Connects to
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.