Let's list the non-XHTML stuff that we can find :)

[Spaceman-Spiff]

i found this today: the category and board title should be checked to convert '&' into '&', maybe it affects a few other characters too, like copyright sign

[Gobalopper]

<font> should be removed.

Certain attributes on tags should be removed. Like border="0" on images, align="center" on pretty much everthing.

[Spaceman-Spiff]

arent those for XHTML 1.1?

News.php isnt valid XHTML 1.0 too, but i think its been fixed

[[Unknown]]

<font> should be removed.

Certain attributes on tags should be removed. Like border="0" on images, align="center" on pretty much everthing.

No!  If you remove border="0" from img tags, all images that are links will get boxes around them... EVEN IN CURRENT BROWSERS!!! That's definitely a bad thing.

I think align="center" is kept for compatiblity with Netscape 4.7.  Please, people, stop using it.... please.

-[Unknown]

[Joel]

No!  If you remove border="0" from img tags, all images that are links will get boxes around them... EVEN IN CURRENT BROWSERS!!! That's definitely a bad thing.

Adding "img { border: 0 }" to the stylesheet will fix that.

[[Unknown]]

No!  If you remove border="0" from img tags, all images that are links will get boxes around them... EVEN IN CURRENT BROWSERS!!! That's definitely a bad thing.

Adding "img { border: 0 }" to the stylesheet will fix that.

What was that I said about "trying to support dinosaur *coughnetscapecough* browsers?

-[Unknown]

[Joel]

NS4 compatibility shouldn't even be considered. It just allows those that still use it to think their browser is still A-OK.

[Gobalopper]

Isn't font is deprecated now? Meaning it shouldn't be used, use something like span instead if you still want the font size everywhere, another bad practice in my opinion.
And I remember reading that the next YaBB wouldn't try bad hacks to make the board look good in NS 4.

Things like <table align="center"> should not be used. There are a few others, I've converted my board to be XHTML 1.1 compliant and there was a bunch of things that needed to change, can't remember them all now.

Which XHTML version/type are we are trying to comply with?

[[Unknown]]

As you can see at the bottom of every page, YaBB SE complies with xhtml 1.0 transitional.

Normally, my code is usually xhtml 1.0 strict.  I don't use font or anything like that, but I do some things that 1.1 doesn't like.

I don't care nearly as much for standards (although I do) as for compatibility.  I want it to work in as many browsers as possible... even if that makes it invalid.  However, I strive for the best of both worlds... which nearly always means going with a slightly older schema.

-[Unknown]

[Manco]

I supposed it is a long ways off before getting rid of nested tables completely and going with a tableless design using CSS positioning.

[andrea]

I don't care nearly as much for standards (although I do) as for compatibility.  I want it to work in as many browsers as possible... even if that makes it invalid.  However, I strive for the best of both worlds... which nearly always means going with a slightly older schema.

Fully agree with that. It would be very wrong to support the newer browsers only. I also think it is very important to support as many browsers as possible.

[Gobalopper]

The layout should still work in older browsers especially if you still use tables. It may not look pretty but it should still work.

[Michele]

Actually, for us web admins sake, you should remove the font sizes from all the files in the Sources directory... it screws up nearly every innovative template out there.

Define a set of sizes in the CSS (preferably, x-small, small, etc) for each class/id and be done with it. For my site, I use small for normal text and x-small for small text. When you combine px sizes in the CSS with <font size=> in the sources files, you turn scalable fonts into non-scalable fonts.

Then, get rid of all the NTS tables (Nested Table Syndrome). Learn how to do cool borders with the CSS and forget about Netscape4 and get rid of those extra tables! And don't forget to use <th> when appropriate.

For the tables that are left, add a title=, summary= and/or <caption> tag to them to improve Accessibility. I haven't found a way to remove the tables from the Sources files, but I think basic table structure in there is fine. If you set up the CSS properly, we can still maintain flexibility.

Thanks for listening, Michele