There’s nothing inherently wrong with tables;
Early browsers like IE 3,4 & NS4 didnt have anything to lay out a webpage; if you didnt use them, you’d have simple paragraphs, images & horizontal rules. ick
(I’ve missed a lot out for the sake of argument)
IE 5 has got positioning, and some other basics, but this doesnt provide for an accessible website, fixed layouts, fontsizes etc.
IE6 has been sitting on windows machines for 2 years, Mozilla has had the same features nearly as long (and is now way ahead), and even Safari/Konq. is nearly up to spec.
So thats win/linux/mac/beos covered. And for all you textmode people, we have an automatic gain without tables - we render well as text.
We should take this time to improve sites for the future, and decide that tables are semantically the wrong way to markup a website.
Taking the current site, i’ve:
- removed images for links (they do look lovely, but they are an accessibility nightmare - if you're interested, read up Image Replacement techniques, there are loads of ideas, none that are foolproof),
- removed all javascript (there's only one small 400b file for IE users only)
- made printing 'nice', doesnt mess up printjobs like tables can & do.
- made it lynx friendly.
- made the layout more flexible, with font-size
At the moment, i’m debating two methods for the side menus, thats my stumbling block.
The downside to this, is discontinuing support for older browsers that are stuck between full css and no css. Netscape 4.0 users will see a lynx style site. Same as IE3 users.
Net+ users are likely to get a slightly garbled site, and thats unfortunate.
kurtis, I don’t want to appear like i’m trying to replace your efforts; I’d like to discuss this with you more, see if you’ll join the rebels 8)
John
*removed rogue /list