Is HTMl/CSS Validation really nessasary?

Question

Sorry for my crappy spelling.

Surely as long as the site looks good and it's easy to use, that shouldn't really matter?

I've discussed this with many webmasters and mistresses and they seem to think it does and it doesnt. Even when coming to selling your designs.

Answer 1

It really doesn't unless you're dealing with a standards-conscious developer, or if 508 (disability accessibility) is a concern. Otherwise, us web designers may care about the integrity of our code, but virtually all clients don't care as long as the page loads quickly and looks good. Granted, proper implementation of CSS will enable faster load times, especially when leaving behind table-based layouts.

Answer 2

It depends on the nature of the errors. It's best to fix non-standard code, because you never know how the next browser release might interpret it. It's good practice to check the validator output to be sure that you're okay with any errors it flags.

But there's a lot of standards compliance junk that I think you can safely ignore. For instance, you'll get an error if any graphics lack alt tags, but when the graphic in question is just a border, who cares. I'd argue that for anyone actually using those alt tags to decipher your site, it's just clutter and better omitted.

Answer 3

As a good web developer you need to add every validation (if necessary security checks) on your websites especially if this holds valuable information.

The truth is.. that question can be answered only by your customer? But it will be nice if you surf your site, you will not see error pages...

Answer 4

m2 isn't a tag ingredient and until eventually you do not make use of XML, you go with to eliminate the "<>". XML you could outline it so it would not get flagged. when you're utilising frames, you'll have the perfect frameset doctype on ALL pages. spacer isn't an ingredient. marquee is a sequence of tags, yet you should code it precise with its attributes. Ron