Being Deaf in Tech: Navigating an Audio-Centric Industry

Being Deaf in the tech industry is a unique experience. On one hand, much of our work is text-based—code, documentation, chat. On the other hand, the industry has increasingly moved toward video calls, voice assistants, and audio-heavy communication. Let me share what that’s really like.

The Good Parts

Let’s start positive. There are aspects of tech work that are genuinely well-suited to Deaf professionals:

Written communication is the norm. Code reviews, documentation, Slack messages, email—these are all inherently accessible. When I’m deep in code, my deafness is essentially invisible.

Remote work has been a game-changer. With proper captioning tools and async communication, I can participate fully in distributed teams. The pandemic-driven shift to remote work actually improved my work experience in many ways.

The community is generally supportive. I’ve found most tech colleagues to be understanding and willing to accommodate once they know what I need.

The Challenges

But let’s be honest about the difficulties too:

Video calls can be exhausting. Even with captions (when they work), following a multi-person video call requires intense concentration. Auto-generated captions often struggle with technical terms. Background noise, multiple speakers, and poor audio quality make things worse.

Conferences are hit or miss. I’ve attended tech conferences where accessibility was excellent—live captioning, sign language interpreters, clear visual presentations. I’ve also attended conferences where I couldn’t follow a single talk because the captioning was broken and nobody noticed or cared.

Impromptu conversations exclude me. The hallway chat, the quick standup, the spontaneous brainstorming session—these informal interactions are where a lot of important information gets shared. And they’re exactly the situations where accessibility often falls through.

What Actually Helps

Here’s what makes a real difference:

1. Quality live captioning (not just auto-captions)
2. Written agendas and notes for meetings
3. Slack/chat summaries of verbal discussions
4. Patience when communication takes a bit longer
5. Visual presentations that don’t rely solely on audio explanation

Why This Matters Beyond Deaf People

Here’s something that often gets overlooked: accessibility improvements help everyone.

Good captions help people in noisy environments, non-native speakers, and anyone who processes information better visually. Clear written documentation helps the whole team. Thoughtful meeting practices (agendas, notes, async options) benefit everyone’s productivity.

This is the curb-cut effect in action. Design for accessibility, and you often end up with better design for everyone.

The Work Ahead

I’m involved with the CNCF Deaf and Hard of Hearing Working Group because I believe the cloud native community can lead on this. When major tech projects and conferences prioritize accessibility, it sets the standard for the industry.

But change doesn’t happen automatically. It requires people advocating, creating guidelines, and holding organizations accountable. It requires allies who speak up even when it doesn’t directly affect them.

If you’re reading this and wondering how you can help: start by asking. Ask the Deaf and hard-of-hearing people in your life what would make their experience better. And then actually listen to the answers.

Final Thoughts

Being Deaf in tech has challenges, but it’s also given me perspective that makes me a better engineer. I think deeply about user experience because I know what it’s like when products don’t work for you. I communicate clearly in writing because that’s my primary mode of communication. I advocate for inclusive design because exclusion shouldn’t be the default.

The tech industry has made progress, but there’s still a long way to go. I’m committed to being part of that journey.