视觉是大多数程序员认为理所当然的感官之一。大多数程序员会花几个小时盯着电脑显示器(尤其是在他们全神贯注的时候)，但我知道有些程序员是盲人(比如目前在谷歌工作的T.V. Raman)。
如果您是一个盲人(或逐渐失明)，您将如何设置您的开发环境来帮助您编程?
(每个回答一个建议。这个问题的目的是把好的想法带到最高层。此外，屏幕阅读器可以更早地阅读到好的想法。)
当前回答
请记住，“失明”是一系列的情况——有一些人在法律上是盲人，他们可以阅读一个非常大的显示器或在放大设备的帮助下，还有一些人根本没有视力。我记得大学时的一个同学有一种可以放大书本的特殊设备，还有一种可以放大屏幕一部分的特殊软件。她正在努力完成大学学业，因为她的视力越来越差，几乎要完全消失了。
编程也有一系列的需求——有些人擅长写出大量的代码，有些人更擅长看大局和架构。我可以想象，考虑到屏幕界面所施加的难度，失明可能会增强你获得大局的能力……
其他回答
我不记得来源，但我听说过/读过一种可听语法“着色”的形式-这样，而不是字符串赋值被读为
Foo = quote这是一个字符串引号
字符串部分将用不同的音高或声音来读，以使元素的分离更清晰。
来自南伊利诺伊大学爱德华维尔分校和华盛顿州立大学的一组学生正在为盲人开发一种编程语言:
http://www.youtube.com/watch?v=lC1mOSdmzFc
我是个盲人，在过去的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.
NVDA是一个很好的开源屏幕阅读器。
发明一种设备，你插入usb端口，它基本上是一块“橡胶”，它会自我修改，显示你的代码，让盲人阅读而不是听到它，怎么样?
