But while current practices actively request and promote using these validation tools, no web-based tool is a substitute for good judgment.The case for under-dependence can be seen by examining the Alexa Top 100 sites and using some basic W3C validation tests.
Front-end and backend frameworks, like Rails and Angular, give structure to our code, dividing it into, smaller, easier to maintain chunks.
Although HTML and CSS validation icons no longer appear at the bottom of every modern-facing website, there is still a general sentiment that validation is necessary.
Can we satisfy standards compliance without the need for validation, or, alternatively, is there a better approach to validation? Validation was created, in part, to drum up interest for standards compliance after newfangled browsers like Netscape and Internet Explorer started extending the capabilities of HTML in the early 1990s. Many rebuffed these additions as going beyond the original intent of the language, to provide document structure, not influence stylistic choices.
Our framework is tested in almost every perceivable browser, and battle-tested daily by our 20-plus team of engineers and designers, and yet we still don't meet validation, even though it renders well in most every browser.
This made us wonder if validation is still relevant?