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.
Keeping valid pages is one step into maintaining a properly coded site.
To administrate W3C Validator, go to : /admin/config/development/w3c_validator To validate manually a page, go to : /validator To check your site and validate it all, go to : /admin/reports/w3c_validator --- NOTE : From version 6.x-1.2 you can alternatively use the HTML Tidy library via its PHP extension.
This also allows you to validate private pages, ie: unpublished nodes, private views.
The service was designed to help people generate syntactically accurate markup in both HTML and CSS. In the early 2000s validation symbolized professionalism among web developers. We are now using better development tools that catch mistakes earlier.
Editing software and IDE's now have linting — a method of validating syntax — built in, or have third party extensions that do the same.
Search for w3c validating:
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.