Tag certifying that a website has been checked for well-formed XHTML (above) and CSS (below) markup

The Markup Validation Service is a validator by the World Wide Web Consortium (W3C) that allows Internet users to check pre-HTML5 HTML and XHTML documents for well-formed markup against a document type definition (DTD). Markup validation is an important step towards ensuring the technical quality of web pages. However, it is not a complete measure of web standards conformance.^[1] Though W3C validation is important for browser compatibility and site usability, it has not been confirmed what effect it has on search engine optimization.

As HTML5 has removed the use of DTD in favor of a "Living Standard", the traditional Markup Validation Service is not applicable to these formats. Validation is instead performed using an open-source "Nu Validator", an instance of which is provided by W3C.^[2]

Criticism

The W3C Markup Validation Service uses or used an SGML parser to parse HTML.^[3][4] This procedure is heavily criticized in the WHATWG HTML5 specification:

While the HTML syntax described in this specification bears a close resemblance to SGML and XML, it is a separate language with its own parsing rules. Some earlier versions of HTML (in particular from HTML2 to HTML4) were based on SGML and used SGML parsing rules. However, few (if any) web browsers ever implemented true SGML parsing for HTML documents; the only user agents to strictly handle HTML as an SGML application have historically been validators. The resulting confusion — with validators claiming documents to have one representation while widely deployed web browsers interoperably implemented a different representation — has wasted decades of productivity. This version of HTML thus returns to a non-SGML basis.

Google.com did not validate in the W3C validator in 2009. Matt Cutts, who was head of Google’s webspam team, mocked the W3C validator saying, “And so we’re a little more worried about compatibility with all those different types of browsers than we necessarily are about whether we validate according to the W3C. ... But it’s important to realize that the vast majority of pages on the web don’t validate.”^[5]

History

The Markup Validation Service began as The Kinder, Gentler HTML Validator, a project by Gerald Oskoboiny.^[1] It was developed to be a more intuitive version of the first online HTML validator written by Dan Connolly and Mark Gaither, which was announced on July 13, 1994.^[6]

In September 1997, Oskoboiny began working for the W3C, and on December 18, 1997, the W3C announced its W3C HTML Validator based upon his works.^[7] In November 2008, the W3C released the validator.nu HTML5 engine and the ability to check documents for conformance to HTML5.^[8]

W3C also offers validation tools for web technologies other than HTML/XHTML, such as CSS, XML schemas, and MathML.^[9]

Browser accommodation

Many major web browsers are often tolerant of certain types of error, and may display a document successfully even if it is not syntactically correct. Certain other XML documents can also be validated if they refer to an internal or external DTD.

Limitations

Mark-up validators cannot see the "big picture" on a web page,^{[clarification needed]} but they excel at picking up missed closing tags and other technicalities.^[9][10]

DTD-based validators are also limited in their ability to check attribute values according to many specification documents. For example, using an HTML 4.01 DOCTYPE, bgcolor="fffff" is accepted as valid for the "body" element even though the value "fffff" is missing a preceding '#' character and contains only five (instead of six) hexadecimal digits. Also, for the "img" element, width="really wide" is also accepted as valid. DTD-based validators are technically not able to test for these types of attribute value problems.

Pages may not display as intended in all browsers, even in the absence of validation errors and successful display in other browsers. The only way to ensure that pages always display as intended is to test them in all browsers expected to render them correctly.^[10]

CSS validation

While the W3C and other HTML and XHTML validators will assess pages coded in those formats, a separate validator like the W3C CSS validator can check that there are no errors in the associated Cascading Style Sheet. CSS validators apply current CSS standards to referenced CSS documents.^[10]

See also

• CSS HTML Validator, offline HTML and CSS validator desktop software
• World Wide Web Consortium (W3C)

References

External links

Wikimedia Commons has media related to W3C validation.

• The W3C Markup Validation Service
• The W3C CSS Validation Service