Hear hear on the need for content as well as developer standards for accessibility. A few years back I wrote the web development standards for my company, and tried to encapsulate the WAI checklist into a set of objective, measurable, testable standards that anyone could measure without needing to understand the complexities of HTML and accessibility compliance. We could only write about 9 standards out of the 30 or so checklist items. We made the others best practices because we couldn't figure out a way to *objectively* measure (with the naked eye) such things as text contrast and using semantic markup rather than text treatments (<h1></h1> rather than <p><b><font size=20></font></b></p>).
Even still, we have the devil of a time achieving compliance to these, as many folks feel they are still "design constraints" and not necessary for most sites. Our federally regulated sites DO have strict accessibility reviews, but compliance is still not 100%, even for these. Sites like Bobby were great for measuring accessibility, but Watchfire bought them and forces you to buy a much bigger bundle of stuff you don't need just to use them on internal apps. A little frustrating that global "standards" for accessibility are not yet that accessible to your typical web developer. - Bryan http://www.bryanminihan.com ---- Alok Jain <[EMAIL PROTECTED]> wrote: > I had a talk abotu sam thing a few years back with the director of > W3C WAI initiative, and the approach we talked about was really being > standards driven. There need to be one set of standards that both > content providers and technology creators follow (Browers, assistive > technologies etc..) > > Part of the problem is that everyone wants to have their own set of > mini standards , so each browser behaves differently, each government > wants to define it's own version of accessibility laws. W3C has been > making effort to talk to technology companies as well governments to > adopt one set of standards. > > If this is done, then content provider's responsibility would > typically stop at complying with standards and the rest would be > technology responsibility. > > > AJ > > On Oct 5, 2007, at 9:59 AM, David Malouf wrote: > > > Where is the responsibility of the Screen Readers vs. the > > responsibility of the code creator/content creators? > > ________________________________________________________________ > Welcome to the Interaction Design Association (IxDA)! > To post to this list ....... [EMAIL PROTECTED] > List Guidelines ............ http://beta.ixda.org/guidelines > List Help .................. http://beta.ixda.org/help > Unsubscribe ................ http://beta.ixda.org/unsubscribe > Questions .................. [EMAIL PROTECTED] > Home ....................... http://beta.ixda.org -- ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] List Guidelines ............ http://beta.ixda.org/guidelines List Help .................. http://beta.ixda.org/help Unsubscribe ................ http://beta.ixda.org/unsubscribe Questions .................. [EMAIL PROTECTED] Home ....................... http://beta.ixda.org
