3 ms·
with a web page using correct markup, a good screen reader interface, and some practice, they can navigate and consume information much faster than we can visua
by PavlovsCat 13y ago
with a web page using correct markup, a good screen reader interface, and some practice, they can navigate and consume information much faster than we can visually.
http://www.youtube.com/watch?v=vK1tlLOavvM http://www.youtube.com/watch?v=vK1tlLOavvM <-- Léonie Watson, "Design like you give a damn: Practical accessibility for Web Pros" = very good talk, crucial crash course, and includes a great demonstration of the bit of your post I quoted :D
- joshuak 13y agoBingo! This Great talk! Slight left turn on the topic, but I think people can lose some elasticity in their thinking when they try to be politically correct. Accessibility implies impairment, but that can give you a mental model of "blind people are people too so we should be careful not to exclude them". But that's bottom up thinking you should be thinking what is possible, or top down thinking. The mental model is completely different if you take political correctness out of the equation. What if we are talking about a person driving a car using a web interface? Now the user can't see because of a situational limitation not a physical one. There is no need for the implication of sympathy. It's inspiring to me to design for any IO method I can think of. Aiding accessibility is useful to everyone, but I call that user experience and usability. This is why I get bent on some of the thinking behind HTML. Design, to me, isn't a second class citizen when communicating with your user/audience. New devices show the same information but did we just use the same html and css no we reformatted for the devices. What about when we are all using google glass and web enabled watches? Granted many web pages that where redesigned for 'mobile' would have done better to leave well enough alone, but that's just bad design.