DevAlly
AI powered accessibility compliance for teams who ship fast
375 followers
AI powered accessibility compliance for teams who ship fast
375 followers
Whether you’re starting or scaling your accessibility compliance program, DevAlly helps product teams automate and streamline compliance under EAA, ADA and Section 508.
This is the 3rd launch from DevAlly. View more
DevAlly AI Agent
Launching today
Describe a user journey in plain English. The DevAlly Agent navigates your app and records a user journey, saving hours of engineering work. The DevAlly platform then audits each stage of journey against the WCAG criterion and suggests fixes for every issue.
Constant changes, requires consistent accessibility monitoring. Our agent does it for you.
Free
Launch Team / Built With
Hey Product Hunt!
Cormac here, CEO and co-founder of DevAlly. You might remember us from May, when we launched DevAlly, and July, when we brought accessibility compliance into your editor with our MCP. Thank you for the support both times. It shaped what we built next.
Here's what we kept hearing. Scans are good at checking pages, but users actually perform journeys. They sign up, check out, book an appointment, reset a password. The barriers that stop a disabled person from finishing a task commonly live between the pages. Think of the modal that traps keyboard focus, the error message a screen reader never announces, the session timeout nobody can extend, or the payment step that only works with a mouse.
WCAG already recognises this. Its conformance rules say that if a page is part of a process, every step of that process has to conform. A checkout that's 90% accessible is a checkout someone can't finish. Yet these flows are the least tested part of most products. Testing them has meant stepping through every click by hand, or writing scripted tests that break every time the UI changes. So teams test the homepage and a handful of templates, and the journeys that matter most go unchecked.
That's what we set out to change with DevAlly Agent and natural language workflows.
You describe the journey in plain English, something like "go to the contact page, fill out the form and submit it". DevAlly Agent walks through your site the way a user would. It handles things like cookie banners, asks you for sign-in details if it needs them, and records the journey. You review the steps, watch a replay of what it did and confirm it's right, because you know your product better than any AI does. There's a human in the loop all the way.
From then on, DevAlly audits that journey. It brings back every issue with the WCAG success criterion it fails and a recommended fix, which you can push straight to your editor through the DevAlly MCP. Every time you ship, the journey can be checked again. A release that breaks checkout for keyboard users gets caught before your customers find it.
And yes, the DevAlly Agent chat works with a screen reader. It would be a bit awkward otherwise.
It's in beta and open to every DevAlly user, including our Free plan. There's no waiting list.
Which journey would you check first? @darrenbritton(CTO) and @bruno_walraven(Head of Product) are here all day for the hard questions.
@darrenbritton @bruno_walraven @cormacchisholm Most teams test the homepage and a few templates, then hope checkout is fine. A checkout that's 90% accessible still blocks people, so testing whole journeys makes a lot of sense. Good that a person reviews the steps too
Congrats on the launch team! Does it replace a human audit? Or how does the agent work with a user?
@charlotte_mattu1 Thanks Charlotte! Short answer, no, it doesn't replace a human audit (and we'd be wary of any tool that claims to). Our Workflows are best thought of as a scoping and automation pass. You, as the domain expert on your product, create workflows with the agent that represent a real user journeys in your product. We scan those workflows for accessibility issues, and they also become the basis for any future human audits run through the platform.
Automation catches a lot, but questions like whether alt text is actually meaningful or whether a flow makes sense with a screen reader still need a person. So the agent handles the repeatable checks on every run deterministically, and when an auditor picks it up they start from your real user journeys with the automated findings already in place, rather than from scratch.
how does the agent handle journeys that include things like popups, dropdowns or content that only appears after a user interaction?
@jharkhandi_chora1 Great question! Yes, the agent captures every step of a user journey, including modals, dropdowns, error states and anything that only appears after an interaction. It works through your product in a real browser, so if a person can get to it, the agent can too.
Hover-only menus, drag and drop, and iframes aren't supported yet. If a journey needs one of those, the agent tells you upfront rather than recording something that quietly breaks.
If you’d like to give it a go you can sign up for our free tier and have the agent record a journey through your own product!
@cormacchisholm @darrenbritton Testing the whole journey is where the nasty accessibility issues usually hide. Really like this approach.
I like that people can review the recorded journey before the checks run. It gives them a chance to catch a wrong turn before it becomes a test they rely on. Congrats on the launch!
Great idea and congrats on the launch! Accessibility audits and corrections take up quite a bit of time, so I appreciate something that does at least part of the work.
@mad94 Anything to help make accessibility easier for folks. Would love our feedback on the product, if you're up for it?