Do you by chance have a PDF or image file of the Braille ASCII & Querty Keyboard? I'd also love to print it out & put it next to my work station!
@AphOrg
2 жыл бұрын
You should be able to find what you're looking for here: www.teachingvisuallyimpaired.com/
@robfielding8566
2 жыл бұрын
the description of ascii braille is annoyingly subtle. the span of 64 values that it spans includes the UPPER case of ASCII; but dot 7 is stripped out of it. This seems to be why my Orbit40 does such strange stuff, including clear bugs in rendering that Orbit20 doesn't have. I took the standard 63 values from 0x20 to 0x5F, and flipped the dot7 on ascii A..Z so that it IS in fact upper-case. I then coppied 0x20..0x39 to 0x00, and flipped ITs dot7. Then I copied 0x40..0x5F to 0x60, and flipped ITS dot7. Then I copied 0x00..0x7F to 0x80 and flipped its dot 8. Because of this, every single byte of ascii can be typed literally; while still having the core braille ascii in there. The difference is that if you want to render 6-dot braille ascii, you must strip off dot 7. And for 8-dot braille, it's all completely literal; where the things outside standard ASCII braille have analogies you can remember if you just remember the hex ascii values. In theory, you should be able to read small binary files exactly this way. This means seeing tabs, linefeeds, and carriage returns literally. I am still sighted in one eye, and the ambiguity penalties in 6-dot renditions make me crazy. The Orbit40 computer braille isn't quite what I setup for myself, where I wrote a small Go program similar to 8-dot liblouis to handle it. The idea is that seeing every char in use completely unambiguously is a bit of a super-power for a computer user to have. I think it has to be this way in the long run to be an employable computer programmer. I am viewing braille as just some possible encoding to communicate with my computer when I can't see. I will probably never read a paper braille book. Given $600 terminals that can do simple computer, braille... it is not too much to ask a typical web development team to actually BUY a terminal and learn uncontracted braille; to really understand now accessibility works. Even a braille terminal that also shows sighted characters as well as tactile dots. Anyways, now that I have my own variation on computer-braille, my only other issue is that it's not easy to get any new "language" setup. I did make a no-monitor Linux computer for practicing. I am terrible at contracted braille, and don't see any sense in it, given that keeps out casual braille users using displays, makes computer coding much more complicated (due to handling ambiguity, and changing the number of chars). If braille were just a font, then lots of sighted people would use it for their own reasons. My daughter learned sign language (mostly just the alphabet), for the purpose of talking in class without getting into trouble; and she has actually used it in contact with deaf strangers. (!)
@robfielding8566
2 жыл бұрын
For example: ,hello should have been ,HELLO To be strictly correct with ASCII. Because the letters in 0x20 to 0x5F are used for the "ascii braille" standard. So a workaround is to know whether the intent is 6-dot or 8-dot. If it's 6-dot, then it's upper-casing all the letters. But dot7 and dot8 are set to zero; including when rendering it to the Unicode 0x2800 + C section of Unicode that is raw dots in binary order.
@robfielding8566
2 жыл бұрын
an example of ambiguity problems, and incompleteness problems. I type "vi" in Linux, and I can't figure out how to type the ESC key. I should be able to reason through it just from knowing the standard ASCII braille table, and how to map it to 8-dot.
@robfielding8566
2 жыл бұрын
Here's an example where Braille Ascii not mapping to 8-dot ASCII is a usability disaster on computers: People complain that "Hey, you aren't following accessibility laws or rules". If it is assumed that 8-dot braille users map to bytes; then you don't need to make special cases for blind people using devices you don't own. You could just have a browser mode in Chrome that is just a 40-char, single line display with arrow keys and select. This is EXACTLY the interface you want to use on a pair of headphones that is too small for a screen, so that you can use Twitter from earbuds and a watch. It's an alternative to qwerty that has no special connection with blind people. It's just a byte stream. So it's not an accessibility feature that needs to be turned on; it's tested just like everything else that gets tested during development, for devices that every single customer potentially uses. In its current state, Google on brltty returns people asking how to DISABLE it. You have to turn on an obnoxious screen reader, rather than having every program return a byte stream that is just always on, and always tested.... which can then be sent to a screen reader, optionally.
@robfielding8566
2 жыл бұрын
Example of getting sighted people to use braille: An iPhone case with thumbs on the front, and 8-dot perkins on the back. That way the keyboard doesn't bother the screen view at all. If braille is just a font, with keyboards to type every byte; then it doesn't necessarily need a weird voice-over setup to use. It would let you type SMS messages quickly while walking around. People would learn braille for that, because they spend all day messing around on their phones; and a qwerty keyboard on a phone is even more preposterous than just learning braille that can represent all 256 bytes.
Пікірлер: 7