Some very cool news... (was RE: alt text & punctuation - best practice?)

>
> The W3C's WCAG states:
>
> 	Priority 2 - 3.1 "When an appropriate markup language
> exists, use markup rather than images to convey information."
>
> It can't be clearer than that.  You keep asking how, many keep suggesting
> don't.

Whoo Hoo!!

While this may not solve all of your problems, Stewart Rosenberger recently
posted an article at A List Apart
(http://www.alistapart.com/articles/dynatext/) which may provide something
of a partial solution to Kurt's dilemma.  I have only just glanced at this
article, but by all accounts it appears that a design hurdle may have been
significantly addressed here.  Normally I advocate *NOT* using Client Side
script except for non-critical "eye-candy"; this I feel falls into that
category, as fully implemented it is backwards compatible and does not
"break" when client side scripting is not available.  I plan on playing
around with this some more but at first glance this technique appears to
support Standards Compliant, Accessible and yet Aesthetically pleasing
development.  Thanks Stewart!

> But forward thinking professionals will seek instead to push the
> envelope, to try and deliver the pizzazz and punch that many have come to
> expect but will do so in accessible ways.  They will think outside of the
> box, try new ideas, fight for a better way, push, prod and plead.  The
> choice is there for all...

(Hey, didn't I just say that?)

Cheers!

JF
--
John Foliot  foliot@wats.ca
Web Accessibility Specialist / Co-founder of WATS.ca
Web Accessibility Testing and Services
http://www.wats.ca   1.866.932.4878 (North America)

Received on Thursday, 24 June 2004 15:25:32 UTC