The content of this document is also available as multiple HTML files.
This specification describes the fifth major version of the HTML language and provides the details necessary for producers of HTML content to create documents that conform to the language, as well as describing a speculative integration of ARIA attributes into the language. By design, it does not define related APIs nor attempt to specify how consumers of HTML content are meant to process documents.
This document is the 3 September 2009 Editor’s Draft of HTML 5: The Markup Language (ARIA Edition).
This document does not represent consensus in the HTML Working Group. In particular, some members of the group do not support normative status for it, and thus do not support its advance on the W3C Recommendation track. Discussions about the normative status of this document are ongoing, and no decision has been reached yet. As with other documents produced by the HTML Working Group, this document uses the design approach described in HTML Design Principles.
This document is a working draft — all parts of it remain subject to significant change or removal, and some parts are currently incomplete; in particular, many elements currently lack complete documentation in the following subsections:
The existence of this document as an Editor’s Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This specification provides the details necessary for producers of HTML content to create conformant documents, and for others to check the conformance of existing documents. It is designed:
Certain purposes are intentionally out of scope for this specification; in particular, it:
This section defines the following:
The following is a list of terms that are common to various other sections in this specification.
A-Z
and the corresponding characters in the range
a-z
are considered to also match.This section provides explanations for the symbols used in the Content model and Attribute model subsections of the per-element documentation in the HTML elements section and in the Common content models, Common attributes, and Forms attributes sections.
The explanations use the term
group
to mean any combination of names and symbols that are
delimited by a pair of matching
"(" and ")"
(parentheses) symbols, and the term
pattern name
to mean any hyperlinked name used in a definition that is not
an element name or an attribute name.
?" (question mark) symbol after an
element name, attribute name,
pattern name,
or
group
indicates that it is optional — meaning that it can either
not occur at all, or it can occur exactly once.*" (asterisk) symbol after an element
name,
pattern name,
or
group
indicates that it may occur
any number of times, including not occurring at all.+" (plus sign) symbol after an element
name,
pattern name,
or
group
indicates that is must occur
at least once, and can occur more than once.|" (vertical line) symbol between
element names, attribute names,
pattern names,
and
groups
indicates an either/or alternative relationship between
the two items it separates; that is, it indicates that
either the item before the "|" symbol can
occur, or the item after the symbol can occur.," (comma) symbol between element
names,
pattern names,
and
groups
indicates that the two
items it separates can only occur in the order shown.&" (ampersand) symbol between
element names, attribute names,
pattern names,
and
groups
indicates that the two items it separates can occur in any
order.This section defines the term document, and provides additional details related to the definition of that term. It is divided into the following parts:
The term document is used in this specification to mean an instance of the HTML language.
The HTML language is the language described in this specification; it is an abstract language that applications can potentially represent in memory in any number of possible ways, and that can be transmitted using any number of possible concrete syntaxes.
This specification makes reference to two particular concrete syntaxes for the HTML language: One syntax which is referred to throughout this specification as the HTML syntax, and another syntax, which is referred to throughout this specification as the XML syntax. Web browsers typically implement two separate parsers for processing documents: an HTML parser which is invoked when processing documents in the HTML syntax, and an XML parser which is invoked when processing documents in the XML syntax.
The HTML syntax is the syntax described in the HTML syntax section of this specification.
The XML syntax is defined by rules in the XML specification [XML] and in the Namespaces in XML 1.0 specification [XMLNS]. Beyond the requirements defined in those specifications, this specification does not define any additional syntax-level requirements for documents in the XML syntax.
The
HTML namespace
is defined as http://www.w3.org/1999/xhtml.
The HTML namespace is the
namespace both for
documents in the HTML syntax
and for
documents in the XML syntax.
Documents that are served with the
text/html MIME type must conform to the rules in this
specification for
documents in the HTML syntax.
Documents that have an
HTML namespace
declaration and that are served with an XML MIME type
such as
text/xml,
application/xml, or
application/xhtml+xml
must conform to the rules in this specification for
documents in the XML syntax.
A conformant document in the HTML syntax must consist of the following parts, in the following order:
Documents in the HTML syntax must conform to the syntax described in the HTML syntax section of this specification.
A conformant document in the XML syntax must consist of the following parts, in the following order:
Documents in the XML syntax must conform to XML constraints as defined in the XML specification [XML] and in the Namespaces in XML 1.0 specification [XMLNS] — including XML well-formedness constraints — and must not make use of any features of the HTML syntax that do not follow XML well-formedness constraints (for example, documents in the XML syntax must not use unquoted attribute value syntax and must not omit tags).
In documents in the HTML syntax:
In documents in the XML syntax:
This section describes the the HTML syntax in detail. In places, it also notes differences between the the HTML syntax and the XML syntax, but it does not describe the XML syntax in detail (the XML syntax is instead defined by rules in the XML specification [XML] and in the Namespaces in XML 1.0 specification [XMLNS]).
This section is divided into the following parts:
A doctype (sometimes capitalized as “DOCTYPE”) is an special instruction which, for legacy reasons that have to do with processing modes in browsers, is a required part of any document in the HTML syntax; it must either be a deprecated doctype, or must consist of the following parts, in exactly the following order:
<"
character.!"
character.DOCTYPE".HTML".>"
character.A doctype legacy string consists of the following parts, in exactly the following order.
SYSTEM".""
character or a
"'"
character.about:legacy-compat".""
character or a
"'"
character).The following are examples of some conformant doctypes.
<!DOCTYPE html>
<!doctype HTML system "about:legacy-compat">
A deprecated doctype is a document type declaration as defined in the XML specification [XML], with the further restriction that it must meet one of the following sets of constraints:
HTML",
its public identifier is an exact match for the literal string
"-//W3C//DTD HTML 4.0//EN",
and its system identifier is either missing or is an exact
match for the literal string
"http://www.w3.org/TR/REC-html40/strict.dtd".HTML",
its public identifier is an exact match for the literal string
"-//W3C//DTD HTML 4.01//EN",
and its system identifier is either missing or is an exact
match for the literal string
"http://www.w3.org/TR/html4/strict.dtd".HTML",
its public identifier is an exact match for the literal string
"-//W3C//DTD XHTML 1.0 Strict//EN",
and its system identifier is either missing or is an exact
match for the literal string
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd".HTML",
its public identifier is an exact match for the literal string
"-//W3C//DTD XHTML 1.1//EN",
and its system identifier is either missing or is an exact
match for the literal string
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd".The following are examples of some deprecated doctypes.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
A character encoding declaration is a mechanism for specifying the character encoding used to store or transmit a document.
The following restrictions apply to character encoding declarations:
If the document does not start with a
U+FEFF BYTE ORDER MARK (BOM) character, and if its
encoding is not explicitly given by a
Content-Type HTTP header, then the character
encoding used must be an
ASCII-compatible character encoding,
and, in addition, if that encoding isn't US-ASCII itself, then
the encoding must be specified using a
meta element with a
charset
attribute or a meta element
in the
encoding declaration
state.
If the document contains a meta
element with a
charset
attribute or a meta element in the
encoding declaration state,
then the character encoding used must be an
ASCII-compatible character encoding.
An ASCII-compatible character encoding is one that is a superset of US-ASCII (specifically, ANSI_X3.4-1968) for bytes in the set 0x09, 0x0A, 0x0C, 0x0D, 0x20 - 0x22, 0x26, 0x27, 0x2C - 0x3F, 0x41 - 0x5A, and 0x61 - 0x7A.
Documents must not use the CESU-8, UTF-7, BOCU-1 and SCSU encodings. [CESU8] [UTF7] [BOCU1] [SCSU]
In a document the XML syntax, the XML declaration, as defined in the XML specification [XML] should be used to provide character-encoding information, if necessary.
An element’s content model defines the element’s structure: What contents (if any) the element can contain, as well as what attributes (if any) the element can have. The HTML elements section of this specification defines the content models for all of elements that are part of the HTML language. An element must not contain contents or attributes that are not part of its content model.
The contents of an element are any elements, character data, and comments that it contains. Attributes and their values are not considered to be the “contents” of an element.
A void element is an element whose content model does not allow it to have contents. Void elements can have attributes.
The following is a complete list of the void elements in HTML:
The following list describes syntax rules for the the HTML syntax. Rules for the the XML syntax are defined in the XML specification [XML].
0–9,
a–z,
and
A–Z.<"
character./"
character, which may be present only if the element is a
void element.>"
character.<"
character./"
character>"
character.If an element has both a start tag and an end tag, its end tag must be contained within the contents of the same element in which its start tag is contained. An end tag that is not contained within the same contents as its start tag is said to be a misnested tag.
In the following example, the
"</i>"
end tag
is a
misnested tag,
because it is not contained
within the
contents
of the
b
element that contains its corresponding
"<i>"
start tag.
<b>foo <i>bar</b> baz</i>
Attributes for an element are expressed inside the element’s start tag. Attributes have a name and a value.
There must never be two or more attributes on the same start tag whose names are a case-insensitive match for each other.
The following list describes syntax rules for attributes in documents in the HTML syntax. Syntax rules for attributes in documents in the XML syntax. are defined in the XML specification [XML].
"",
"'",
">",
"/",
"=",
the control characters,
and any characters that are not defined by Unicode.Name production defined in
the XML specification [XML]
and that contain no
":"
characters, and whose first three characters are not a
case-insensitive match
for the string "xml".In the the HTML syntax, attributes can be specified in four different ways:
Certain attributes may be specified by providing just the attribute name.
In the following example, the
disabled
attribute is given with the empty attribute
syntax:
<input disabled>
An unquoted attribute value is specified by providing the following parts in exactly the following order:
="
characterIn addition to the general requirements given above for attribute values, an unquoted attribute value has the following restrictions:
"",
"'",
">",
"=",
charactersIn the following example, the
value
attribute is given with the unquoted attribute value
syntax:
<input value=yes>
If the value of an attribute using the unquoted
attribute syntax is followed by a
"/"
character, then there must be at least one
space character
after the value and before the
"/"
character.
A single-quoted attribute value is specified by providing the following parts in exactly the following order:
="
character'"
character'"
character.In addition to the general requirements given above for attribute values, a single-quoted attribute value has the following restriction:
'"
charactersIn the following example, the
type attribute
is given with the single-quoted attribute value
syntax:
<input type='checkbox'>
A double-quoted attribute value is specified by providing the following parts in exactly the following order:
="
character""
character""
characterIn addition to the general requirements given above for attribute values, a double-quoted attribute value has the following restriction:
""
charactersIn the following example, the
title attribute is
given with the double-quoted attribute value syntax:
<code title="U+003C LESS-THAN SIGN"><</code>
Text in element contents (including in comments) and attribute values must consist of Unicode characters, with the following restrictions:
There are two special types of text, known as escaping text span starts and escaping text span ends, that can occur within certain elements.
Character data contains text, in some cases in combination with character references, along with certain additional restrictions. There are three types of character data that can occur in documents:
Certain elements and strings in the values of particular attributes contain normal character data. Normal character data can contain the following:
Normal character data has the following restrictions:
<"
charactersIn documents in the HTML syntax, the title and textarea elements can contain replaceable character data. Replaceable character data can contain the following:
<"
characters and
escaping text spans
Replaceable character data has the following restrictions:
</"
followed by characters that are a
case-insensitive match
for the tag name of the element containing the
replaceable character data (for example,
"</title" or
"</textarea"),
followed by one of
U+0009 CHARACTER TABULATION,
U+000A LINE FEED (LF),
U+000C FORM FEED (FF),
U+0020 SPACE,
">",
or
"/",
unless that string is part of an
escaping text span.Replaceable character data, as defined in this specification, is a feature of the HTML syntax that is not available in the XML syntax. Documents in the XML syntax must not contain replaceable character data as defined in this specification; instead they must conform to all syntax constraints defined in the XML specification [XML].
In documents in the HTML syntax, the script, and style elements can contain non-replaceable character data. Non-replaceable character data can contain the following:
<"
characters and
escaping text spans
Non-replaceable character data has the following restrictions:
</",
followed by characters that are a
case-insensitive match
for the tag name of the element containing the
replaceable character data (for example,
"</script"
or
"</style",
followed by one of
U+0009 CHARACTER TABULATION,
U+000A LINE FEED (LF),
U+000C FORM FEED (FF),
U+0020 SPACE,
">",
or
"/",
unless that string is part of an
escaping text span.Non-replaceable character data, as defined in this specification, is a feature of the HTML syntax that is not available in the XML syntax. Documents in the XML syntax must not contain non-replaceable character data as defined in this specification; instead they must conform to all syntax constraints defined in the XML specification [XML].
Character references are a form of markup for representing single individual characters. There are three types of character references:
Named character references consist of the following parts in exactly the following order:
&"
character.;"
character.The following is an example of a named character
reference for the character
"†"
(U+2020 DAGGER).
†
Decimal numerical character references consist of the following parts, in exactly the following order.
&"
character.#"
character.0–9,
representing a base-ten integer that itself is a Unicode
code point that is not
U+0000,
U+000D,
in the range U+0080–U+009F,
or in the range 0xD8000–0xDFFF (surrogates).;"
character.The following is an example of a decimal numeric
character reference for the character
"†"
(U+2020 DAGGER).
†
Hexadecimal numeric character references consist of the following parts, in exactly the following order.
&"
character.#"
character.x"
character
or a
"X"
character.0–9,
a–f,
and
A–F,
representing a base-sixteen integer that itself is a
Unicode code point that is not
U+0000,
U+000D,
in the range U+0080–U+009F,
or in the range 0xD800–0xDFFF (surrogates).;"
character.The following is an example of a hexadecimal numeric
character reference for the character
"†"
(U+2020 DAGGER).
†
Character references are not themselves text, and no part of a character reference is text.
An
ambiguous ampersand
is an
"&"
character that is followed by some
text
other than a
space character,
a
"<",
character, or another
"&"
character.
An escaping text span is a span of text that starts with an escaping text span start that is not itself in an escaping text span, and ends at the next escaping text span end. Escaping text spans have the following restriction:
An
escaping text span start
is the
text
string
"<!--".
An
escaping text span end
is the
text
string
"-->".
An
escaping text span start
may share its
"-"
characters with its corresponding
escaping text span end.
The text in style, script, title, and textarea elements must not have an escaping text span start that is not followed by an escaping text span end.
The following is an example of an escaping text span within a style element.
<style>
<!--
dfn { font-weight: bold; color: brown; }
-->
</style>
SVG and MathML elements are elements from the SVG and MathML namespaces. SVG and MathML elements can be used both in documents in the HTML syntax and in documents in the XML syntax. Syntax rules for SVG and MathML elements in documents in the XML syntax are defined in the XML specification [XML]. The following list describes additional syntax rules that specifically apply to SVG and MathML elements in documents in the HTML syntax.
/"
character before the closing
">"
character are said to be
marked as self-closing.CDATA sections in SVG and MathML contents in documents in the HTML syntax consist of the following parts, in exactly the following order:
<![CDATA["]]>“]]>"CDATA sections are allowed only in the contents of elements from the SVG and MathML namespaces.
The following shows an example of a CDATA section.
<annotation encoding="text/latex">
<![CDATA[\documentclass{article}
\begin{document}
\title{E}
\maketitle
The base of the natural logarithms, approximately 2.71828.
\end{document}]]>
</annotation>
The complete set of HTML elements is the set of elements described in the following sections.
The a element represents a hyperlink.
The abbr element represents an abbreviation or acronym.
The address element represents contact information.
The area element represents either a hyperlink with some text and a corresponding area on an image map, or a dead area on an image map.
area = empty & area.attrs
area.attrs
=
common.attrs
& (alt
& href)?
& target?
& ping?
& rel?
& media?
& hreflang?
& type?
&
(shape.rect?
& coords.rect)
| (shape.circle
& coords.circle)
| (shape.poly
& coords.poly)
| shape.default?
The area element is a void element. An area element must have a start tag but must not have an end tag.
The article element represents a section of content that forms an independent part of a document or site; for example, a magazine or newspaper article, or a blog entry.
The aside element represents content that is tangentially related to the content that forms the main textual flow of a document.
An audio element represents an audio stream.
The b element represents a span of text offset from its surrounding content without conveying any extra importance; for example, keywords in a document abstract, product names in a review, or other spans of text whose typical typographic presentation is bold text.
The base element specifies a document-wide base URL for the purposes of resolving relative URLs, and document-wide default browsing context name for the purposes of following hyperlinks.
base = empty & base.attrs
The base element is a void element. A base element must have a start tag but must not have an end tag.
The bdo element provides a means to specify a direction override of the Unicode BiDi algorithm.
The blockquote element represents a section that is quoted from another source.
A blockquote element must have both a start tag and an end tag.
The body element represents the body of a document (as opposed to the document’s metadata).
A body element's start tag may be omitted if
the first thing inside the body element is not a space character or a comment, except if the first thing
inside the body element is a
script or style element.
A body element's end tag may be omitted if the
body element is not immediately
followed by a comment and the element is either
not empty or its start tag
has not been omitted.
The br element represents a line break.
The br element is a void element. A br element must have a start tag but must not have an end tag.
The canvas element represents a resolution-dependent bitmap canvas, which can be used for dynamically rendering of images such as game graphics, graphs, or other images.
The cite element represents the cited title of a work; for example, the title of a book mentioned within the main text flow of a document.
The code element represents a fragment of computer code.
The col element represents one or more columns in the column group represented by its colgroup parent.
The col element is a void element. A col element must have a start tag but must not have an end tag.
A colgroup element's
start tag may be omitted
if the first thing inside the colgroup element is a col element, and if the element is not
immediately preceded by another colgroup element whose end tag has been omitted.
A
colgroup element's end tag may be omitted if the
colgroup element is not
immediately followed by a space character or
a comment.
A command element with no type attribute specified represents the same thing as a command element with its type attribute set to "command".
The command element
with a type attribute whose
value is "command" represents a command with an
associated action.
command.command = empty & command.command.attrs
The command element is a void element. A command element must have a start tag but must not have an end tag.
The command element
with a type attribute whose
value is "radio" represents
a selection of one item from a list of items.
command.radio = empty & command.radio.attrs
The command element is a void element. A command element must have a start tag but must not have an end tag.
The command element
with a type attribute whose
value is "checkbox" represents a state or option
that can be toggled.
command.checkbox = empty & command.checkbox.attrs
The command element is a void element. A command element must have a start tag but must not have an end tag.
The datalist element represents a set of option elements that represent predefined options for other controls.
The dd element represents either a description or a span of discourse.
A dd element must have a
start tag.
A
dd element's end tag may be omitted if the
dd element is immediately
followed by another dd element or
a dt element, or if there is no
more content in the parent element.
If a dd element’s parent is a dl element, then the dd element represents the description (or value) part of a term-description (name-value) grouping in a description list.
If a dd element’s parent is a dialog element, then the dd element represents a span of discourse (a quote) in a talker-discourse (speaker-quote) pair in a conversation.
The del element represents a range of text that has been deleted from a document.
The details element represents additional information or controls which the user can obtain on demand.
The dfn element represents the defining instance of a term.
The dialog element represents a conversation.
The div element is a generic container for flow content that by itself does not represent anything.
The dl element represents a description list.
A dt element must have a
start tag.
A
dt element's end tag may be omitted if the
dt element is immediately
followed by another dt element or
a dd element.
If a dt element’s parent is a dl element, then the dt element represents the term (or name) part of a term-description (name-value) grouping in a description list.
If a dt element’s parent is a dialog element, then the dt element represents a “talker” (or speaker) part of a talker-discourse (speaker-quote) pair in a conversation.
The em element represents a span of text with emphatic stress.
The embed element represents an integration point for external content.
embed = empty & embed.attrs
The embed element is a void element. An embed element must have a start tag but must not have an end tag.
The fieldset element represents a
set of form controls grouped under a common name.
The figure element represents some flow content, optionally with a caption, which can be moved away from the main flow of the document without affecting the document’s meaning.
The form element represents a user-submittable form.
The head element collects the document’s metadata.
A head element's
start tag may be
omitted if the first thing inside the
head element is an
element.
A head element's end tag may be omitted if the
head element is not
immediately followed by a space character
or a comment.
The header element represents the header of a section.
The hgroup element represents a group of headings.
The hr element represents a paragraph-level thematic break.
The hr element is a void element. An hr element must have a start tag but must not have an end tag.
Some examples of thematic breaks that can be marked up using the hr element include a scene change in a story, or a transition to another topic within a section of a reference book.
The html element represents the root of a document.
An html element's start tag may be omitted if
the first thing inside the html element is not a comment.
An html element's end tag may be omitted if the
html element is not
immediately followed by a comment and the element contains a
body element that is either not
empty or whose start tag
has not been omitted.
The i element represents a span of text in an alternate voice or mood, or otherwise offset from the normal prose (content whose typical typographic presentation is italicized).
Some examples of spans that might use the i element include a taxonomic designation, a technical term, an idiomatic phrase from another language, a thought, a ship name, or some other prose whose typical typographic presentation is italicized.
The iframe element introduces a new nested browsing context.
iframe.iframe element's browsing context is to be rendered
in a manner that makes it appear to be part of the
containing document (seamlessly included in the parent
document).The img element represents an image.
The img element is a void element. An img element must have a start tag but must not have an end tag.
An input element with no type attribute specified represents the same thing as a input element with its type attribute set to "text".
The input element
with a type attribute whose
value is "text" represents
a one-line plain text edit control for the input element’s value.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "password" represents
a one-line plain-text edit control for entering a password.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "checkbox" represents
a state or option that can be toggled.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "radio" represents
a selection of one item from a list of items (a radio
button).
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "submit" represents a button for
submitting a form.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "reset" represents a button for
resetting a form.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "file"
represents a list of file items, each consisting of a file
name, a file type, and a file body (the contents of the
file).
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "image"
represents either an image from which the UA enables a user
to interactively select a pair of coordinates and submit the
form, or alternatively a button from which the user can submit
the form.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "datetime" represents
a control for setting the element’s value to a string
representing a global date and time (with timezone
information).
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "datetime-local" represents
a control for setting the element’s value to a string
representing a local date and time (with no timezone
information).
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "date" represents
a control for setting the element’s value to a string
representing a date.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "month" represents
a control for setting the element’s value to a string
representing a month.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "time" represents
a control for setting the element’s value to a string
representing a time (with no timezone information).
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "week" represents
a control for setting the element’s value to a string
representing a week.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "number" represents
a precise control for setting the element’s value to a
string representing a number.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "range" represents
an imprecise control for setting the element’s value to a
string representing a number.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "email" represents
a control for editing a list of e-mail addresses given in the
element’s value.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "url" represents
a control for editing an absolute URL given in the element’s
value.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "search" represents
a one-line plain-text edit control for entering one or more
search terms.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "tel" represents a one-line plain-text
edit control for entering a telephone number.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The input element
with a type attribute whose
value is "color" represents
a color-well control, for setting the element’s value to a
string representing a simple color.
The input element is a void element. An input element must have a start tag but must not have an end tag.
The ins element represents a range of text that has been inserted (added) to a document.
The kbd element represents user input.
The keygen element represents a control for generating a public-private key pair and for submitting the public key from that key pair.
keygen = empty & keygen.attrs
The label element represents a caption for a form control.
The legend element represents a title or explanatory caption for the rest of the contents of the legend element’s parent element.
The li element represents a list item.
An li element must have a
start tag.
An li element's end tag may be omitted if the
li element is immediately
followed by another li element
or if there is no more content in the parent element.
The link element represents metadata that expresses inter-document relationships.
link = empty & link.attrs
The link element is a void element. A link element must have a start tag but must not have an end tag.
If the id attribute and name attribute specified on the map element, both attributes must have the same value.
The mark element represents a run of text in one document marked or highlighted for reference purposes, due to its relevance in another context.
The meta element with a name attribute sets document metadata in the form of name/value pairs.
meta.name = empty & meta.name.attrs
The meta element is a void element. A meta element must have a start tag but must not have an end tag.
The name attribute on the meta element must be either a defined metadata name or a registered metadata name.
A defined metadata name is any of the following:
description",
the value of the content attribute
must be a string that describes the page.generator",
the value of the content attribute
must be a string
that identifies the software used to generate the
document.application-name",
the value of the content attribute
must be a string representing the name of the Web
application that the page represents.A registered metadata name is any metadata name registered in the central MetaExtensions registration page.
The meta element
with a http-equiv attribute
whose value is "refresh" represents a pragma
directive that specifies either a number of seconds after
which to reload the current page,
or a number of seconds after which to load a different page in
place of the current page, and the URL for the replacement
page.
The meta element is a void element. A meta element must have a start tag but must not have an end tag.
The meta element
with a http-equiv attribute
whose value is "default-style" represents a pragma
directive that specifies the document’s preferred stylesheet.
The meta element is a void element. A meta element must have a start tag but must not have an end tag.
The meta element
with a http-equiv attribute
whose value is "content-language" represents a pragma
directive that specifies a document-wide default language.
The meta element is a void element. A meta element must have a start tag but must not have an end tag.
The meta element with a charset attribute represents a character encoding declaration.
meta.charset = empty & meta.charset.attrs
The meta element is a void element. A meta element must have a start tag but must not have an end tag.
A meta element with a http-equiv attribute whose value is "content-type" and which has an accompanying content attribute and value represents a character encoding declaration.
The meta element is a void element. A meta element must have a start tag but must not have an end tag.
A meta element in the encoding declaration state may be used in a document in the HTML syntax, but it must not be used in a document in the XML syntax.
There must not be more than one meta element in the encoding declaration state per document.
If a document contains a meta element in the encoding declaration state, then the document must not contain a meta element with a charset attribute.
A meta element with a http-equiv attribute whose value is "content-type" and which has an accompanying content attribute and value is said to be in the encoding declaration state.
The meter element represents a scalar gauge providing a measurement within a known range, or a fractional value.
The noscript element is used to present different markup to user agents that don’t support scripting, by affecting how the document is parsed.
The noscript element
must not be used in a document in the XML syntax.
The object element represents external content.
The ol element represents a list (or sequence) of items; that is, a list in which the items are intentionally ordered, such that changing the order would change the meaning of the list.
The option element represents an option in a select control, or an option in a labelled set of options grouped together in an optgroup, or an option among the list of suggestions in a datalist.
The output element represents the result of a calculation.
The p element represents a paragraph.
A p element must have a start tag.
A p element's end tag may be omitted if the
p element is immediately
followed by an
address,
article,
aside,
blockquote,
dialog,
dir,
div,
dl,
fieldset,
footer,
form,
h1,
h2,
h3,
h4,
h5,
h6,
header,
hr,
menu,
nav,
ol,
p,
pre,
section,
table, or
ul,
element, or if there is no more content in the parent
element and the parent element is not an
a element.
param = empty & param.attrs
The param element is a void element. A param element must have a start tag but must not have an end tag.
The pre element represents a block of preformatted text, in which structure is represented by typographic conventions rather than by elements.
The progress element represents the completion progress of a task.
The q element represents phrasing content quoted from another source.
The rp element can be used to provide parentheses around a ruby text component of a ruby annotation, to be shown by UAs that don’t support ruby annotations.
The rt element marks the ruby text component of a ruby annotation.
The ruby element allows spans of phrasing content to be marked with ruby annotations.
The samp element represents (sample) output from a program or computing system.
The script element dynamic script and data blocks to be included in documents.
The section element represents a section of a document, typically with a title or heading.
The select element represents a control for selecting among a list of options.
The small element represents so-called “small print” such as legal disclaimers and caveats.
The source element enables multiple media sources to be specified for audio video .
source = empty & source.attrs
The source element is a void element. A source element must have a start tag but must not have an end tag.
The span element is a generic wrapper for phrasing content that by itself does not represent anything.
The strong element represents a span of text with strong importance.
The style element allows style information to be embedded in documents.
The sub element represents subscript.
The sup element represents superscript.
The table element represents a table; that is, data with more than one dimension.
The tbody element represents a block of rows that consist of a body of data for its parent table element.
A tbody element's start tag may be omitted if
the first thing inside the tbody element is a tr element, and if the element is not
immediately preceded by a tbody,
thead, or tfoot element whose end tag has been omitted.
A tbody element's end tag may be omitted if the
tbody element is immediately
followed by a tbody or
tfoot element, or if there
is no more content in the parent element.
The td element represents a data cell in a table.
A td element must have a
start tag.
A td element's end tag may be omitted if the
td element is immediately
followed by a td or th element, or if there is no more
content in the parent element.
The textarea element represents a multi-line plain-text edit control for the element’s raw value.
The tfoot element represents the block of rows that consist of the column summaries (footers) for its parent table element.
A tfoot element must have
a start tag.
A tfoot element's end tag may be omitted if the
tfoot element is immediately
followed by a tbody element,
or if there is no more content in the parent element.
The th element represents a header cell in a table.
A th element must have a
start tag.
A th element's end tag may be omitted if the
th element is immediately
followed by a td or
th element, or if
there is no more content in the parent
element.
The thead element represents the block of rows that consist of the column labels (headings) for its parent table element.
A thead element must have
a start tag.
A thead element's end tag may be omitted if the
thead element is immediately
followed by a tbody or
tfoot element.
The time element represents a date and/or time.
If the datetime attribute is not specified, then the date or time represented is given by the contents of the element, and the character data in those contents must conform to the date-or-time datatype.
The title element represents the document’s title or name.
The tr element represents a row of cells in a table.
A tr element must have a
start tag.
A tr element's end tag may be omitted if the
tr element is immediately
followed by another tr element,
or if there is no more content in the parent element.
The ul element represents an unordered list of items; that is, a list in which changing the order of the items would not change the meaning of list.
The var element represents either a variable in a mathematical expression or programming context, or placeholder text that the reader is meant to mentally replace with some other literal value.
The video element represents a video or movie.
This section defines content models that are referenced by a number of different element definitions in the Content model subsections of the per-element documentation in the HTML elements section.
This section defines attributes that are common to all elements in the HTML language.
common.attrs.event-handler = onabort? & onblur? & oncanplay? & oncanplaythrough? & onchange? & onclick? & oncontextmenu? & ondblclick? & ondrag? & ondragend? & ondragenter? & ondragleave? & ondragover? & ondragstart? & ondrop? & ondurationchange? & onemptied? & onended? & onerror? & onfocus? & onformchange? & onforminput? & oninput? & oninvalid? & onkeydown? & onkeypress? & onkeyup? & onload? & onloadeddata? & onloadedmetadata? & onloadstart? & onmousedown? & onmousemove? & onmouseout? & onmouseover? & onmouseup? & onmousewheel? & onpause? & onplay? & onplaying? & onprogress? & onratechange? & onreadystatechange? & onscroll? & onseeked? & onseeking? & onselect? & onshow? & onstalled? & onsubmit? & onsuspend? & ontimeupdate? & onvolumechange? & onwaiting?
xml:space
attribute should only be used with
documents in the XML syntax;
it must not be used in
documents in the HTML syntax.xml:base
attribute should only be used with
documents in the XML syntax;
it must not be used in
documents in the HTML syntax.This section defines attributes that are common to a number of forms elements.
This section defines datatypes that are referenced by attribute definitions in the HTML elements, Common attributes, and Forms attributes sections.
For any attribute definition in this document that references the string datatype, a string is defined as normal character data.
The Attributes section of this document describes additional restrictions on strings in attribute values — in particular, restrictions for the following cases:
For any attribute definition in this document that references the token datatype, a token is defined as a string that does not contain any space characters.
_blank_self_parent_top#"
character, followed by a string which
exactly matches the value of the
name
attribute of an element in the document with type
type.0—9,
optionally prefixed with a
"-"
character.-"
character.0—9".."
character0—9"e"
character or
"E"
character-"
character or
"+"
character0—9".T and
Z in the date/time syntax must always be
uppercaseExamples:
1990-12-31T23:59:60Z1996-12-19T16:39:57-08:00
any"0"
character and that are separated by a single
"x"
character.For documents in the HTML syntax: Any character set name listed in the IANA Character Sets list [IANACHARSET].
For documents in the XML
syntax, any
case-insensitive match
for the string
"UTF-8".
text/html;".charset=".;"
character.url=".javascript".Example:
1996-12-19-".Example:
1996-12-W".Example:
1996-W16Examples:
foo-bar.baz@example.comThis section provides information about ARIA attributes.
alert"
& aria-expanded?
alertdialog"
& aria-expanded?
application"
& aria-expanded?
article"
& aria-expanded?
checkbox"
& aria-checked
combobox"
& aria-activedescendant?
& aria-expanded
complementary"
& aria-expanded?
contentinfo"
& aria-expanded?
definition"
& aria-expanded?
dialog"
& aria-expanded?
directory"
& aria-expanded?
document"
& aria-expanded?
grid"
& aria-level?
& aria-multiselectable?
& aria-readonly?
& aria-activedescendant?
& aria-expanded?
gridcell"
& aria-level?
& aria-readonly?
& aria-selected?
& aria-expanded?
group"
& aria-activedescendant?
& aria-expanded?
img"
& aria-expanded?
list"
& aria-expanded?
listbox"
& aria-multiselectable?
& aria-activedescendant?
& aria-expanded?
listitem"
& aria-posinset?
& aria-setsize?
& aria-level?
& aria-expanded?
log"
& aria-expanded?
main"
& aria-expanded?
marquee"
& aria-expanded?
math"
& aria-expanded?
note"
& aria-expanded?
option"
& aria-checked?
& aria-selected?
presentation"
& aria-expanded?
progressbar"
& aria-valuemax?
& aria-valuemin?
& aria-valuenow?
& aria-valuetext?
radio"
& aria-checked
& aria-selected?
radiogroup"
& aria-activedescendant?
& aria-expanded?
region"
& aria-expanded?
row"
& aria-level?
& aria-selected?
& aria-activedescendant?
& aria-expanded?
search"
& aria-expanded?
separator"
& aria-expanded?
slider"
& aria-valuemax
& aria-valuemin
& aria-valuenow
& aria-valuetext
status"
& aria-activedescendant?
& aria-expanded?
tab"
& aria-selected?
& aria-expanded?
tabpanel"
& aria-expanded?
textbox"
& aria-autocomplete?
& aria-multiline?
& aria-readonly?
timer"
& aria-activedescendant?
& aria-expanded?
toolbar"
& aria-activedescendant?
& aria-expanded?
tooltip"
& aria-expanded?
tree"
& aria-multiselectable?
& aria-activedescendant?
& aria-expanded?
treegrid"
& aria-activedescendant?
& aria-expanded?
& aria-level?
& aria-multiselectable?
& aria-readonly?
treeitem"
& aria-checked?
& aria-expanded?
& aria-level?
& aria-posinset?
& aria-selected?
& aria-setsize?
The semantics of the following attributes are normatively defined in the ARIA specification.
aria-atomic = "true" | "false"
aria-autocomplete = "inline" | "list" | "both" | "none"
aria-checked = "true" | "false" | "mixed" | "undefined"
aria-disabled = "true" | "false"
aria-dropeffect = "none" | "popup" | "execute" | list{ "copy", "execute"? } | list{ "move", "execute"? } | list{ "reference", "execute"? } | list{ "execute", "copy" } | list{ "execute", "move" } | list{ "execute", "reference" }
aria-expanded = "true" | "false" | "undefined"
aria-grabbed = "true" | "false" | "undefined"
aria-haspopup = "true" | "false"
= "true" | "false"
aria-invalid = "true" | "false" | "grammar" | "spelling"
aria-live = "off" | "polite" | "assertive"
aria-multiline = "true" | "false"
aria-multiselectable = "true" | "false"
aria-posinset = integer.positive
aria-pressed = "true" | "false" | "mixed" | "undefined"
aria-readonly = "true" | "false"
aria-relevant = "all" | list{ "additions", "removals"?, "text"? } | list{ "additions", "text"?, "removals"? } | list{ "removals", "additions"?, "text"? } | list{ "removals", "text"?, "additions"? } | list{ "text", "additions"?, "removals"? } | list{ "text", "removals"?, "additions"? }
aria-required = "true" | "false"
aria-selected = "true" | "false" | "undefined"
aria-setsize = integer.non-negative
This document incorporates a modified version of a RELAX NG schema for HTML 5 from the syntax.whattf.org source repository, distributed with the following copyright notice and license statement:
The RELAX NG Schema for (X)HTML 5 is licensed under the MIT open source license. The following legal notice applies to all files in this directory: Copyright (c) 2005-2007 Elika J. Etemad (fantasai) and Henri Sivonen (hsivonen) Copyright (c) 2007-2008 Mozilla Foundation Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
This document incorporates a modified version of a CSS stylesheet from the WebKit source repository, distributed with the following copyright notice and license statement:
Copyright (C) 2000 Lars Knoll (knoll@kde.org) Copyright (C) 2003, 2004, 2005, 2006, 2007, 2008 Apple Inc. All rights reserved. This library is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General Public License for more details. You should have received a copy of the GNU Library General Public License along with this library; see the file COPYING.LIB. If not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
This document incorporates modified and verbatim content from the document HTML5, distributed with the following copyright notice and license statement:
© Copyright 2004-2008 Apple Computer, Inc., Mozilla Foundation, and Opera Software ASA. You are granted a license to use, reproduce and create derivative works of this document.
4.07. Comments # T
Comments consist of the following parts, in exactly the following order:
<!--"-->"The text part of comments has the following restrictions:
>" character->"--"-" characterThe following is an example of a comment.