Surviving public school as a blind girl in 1955
blog.tutorspree.com
blog.tutorspree.com
I think some of the issues this person had were caused by having some vision. Because I’m totally blind it’s pretty clear that print won’t do me any good and major accommodations have to be made. When you have some vision it’s difficult for others to understand what you can and can’t do, especially if that changes as your vision gets worse.
I have an issue with the only 10% of legally blind people can read braille statistic because it is not made clear what the population of legally blind people consists of. Often times being blind is in addition to severe mental handicaps. If someone can’t use the bathroom on their own then learning to read books is low on the list of things that are important. In addition braille may not make sense to elderly people who recently lost their vision. If their fingers are no longer sensitive enough to read braille then should they still count in the statistic? Older people who have lost their vision also have prior experience reading print material. This means that with the prevalence of text to speech software it may not be worth learning braille if they already know how words are spelled and how to construct a sentence.
edit: much better!
1. How common is it for web application developers to directly make part of a page clickable without using an appropriate semantic tag or ARIA role?
2. How common is it for web application developers to roll their own widgets, e.g. buttons, menus, or sliders? One has to assume that most such widgets implemented directly by the application developer won't have proper ARIA support.
3. Which reusable UI components and toolkits are most common among web application developers, particularly those working on a minimum viable product? How accessible are these?
Rich web applications are more challenging, since they often invent their own UI widgets (or build on top of toolkits that do this), in addition to or even instead of using standard links and form controls. For these, the W3C has a standard called Accessible Rich Internet Applications (http://www.w3.org/WAI/intro/aria). But in my experience, ARIA is often subject to misinterpretation by the browser, the assistive technology, the application/toolkit developer, or some combination of the three.
No, we can't let the Kindle read books aloud with text-to-speech; it'll deprive publishers of audiobook revenue!
Don't know the latest on it but it was totally a legal battle.
Deleted comment
Newer template engines make this better since templates are likely to be stored as Javascript objects/functions that are written to the DOM when they are relevant.
It's aimed at children, but I found it interesting.