Do you think having braces over indentation would have helped for accessibility. Any other issues with the language syntax?
Although, it would seem to me that it would involve a lot of counting of white-space.
That's just amazing, but I guess it makes a lot of sense... since your display is not 2d-based in the same way as standard screens are and you can read the code itself (i.e. the display is consistent). I'd upvote you a thousand times just for how cool it is to workaround difficulties in so leet way :)
Of course it also reminds me of... I don't see code, just blondes, brunettes, redheads...
For regular text, we used to do a simple text conversion and print it using a special printer called braille embosser. We used a software called duxbury for the purpose. http://www.duxburysystems.com/dbt.asp
For math(non single line), braille uses something called, nemeth code. So we used code almost all the math functions/equations manually in nemeth code.
For graphics, we used to emboss 2d picture on a special paper. The process involved, scan the picture -> convert it into a grayscale -> remove all the noise -> take a print out -> use a tactile embosser to put it on a swell touch paper (http://www.abledata.com/abledata.cfm?pageid=19327&top=15...) Typically, a chart or graph or waveforms were key in understanding the material.
During the process I interacted with few blind cs engineers who were graduated and were working for Microsoft. At that time(10yrs ago), Microsoft was the best blind friendly company. They used the visual studio for daily hacking.
Coding blind would be much different. The input is physical but there is nothing tangible coming back. It is more or less all visual. Come to think of it, if I ever lost my vision I would probably become a full time sailor :)
Not really. At the end of the day it's just data, text, how you encode it is not very important as long as it can be understood.
Because humans very strongly rely on sight, it makes sense that the default serialization format for text output be print/visual, but there are a number of non-visual interfaces to text. And if none fits, build a new paradigm.
I think samlittlewood below makes a good point: even with a fairly slow (e.g. braille) output, it's at worst similar to coding using a line-oriented editor (e.g. ed). Except you're used to it because you see pretty much everything via a line-editor so you're probably proficient at it.
PS: Ok, his is not going to be building a GUI but text to speech works well. And a keyboard only interface works fine for both VI and visual studio.
Which is to say with the boat heeled over or the jib up, the helm is reliant on the bowman and the rest of the crew keeping watch anyway, you can't see much forward.