Beta Phase • Week #1 Recap

CheckFox is an accessibility auditing tool built to help teams catch issues early and ship more inclusive products. For the past few days, a group of beta testers has been putting it through its paces, and their feedback is already shaping the roadmap. Here's a look at where things stand.

Pro features, now in testers' hands

Everyone who has set up a personal or shared workspace during the beta now has full access to Pro-tier features, including User Journeys and Integrations. That means testers can already push audit results directly into the tools their teams use every day, including Jira, GitHub, and Linear.

The goal is simple: accessibility findings shouldn't live in a silo. They should show up where the work actually happens, next to the tickets and pull requests your team is already tracking.

What your feedback has already changed

Beta feedback isn't just collected, it's acted on. In the past few weeks alone, tester input has led to:

• Clearer messaging during audit creation, so it's easier to understand what's happening at each step
• A reworked "Audit" view, with better ergonomics and a smoother flow
• A round of bug fixes, including missing translations and responsive design gaps

This is the part of beta testing that matters most: real usage surfacing real friction, and a team that fixes it quickly.

Currently in progress

A few features are being refined before wider rollout:

• Workspace management: teams (yes, even a two-person team counts) will soon get more visibility into member roles and easier ways to invite collaborators.
• In-app scanning: the scanner, which combines axe-core with CheckFox's own custom checks, has been rebuilt from the ground up. It's not yet available to testers, but it's coming.

What's being designed next

Several requests from accessibility professionals have pushed CheckFox toward a bigger evolution:

• A public API, so any team or tool can interact with CheckFox from the outside (a real step forward for developer experience)
• An MCP (Model Context Protocol) for people building AI-assisted workflows
• A Skill built on top of that MCP, adding guardrails and a defined methodology rather than leaving AI to freestyle

That last point matters, and it's worth being direct about it: this is not a move to let AI replace human judgment. CheckFox will not use AI by default, and the tool will keep working exactly as it does today for everyone who prefers it that way.

The intent is the opposite of replacement. Many accessibility criteria simply cannot be automated and still require a trained human eye. The goal of these AI-related tools is to support the professionals who already use them, and help them understand where automation is useful and, just as importantly, where it isn't.

Why this matters

Accessibility tooling often forces a tradeoff: either a tool is thorough and slow to integrate into existing workflows, or it's fast but shallow. CheckFox is being built around a different bet: that audits should plug into the tools teams already use, that automation should know its own limits, and that the people doing the work should stay in control of the judgment calls.

The beta is still shaping that direction, one round of feedback at a time.

Want in?

CheckFox is still in beta, and spots are opening up gradually. If you want early access to the tool, including the upcoming API, MCP, and Skill, join the waitlist and I'll be in touch. (form available in the web page footer)