"I built a tool that scans websites for accessibility issues and generates prioritized compliance reports."
Hi Indie Hackers 👋
After 16+ years working in Accessibility Testing and Compliance, I recently launched AccessLumens - https://accesslumens.com
While there are several great accessibility scanners available today, I felt there was still a gap between finding issues and understanding what they actually mean for users, developers, and businesses.
A few things I'm experimenting with in AccessLumens:
• Multi-page website crawling instead of single-page scans
• Accessibility benchmarking to compare your website against industry peers
• Keyboard & Experience Analysis to identify issues that automated accessibility checks often miss
• User Journey Scans that analyze accessibility across multi-step workflows instead of isolated pages
• WCAG-aligned compliance insights and remediation guidance
I would love honest feedback from fellow founders, developers, designers, QA engineers, and accessibility professionals.
What resonates?
What feels unnecessary?
What would make a tool like this genuinely useful in your workflow?
Happy to answer any questions and share what I've learned building in the accessibility space.
The shift from "finding accessibility issues" to "helping teams decide what to fix first" is what stood out to me. Most reports overwhelm people with violations. The real bottleneck is deciding which fixes reduce the most user pain and business risk. If AccessLumens consistently answers that question, it stops being another scanner and starts becoming a decision tool.
That's a great observation, and honestly one of the problems I'm trying to solve.
Most accessibility tools are good at finding issues, but teams often struggle with prioritization once they receive hundreds of findings. The goal with AccessLumens is to move beyond issue detection and help teams understand which barriers have the highest user impact, compliance risk, and remediation value so they can focus their efforts where they'll make the biggest difference.
Appreciate the feedback!
That's exactly what I was getting at.
Reading your reply, one implication immediately came to mind that I don't think is obvious yet, but it's probably too much to unpack properly in a thread.
Happy to explain what I mean if it's useful. What's the best email to reach you on?
you can reach out to me on support@accesslumens.com, thanks!
Just sent it over by email.
Looking forward to hearing your thoughts once you've had a chance to read it.