Latest / The Diversity Career Podcast with Fexingo: Inclusion, Equity, and Underrepresented Professionals / How Blind Professionals Navigate Tech Careers
Transcript
- Lucas: When we talk about remote work changing career equity, as we did in the last episode, we usually focus on flexibility or geography. But there is a massive blind spot in that conversation: how remote infrastructure actually creates new barriers for blind and low-vision professionals. The assumption that working from home levels the playing field ignores the fact that most corporate digital ecosystems are built for sighted users first. Luna: Right, because if your entire daily workflow depends on navigating interfaces designed for mouse clicks and visual cues, remote just makes you isolated in a broken system. It is not about wanting special treatment; it is about having a functional toolset. Lucas: Exactly. And the irony is that many of these professionals are highly skilled technologists themselves. They know more about accessibility constraints than the average product manager. Yet, when they try to onboard into a new role, they hit walls with proprietary software, internal communication platforms, and even basic document formats that assume visual literacy. It is a structural failure, not a skill gap. Luna: So when companies say they are inclusive, are they talking about the website footer where you can tab through links, or are they talking about the actual job performance environment? Lucas: That is the critical distinction. Most organizations treat accessibility as a compliance checkbox for their customer-facing site. They hire an external firm to audit their homepage, fix the contrast ratios, and move on. But internally, they run on a patchwork of legacy systems, Slack channels with image-heavy memes, and code repositories that lack proper alt-text or semantic structure. For a blind developer or data analyst, that internal chaos is a daily negotiation. Luna: It sounds like the difference between looking accessible and actually being usable. One is marketing, the other is engineering. Lucas: Precisely. And the cost of that failure is high. We are seeing a shortage of diverse technical talent, yet we are actively filtering out qualified candidates because we refuse to invest in the right assistive technology stack. It is cheaper to buy a good screen reader license and train managers on inclusive communication than it is to replace a talented employee who quit because the tools didn't work. But the mindset is still stuck in the nineties. Luna: What does the right tech stack actually look like? Are we just talking about JAWS or NVDA, or has it evolved past that? Lucas: The core screen readers have been stable for years. NVDA is free and excellent, JAWS is the enterprise standard. The problem isn't the reader itself; it is the content feeding it. If a company uses a project management tool that loads dynamic images without descriptions, or if their internal wiki is full of screenshots instead of text, the best screen reader in the world will just read gibberish or silence. The bottleneck is content creation, not hardware. Luna: So the burden shifts from the individual trying to adapt to the system, to the system adapting to human variation. That requires a total rethink of documentation standards. Lucas: It does. And it requires leadership to accept that 'good enough' for sighted users is unacceptable for everyone else. We need to look at specific examples where companies got this right. There is a growing cohort of tech firms that have embedded accessibility engineers into every product team, not just at the end of the cycle. They build with semantic HTML and keyboard navigation from line one. Luna: Does that change the velocity of development? I always hear the argument that accessibility slows down shipping speed. Lucas: That is the old myth. In reality, writing clean, semantic code improves maintainability and reduces bugs across the board. Screen readers rely on structure. If you build for structure, you build better software for everyone. The slowdown comes when you try to bolt accessibility on after launch. That is when it becomes a nightmare. Integrated access is actually faster. Luna: I think people forget that blindness is not just black and white. Low vision, color blindness, photophobia—these are all different experiences that require different accommodations. Lucas: True, but let us stick to the most severe end of the spectrum for now, because that is where the design challenges are hardest. If you can make the system work for someone who cannot see the screen at all, you automatically make it easier for someone with low vision. It raises the floor for usability. High contrast modes, clear typography, and logical reading order help everyone. Luna: But what about the social aspect? Remote work already isolates people. How do you ensure blind employees aren't excluded from the informal networking that drives promotions? Lucas: That is a profound point. In an office, you might overhear conversations, get invited to lunch, or catch body language cues. Remote work removes those ambient signals. For a blind professional, relying on verbal communication means you miss nothing socially, but you also lose the non-verbal rapport building. Companies need to be intentional about virtual water cooler moments that are audio-first or text-based, not video-heavy. Luna: So instead of Zoom happy hours where everyone stares at each other, maybe it's voice chats or structured text channels. Something that doesn't privilege the visual. Lucas: Exactly. Voice notes, threaded discussions, clear agendas shared in advance. These are simple changes that signal inclusion. It shows you care about participation, not just presence. And it helps neurodivergent employees too, who often thrive on written communication over spontaneous social interaction. Luna: It seems like the common thread here is intentionality. You don't stumble into inclusion. You have to design for it deliberately. Lucas: Absolutely. Inclusion is a feature, not a bug. You have to specify the requirements, test against them, and iterate. If you leave it to chance, you default to the status quo, which excludes anyone who doesn't fit the narrow mold of the typical worker. Luna: Before we dig deeper into the specific tools, I want to pause and mention something important. We deliberately don't run ads on these shows because we believe our listeners deserve a clean, focused space for professional growth. If you want to support that choice and keep the network independent, the link is buy me a coffee dot com slash fexingo. Your support directly funds the research and production quality you hear here. Luna: Thanks for keeping this space ad-free and respectful of your time. Now, back to the tools. What are some concrete examples of software that actually works well for blind developers? Lucas: Visual Studio Code has gotten much better, especially with extensions like Code Companion that use AI to describe code blocks verbally. It is not perfect, but it is a huge leap forward. Also, GitHub has improved its accessibility significantly over the last two years. The issue tracker, pull request views, and repository structures are now largely navigable via keyboard and screen reader. Luna: That is surprising, given how code-heavy and complex those interfaces are. Did they overhaul the UI completely? Lucas: They didn't necessarily change the look, but they fixed the underlying code. They added ARIA labels, ensured focus states were visible to screen readers, and standardized the tab order. It was a backend fix, not a frontend redesign. That is the key takeaway: accessibility lives in the markup, not the pixels. Luna: So if a company wants to start fixing this, where should they begin? Is it a big IT project or something smaller? Lucas: Start with the basics. Audit your internal documents. Are your PDFs tagged correctly? Can they be read linearly? Check your email templates. Are they responsive and accessible on mobile? These are low-hanging fruit. Then, move to the core collaboration tools. Do your project management boards have alt-text for icons? Are your meeting invites sent in accessible formats? Luna: It sounds like a lot of homework. Most HR departments probably haven't even thought about PDF tagging. Lucas: Most haven't. But once they realize that a simple formatting error can lock out a qualified candidate, the motivation changes. It stops being a nice to have and becomes a business imperative. You are losing talent because of bad file formats. That is a solvable problem. Luna: And it sets a precedent. If you fix the docs, you start thinking about the culture of communication. It ripples outward. Lucas: It does. And it empowers employees to advocate for themselves. When a company has clear accessibility standards, it is easier for a blind employee to say, 'I need this specific tool,' rather than begging for exceptions. It normalizes the accommodation. Luna: Normalization is such a powerful word. It takes the shame out of asking for what you need to do your job effectively. Lucas: Right. No more hidden struggles. Just clear expectations and the right tools. That is what true equity looks like. It is boring, practical, and deeply respectful. Luna: So, if you are listening and you manage a team, what is one thing you can check today to see if your workspace is truly inclusive? Lucas: Try running your main dashboard or reporting tool through a free screen reader extension. Just listen to how it flows. If you hear repetitive noise or missing context, you have found your first fix. It is a quick way to see the world through a different lens. Luna: Practical, immediate, and revealing. I think that is a great place to stop for now. Lucas: Agreed. The next step is implementation. But knowing where to look is half the battle. Thanks for tuning in to Fexingo Business.