A recent post on Movable Tweak listed a few things the author would like to see changed in Movable Type. All well and good, until I read the following comment by Su:
Ajax: Meh. It’s possible to avoid buzzwords while still buying into the hype, you know. AJAX has serious usability(and accessibility) issues that haven’t even all been discovered yet. While I wouldn’t particularly object(actually, even care) if more software made use of it, I can think of many reasons to avoid it for the time being.
And the follow-up by Jesse Gardner:
I get the distinct impression that in this comment, accessibility is treated as an important consideration only in OUTPUT, and not in the TOOLS that are used to create that output.
Do people with disabilities not want to create content? Would they consider it an acceptable loss to sacrifice accessibility and render the tool unusable for them just so the rest of us could have an enhanced UI? Would they think it “doesn’t really matter”?
(I’ve never given much thought to whether people with disabilities would be able to use Movable Type to create websites, and that reflects poorly on me since I have often promoted its virtues to others. Time to ask more questions.)