Thoughts on RGD’s webinar on accessible design

So I told Lester that I’ll wait until today’s webinar is over and then I’ll decide. I showed up a few minutes late, but stayed through the end. It was a pretty rushed session, so I’m not sure if I had my questions answered (and honestly I don’t even know what my questions are, or I’d have zeroed in my thesis topic on one of those questions), but I guess in terms of inspiration there probably was something there. But getting the couple of questions that I managed to ask asked was like playing a game of Telephone. The questions were sort of rephrased, and you can’t fix things if you realize what you had put into words was not really what you intended to say. I’ll email, I think. In any case, a few things stuck out really bad:
  • The presenter mentioned two dyslexic typefaces that I had never heard of (Read Regular and Fabula), both of which are available only on request, with the web site of one of the two apparently having been taken over by a plastic surgeon and so must be no longer available. The two I know about were not mentioned even though they are available in more normal ways. I find this extremely curious.
  • Not unexpectedly, “plain language” and a “conversational style” were recommended. However, Louise Ravelli has long pointed out that conversational styles are not simple and in fact as complex as non-conversational styles, only in different ways.
  • The ADOD was suggested as a reference for creating accessible documents. While I don’t think there is anything better, I’m not sure if a failure to mention what it cannot do (which is not unimportant) says anything.
  • AChecker was mentioned. But as our AChecker assignment from last Fall shows, AChecker is hardly useful for anything but trivial sites. I am extremely concerned this has not been pointed out, or the fact that AChecker made it to the list of recommended tools despite its serious shortcomings.
In fact the presenter seems to really like the work that the IDRC has produced. Which is of course great from an ego standpoint, but very disturbing from a graphic design practitioner’s standpoint. If the presenter used these tools and failed to recognize there are huge problems, something must be deeply wrong (which suggests there are thesis topics buried in here, but I don’t know how to find them…). On a side note, the presenter used “roman” as the opposite of “italic.” This is rare gold; I need to ask him if he’s got some sort of printed reference somewhere so that I can to stash it in Wikipedia references.