Sent by aardvark on 18 July 2002 10:10
> From: "Ines Robbers" [EMAIL-REMOVED]>
>
> I'm building a new homepage for a university. Since especially
> universities often still use Netscape 4.x the site must be compatible
> with this unfortunate browser too. Javascript is also not permitted
> because of firewalls and other issues. Last but not least it has to be
> accessable to handicapped people. All these restrictions make it
[...]
you don't necessarily need to use client- or server-side scripting...
client-side scripting in particular will result in the most problems...
disabled JS is also more common than people think...
the technique i use most successfully, and which removes the
need for browser detection, is the @import method...
i first call a CSS file through <link>, and make sure all the style
contained work nicely on NN4.x...
then i call a CSS file via @import, and insert styles that would
otherwise hose NN4.x (things like line-height, for example)...
if you use valid, structural HTML for your page, then accessibility
really won't be a concern... read through the WAI guidelines to be
sure you don't do things like set all your copy in images, or fail to
provide enough contrast on the page...
--
Read the evolt.org case study
Usability: The Site Speaks for Itself
http://amazon.com/exec/obidos/ASIN/1904151035/evoltorg02-20
ISBN: 1904151035
