XHTML

From Wikipedia, the free encyclopedia

XHTML

Filename extension	.xhtml, .xht, .xml, .html, .htm
Internet media type	application/xhtml+xml
Developed by	World Wide Web Consortium
Type of format	Markup language
Extended from	XML, HTML
Standard(s)	1.0 (Recommendation), 1.1 (Recommendation), 1.1 SE (Working Draft), 5 (Working Draft), 2.0 (Working Draft)

The Extensible Hypertext Markup Language, or XHTML, is a markup language that has the same depth of expression as HTML, but also conforms to XML syntax.

While HTML prior to HTML 5 was defined as an application of Standard Generalized Markup Language (SGML), a very flexible markup language, XHTML is an application of XML, a more restrictive subset of SGML. Because they need to be well-formed, true XHTML documents allow for automated processing to be performed using standard XML tools—unlike HTML, which requires a relatively complex, lenient, and generally custom parser. XHTML can be thought of as the intersection of HTML and XML in many respects, since it is a reformulation of HTML in XML. XHTML 1.0 became a World Wide Web Consortium (W3C) Recommendation on January 26, 2000. XHTML 1.1 became a W3C Recommendation on May 31, 2001.

[edit] Overview

XHTML is "a reformulation of the three HTML 4 document types as applications of XML 1.0".^[1] The W3C also continues to maintain the HTML 4.01 Recommendation and the specifications for HTML 5 and XHTML 5 are being actively developed. In the current XHTML 1.0 Recommendation document, as published and revised to August 2002, the W3C comments that, "The XHTML family is the next step in the evolution of the Internet. By migrating to XHTML today, content developers can enter the XML world with all of its attendant benefits, while still remaining confident in their content's backward and future compatibility."^[1]

[edit] Motivation

In the late 1990s, many considered that the future of HTML lay in the creation of a version adhering to the syntax rules of XML.^[2] The then current version of HTML, HTML 4, was ostensibly an application of Standard Generalized Markup Language (SGML); however the specification for SGML was complex, and neither web browsers nor the HTML 4 Recommendation were fully conformant with it.^[3] By shifting the underlying base from SGML to the simpler XML, HTML would become compatible with common XML tools.^[4] Servers and proxies would be able to transform content, as necessary, for constrained devices such as mobile phones.^[5]

Another key advantage was extensibility. By utilising namespaces, XHTML documents could include fragments from other XML-based languages such as Scalable Vector Graphics and MathML.^[6] Finally, the renewed work would provide an opportunity to divide HTML into reusable components (XHTML Modularization) and clean up untidy parts of the language.^[7]

[edit] Relationship to HTML

HTML is the antecedent technology to XHTML. The changes from HTML to first-generation XHTML 1.0 are minor and are mainly to achieve conformance with XML. The most important change is the requirement that the document must be well-formed and that all elements must be explicitly closed as required in XML.^[8] In XML, all element and attribute names are case-sensitive, so the XHTML approach has been to define all tag names to be lowercase.

This contrasts with some earlier established traditions that began around the time of HTML 2.0, when many used uppercase tags. In XHTML, all attribute values must be enclosed by quotes; either single (') or double (") quotes may be used. In contrast, this was sometimes optional in SGML-based HTML, where attributes can omit quotes in certain cases.^[9] All elements must also be explicitly closed, including empty (aka singleton) elements such as img and br. This can be done by adding a closing slash to the start tag, e. g., <img /> and <br />. Attribute minimization (e. g., <option selected>) is also prohibited, as the attribute selected contains no explicit value; instead this would be written as <option selected="selected">.

HTML elements that are optional in the content model will not appear in the DOM tree unless they are explicitly specified. For example, an XHTML page must have a <body> element, and a table will not have a <tbody> element unless the author specifies one.

The XHTML 1.0 recommendation devotes a section to differences between HTML and XHTML.^[10] The WHATWG wiki similarly considers differences that arise with the use of (X)HTML5.^[11]

Because XHTML and HTML are closely related technologies, sometimes they are written about and documented in parallel. In such circumstances, some authors conflate the two names by using a parenthetical notation, such as (X)HTML. This indicates that the documentation and principles can be considered to apply generally to both standards.^[12]

[edit] Adoption

The similarities between HTML 4.01 and XHTML 1.0 led many web sites and content management systems to adopt the initial W3C XHTML 1.0 Recommendation. To aid authors in the transition, the W3C provided guidance on how to publish XHTML 1.0 documents in an HTML-compatible manner, and serve them to browsers that were not designed for XHTML.^[13][14]

Such "HTML-compatible" content is sent using the HTML media type (text/html) rather than the official Internet media type for XHTML (application/xhtml+xml). When measuring the adoption of XHTML to that of regular HTML, therefore, it is important to distinguish whether it is media type usage or actual document contents that is being compared.

Most web browsers have mature support^[15] for all of the possible XHTML media types.^[16] The notable exception is Internet Explorer by Microsoft; rather than rendering application/xhtml+xml content, a dialog box invites the user to save the content to disk instead. Both Internet Explorer 7 (released in 2006) and Internet Explorer 8 Release Candidate 1 (released in January 2009) exhibit this behavior, and it is unclear whether this will be resolved in a future release.^[17] As long as this remains the case, most web developers avoid using XHTML that isn’t HTML-compatible,^[18] so advantages of XML such as namespaces, faster parsing and smaller-footprint browsers do not benefit the user. Microsoft developer Chris Wilson explained in 2005 that IE7’s priorities were improved security and CSS support, and that proper XHTML support would be difficult to graft onto IE’s compatibility-oriented HTML parser.^[19]

[edit] Criticism

In the early 2000s, some web developers began to question why Web authors ever made the leap into authoring in XHTML.^[20][21][22] Others countered that the problems ascribed to the use of XHTML could mostly be attributed to two main sources: the production of invalid XHTML documents by some Web authors and the lack of support for XHTML built into IE6.^[23][24] They went on to describe the benefits of XML-based Web documents (i.e. XHTML) regarding searching, indexing and parsing as well as future-proofing the Web itself.

In October 2006, HTML inventor and W3C chair Tim Berners-Lee, introducing a major W3C effort to develop new HTML 5 and XHTML 5 specifications, posted in his blog that, "The attempt to get the world to switch to XML … all at once didn't work. The large HTML-generating public did not move … Some large communities did shift and are enjoying the fruits of well-formed systems … The plan is to charter a completely new HTML group."^[25] In the current HTML and XHTML 5 working draft, its authors say that, "special attention has been given to defining clear conformance criteria for user agents in an effort to improve interoperability", "…while at the same time updating the HTML specifications to address issues raised in the past few years." Ian Hickson, author of a paper criticising the improper use of XHTML in 2002,^[20] is a member of the group developing this specification and is listed as one of the co-authors of the current working draft.^[26]

[edit] Versions of XHTML

[edit] XHTML 1.0

Wikipedia uses XHTML 1.0 Transitional

December 1998 saw the publication of a W3C Working Draft entitled Reformulating HTML in XML. This introduced Voyager, the codename for a new markup language based on HTML 4 but adhering to the stricter syntax rules of XML. By February 1999 the specification had changed name to XHTML 1.0: The Extensible HyperText Markup Language, and in January 2000 it was officially adopted as a W3C Recommendation.^[27] There are three formal DTDs for XHTML 1.0, corresponding to the three different versions of HTML 4.01:

• XHTML 1.0 Strict is the equivalent to strict HTML 4.01, and includes elements and attributes that have not been marked deprecated in the HTML 4.01 specification.
• XHTML 1.0 Transitional is the equivalent of HTML 4.01 Transitional, and includes the presentational elements (such as center, font and strike) excluded from the strict version.
• XHTML 1.0 Frameset is the equivalent of HTML 4.01 Frameset, and allows for the definition of frameset documents—a common Web feature in the late 1990s.

The second edition of XHTML 1.0 became a W3C Recommendation in August 2002.^[28]

[edit] Modularization of XHTML

Modularization provides an abstract collection of components through that XHTML can be subsetted and extended. The feature is intended to help XHTML extend its reach onto emerging platforms, such as mobile devices and Web-enabled televisions. The initial draft of Modularization of XHTML became available in April 1999, and reached Recommendation status in April 2001.^[29]

The first XHTML Family Markup Languages to be developed with this technique were XHTML 1.1 and XHTML Basic 1.0. Another example is XHTML-Print (W3C Recommendation, September 2006), a language designed for printing from mobile devices to low-cost printers.^[30]

In October 2008 Modularization of XHTML was superseded by XHTML Modularization 1.1, which adds an XML Schema implementation.^[31]

[edit] XHTML 1.1—Module-based XHTML

XHTML 1.1 evolved out of the work surrounding the initial Modularization of XHTML specification. The W3C released a first draft in September 1999; Recommendation status was reached in May 2001.^[32] The modules combined within XHTML 1.1 effectively recreate XHTML 1.0 Strict, with the addition of ruby annotation elements (ruby, rbc, rtc, rb, rt and rp) to better support East-Asian languages. Other changes include removal of the lang attribute (in favour of xml:lang), and removal of the name attribute from the a and map elements.

Although XHTML 1.1 is largely compatible with XHTML 1.0 and HTML 4, in August 2002 the W3C issued a formal Note advising that it should not be transmitted with the HTML media type.^[33] With limited browser support for the alternate application/xhtml+xml media type, XHTML 1.1 proved unable to gain widespread use. In January 2009 a second edition of the document was issued, relaxing this restriction and allowing XHTML 1.1 to be served as text/html.^[34]

XHTML 1.1 Second Edition is expected in the first quarter of 2009.^[35]

[edit] XHTML Basic and XHTML-MP

To support constrained devices, XHTML Basic was created by the W3C; it reached Recommendation status in December 2000.^[36] XHTML Basic 1.0 is the most restrictive version of XHTML, providing a minimal set of features that even the most limited devices can be expected to support.

The Open Mobile Alliance and its predecessor the WAP Forum released three specifications between 2001 and 2006 that extended XHTML Basic 1.0. Known as XHTML Mobile Profile or XHTML-MP, they were strongly focussed on uniting the differing markup languages used on mobile handsets at the time. All provide richer form controls than XHTML Basic 1.0, along with varying levels of scripting support.

XHTML Basic 1.1 became a W3C Recommendation in July 2008, superseding XHTML-MP 1.2.^[37] XHTML Basic 1.1 is almost but not quite a subset of regular XHTML 1.1. The most notable addition over XHTML 1.1 is the inputmode attribute—also found in XHTML-MP 1.2—which provides hints to help browsers improve form entry.

[edit] XHTML 1.2

This article or section contains information about scheduled or expected future software. The content may change as the software release approaches and more information becomes available.

The XHTML 2 Working Group is considering the creation a new language based on XHTML 1.1.^[38] If XHTML 1.2 is created, it will include WAI-ARIA and role attributes to better support accessible web applications, and improved Semantic Web support through RDFa. The inputmode attribute from XHTML Basic 1.1, along with the target attribute (for specifying frame targets) may also be present. It's important to note that the XHTML2 WG have not yet been chartered to carry out the development of XHTML1.2, this means that the XHTML1.2 proposal may not eventuate.

[edit] XHTML 2.0

This article or section contains information about scheduled or expected future software. The content may change as the software release approaches and more information becomes available.

Between August 2002 and July 2006 the W3C released the first eight Working Drafts of XHTML 2.0, a new version of XHTML able to make a clean break from the past by discarding the requirement of backward compatibility. This lack of compatibility with XHTML 1.x and HTML 4 caused some early controversy in the web developer community.^[39] Some parts of the language (such as the role and RDFa attributes) were subsequently split out of the specification and worked on as separate modules, partially to help make the transition from XHTML 1.x to XHTML 2.0 smoother. A ninth draft of XHTML 2.0 is expected to appear in 2009.

New features introduced by XHTML 2.0 include:

• HTML forms will be replaced by XForms, an XML-based user input specification allowing forms to be displayed appropriately for different rendering devices.
• HTML frames will be replaced by XFrames.
• The DOM Events will be replaced by XML Events, which uses the XML Document Object Model.
• A new list element type, the nl element type, will be included to specifically designate a list as a navigation list. This will be useful in creating nested menus, which are currently created by a wide variety of means like nested unordered lists or nested definition lists.
• Any element will be able to act as a hyperlink, e. g., <li href="articles.html">Articles</li>, similar to XLink. However, XLink itself is not compatible with XHTML due to design differences.
• Any element will be able to reference alternative media with the src attribute, e. g., <p src="lbridge.jpg" type="image/jpeg">London Bridge</p> is the same as <object src="lbridge.jpg" type="image/jpeg"><p>London Bridge</p></object>.
• The alt attribute of the img element has been removed: alternative text will be given in the content of the img element, much like the object element, e. g., <img src="hms_audacious.jpg">HMS <span class="italic">Audacious</span></img>.
• A single heading element (h) will be added. The level of these headings are determined by the depth of the nesting. This allows the use of headings to be infinite, rather than limiting use to six levels deep.
• The remaining presentational elements i, b and tt, still allowed in XHTML 1.x (even Strict), will be absent from XHTML 2.0. The only somewhat presentational elements remaining will be sup and sub for superscript and subscript respectively, because they have significant non-presentational uses and are required by certain languages. All other tags are meant to be semantic instead (e. g. <strong> for strong or bolded text) while allowing the user agent to control the presentation of elements via CSS.
• The addition of RDF triple with the property and about attributes to facilitate the conversion from XHTML to RDF/XML.

[edit] HTML 5—Vocabulary and APIs for HTML 5 and XHTML 5

This article or section contains information about scheduled or expected future software. The content may change as the software release approaches and more information becomes available.

HTML 5 initially grew independently of the W3C, through a loose group of browser manufacturers and other interested parties calling themselves the WHATWG, or Web Hypertext Application Technology Working Group. The WHATWG announced the existence of an open mailing list in June 2004, along with a website bearing the strapline “Maintaining and evolving HTML since 2004.”^[40] The key motive of the group was to create a platform for dynamic web applications; they considered XHTML 2.0 to be too document-centric, and not suitable for the creation of forum sites or online shops.^[41]

In April 2007, the Mozilla Foundation and Opera Software joined Apple in requesting that the newly rechartered HTML Working Group of the W3C adopt the work, under the name of HTML 5.^[42] The group resolved to do this the following month,^[43] and the First Public Working Draft of HTML 5 was issued by the W3C in January 2008. The most recent W3C Working Draft was published in June 2008.^[26]

HTML 5 has both a regular text/html serialization and an XML serialization, which is known as XHTML 5. In addition to the markup language, the specification includes a number of application programming interfaces. The Document Object Model is extended with APIs for editing, drag-and-drop, data storage and network communication.

The language can be considered more compatible with HTML 4 and XHTML 1.x than XHTML 2.0, due to the decision to keep the existing HTML form elements and events model. It adds many new elements not found in XHTML 1.x, however, such as section and aside. (The XHTML 1.2 equivalent (which (X)HTML 5 replaces) of these structural elements would be <div role="region"> and <div role="complementary">.)

The specification is expected to add WAI-ARIA support in a future draft. There is currently no indication as to whether HTML 5 will support RDFa.

[edit] Valid XHTML documents

An XHTML document that conforms to an XHTML specification is said to be valid. Validity assures consistency in document code, which in turn eases processing, but does not necessarily ensure consistent rendering by browsers. A document can be checked for validity with the W3C Markup Validation Service. In practice, many web development programs provide code validation based on the W3C standards.

[edit] Root element

The root element of an XHTML document must be html, and must contain an xmlns attribute to associate it with the XHTML namespace. The namespace URI for XHTML is http://www.w3.org/1999/xhtml. For XHTML 1.1 and later there should also ideally be a version attribute to clearly identify the version of XHTML being used. The example tag below additionally features an xml:lang attribute to identify the document with a natural language:

<html xmlns="http://www.w3.org/1999/xhtml" version="XHTML 1.2" xml:lang="en">

For XHTML 1.1 and 2.0 an optional schemaLocation attribute can be added, to associate the namespace with an XML Schema. The example below is for XHTML 2.0:

<html xmlns="http://www.w3.org/2002/06/xhtml2/" version="XHTML 2.0" xml:lang="en"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.w3.org/1999/xhtml
 
    http://www.w3.org/MarkUp/SCHEMA/xhtml2.xsd">

This example also demonstrates the use of multiple namespaces within a document. The xmlns:xsi declaration indicates that any elements or attributes prefixed with xsi: fall within the XML Schema instance namespace rather than the XHTML namespace. This mechanism of prefixes allows elements and attributes from different XML vocabularies to be mixed together in the same document, without the potential for naming clashes.

[edit] DOCTYPEs

In order to validate an XHTML document, a Document Type Declaration, or DOCTYPE, may be used. A DOCTYPE declares to the browser that Document Type Definition (DTD) the document conforms to. A Document Type Declaration should be placed before the root element.

The system identifier part of the DOCTYPE, which in these examples is the URL that begins with http://, need only point to a copy of the DTD to use, if the validator cannot locate one based on the public identifier (the other quoted string). It does not need to be the specific URL that is in these examples; in fact, authors are encouraged to use local copies of the DTD files when possible. The public identifier, however, must be character-for-character the same as in the examples.

[edit] XML declaration

A character encoding may be specified at the beginning of an XHTML document in the XML declaration when the document is served using the application/xhtml+xml MIME type. (If an XML document lacks encoding specification, an XML parser assumes that the encoding is UTF-8 or UTF-16, unless the encoding has already been determined by a higher protocol.)

For example:

<?xml version="1.0" encoding="UTF-8"?>

The declaration may be optionally omitted because it declares as its encoding the default encoding. However, if the document instead makes use of XML 1.1 or another character encoding, a declaration is necessary. Internet Explorer prior to version 7 enters quirks mode, if it encounters an XML declaration in a document served as text/html.

[edit] Common errors

Some of the most common errors in the usage of XHTML are:

• Not closing empty elements (elements without closing tags in HTML4)
  • Incorrect: <br>
  • Correct: <br />
    Note that any of these are acceptable in XHTML: <br></br>, <br/> and <br />. Older HTML-only browsers interpreting it as HTML will generally accept <br> and <br />.
• Not closing non-empty elements
  • Incorrect: <p>This is a paragraph.<p>This is another paragraph.
  • Correct: <p>This is a paragraph.</p><p>This is another paragraph.</p>
• Improperly nesting elements (Note that this would also be invalid in HTML)
  • Incorrect: <em><strong>This is some text.</em></strong>
  • Correct: <em><strong>This is some text.</strong></em>
• Not putting quotation marks around attribute values
  • Incorrect: <td rowspan=3>
  • Correct: <td rowspan="3">
  • Correct: <td rowspan='3'>
• Using the ampersand character outside of entities (Note that this would also be invalid in HTML)
  • Incorrect: <title>Cars & Trucks</title>
  • Correct: <title>Cars &amp; Trucks</title>
  • Incorrect: <a href="index.php?page=news&id=5">News</a>
  • Correct: <a href="index.php?page=news&amp;id=5">News</a>
• Failing to recognize that XHTML elements and attributes are case sensitive
  • Incorrect: <BODY><P ID="ONE">The Best Page Ever</P></BODY>
  • Correct: <body><p id="ONE">The Best Page Ever</p></body>
• Using attribute minimization
  • Incorrect: <textarea readonly>READ-ONLY</textarea>
  • Correct: <textarea readonly="readonly">READ-ONLY</textarea>
• Mis-using CDATA, script-comments and xml-comments when embedding scripts and stylesheets.
  • This problem can be avoided altogether by putting all script and stylesheet information into separate files and referring to them as follows in the XHTML head element.

 <link rel="stylesheet" href="/style/screen.css" type="text/css" />
 <script type="text/javascript" src="/script/site.js"></script>

Note: The format <script …></script>, rather than the more concise <script … />, is required for HTML compatibility when served as MIME type text/html.

• If an author chooses to include script or style data inline within an XHTML document, different approaches are recommended as shown in the examples below, depending whether the author intends to serve the page as application/xhtml+xml and target only fully conformant browsers, or serve the page as text/html and try to obtain usability in Internet Explorer 6 and other non-conformant browsers.

[edit] Backward compatibility

XHTML 1.x documents are mostly backward compatible with HTML 4 user agents when the appropriate guidelines are followed. XHTML 1.1 is essentially compatible, although the elements for ruby annotation are not part of the HTML 4 specification and thus generally ignored by HTML 4 browsers. Later XHTML 1.x modules such as those for the role attribute, RDFa and WAI-ARIA degrade gracefully in a similar manner.

HTML 5 and XHTML 2 are significantly less compatible, although this can be mitigated to some degree through the use of scripting. (This can be simple one-liners, such as the use of “document.createElement()” to register a new HTML element within Internet Explorer, or complete JavaScript frameworks, such as the FormFaces implementation of XForms.)

[edit] Examples

The following are examples of XHTML 1.0 Strict, with both having the same visual output. The former one follows the HTML Compatibility Guidelines of the XHTML Media Types Note while the latter one breaks backward compatibility but provides cleaner markup.^[34]

Example 1.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
 <title>XHTML 1.0 Example</title>
 <script type="text/javascript">
 //<![CDATA[
 function loadpdf() {
    document.getElementById("pdf-object").src="http://www.w3.org/TR/xhtml1/xhtml1.pdf";
 }
 //]]>
 </script>
 </head>
 <body onload="loadpdf()">
 <p>This is an example of an
 <abbr title="Extensible HyperText Markup Language">XHTML</abbr> 1.0 Strict document.<br />
 <img id="validation-icon"
    src="http://www.w3.org/Icons/valid-xhtml10"
    alt="Valid XHTML 1.0 Strict" /><br />
 <object id="pdf-object"
    name="pdf-object"
    type="application/pdf"
    data="http://www.w3.org/TR/xhtml1/xhtml1.pdf"
    width="100%"
    height="500">
 </object>
 </p>
 </body>
</html>

Example 2.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
 <head>
 <title>XHTML 1.0 Example</title>
 <script type="application/javascript">
 <![CDATA[
 function loadpdf() {
    document.getElementById("pdf-object").src="http://www.w3.org/TR/xhtml1/xhtml1.pdf";
 }
 ]]>
 </script>
 </head>
 <body onload="loadpdf()">
 <p>This is an example of an
 <abbr title="Extensible HyperText Markup Language">XHTML</abbr> 1.0 Strict document.<br/>
 <img id="validation-icon"
    src="http://www.w3.org/Icons/valid-xhtml10"
    alt="Valid XHTML 1.0 Strict"/><br/>
 <object id="pdf-object"
    type="application/pdf"
    data="http://www.w3.org/TR/xhtml1/xhtml1.pdf"
    width="100%"
    height="500"/>
 </p>
 </body>
</html>

Notes:

1. The "loadpdf" function is actually a workaround for Internet Explorer. It can be replaced by adding <param name="src" value="http://www.w3.org/TR/xhtml1/xhtml1.pdf" /> within <object>.
2. The img element does not get a name attribute in the XHTML 1.0 Strict DTD. Use id instead.

[edit] Notes

[edit] External links

Wikibooks has a book on the topic of XHTML

• W3C's Markup Home Page
• XHTML 1.0 Recommendation
• XHTML 1.1 Recommendation
• XHTML 1.1 Second Edition Working Draft
• XHTML 2.0 Working Draft
• XHTML Basic
• XHTML 1.0 Strict / 1.1 Online Reference
• An Overview of Mobile Versions of XHTML
• Links dealing with the MIME type of XHTML documents:
  • Beware of XHTML
  • Sending XHTML as text/html Considered Harmful
  • Serving up XHTML with the correct MIME type
  • The Road to XHTML 2.0: MIME Types - Mark Pilgrim (3/19/2003). Includes examples for conditionally serving application/xhtml+xml using PHP, Python, and Apache (mod rewrite).
  • Mozilla Web Author FAQ: How is the treatment of application/xhtml+xml documents different from the treatment of text/html documents? - summarizes one web browser's XHTML processing mode
• Empty elements in SGML, HTML, XML, and XHTML
• Heptagrama's Basic XHTML 1.0 Strict Tutorial

[edit] Validators

• W3C's Markup Validator
• Firefox page validator Extension to Mozilla Firefox browser
• WDG HTML Validator
• Hermish Web Accessibility Validator
• Off-line HTML Validator A clipbook for NoteTab text editor
• XHTML Validator Module for ASP.NET 2.0
• Validating XML/XHTML Editor
• Multipage Validator
• Total Validator