- From: Kynn Bartlett <kynn-edapta@idyllmtn.com>
- Date: Sun, 20 Jan 2002 10:51:01 -0800
- To: <gdeering@acslink.net.au>, <kynn-eda@idyllmtn.com>, "Charles McCathieNevile" <charles@w3.org>
- Cc: "Slaydon Eugenia" <ESlaydon@beacontec.com>, <gian@stanleymilford.com.au>, <w3c-wai-gl@w3.org>
At 9:23 PM +1100 1/19/02, Geoff Deering wrote: >This is basically my question too. As I read Checkpoint 3.1; "When an >appropriate markup language exists, use markup rather than images to convey >information" (Priority 2). > >I take this to mean "use markup rather than gifs, jpegs, etc when >representing anything in text form". And this could be expanded to use SVG >instead of GIFs & JPGs (when the technology is mature and widespread >enough). > >That's how I interpret this checkpoint and priority 2 compliance. Would >appreciate an enlightened view on this to correct me if this is not so. I think the checkpoint is poorly worded in that it is all about _not_ using something, instead of "providing alternatives". This is an example of a buggy checkpoint, which is why we're having so many problems with it. Access shouldn't be about stopping doing something, but instead supplementing what you're doing. If you can work out some way to deliver text images and still make the content accessible to audiences who can't see those text audiences, then you should be encouraged to go for it. You should not be "marked down" any more than you should be marked down for providing PDF _and_ HTML. --Kynn -- Kynn Bartlett <kynn@idyllmtn.com> http://kynn.com Chief Technologist, Idyll Mountain http://idyllmtn.com Web Accessibility Expert-for-hire http://kynn.com/resume January Web Accessibility eCourse http://kynn.com/+d201 Forthcoming: Teach Yourself CSS in 24 Hours
Received on Sunday, 20 January 2002 14:04:53 UTC