Munshi Abrar

WebAble started as a hackathon project. The brief was to use AI to solve a real-world problem for a community. I built an early accessibility/control prototype, won first place at UB's AI for Good Hackathon, and realized the bigger problem wasn't the technology. It was distribution.

Accessibility tools usually only exist where a website owner has installed them, paid for them, or prioritized them. That leaves users waiting on every site to care. WebAble started from a different question: what if the user could carry their own accessibility layer across the web?

I studied Information Technology and Management at the University at Buffalo with a Cybersecurity minor, combining technical systems, business operations, and product thinking.

I've worked across web development, automation, analytics, SEO, internal tooling, and digital operations with organizations including The Bee Conservancy and VSG Power. That work exposed the same pattern repeatedly: websites break down in predictable ways, and once you understand the issue, the next step is automating the fix.

I've also built startup plans through UB Blackstone LaunchPad and ILF-style incubator work, and continue funding WebAble through related technical and digital systems work.

I'm red-green colorblind. It's a small detail, but it changes how you notice interfaces. Accessibility barriers don't always announce themselves. Sometimes they're quiet, cumulative, and easy to miss when you weren't the person a product was designed around.

WebAble became inevitable because it sits at the intersection of everything I kept seeing: users adapting to broken interfaces, teams lacking practical tools, and technology finally reaching the point where the web can adapt back.

The goal isn't another accessibility checklist. The goal is to make the web easier to use for people and easier to improve for the teams responsible for it.