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.
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.
the journeys-not-just-pages framing is the right fix for the problem you describe, but I'm stuck on how the agent itself gets through the journey. if it's navigating via the DOM or a vision model clicking around, it can still verify each step passes WCAG rules, but that's different from the journey actually being completable by someone tabbing through with a screen reader, where the failure is often about focus order and timing, not any single element being non-conformant. does the agent walk the journey the way a sighted mouse user would, or does it attempt it the way assistive tech would, keyboard only, reading the announced state at each step
Hi DevAlly team! I did a lot of work on accessibility & section 508 ages ago. I'm assuming your targeted audience is for those who want to verify a website against WCAG. If so, what does the flow look like when the agent encounters an issue? the only images of DevAlly that I've seen are the ones included here.
also is it possible for the person using your product for testing to update the system prompt or give customized instructions to the agent? I noticed in my own AI engineering usage, I have to explicitly state my intention, e.g. "test this new way of deploying a feature" versus "get this feature deployed no matter what it takes." I'm wondering if you've noticed the agent brute-force a solution that should have otherwise been reported as a WCAG bug?
Congrats on the launch today!
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!
@cormacchisholm@darrenbritton Testing the whole journey is where the nasty accessibility issues usually hide. Really like this approach.
Congrats on the launch team! Does it replace a human audit? Or how does the agent work with a user?
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.
how does the agent handle journeys that include things like popups, dropdowns or content that only appears after a user interaction?
About DevAlly AI Agent on Product Hunt
“User journeys captured with natural language”
DevAlly AI Agent launched on Product Hunt on October 7th, 2026 and earned 95 upvotes and 19 comments, placing #17 on the daily leaderboard. 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.
DevAlly AI Agent was featured in SaaS (44.8k followers), Developer Tools (521.2k followers) and Inclusivity (553 followers) on Product Hunt. Together, these topics include over 147.8k products, making this a competitive space to launch in.
Who hunted DevAlly AI Agent?
DevAlly AI Agent was hunted by Cormac Chisholm. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how DevAlly AI Agent stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Cormac Chisholm
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.