我是个盲人，已经在Windows、Mac、Linux和DOS上编程了大约13年，使用的语言包括C/ c++、Python、Java、c#和各种较小的语言。虽然最初的问题是关于配置环境的，但我认为最好的回答是看看盲人如何使用计算机。

有些人使用谈话环境，比如在其他答案中提到的拉曼和Emacspeak环境。到目前为止，更常见的解决方案是有一个屏幕阅读器，它在后台监控操作系统活动，并通过合成语音或物理盲文显示(通常一次显示20到80个字符)提醒用户。这意味着盲人可以使用任何可访问的应用程序。

因此，我个人现在使用Visual Studio 2008，并且运行它时只做了很少的修改。我关闭了某些功能，比如在打字时显示错误，因为我觉得这会让人分心。在加入微软之前，我所有的开发都是在一个标准的文本编辑器(如记事本)中完成的，所以同样没有定制。

可以配置屏幕阅读器来宣布缩进。我个人不使用这个，因为Visual Studio会处理这个问题，而c#使用大括号。但这在Python这样的语言中是非常重要的，因为这里有空格。最后，Emacspeak使用不同的声音/音调来表示语法的不同部分(关键字、注释、标识符等)。

我是个盲人，在过去的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.

我是盲人，几个月来我一直在使用VINUX(一个基于Ubuntu的linux发行版)和SODBEANS(一个netbeans版本，带有一个名为SAPPY的插件，添加了TTS支持)。 这个解决方案工作得很好，但有时我更喜欢启动Win XP和NVDA来启动FireFox上的许多页面，因为当你试图打开超过3个FireFox窗口时，Vinux工作得不太好……

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

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

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

这篇博文有一些关于Visual Studio团队如何使他们的产品易于访问的信息:

Visual Studio核心团队的无障碍实验室参观活动

许多程序员使用Emacspeak:

Emacspeak—完整的音频桌面

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

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