why validate websites

Why do I need to validate my website using w3c? Is that that necessary and what does it help with?

It make sure that you don't have any invalid mark-up. That's all. There are more important things to worry about.

Valid code is definitely part of the deal though. Valid code (usually) means that your code will be more accessible to more people, will render properly in most browsers and can potentially increase your search engine rankings. It is also important that your code is intelligently structured and as semantica as is possible. Simply using valid code will not deliver these results though; you need to go along with the whole web standards shebang. Semantic code, valid code, accessible code, separation on structure, presentation and behaviour. All of these things combined will help you to create a web experience that as many people as possible can enjoy with a good degree of consistency.

Pete.

There was a lengthy discussion about this already ... just a few threads down

Importance of Validation

Page not found

I found it thanks. lol I'm now confused if to validate or not. I have never done it. I think I will validate one site and find out which the advantages and the dis. Thanks anyway. I think Pete convinced me that validating is a waste of time but I will give it a try.

To each his own ... I will not get into this again as I've stated my position in the mentioned thread but I find validating an integral part of what I do ... helps me eliminate stupid mistakes.

I said Validating was waste of my time. Valid code is essential. If you are confident that your can write perfectly valid code then by all means stop validating but don't stop writing valid code. That was my point. I was irritated that people seemed to treat validation as the key thing, when validation for its own sake is pointless. Concentrate on the code, make sure you validate not for the sake of good code but for your visitors and definitely don't do it for the special badge.

Pete.

I am learning hand coding and I validate with great regularity to make sure I am close formating correctly. Besides I actually smile when something validates for me.

Yes, I think the validation tool is very useful when you are still learning, it can help you discover the reason why something isn't working as it should. I like to think of the validator as like someone marking my work. I think like Pete says, if you're confident that you can write valid code anyway, then the actual act of validating MIGHT not be necessary for you.

I used it a lot at first and think it's an excellent learning tool. Besides, I have similar tools on my HTML editors.

Pete.

Ok, I haven't seen the previous thread but have seen many like them, and they are usually a heated debate. I'll make one quick comment. It has been my experience that the validation issue usually comes down to the difference between web site developers and web site designers. To be proficient in both aspects is not an easy task. A designer is a different animal from a developer. Not to say that one can't be a little of both.

A Web Developer cares a great deal about validation. And most likely validates every page they create. They are more concerned with how the web site works then about how "pretty" it is. Not to say that a developer doesn't create aesthetically pleasing pages. But they place things like accessibility and usability first. Then work on making the page pleasing to the eye.

A Web Designer cares a great deal about what the site looks like, and that the message they are trying to convey by the use of colors and images is received by the viewer or user. They often do validate, but do not put the effort into it that a developer would. And again, this is not to say that a designer cannot be a great developer.

Hope that clears up the validation debate a little for ya.

And finally...My Disclaimer - These are my opinions based on my experience.

Scott

__________________
Web Design and Development

To answer your question: Yes, you should validate your code. Especially if you are learning! That way, you can iron out any errors and avoid repeating them in future!

Validation is not important, validity is. Sometimes truly accessible code is not valid. It happens, not often I'll grant you, but it has been known.

Pete.

Confidence may be misplaced.

I'm confident of writing valid code: I know the general rules. But sometimes I make errors. Constant background validation alerts me when I make a mistake.

I just discovered that my javascript, which was generating extra (presentational) markup, was making my HTML invalid. I did not detect this, because the W3C validator checks the page without javascript transformations (and so does my background validator).

My error was to put <div>s inside a <dl>. They are not allowed there.

I suspect this mistake was the cause of an irregularly occurring, unpredictable browser rendering bug. Validation greatly reduces the need for bug-hunting.

It's late mike, go to bed. There is a time for valid code, I don't know if that time is 2:10 AM. I may put a disclaimer on all future sites "Website only valid from 9AM til 5PM". But I may not.

Pete.

Looks like I'm not the only one unable to sleep tonight!