The Accessibility Problem That Changed Luke’s Career

Luke was working as a software engineer when his employer found itself facing litigation over software that did not comply with the Americans with Disabilities Act. The problem wasn’t theoretical. Blind users couldn’t adequately use what the company had built, and the issue had become serious enough to end up in court.

Luke didn’t have an accessibility title or a team built around the problem. What he did have was someone in his life who understood the failure in a way the engineering team couldn’t: his stepfather, who is blind.

Rather than asking engineers to imagine where the product failed for a blind person, Luke got his stepfather hired by the company and began working with him directly. His stepfather used the product with the assistive technology he depended on, identified where the experience broke, and worked with Luke to find and resolve failures in the company’s code.

That changed the feedback loop. Accessibility was no longer something being interpreted exclusively through requirements, standards, or assumptions about how somebody else might experience the software. The person actually encountering the barriers was now participating in the process of removing them.

Built In Austin independently documented the arrangement in its 2021 profile of Clusiv. But the part of the story that appears to have stayed with Luke wasn’t simply that they found broken code.

Luke’s stepfather told him that the work made him feel intellectually valued again after losing his sight.

The immediate assignment was software. The bigger discovery was how much technology was being designed around assumptions about disabled users instead of with the people expected to use it.

That distinction matters.

A product can technically satisfy an accessibility requirement and still be frustrating, inefficient, or functionally useless to the person on the other side of the screen. Luke had seen what happened when that person moved from the edge of the process into the middle of it. Problems became visible earlier. Engineers stopped having to guess. The conversation changed from what should work to what actually worked.

The experience pushed Luke toward a much larger problem: blind and visually impaired people weren’t just encountering inaccessible websites. They were navigating education, job training, workplace software, and hiring systems that frequently had not been designed with their experience represented in the process.

Clusiv became an e-learning and workforce development platform designed for blind and visually impaired people. But one of the more important details of the story is how Luke applied the lesson that preceded it.

When Built In Austin profiled Clusiv in 2021, the company had 12 employees. Seven were visually impaired engineers.

That is the connective tissue between this story and the company that followed it.

The lesson from Luke’s stepfather wasn’t simply that accessibility mattered. It was that people living with a problem could contribute something fundamentally different when they were given a meaningful role in solving it.

It was changing who got to participate in solving the problem.

Luke started with a company facing an accessibility issue and brought someone who actually experienced that issue into the engineering process. What began as an attempt to fix inaccessible software became a much bigger lesson about how products, companies, and systems get built.

The people closest to a problem often know things the people designing the solution don’t.

That idea became part of the operating logic behind Clusiv. It would also become a recurring pattern in Luke’s later work: get closer to the person the system is failing, understand what the problem looks like from their side, and build from there.