About seven years ago, my daily workflow looked something like this: build for hours, then call a sighted friend. Ten times a day. Fifteen. Sometimes more.
“Is this button in the right place?” “Are the margins balanced?” “Does the layout break on wider screens?”
I never asked anyone to write code for me. Code is what I do. What I needed was harder than that. I needed someone to be my eyes.
For years, that was the single biggest barrier in my career as a blind developer. Not logic. Not algorithms. Not databases. The visual layer alone stood between me and being a true full-stack developer, someone who builds a product end to end with his own hands.
Then the rules changed.
The barrier that wouldn’t break
CSS, for all its power and elegance, was never built with blind developers in mind. There is no direct way for a screen reader to convey the feel of a UI. Is the contrast comfortable? Are elements where users expect them? Does the hero image carry the right message?
These questions lived entirely outside my sensory world. And because business logic serves function while visual design serves experience, I was always building half a product. I owned the part no one sees. I depended on others for the part everyone does.
I’ll be honest: that model was a burden on everyone involved. On me, because I had to wait for someone to be available at the right moment. On my friends, because I couldn’t keep asking them to check every detail. On the product itself, because the entire development cycle stalled at every visual element until someone sighted showed up to look at it.
And the deeper cost: that dependency kept me from judging the quality of my own work. From improving it. From owning it the way any other developer owns theirs.
New eyes
Today, the picture is completely different.
What modern AI models can do goes beyond what most people imagine. Everyone knows they generate text and images. What fewer people realize is that they can be your eyes, too.
One of my favorite workflows right now is the combination of Claude and Gemini Image Generation. Claude crafts a precise prompt, sends it to Gemini (the strongest image generation model at this stage), reviews the output, judges whether it serves the purpose, then either uses it or regenerates. One loop, no sighted human required.
But image generation is only a small part of the story. AI models today can look at a screenshot and describe what they see with precision: element arrangement, colors, spacing, visual bugs that a screen reader alone would never catch. I no longer need to wait for a friend to confirm that a section renders correctly. I share a screenshot with Claude and ask: what do you see?
And beyond reading, I bring it into the decision. “Does this green button work with the rest of the palette? Is the spacing between it and the heading comfortable? Any visual improvement you’d suggest?” It responds with specific, actionable critique grounded in real design principles. Not generic praise.
I discuss UX with it too. How does the user flow from one screen to the next? Is there friction in the checkout journey? How should I structure the sidebar for different user segments? The conversation feels like having a new team member, not a mute tool.
These roles (generation, review, evaluation, discussion) used to require a full team of sighted people. They’re now at my disposal. Mine alone.
What strikes me about this shift isn’t the tools themselves. It’s the autonomy they unlock. I can now judge the beauty of what I build. I can evaluate my product visually, iterate on it, and improve it myself, in a complete development cycle. This isn’t a luxury. It’s the same independence the disability community has demanded for decades, and it’s starting to materialize, even if only in my small corner of the world.
A blind developer is no longer hostage to lost sight. With persistence, patience, and relentless experimentation, we build complete applications, ship websites that deserve to be seen, and engage with the visual layer as creators, not as people asking permission.
But the world hasn’t caught up
Here’s the thing, though. All this technical empowerment, as hopeful as it is, slams into a reality that hasn’t evolved at the same pace.
In the tech industry specifically, people with disabilities are still viewed as consumers, not producers. Beneficiaries of services, not builders of them. An audience that solutions are built for, not a team that builds them.
If you think that perception has faded, let me share from my own experience.
I’ve lost count of how many interviews were shut down before my resume was even read. The barrier was never my competence, my projects, or the lines of code I’d written. It was a single assumption: “Blind, therefore can’t code.”
I’ve seen the same pattern repeat in conversation after conversation. Interviewers who treat a candidate with a disability as someone who needs to be handled with thick gloves, not evaluated on the same terms as everyone else. They ask questions that assume fragility, not independence. They answer questions that were never asked.
This isn’t subtle. It’s a genuine failure to understand what capability looks like today. It wasn’t accurate years ago. It’s even further from the truth now, after everything technology has given us.
People with disabilities build, ship, and design. They write code, lead teams, and contribute to shaping policies that affect millions. We are not an audience waiting for companies to appease us with an “Accessibility” toggle buried in settings. We are partners in building products from the start.
Closing
Visual design, which was once the tallest barrier for every blind developer, has moved from a present obstacle to a memory we talk about in past tense. That’s an achievement worth celebrating.
But the journey isn’t complete. For every technical breakthrough this era has given us, there stands an outdated mental image that hasn’t been revised in decades: one that reduces people with disabilities to users, when they are, in fact, builders.
To employers and hiring managers in tech: when you meet a candidate with a disability, measure them by your full standards, the same way you’d measure anyone else. Treat their capabilities as facts, not assumptions. And if you don’t know how a screen reader works, or how a blind person writes code, ask with honesty and curiosity, instead of closing the door before it opens.
To my fellow disabled professionals: we are living in a rare historical moment. We have the tools to be where we deserve to be. So let’s build. Let’s ship beautiful things that deserve to be seen and pointed at. And let’s prove through our work that the future belongs to us, just as it belongs to everyone else.