What is the point of making an HTML page reasonable?

Question

Since I learned about the W3C Validator , I have made sure that every HTML document I made is valid HTML.

However, in my opinion, sometimes you just don’t need to waste time making it valid. Of course, for actual web pages it can be important, but it makes pages on the intranet or even small interfaces that are used with other programs when the HTML page is displayed correctly in the most used browsers (not necessarily counting IE 6 and 7).

I think that I am mainly talking about small improvements over the code, for example, wrapping each page element displayed with <p> or <div> tags.

Answer 1

Creating a page for self-examination is not a business proposal. What happens to end users (with their confusing browsers) is a real test.

However, checking periodically helps you debug. It will catch more significant errors, such as closed tags. Which, in turn, affects end users. Therefore, consider validation as compiler warnings — good for discipline.

Answer 2

This is best practice, but it really comes down to organizational requirements / desire. Is it important enough that standards add value to your organization? Or is it just enough that it displays correctly? Often with intranets, his last.

Answer 3

Creating an HTML page is "really" worth it if you intend to be friendly in the future. That is, when browsers begin to cross out outdated or provider-specific tags, you will find that your page does not display correctly.

Web standards exist for some reason - to ensure consistent display / output among web browsers and interpreters. Selecting your pages in inappropriate HTML is your decision. It is also to take the old proverb, your "funeral."

Answer 4

What happens when the intranet browser changes? It is impossible to guarantee that the code that you have will be displayed correctly in EVERY browser. But in many cases, browsers will be pretty close to the standard. I think it also depends on how complex the page is, because the chances that it renders differently in different browsers increase as CSS becomes more complex and the depth of the tags. The best way is to write valid cross-browser code and test target browsers. Its stupid to think about writing once and making the same thing everywhere possible for all browsers. But adhering to standards is the best way to get closer.