Your automated tests passed.
Your users left.
Automated tools catch 30 to 40 percent of accessibility issues. The rest requires keyboard testing, screen reader testing, and voice control testing. Most developers were never taught how to do this.
TestAlly is being built to change that.
What TestAlly does
TestAlly is an open source, AI-powered assistant that analyses your component and tells you exactly what to test manually, step by step.
You paste your HTML, CSS, and JavaScript. You tell it what the component is meant to do. TestAlly runs static checks, cross-references the results against WCAG-backed documentation, and returns one of two things: a clear set of manual testing instructions with “if this, then that” guidance, or a definitive all-clear if no manual testing is needed.
Every recommendation cites its source. TestAlly does not guess. If it cannot back up a claim with a reference, it says so.
Why does this matter?
The ship-fail-fix loop is one of the most expensive patterns in web development, and most teams do not even track it.
A developer builds a component. It passes automated checks. It gets shipped. Weeks later, an accessibility tester flags problems that were invisible to the tooling. Now the developer has to context-switch back into code they have mentally moved on from, understand what went wrong, and fix it under pressure.
You are paying for the developer’s time twice and the tester’s time once, just to arrive at a result that should have been right the first time.
For a small agency with five developers, this pattern quietly burns through tens of thousands of euros every year. At enterprise scale, with separate accessibility departments and cross-team coordination overhead, the waste multiplies fast.
TestAlly gives developers the knowledge to verify their own work before it leaves their hands. That is not just better accessibility. It is better engineering, shorter feedback loops, and healthier project margins.
How it works
1
Add your component, either rendered output or source code.
2
Describe what it is in one sentence. An accordion, a tab panel, a data table.
3
TestAlly analyses the patterns used: animations, transitions, click events, focus behaviour.
4
You get a structured manual test scenario you can follow immediately.
TestAlly is built for developers who want to get accessibility right without needing to become accessibility specialists themselves. It is also useful for QA testers who need structured test scenarios, tech leads who want to reduce rework, and agencies that want to protect their margins by catching problems before they compound.
If you build components for the web and you want to stop shipping code that fails its next audit, TestAlly is for you.
Open source, community driven
TestAlly is a not-for-profit, open source project. It was born at the CloudFest Hackathon 2026 and is built to be extended, challenged, and improved by the community.
The code is on GitHub. The documentation is public. Contributions are welcome, whether you write code, test components, improve documentation, or help translate.