New Mols guidelines: Will not use the term "Accessibility" at ALL unless it's within a work context. Will not shorthand. Will use "Access"

Mar 21, 2013 · 5:14 PM UTC

7
Replying to @mholzschlag
@mollydotcom then you might bug those who think it as the Micro app for databases
Replying to @mholzschlag
@mollydotcom as much as I loathe it, the term Universal Design seems friendlier, more embracing. I guess @saqibs is right.
Replying to @mholzschlag
@mollydotcom the Microsoft database? :P
Replying to @mholzschlag
@mollydotcom Availability is the word I used in my as-yet-unfinished best practices stuff.
Replying to @mholzschlag
@mollydotcom e.g. a page that has broken JS and doesn’t work is both unavailable to all and inaccessible.
1
1
Replying to @mholzschlag
@mollydotcom I suggest "Barrier Free", I personally would prefer inclusive design - not universal design. (1/2)
1
Replying to @mholzschlag
@mollydotcom 2/2 universal design doesn't imply IMHO the additional adaptions needed to include all disabilities, e.g. sign-language videos
1