Developers you build for the future...Don't forget to be inclusive!
I build things for blind people. I'm a braille transcriber. I work in accessibility every day.
Last January, at an NFB chapter meeting, a member walked in wearing Meta Ray-Ban smart glasses. AI. Camera. Voice. Every blind person in that room wanted to know: How do we get these?
So I built pifcoin.org — a charity crypto to fund assistive tech access. I built aurastoria.com to generate revenue and give the token real liquidity. I built an Accessibility Center into the site because, shockingly, accessibility should be accessible.
Then marketing agencies evaluated my work.
They talked SEO. Funnels. Viral loops. Social traction.
They never asked about the blind users. They never asked about the NFB chapter. And they completely missed the Accessibility Center.
On a website built by an accessibility professional. For an accessibility mission.
Here's what I need from you, developer to developer:
Stop treating accessibility like a feature ticket you close in Sprint 3. It's not a checkbox. It's architecture. If you're building AI tools, camera apps, voice interfaces, or literally anything with a screen — blind users are not an edge case. They're your users.
The Meta Ray-Bans exist right now. The software exists right now. The only gap is the pipeline between "built" and "in their hands."
If you're a developer who wants to build accessible AI tools, or you know how to bridge that gap, I want to talk. Not "let's circle back." Not "I'll put it on the roadmap." Now. Email me at chrisj1s712@gmail.com. Or drop a comment below. But don't just upvote and scroll. That's how we got here.