Just out of curiousity, does it really matter if there are remaining validation errors on a web page if the page seems to work fine across the different browsers?

I guess the point in question relates to the menu things I've been playing with.

On my index page I have 5 individual menus and I don't seem to be able to avoid getting away with declaring the ul id repeatedly without the menu falling apart (if anyone has any suggestions I'd be glad to hear them).

I tried creating a table around the menu (see the fonts page) with fixed width cells - I know that should be done in the css - thereby removing the excess ul id's & it works brilliantly across all browsers (also removing the need to have such a large gap down the bottom... some lining up still needs to be done on the menu) but on validating I now get the message that tables & ul's don't play together???

While it may not be kosher, to what extent is it really an issue?

I haven't checked your code, but I assume you have given the various ul's different IDs. One and the same ID can only be used once per page. If you have ul classes, you can use them several times.

Regarding the validation:

Two browsers will never show a web page 110% the same because of differing browser specific settings. But to make a page look at least 99% the same, you should use valid code, both for html and css. The two most common browsers, IE and Ffx usually set the standard, and it can be hard enough to show exactly the same in those two, even with resetting rules, especially when html5 and css3 are involved.

Having said that, it depends on what kind of errors you get when validating. A misplaced or forgotten </div> can produce quite different page views, as some browsers are more 'forgiving' and ignore the error, assuming it knows what was intended (which is not always right), whereas other browsers are more strict.

Such errors as something 'is obsolete, use css instead' are not so important to how a site appears.

You'll have to 'suck it and see'. Best practice is valid code, several browsers installed and testing as you go.

I'm pretty sure I have the solution to my home page validation worked out not as far as declaring different IDs via the css file.

While the font page works fine, the issue seems to come down to using tables for layout. The fun police are saying no...

Looking a bit closer at your code I noticed the same ID more than once on the same page.

As to tables versus css for layout... Css is more flexible and the 'modern' way to go, but tables are not forbidden. Surely, if you used more css for layout and appearence, it would be much easier if you wanted to change something.

Sorry Inger, my last comments didn't quite come out right. The "not" shouldn't have been in there. Fully validated now with different IDs.

Congratulations!

You could also try validating the css. You will get a lot of errors like 'property -moz/-webkit-whatever does not exist', but those can be ignored. Those properties pertain to css3, but not to css2.1. But there are some parse errors in between that you should look at.

Thanks Inger
I'll definitely get around to the rest of the pages & css files.

In the case of issues where css (or html for that matter) may not be necessarily valid for an older version but is for the current as in the case you mentioned, and providing it doesn't adversely affect the on-screen results it probably should be ignored then shouldn't it?

I wouldn't say SHOULD be ignored...