How important is it really to validate codes by the W3C?

Question

How important is it really to validate codes by the W3C?

Navigation

#1 by (3 votes)

7

I understand that validating the code can be important and especially help those who are starting to correct errors and become more informed about obsolete elements in current versions of the languages.

But how much should I worry about validating my HTML and CSS , for example, my code HTML gave an alert that I'm using an iframe that has a frameborder attribute, and it's obsolete, but this part of the code is actually a Faceboook plugin and anything I change in that part of the code it crashes (I'm not in favor of using these social plugins but it was the customer's requirement).

This has only been an example of things like libraries or frameworks that I have tried to use, or even browser hacks that I needed to use to fix CSS problems in some browsers, and of course hacks are accused of validation errors.

I currently use this W3C validation only to correct simple errors that I have missed, and I do not try to meet 100% of what they indicate.

So, I wanted to know how much effort it takes to have your code validated 100% by W3C, I mean time and give up elements that you use but that you did not develop. Also, is there any real benefit in having the validation or is it simply a fix that lets you hang around saying that your code is good because the W3C said it is?

NOTE: I am not advocating completely crazy codes and bad done full of errors and etc.

html css w3c

asked by anonymous 24.10.2017 / 15:05

1 answer

Nav-bar responsive at the Foundation? How to get the current location of the android device?

score 3 · Accepted Answer

Do you need it? if you are a web developer or a web designer this tool will be a powerful ally. It is not only capable of compare a style sheet with the specifications for CSS, pointing out mistakes, incorrect spelling or inappropriate use of CSS, but also will alert you to potential usability risks.

Source: link

The validation service is a tool, so it is up to the developer to evaluate whether or not it is worth making certain changes to conform to the w3c standards, it is always good to look for a code that is as correct as possible, the example that you informed, there was no way the customer requested something and you have to comply, is it worth explaining to the customer what is happening? Will the customer want to wait this time? Or shoulder the costs? Will this generate future problems? All of this should be taken into account at the time of evaluation.

And as written in the link above:

It is only a valuable and reliable tool, being a tool based on software, is subject to bugs and inaccuracies & legacy bugs and inaccuracies

In other words, it is a great tool, it will show many errors automatically, but it will not be able to have the discernment of the domain, it is up to the developer to evaluate in the end whether or not to make a certain change.