Broadly Accessible (was Re: Table problem

by Tamara <tamara(at)abbeyink.com>

 Date:  Wed, 16 May 2001 08:05:28 -0500
 To:  kixi(at)altavista.net
 Cc:  HWG-basics <HWG-basics(at)hwg.org>
 References:  canopy
  todo: View Thread, Original
At 10:07 AM 5/16/2001 +0200, Jakob D=F6lling wrote:
>Thanks. BTW: My client wants me to have website that is as broadly as
>possible accessible. What happens if a user who has a browser of a older
>generation is visiting his website?

Jakob,

You're going to have to define that one.

You can use older DTDs which the Cap'n will recommend, but even more=20
current DTDs, such as XHTML /should/ still make the pages accessible and=20
usable if you do it right.

It just depends on what's more important to the customer and what features=
=20
s/he needs. Remember the ruckus over http://www.alistapart.com/ going to=20
XHTML 1.0 Strict and using CSS positioning? It looked awful in NN 4+, but,=
=20
IIRC, the site still worked. It's been awhile since I went there, but it=20
did work.

That's a drastic example, but I'm sure they, too, considered their audience=
=20
and decided to go with the latest and greatest anyway.

FWIW,
<tamara />

HTML: hwg-basics mailing list archives, maintained by Webmasters @ IWA