Contributing to an open-source project like NVDA isn’t just about solving today’s problems — it’s about building the foundation for a future where technology is more inclusive, more ethical, and more human-centered. As computational techniques evolve rapidly, we have to ask: What does the future of free/libre and open-source software (FLOSS) look like, especially in accessibility? What ethical choices must we face?
In my experience working with NVDA, I’ve encountered both the promise and the complexity of this future. FLOSS, at its best, is a collective act of care. But its path forward requires deep reflection on power, responsibility, and inclusion.
AI, Automation, and the Future of Accessibility
One of the biggest shifts on the horizon is the increasing use of artificial intelligence in accessibility tools. Already, we see apps that use computer vision to describe images, read handwriting, or generate audio captions. AI can fill in accessibility gaps where human effort falls short.
But in FLOSS projects like NVDA, which operate on transparency and community consensus, integrating AI raises tough questions:
- How do we balance machine-generated content with trustworthy, human-curated accessibility?
- Can AI decisions be audited, corrected, or explained?
- Who is responsible when automated features fail — and what if they fail silently?
In proprietary systems, these trade-offs are often made behind closed doors. But FLOSS developers must negotiate them in public, with their communities, and in code everyone can read.
Globalisation, Language, and Digital Justice
Another challenge is scaling accessibility tools to a global user base. NVDA already supports dozens of languages thanks to its volunteer translation community. But as it grows, there’s pressure to ensure equal quality of access — not just for major languages, but for those underrepresented online.
For example, when I wrote the code for the setting comfirmation, I did not took translation into my consideration because I thought it was not really my responsibility. As a result, I was told by the reviewer to change this. They said “UI string has to be translatable. This is not optional.” It was a powerful comment that taught how much I need to grow to make products/solutions that are truly inclusive to all.
This isn’t just a technical issue; it’s a matter of digital justice. If FLOSS tools don’t work equally well across different cultures, alphabets, or accessibility norms, we risk reproducing inequality even within free software.
In this sense, the future of FLOSS must be linguistically and culturally inclusive, not just free.
Sustainability and Ethical Funding
FLOSS projects often struggle with sustainability. NVDA is maintained by a nonprofit, NV Access, and survives through donations, grants, and government support.
For many open source project, as demand for advanced features grows (e.g., AI integration, mobile platforms, enterprise support), there’s increasing pressure to commercialise parts of the project. The question becomes:
- How do we fund open-source accessibility ethically?
- Can we ensure that users aren’t turned into customers, or that essential features remain free?
This is especially urgent in accessibility work, where many users rely on FLOSS because they cannot afford commercial tools. The future must prioritize not just openness, but also economic fairness.
Shifting Community Norms
The FLOSS world is becoming more diverse — in gender, geography, disability, and skillset. That’s a positive trend. But with it comes the need to rethink community norms.
In older FLOSS cultures, “code speaks louder than words” was the default. But in accessibility-focused projects, non-code contributions — like user testing, documentation, lived experience, or design feedback — are equally valuable.
The future FLOSS community needs to:
- Reward accessibility advocacy alongside pull requests
- Create space for disabled contributors to lead and shape the roadmap
- Reconsider what “meritocracy” means in an ethical, inclusive context
Projects like NVDA are already showing how this can work — but it needs to scale across the ecosystem.
Final Thoughts
Technology is moving faster than ever, but FLOSS gives us a powerful compass: freedom, transparency, and community ownership. As I worked on NVDA, I saw how these values guide development in ways that feel ethical, not just efficient.
But the future isn’t guaranteed. We must actively shape it. We must ask:
- Who is left out?
- What are we automating — and why?
- Are we making software that adapts to people, or forcing people to adapt to software?
I believe the next chapter of open source will be written by contributors who care not just about performance and elegance, but also about fairness, access, and dignity.
And I hope to be one of them.
Leave a Reply