Why do we need Web standardization?

It is correct to adopt the W3C Recommendation standards for design. When I was about to redesign the adaptivepath.com site, my partner agreed to use a standard-compliant approach to build it. But before we started, we also had some discussions: the adoption of web standards requires a lot of effort, is this worthwhile?
Of course, re-design can establish credibility in "web standards supporter", but apart from the praise of the industry, is the standard really important for personal business sites like ours? Can web standards return to us? Is there any economic benefit for converting to XHTML + CSS? All the answers are: yes.
Accelerated development
Although the simplicity of HTML pages has greatly promoted the development of web, it has become a curse. Because they are so "tolerant" to the code format, they contribute to the development of some browser private code, these private code makes countless users unable to get the best experience (see the best results of the page ).
Many of our customers have created multiple versions for the site to provide the most perfect design for as many users as possible. For our company, we only need to use a set of HTML pages, a style sheet, and a small amount of development, more than 95% of adaptivepath.com website users use a browser that complies with the standard (standards-c ompliant), so we think it is time to transition to the web standard.
Web standards force you to perform error verification. Simply declare the version of your HTML, and the verification program will verify your page according to the declared standard. The validator will strictly verify and tell you in detail what errors are there, which shortens the developer's time spent on quality and ensures high consistency of your sites on different browsers. Even though the browser still has some bugs, it is much better than it was five years ago.
Easy to maintain and increase opportunities
For many years, the web Standard Group has always recommended the advantages of "keeping visual design and content separated", which means HTML becomes very simple (almost ridiculous ), most xhtm l pages only have <div> and <p> tags with rich semantics, as well as a link to a powerful CSS file. This complete separation simplifies page development and maintenance. The first reason is that it enables better coordination between development teams. For example, editors and designers can work separately.
Recently, there was a project where we used CSS technology and we developed CSS files for our customers on our own development server. While they prepare content on the backend server, we can also constantly modify the design. We only need to simply edit the CSS file without the need to combine it with their version release system, work is done in parallel, and we dramatically shorten the development time. Rapid development has gained competitive and cost advantages. Shorter development time not only saves costs, but also makes resources idle, so more opportunities are available.
Expand access channels
Clean Code brings more benefits. Browsers that do not support CSS can now simply ignore style sheets. In other words, the semantic XHTML representation can be presented by any browser, including non-traditional clients, for example, mobile phones, PDAs, Voice readers, and screen readers can be used by any device that supports these simple tags.