Differences between revisions 10 and 11
⇤ ← Revision 10 as of 2012-12-02 23:58:08 →
Size: 1545
Editor: shoobe01
Comment:
← Revision 11 as of 2012-12-04 01:20:34 → ⇥
Size: 1640
Editor: shoobe01
Comment:
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
 * http://eyes-free.googlecode.com/svn/trunk/documentation/android_access/developers.html

I have traditionally said that good design is also design for accessibility. And there are many cases where mobiles are used by anyone in an environment where some input our output may be obscured, so every design should assume accessibility.

But... that's not always 100% true, and if you do have a special population, there are special cases to consider.

I'll eventually put some effort into specific guidelines, or at least a series of links. Here's some to start with:

Shay Howe had a GREAT presentation on semantics and html 5 at the 2012 Float Mobile eLearning Symposium. When the video comes out, at least, find and watch that.

More notes from recent work and pondering: Accessibility modes for non-sighted users are VERY different interfaces and interactions. Try it, and see what I mean. Labels and types of interfaces matter.

Design for Accessibility (last edited 2015-02-03 16:56:12 by shoobe01)