I'm a postgraduate student in Beijing,China. I major in computer science and a lot of my work is programming. I am born with low sight, I need to use magnifying tools to see fonts on screen clearly. I use microsoft's mgnify tools on windows and use compiz's magnify plug in if on linux. I usally set the tool to magnify as three times many as the original font size. For me maginify tools is ok, the main problem is the speed,I have to move mouse to keep cursors follow the text I'm looking at, microsoft's magnify provides a option of "auto follow the text edit points",that set me from continuously mouse movement when editting or coding. But it doesn't always works because of the edit software or IDE may not support that. Magnifying tools on linux are hard to use. The KMag come with KDE has a terrible refresh rate which make my eyes unconfortable, compiz's magnifying plugs which I'm using now is OK,but has no function of auto focus(focus auto following). iOS provides quite perfect solution for me with full screen magnifying, especially on ipad's 9.7 inches screen. there auto focus is not necessary because I hardly use them to code or do other edit stuff. Android provides very little accessibility functions, only like shake feedback, which is useless for me. there is no any kind of good magnifying tools on android , not to mention advance function like full screen magnify on iOS. I used to study Qt, want to build a useful magnify tools on linux, even on android. But hardly have some progress.

我是一个完全失明的大学生，有过几次编程实习，所以我的答案将基于这些。我使用windows xp作为我的操作系统，“大白鲨”用合成语音来阅读屏幕上出现的内容。对于java编程，我使用eclipse，因为它是一个可访问的功能齐全的IDE。

根据我的经验，使用SWT作为GUI工具包的java程序比使用Swing的程序更容易访问，这就是为什么我远离netbeans的原因。对于任何。net编程，我都使用visual studio 2005，因为它是我实习时使用的标准版本，使用Jaws和一组脚本非常容易访问，这些脚本是为了使表单设计器等东西更容易访问而开发的。

对于C和c++编程，我使用cygwin和gcc作为我的编译器，emacs或vim作为我的编辑器，这取决于我需要做什么。我的很多实习工作都是为Z/OS编程。我使用rlogin会话通过Cygwin访问大型机上的USS子系统，并使用C3270作为我的3270模拟器访问大型机的ISPF部分。

我通常依赖于合成语音，但也有盲文显示。我发现我通常用语音工作得更快，但在标点符号很重要且复杂的情况下使用盲文显示。这方面的例子是带有大量嵌套括号和JCL的if语句，其中标点符号非常重要。

更新

我正在cygwin http://emacspeak.sourceforge.net下使用Emacspeak，我不确定这是否可以用作编程编辑器，因为它似乎有点反应不太好，但我还没有查看任何配置选项。

Emacs有许多扩展，允许盲人用户操作文本文件。您必须就该主题咨询专家，但emacs具有文本到语音的功能。甚至可能更多。

此外，还有linux:

http://leb.net/blinux/

盲人的Linux。已经存在很长一段时间了。我想十几年了，而且很成熟。

发明一种设备，你插入usb端口，它基本上是一块“橡胶”，它会自我修改，显示你的代码，让盲人阅读而不是听到它，怎么样?

Hanselman最近与一位盲人开发人员进行了一次非常有趣的播客。

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