在我读研究生的时候，我们的研究团队中有一个盲人。他年纪大一点，大概四十五岁左右。他向我们讲述了他如何编写自己的第一台计算机(那时候文本语音转换还不普及)，以莫尔斯电码输出屏幕上的内容。为了克服这个明显的“先有鸡还是先有蛋”的问题，他每次都必须从头开始重写代码，直到代码能够正常工作，可以重新读给他听为止。

现在他使用文本转语音，尽管他在实际编写任何代码之前都非常彻底地计划了代码，以最小化调试循环。

他还非常擅长做ppt演讲，尽管他视力不好，但格式和其他视力正常的演讲者一样好。

我不记得来源，但我听说过/读过一种可听语法“着色”的形式-这样，而不是字符串赋值被读为

Foo = quote这是一个字符串引号

字符串部分将用不同的音高或声音来读，以使元素的分离更清晰。

正如许多人指出的那样，emacspeak是许多老黑客的跨平台持久解决方案。由于它支持Linux和Mac开箱即用，它已经成为我开发Windows无关项目的首选方法。

关于通过听觉而不是视觉来真正理解语法的问题，我发现存在各种各样的技术来接近语法，即使不是在同一个领域。

例如，听觉图标可以代替口头描述符。你可以用音调表示一行缩进的程度。音调越长，缩进越远。由于音调可以与文本和语音并行播放，信息在相同的时间框架内传递，而不会序列化如此基本的交流。

盲文能够快速而精确地解码出一行文字的确切语法。这对于日常生活中使用盲文的人来说更有用;最大的优点是可以随机访问显示的内容。可刷新单元通常在每个字符单元上方有路由器键，可以将光标指向该单元。不要摆弄方向键O(n) op vs O(1)访问。

听觉维度(音调、速率、音量、变化、丰富度、重音等)可以传达一个概念(关键字、类别、变量、错误等)。例如，注释可以用单调变化来读……正合适，如果我可以这么说的话:)。

Emacs和其他较小程度的编辑器(Visual Studio)允许编码器严格地阅读程序(下一个块、折叠块、向下defun、跳转到def、向上解析树等)。这样做，你可以很快得到整个项目结构的“大”图景;通过像Cedet这样的扩展，你可以在文本编辑器中跨平台地使用VS/Eclipse/etc的优点。

可能还有很多，但简而言之，这就是为什么我们中的一些人在工业、学术界或地下室里不停地工作的基础:)。

harald van Breederode是荷兰著名的Oracle DBA专家、培训师和演讲者，他是一位盲人。他的博客为视障人士提供了一些有用的建议。

我认为这在使用结对编程原理的极限编程中会很有效。如果你是为盲人开发软件，那么谁会比那些真正了解业务需求的人更适合做这个软件呢，所以我认为这一点都不牵强。

至于写代码，除非有某种反馈，否则我认为一个人可能会在语法上挣扎。音频反馈可能会有所帮助。

我是个盲人，在过去的12年里一直是一名程序员。目前，我是一名高级架构师，在Sapient公司(一家总部位于剑桥的咨询公司，创建基于web和基于厚客户端的企业解决方案)工作。 我使用了几个屏幕阅读器，但大多数情况下都坚持使用Jaws用于窗口和NVDA。

I have mostly worked on the Microsoft platform and visual studio as my environment. I also use tools like the MS Sql enterprise studio and others for DB access, network monitoring etc. I tried to spend some time with emacspeak but since my work was mostly based on the MS platform, never really spent a lot of time there. I have also spent a couple of years working on C++ on linux - mostly used notepad or visual studio on windows for all the coding and then samba to share files with the linux environment. Also used borland C for some experimental stuff. Have recently been playing around with python, which as other people have noted above is particularly unfriendly for a blind user because it is written using indentation as the nesting mechanism. Having said that, NVDA, the most popular open source screen reader is written completely using python and some of the commiters on that project are themself blind. A particularly interesting question I get frequently asked as an architect is how do I deal with diagrams - UML and visio and rational rose etc. Visio is probably the most accessible diagraming tool out there. I was able to write jaws scripts to read rational rose diagrams for me. I've used a tool called T-dub (technical diagram understanding for the blind) developed by some german university for accessing UML 2.0 diagrams. Have used a java-based ugly tool called magic draw for doing model-driven development and was a commiter on the androMDA project and helped develop the .Net code generator from a UML model.

In general, I find that I thrive most in a team environment where I can work on my strengths. For example, while a diagram is extremely useful to communicate/document a design, the actual design process involves a lot of thinking and brainstorming and when the design has been thought out, one of your team mates can help you quickly put together a neatly drawn picture out of it. People incorrectly mis-construe the above to be lack of independence or ability while I see this as pure inter-dependence -- as in I am sure that the team mate alone could never have come up with that design on his/her own and in-turn, if I depend on him to document the design, so be it. Most hurdles I face are tool-based inaccessibility. For example all oracle products have been progressively declining in accessibility over the years (shame on them) and a team environment basically allows me an extra layer of defense against these over and above my screen readers and custom scripts.