View source for HTML element

{{Use American English|date=March 2018}}
{{Selfref|This article is about the [[HTML]] elements in general. For information on how to format Wikipedia entries, see [[Help:Wiki markup]] and [[Help:HTML in wikitext]].}}
{{redirect|nobr|the chemical compound NOBr|Nitrosyl bromide}}
{{Html series}}
An '''HTML element''' is an individual component of an [[HTML]] (Hypertext Markup Language) document or [[web page]], once this has been parsed into the [[HTML Document Object Model|Document Object Model]]. HTML is composed of a [[Tree structure|tree]] of HTML [[Node (computer science)|nodes]], such as text nodes. Each node can have [[HTML attribute]]s specified. Nodes can also have content, including other nodes and text. Many HTML nodes represent [[semantics]], or meaning. For example, the {{tag|title|o}} node represents the title of the document.

==Concepts==

===Document vs. DOM===
HTML documents are delivered as "documents".{{refn|group=note|"Document" may refer interchangeably to either a file stored on a computer filesystem, usually on disk, or to a document delivered across the Web by [[HTTP]]. Such documents may equally be copies of disk files stored on the web server, or they may be generated on demand.}} These are then [[parsing|parsed]], which turns them into the [[HTML Document Object Model|Document Object Model]] (DOM) internal representation, within the web browser.{{refn|group=note|[[Document Object Model]] is now a formalized specification by the [[W3C]].<ref name="W3C Current DOM version" >{{Cite web
  |title=Document Object Model (DOM) Current Version
  |date=26 July 2016
  |url=http://www.w3.org/TR/dom
  |publisher=[[W3C]]
}}</ref> It defines {{em|an interface to}} this internal model, rather than the internal model itself. Early web browsers used their own internal representation that bore little relation to the DOM. The term "document tree" has also been applied.<ref>{{Cite web
  |title=Definitions – Document tree
  |at="§&thinsp;3 Conformance: Requirements and Recommendations"
  |work=Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification
  |date=7 June 2011
  |url=http://www.w3.org/TR/CSS2/conform.html#doctree
  |publisher=[[W3C]]
}}</ref> However for the purpose here, of explaining the difference between a document of tags and a parsed model of elements, it is convenient to use the term DOM throughout.}}{{refn|group=note|The term "web browser" here is used for simplicity. It does of course include other sorts of [[web user agent]], such as search engine [[web crawler]]s, automatic news-feed retrievers etc.}}

Presentation by the web browser, such as screen rendering or access by JavaScript, is then performed on this internal model, not the original document.

Early HTML documents, and to a lesser extent today, were largely [[invalid HTML]] and riddled with [[well-formed HTML|syntax errors]]. The parsing process was also required to "fix-up" these errors, as best it could. The resultant model was often not {{em|correct}} (i.e., it did not represent what a careless coder had originally intended), but it would at least be [[Valid HTML|valid]], according to the HTML standard. A valid model was produced, no matter how bad the "[[tag soup]]" supplied had been. Only in the rarest cases would the parser abandon parsing altogether.

===Elements vs. tags===
"Elements" and "tags" are terms that are widely confused. {{citation needed span|text=HTML documents contain tags, but do not contain the elements. The elements are only generated {{em|after}} the parsing step, from these tags.|date=March 2017|reason=This has been challenged on the talk page.}}

As is generally understood, the position of an element is indicated as spanning from a start tag, possibly including some child content, and is terminated by an end tag.<ref>{{Cite web
  |at="§&thinsp;3.2.1 Elements"
  |title=§&thinsp;3 On SGML and HTML
  |work=HTML 4.01 Specification
  |date=24 December 1999
  |url=http://www.w3.org/TR/1999/REC-html401-19991224/intro/sgmltut.html#h-3.2.1
  |publisher=[[W3C]]
}}</ref> This is the case for many, but not all, elements within an HTML document.

As HTML is based on [[SGML]],<ref>{{Cite web
  |at="§&thinsp;3.1 Introduction to SGML"
  |title=§&thinsp;3 On SGML and HTML
  |work=HTML 4.01 Specification
  |date=24 December 1999
  |url=http://www.w3.org/TR/1999/REC-html401-19991224/intro/sgmltut.html
  |publisher=[[W3C]]
}}</ref> its parsing also depends on the use of a [[Document Type Definition|DTD]], specifically an HTML DTD such as that for HTML 4.01.<ref name="W3C, HTML 401 DTD" >{{Cite web
  |title=HTML 4.01, §&thinsp;21, Document Type Definition
  |date=24 December 1999
  |url=http://www.w3.org/TR/1999/REC-html401-19991224/sgml/dtd.html
  |publisher=[[W3C]]
}}</ref>{{refn|group=note|HTML 4.01 is one of a small number of well-known HTML DTDs. It is chosen here as the best illustrative example, although the same behavior applies to the other W3C-published DTDs for HTML.}} The DTD specifies which element types are possible (i.e. it defines the set of element types that go to make up HTML) and it also specifies the valid combinations in which they may appear in a document. It is part of general SGML behavior that where only one valid structure is {{em|possible}} (per the DTD), it is not generally a requirement that the document explicitly states that structure. As a simple example, the {{code|lang=html|code=<p>}} start tag indicating the start of a paragraph element should be closed by a {{code|lang=html|code=</p>}} end tag, indicating the end of the element. Also the DTD states that paragraph elements cannot be nested. The HTML document fragment:
: {{code|lang=html|code=<p>Para 1 <p>Para 2 <p>Para 3 }}
can thus be inferred to be equivalent to:
: {{code|lang=html|code=<p>Para 1 </p><p>Para 2 </p><p>Para 3 }}
(If one paragraph element cannot contain another, any currently open paragraph must be closed before starting another.)

Because of this implied behavior, based on the combination of the DTD and the individual document, it is not possible to infer elements from the document tags {{em|alone}}, but only by also using an SGML or HTML aware parser, with knowledge of the DTD.

===SGML vs. XML===
SGML is complex, which has limited its widespread adoption and understanding. [[XML]] was developed as a simpler alternative. XML is similar to SGML, that can also use the DTD mechanism to specify the supported elements and their permitted combinations as document structure. XML parsing is simpler. The relation from tags to elements is always that of parsing the actual tags included in the document, without the implied closures that are part of SGML.{{refn|group=note|A macro-like feature of DTDs may still be used within XML.}}

In Macros HTML can be formed as XML, either through [[XHTML]] or through [[HTML5]], the parsing of document tags as DOM elements is simplified. Once the DOM of elements is obtained, behavior beyond that point (i.e. screen rendering) is identical.{{refn|group=note|One minor point is that XML, even after the DOM interface, is case-sensitive.<ref>{{Cite web
  |at="§&thinsp;1.3. XHTML and the HTML DOM"
  |work=Document Object Model (DOM) Level 2 HTML Specification
  |date=9 January 2003
  |title=§&thinsp;1. Document Object Model HTML
  |url=http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109/html.html#ID-5353782642
  |publisher=[[W3C]]
}}</ref>}}

===<code>%block;</code> vs. box===
Part of this CSS presentation behavior is the notion of the "[[CSS box model|box model]]". This is applied to those elements that CSS considers to be "block" elements, set through the CSS {{code|lang=css|code=display: block;}} declaration.

HTML also has a similar concept, although different, and the two are very frequently confused. <code>%block;</code> and <code>%inline;</code> are groups within the HTML DTD that group elements as being either "block-level" or "inline".<ref name="W3C, HTML 4.01, block and inline" >{{Cite web
  |at="§&thinsp;7.5.3 Block-level and inline elements"
  |title=§&thinsp;7 The global structure of an HTML document
  |work=HTML 4.01 Specification
  |date=24 December 1999
  |url=http://www.w3.org/TR/1999/REC-html401-19991224/struct/global.html#h-7.5.3
  |publisher=[[W3C]]
}}</ref> This is used to define their nesting behavior: block-level elements cannot be placed into an inline context.{{refn|group=note|However, see {{code|lang=html|code=<object>}} for the inevitable exception.}} This behavior cannot be changed; it is fixed in the DTD. Block and inline elements have the appropriate and different CSS behaviors attached to them by default,<ref name="W3C, HTML 4.01, block and inline" /> including the relevance of the box model for particular element types.

Note though that this CSS behavior can, and frequently is, changed from the default. Lists with {{code|lang=html|code=<ul><li> ...}} are <code>%block;</code> elements and are presented as block elements by default. However, it is quite common to set these with CSS to display as an inline list.<ref>{{Cite web
  |title=CSS Design: Taming Lists
  |author=Mark Newhouse
  |date=27 September 2002
  |url=http://alistapart.com/article/taminglists/
  |publisher=[[A List Apart]]
}}</ref>

==Overview==

===Syntax===

{{Image frame|caption=Parts of an HTML container element
|content=<math>
\overbrace{
  \overbrace{\mathtt{\color{BrickRed}<\!p\ }\color{Magenta}\underbrace\mathtt{class}_\mathsf{\color{Black}{Attribute \atop name}}\mathtt{= ''}\!\underbrace\mathtt{foo}_\mathsf{\color{White}{Attr} \atop \color{Black}value}''\mathtt{\color{BrickRed}>}}^\mathsf{Start\ tag}
  \overbrace\mathtt{\color{Green}This\ is\ a\ paragraph.}^\mathsf{Content}
  \overbrace\mathtt{\color{BrickRed}<\!/p\!>}^\mathsf{End \atop tag}
}^\mathsf{Element}
</math>
}}
In the HTML syntax, most elements are written with a start tag and an end tag, with the content in between. An '''HTML tag''' is composed of the name of the element, surrounded by [[angle brackets]]. An end tag also has a slash after the opening angle bracket, to distinguish it from the start tag. For example, a paragraph, which is represented by the {{tag|p|o}} element, would be written as:
<syntaxhighlight lang="html4strict">
<p>In the HTML syntax, most elements are written ...</p>
</syntaxhighlight>
However, not all of these elements {{em|require}} the end tag, or even the start tag, to be present. <!--Examples will be given throughout the article when I get around to it. —Ms2ger--> Some elements, the so-called ''[[#Void elements|void elements]]'', do not have an end tag. A typical example is the {{tag|br|s}} (hard line-break) element. A void element's behavior is predefined, and it cannot contain any content or other elements. For example, an address would be written as:
<syntaxhighlight lang="html4strict">
<p>P. Sherman<br>42 Wallaby Way<br>Sydney</p>
</syntaxhighlight>
When using an [[XHTML]] [[Document Type Declaration|DTD]], it is required to open and close the element with a single tag. To specify that it is a void element, a <code>&#47;</code> is included at the {{em|end}} of the tag (not to be confused with the <code>&#47;</code> at the {{em|beginning}} of a closing tag).
<syntaxhighlight lang="html4strict">
<p>P. Sherman<br />42 Wallaby Way<br />Sydney</p>
</syntaxhighlight>

[[HTML attributes]] are specified inside the start tag. For example, the {{tag|abbr|o}} element, which represents an [[abbreviation]], expects a <code>title</code> attribute within its opening tag. This would be written as:
<syntaxhighlight lang="html4strict">
<abbr title="abbreviation">abbr.</abbr>
</syntaxhighlight>

There are multiple kinds of [[HTML]] elements: void elements, raw text elements, and normal elements.

'''{{Anchor|Empty element}}{{vanchor|Void elements}}''' (also sometimes called empty elements, single elements or stand-alone elements) only have a start tag (in the form {{tag|{{var|tag}}|s}}), which contains any [[HTML attributes]]. They may not contain any children, such as text or other elements. In early versions of HTML, the slash was not required for such elements ({{tag|{{var|tag}}|o}} was permissible). The space is not required in HTML, strictly speaking (<code>&lt;{{var|tag}}/&gt;</code> is valid), but is required ({{tag|{{var|tag}}|s}}) in [[XHTML]] and other [[XML]] applications.
Two common void elements are {{tag|br|s}} (for a [[Hard return|hard line-break]], such as in a poem or an address) and {{tag|hr|s}} (for a horizontal rule). Other such elements are often place-holders which reference external files, such as the image ({{tag|img|s}}) element. The attributes included in the element will then point to the external file in question. Another example of a void element is {{tag|link|s}}, for which the syntax is:
<syntaxhighlight lang="html4strict">
<link rel="stylesheet" href="fancy.css" type="text/css">
</syntaxhighlight>
This {{tag|link|s}} element points the browser at a [[Style sheet (web development)|style sheet]] to use when presenting the HTML document to the user. Note that in the HTML syntax, attributes don't have to be quoted if they are composed only of certain characters: letters, digits, the hyphen-minus and the full stop. When using the XML syntax (XHTML), on the other hand, all attributes must be quoted, and a spaced trailing [[Slash (punctuation)|slash]] is required before the last angle bracket:
<syntaxhighlight lang="xml">
<link rel="stylesheet" href="fancy.css" type="text/css" />
</syntaxhighlight>

'''{{vanchor|Raw text elements}}''' (also known as text or text-only elements) are constructed with:
* a ''start tag'' (in the form {{tag|{{var|tag}}|o}}) marking the beginning of an element, which may incorporate any number of [[HTML attributes]];
* some amount of text ''content'', but no elements (all tags, apart from the applicable end tag, will be interpreted as content);
* an ''end tag'', in which the element name is prefixed with a slash: {{tag|{{var|tag}}|c}}. In some versions of HTML, the end tag is optional for some elements. The end tag is required in [[XHTML]].
An example is the {{tag|title|o}} element must not contain other elements (including markup of text), only {{em|plain}} text.

'''{{vanchor|Normal elements}}''' usually have both a start tag and an end tag, although for some elements the end tag, or both tags, can be omitted. It is constructed in a similar way:
* a ''start tag'' ({{tag|{{var|tag}}|o}}) marking the beginning of an element, which may incorporate any number of [[HTML attributes]];
* some amount of ''content'', including text and other elements;
* an ''end tag'', in which the element name is prefixed with a [[Slash (punctuation)|slash]]: {{tag|{{var|tag}}|c}}.

[[HTML attributes]] define desired behavior or indicate additional element properties. Most attributes require a ''value''. In HTML, the value can be left unquoted if it does not include spaces (<code>{{var|attribute}}={{var|value}}</code>), or it can be quoted with single or double quotes (<code>{{var|attribute}}='{{var|value}}'</code> or <code>{{var|attribute}}='{{var|value}}'</code>). In [[XML]], those quotes are required. [[Boolean data type|Boolean]] attributes, on the other hand, don't require a value to be specified. An example is the <code>checked</code> for checkboxes:
<syntaxhighlight lang="html4strict">
<input type=checkbox checked>
</syntaxhighlight>
In the XML (and thus [[XHTML]]) syntax, though, the name should be repeated as the value:
<syntaxhighlight lang="xml">
<input type="checkbox" checked="checked" />
</syntaxhighlight>

Informally, HTML elements are sometimes referred to as "tags" (an example of [[synecdoche]]), though many prefer the term ''tag'' strictly in reference to the markup delimiting the start and end of an element.

Element (and attribute) names may be written in any combination of upper or lower case in HTML, but must be in lower case in XHTML.<ref name="XHTML10-42">[[#XHTML10|XHTML 1.0]] §&thinsp;4.2</ref> The canonical form was upper-case until [[HTML 4]], and was used in HTML specifications, but in recent years, lower-case has become more common.

===Element standards===

HTML elements are defined in a series of freely available open standards issued since 1995, initially by the [[IETF]] and subsequently by the [[W3C]].

During the [[browser wars]] of the 1990s, developers of [[user agent]]s (e.g. [[web browser]]s) often developed their own elements, some of which have been adopted in later standards. Other user agents may not recognize non-standard elements, and they will be ignored, possibly causing the page to be displayed improperly.

In 1998, [[XML]] (a simplified form of SGML) introduced mechanisms to allow anyone to develop their own elements and incorporate them in [[XHTML]] documents, for use with XML-aware user agents.<ref>[[#XML10|XML 1.0]]  (The ability to produce additional elements is part of the ''eXtensibility'' in the acronym.)</ref>

Subsequently, HTML 4.01 was rewritten in an [[XML]]-compatible form, [[#XHTML10|XHTML 1.0]] (''eXtensible HTML''). The elements in each are identical, and in most cases valid [[XHTML]] 1.0 documents will be valid or nearly valid HTML 4.01 documents. This article mainly focuses on real HTML, unless noted otherwise; however, it remains applicable to [[XHTML]]. See [[HTML#SGML-based versus XML-based HTML|HTML]] for a discussion of the minor differences between the two.

===Element status===

Since the first version of HTML, several elements have become outmoded, and are ''[[deprecated]]'' in later standards, or do not appear at all, in which case they are ''invalid'' (and will be found invalid, and perhaps not displayed, by [[XML validation|validating]] user agents).<ref name="XML10-51">[[#XML10|XML 1.0]] §&thinsp;5.1</ref>

At present, the status of elements is complicated by the existence of three types of [[HTML 4.01]] / [[XHTML 1.0]] [[Document Type Definition|DTD]]:
* '''Transitional''', which contain deprecated elements, but which were intended to provide a transitional period during which authors could update their practices;
* '''Frameset''', which are versions of the Transitional DTDs which also allow authors to write '''frameset''' documents;
* '''Strict''', which is the up-to-date (as at 1999) form of HTML.

The first Standard ([[HTML#First specifications|HTML 2.0]]) contained four deprecated elements, one of which was invalid in [[HTML 3.2]]. All four are invalid in [[HTML 4|HTML 4.01 Transitional]], which also deprecated a further ten elements. All of these, plus two others, are invalid in [[HTML 4|HTML 4.01 Strict]]. While the frame elements are still current in the sense of being present in the Transitional and Frameset DTDs, there are no plans to preserve them in future standards, as their function has been largely replaced, and they are highly problematic for user accessibility.

(Strictly speaking, the most recent ''XHTML'' standard, [[XHTML 1.1]] (2001), does not include frames at all; it is approximately equivalent to [[XHTML 1.0|XHTML 1.0 Strict]], but also includes the '''[[Ruby (annotation markup)|Ruby markup]]''' module.)<ref name="XHTML11">[[#XHTML11|XHTML 1.1]] §&thinsp;A</ref>

A common source of confusion is the loose use of ''deprecated'' to refer to both deprecated and invalid status, and to elements which are expected to be formally deprecated in future.

===Content vs. presentation and behavior===

Since HTML 4, HTML has increasingly focused on the separation of content (the visible text and images) from presentation (like color, font size, and layout).<ref>{{Cite web
  |title=HTML & CSS
  |url=http://www.w3.org/standards/webdesign/htmlcss
  |year=2013
  |publisher=[[W3C]]
}}</ref>  This is often referred to as a [[separation of concerns]]. HTML is used to represent the structure or content of a document, its presentation remains the sole responsibility of [[CSS]] [[style sheet (web development)|style sheets]]. A default style sheet is suggested as part of the CSS standard, giving a default rendering for HTML.<ref>{{Cite web
  |title=Appendix D. Default style sheet for HTML 4
  |work=Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification
  |date=7 June 2011
  |url=http://www.w3.org/TR/CSS2/sample.html
  |publisher=[[W3C]]
}}</ref>

Behavior (interactivity) is also kept separate from content, and is handled by [[Client-side scripting|scripts]]. Images are contained in separate [[graphics]] files, separate from text, though they can also be considered part of the content of a page.

Separation of concerns allows the document to be presented by different user agents according to their purposes and abilities. For example, a user agent can select an appropriate style sheet to present a document by displaying on a monitor, printing on paper, or to determine speech characteristics in an audio-only user agent. The structural and semantic functions of the markup remain identical in each case.

Historically, user agents did not always support these features. In the 1990s, as a stop-gap, presentational elements (like {{tag|b|o}} and {{tag|i|o}}) were added to HTML, at the cost of creating problems for interoperability and user accessibility. This is now regarded as outmoded and has been superseded by style sheet-based design; most presentational elements are now deprecated.<ref name="HTML401-141">[[#HTML401|HTML 4.01]] §&thinsp;14.1</ref>

External image files are incorporated with the {{tag|img|s}} or {{tag|object|s}} elements. (With [[XHTML]], the [[SVG]] language can also be used to write graphics within the document, though linking to external SVG files is generally simpler.)<ref name="SVG11-23">{{cite web |editor-last1=Ferraiolo |editor-first1=J. |editor-last2=Fujisawa |editor-first2=J. |editor-last3=Jackson |editor-first3=D. |work=Scalable Vector Graphics (SVG) 1.1 Specification |title=§&thinsp;2.3 Options for using SVG in Web pages |publisher=[[W3C]] |date=2003-01-14 |url= http://www.w3.org/TR/2003/REC-SVG11-20030114/ |access-date=2009-03-25}}</ref> Where an image is not purely decorative, HTML allows replacement content with similar semantic value to be provided for non-visual user agents.

An HTML document can also be extended through the use of scripts to provide additional behaviors beyond the abilities of HTML hyperlinks and forms.

The elements {{tag|style|o}} and {{tag|script|o}}, with related [[HTML attributes]], provide style sheets and scripts.
* In the document head, {{tag|style|s}} and {{tag|script|s}} may link to shared external documents, or {{tag|style}} and {{tag|script}} may contain embedded instructions. (The {{tag|link|o}} element can also be used to link style sheets.)
* {{tag|script|s}} or {{tag|script}} can occur at any point in the document (head or body).
* The <code>style</code> attribute is valid in most document body elements (e.g. {{tag|div|o|attribs=style="..."}}) for inclusion of ''inline style'' instructions.
* ''Event-handling attributes'', which provide links to scripts, are optional in most elements.
* For user agents which do not operate scripts, the {{tag|noscript}} element provides embedded alternative content where appropriate; however, it can only be used in the document head and in the body as a block-level element.

==Document structure elements==

{{Anchor|html|html_tag}}{{XMLElement|html|HTML|...}}
:The [[root element]] of an [[HTML]] document; all other elements are contained in this.
:The HTML element delimits the beginning and the end of an HTML document.
:'''Standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|head|head_tag}}{{XMLElement|head|Head|...}}
:Container for processing information and metadata for an HTML document.
:'''Standardized''' in [[#HTML20|HTML 2.0]]; still current.
:(See [[#Document head elements|document head elements]] for child elements.)

{{Anchor|body|body_tag}}{{XMLElement|body|Body|...}}
:Container for the displayable content of an HTML document.
:'''Standardized''' in [[#HTML20|HTML 2.0]]; still current.
:(See [[#Document body elements|document body elements]] for child elements.)

==Document head elements==

{{Anchor|base|base_tag}}{{XMLElement|base|Base|...|end=no}}
:Specifies a '''base URL''' for all relative <code>href</code> and other links in the document. Must appear before any element that refers to an external resource. HTML permits only one {{tag|base|o}} element for each document. This element has [[HTML attributes]], but no contents.
:A development version of this element (as <code>BASE</code>) is mentioned in ''[[#HTMLTAGS|HTML Tags]]''; '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|basefont|basefont_tag}}{{XMLElement|basefont|Base Font|...|deprecated=1|end=no}}
:Specifies a base font size, typeface, and color for the document. Used together with {{tag|font|o}} elements. [[Deprecation|Deprecated]] in favor of [[Style sheet (web development)|style sheets]].
:'''Standardized''' in [[#HTML32|HTML 3.2]]; '''deprecated''' in [[#HTML401|HTML 4.0 Transitional]]; '''invalid''' in [[#HTML401|HTML 4.0 Strict]].

{{Anchor|isindex|isindex_tag}}{{XMLElement|isindex|Index|...|end=no|deprecated=1}}
:{{code|lang=html|code=<isindex>}} could either appear in the document head or in the body, but only once in a document. See [[Fieldset|Forms]].

{{Anchor|link|link_tag}}{{XMLElement|link|Link|...|end=no}}
:Specifies links to other documents, such as ''previous'' and ''next'' links, or alternate versions.<ref>[[#HTML401|HTML 4.01]] §&thinsp;12.3</ref>  A common use is to link to external [[Cascading Style Sheets|style sheets]], using the form:
::{{code|lang=html|code=<link rel="stylesheet" type="text/css" href="url" title="description_of_style">}}<ref>[[#HTML401|HTML 4.01]] §&thinsp;14.3.2</ref>
:A less-common, but important, usage is to supply navigation hints consistently through use of [[microformat]]s. Several common relationships are defined, that may be exposed to users through the browser interface rather than directly in the web page.
::{{code|lang=html|code=<link rel="next" href="url">}}
:A document's {{tag|head|o}} element may contain any number of {{tag|link|s}} elements. This element has [[HTML attributes]], but no contents.
:<code>LINK</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|meta|meta_tag}}[[Meta element|{{XMLElement|meta|Meta|...|end=no}}]]
{{Main|Meta element}}
:Can be used to specify additional [[metadata]] about a document, such as its author, publication date, expiration date, page description, keywords, or other information not provided through the other header elements and [[HTML attributes]]. Because of their generic nature, {{tag|meta|s}} elements specify associative [[Associative array|key-value pairs]]. In general, a meta element conveys hidden information about the document. Several meta tags can be used, all of which should be nested in the head element. The specific purpose of each {{tag|meta|s}} element is defined by its attributes. Outside of [[XHTML]], it is often given without the slash ({{tag|meta|o}}), despite being a [[#Void elements|void element]].
:In one form, {{tag|meta|s}} elements can specify [[HTTP]] headers which should be sent by a [[web server]] before the actual content. For example, {{code|lang=html|code=<meta http-equiv="foo" content="bar" />}} specifies that the page should be served with an HTTP header called <code>foo</code> that has a value <code>bar</code>.
:In the general form, a {{tag|meta|s}} element specifies <code>name</code> and associated <code>content</code> [[HTML attributes]] describing aspects of the HTML page. To prevent possible ambiguity, an optional third attribute, <code>scheme</code>, may be supplied to specify a semantic framework that defines the meaning of the key and its value. For example, in {{code|lang=html|code=<meta name="foo" content="bar" scheme="DC" />}} the {{tag|meta|s}} element identifies itself as containing the <code>foo</code> element, with a value of <code>bar</code>, from the DC or [[Dublin Core]] [[Resource Description Framework|resource description framework]].
:'''Standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|object}}{{XMLElement|object|Object|...}}
:Used for including generic objects within the document header. Though rarely used within a {{tag|head|o}} element, it could potentially be used to extract foreign data and associate it with the current document.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{Anchor|script|script_tag}}{{XMLElement|script|Script|...}}
:Can act as a container for script instructions or link to an external script with the optional <code>src</code> attribute.<ref>[[#HTML401|HTML 4.01]] §&thinsp;18</ref> Also usable in the document body to dynamically generate either both block or inline content.
:'''Standardized''' in [[#HTML32|HTML 3.2]]; still current.

{{Anchor|style|style_tag}}{{XMLElement|style|Style|...}}
:Specifies a [[Cascading Style Sheets|style]] for the document, usually in the form:
::{{code|lang=html|code=<style type="text/css"> ... </style>}}
:Can either act as a container for style instructions or link to external style sheets – for example, in [[Cascading Style Sheets|CSS]], with <code>@import</code> directives of the form:
::{{code|lang=html|code=<style> @import url; </style>}}<ref>[[#CSS1|CSS]] §&thinsp;1.1</ref>
:'''Standardized''' in [[#HTML32|HTML 3.2]]; still current.

{{Anchor|title|title_tag}}{{XMLElement|title|Title|...}}
:Define a document title. Required in every [[HTML]] and [[XHTML]] document. User agents may use the title in different ways. For example:
:* Web browsers usually display it in a window's [[title bar]] when the window is open, and (where applicable) in the [[task bar]] when the window is minimized.
:* It may become the default file-name when saving the page.
:* [[Web search engine]]s' [[web crawler]]s may pay particular attention to the words used in the title.
:The {{tag|title|o}} element must not contain other elements, only text. Only one  {{tag|title|o}} element is permitted in a document.
: Existed in ''[[#HTMLTAGS|HTML Tags]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

==Document body elements==

In visual browsers, displayable elements can be rendered as either ''block'' or ''inline''. While all elements are part of the document sequence, block elements appear within their parent elements:
* as rectangular objects which do not break across lines;
* with block margins, width and height properties which can be set independently of the surrounding elements.
Conversely, inline elements are treated as part of the flow of document text; they cannot have margins, width or height set, and do break across lines.

===Block elements===

Block elements, or block-level elements, have a rectangular structure. By default, these elements will span the entire width of its parent element, and will thus not allow any other element to occupy the same horizontal space as it is placed on.

The rectangular structure of a block element is often referred to as the [[:File:W3C and Internet Explorer box models.svg|box model]], and is made up of several parts. Each element contains the following:
* The '''content''' of an element is the actual text (or other media) placed between the opening and closing tags of an element.
* The '''padding''' of an element is the space around that content, which still form part of said element. Padding is physically part of an element, and should not be used to create white space between two elements. Any background style assigned to the element, such as a background image or color, will be visible within the padding. Increasing the size of an element's padding increases the amount of space this element will take up.
* The '''border''' of an element is the absolute end of an element, and spans the perimeter of that element. The thickness of a border increases the size of an element.
* The '''margin''' of an element is the white-space that surrounds an element. The content, padding and border of any other element will not be allowed to enter this area, unless forced to do so by some advanced [[CSS]] placement. Using most standard [[Document Type Definition|DTDs]], margins on the left and right of different elements will push each other away. Margins on the top or bottom of an element, on the other hand, will not stack, or will intermingle. This means that the white-space between these elements will be as big as the larger margin between them.

The above section refers only to the detailed implementation of CSS rendering and has no relevance to HTML elements themselves.

====Basic text====

{{Anchor|p|p_tag}}{{XMLElement|p|Paragraph|...}}
:Creates a paragraph, perhaps the most common block level element.
:<code>P</code> existed in ''[[#HTMLTAGS|HTML Tags]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|heading}}{{Anchor|h1|h1_tag}}{{XMLElement|h1|Primary Headline|...}}
{{Anchor|h2|h2_tag}}{{XMLElement|h2|Secondary Headline|...}}
{{Anchor|h3|h3_tag}}{{XMLElement|h3|Third Level Headline|...}}
{{Anchor|h4|h4_tag}}{{XMLElement|h4|4. Level Headline|...}}
{{Anchor|h5|h5_tag}}{{XMLElement|h5|5. Level Headline|...}}
{{Anchor|h6|h6_tag}}{{XMLElement|h6|6. Level Headline|...}}
:Section headings at different levels. <code>h1</code> delimits the highest-level heading, <code>h2</code> the next level down (sub-section), <code>h3</code> for a level below that, and so on to <code>h6</code>. They are sometimes referred to collectively as <code>h''n''</code> tags, ''n'' meaning any of the available heading levels.
:Most visual browsers show headings as large bold text by default, though this can be overridden with [[Cascading Style Sheets|CSS]]. Heading elements are not intended merely for creating large or bold text – in fact, they should {{em|not}} be used for explicitly styling text. Rather, they describe the document’s structure and organization. Some programs use them to generate outlines and tables of contents.
:Headings existed in ''[[#HTMLTAGS|HTML Tags]]'', and were '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

====Lists====
{{Anchor|dl|dl_tag}}{{XMLElement|dl|Definition List|...}}
{{redirect|Definition list|Wikipedia's article on lists of definitions|Glossary}}
:A description list (a.k.a. [[association list]] or definition list), which consists of name–value groups,<ref name="W3C-5-DL">{{cite web |url=http://www.w3.org/TR/html5/grouping-content.html#the-dl-element |title=4.4 Grouping content – HTML5 |work=HTML5: A vocabulary and associated APIs for HTML and XHTML – W3C Recommendation |publisher=[[World Wide Web Consortium]] |at="§&thinsp;4.4.8 The dl element" |date=28 October 2014 |accessdate=16 August 2015}}</ref> and was known as a definition list prior to HTML5.<ref>{{cite web |url=http://www.w3.org/TR/html4/struct/lists.html#edef-DL |title=Lists in HTML documents |at="§&thinsp;10.3 Definition lists: the DL, DT, and DD elements" |work=HTML 4.01 Specification – W3C Recommendation |date=24 December 1999 |publisher=World Wide Web Consortium |accessdate=2 May 2015 }}</ref>  Description lists are intended for groups of "terms and definitions, metadata topics and values, questions and answers, or any other groups of name–value data".<ref>{{cite web |author=[[W3C]]|title=HTML5: A Vocabulary and Associated APIs for HTML and XHTML, W3C Working Draft|date=5 April 2011|url=http://www.w3.org/TR/2011/WD-html5-20110405/grouping-content.html#the-dl-element}}.</ref>
:<code>DL</code> existed in ''[[#HTMLTAGS|HTML Tags]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|dt|dt_tag}}{{XMLElement|dt|Definition Term|...}}
:A name in a description list (previously definition term in a definition list).
:<code>DT</code> existed in ''[[#HTMLTAGS|HTML Tags]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|dd|dd_tag}}{{XMLElement|dd|Definition|...}}
:A value in a description list (previously definition data in a definition list).
:<code>DD</code> existed in ''[[#HTMLTAGS|HTML Tags]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|ol|ol_tag}}{{XMLElement|ol|Ordered List|...}}
<dd>An ordered (enumerated) list. The <code>type</code> attribute can be used to specify the kind of marker to use in the list, but style sheets give more control. The default is Arabic numbering.  In an HTML attribute: {{nobr|{{code|lang=html|code=<ol type="foo">}}}}; or in a CSS declaration: {{nobr|{{code|lang=css|code=ol { list-style-type: foo; } }}}} – replacing <code><var>foo</var></code> with one of the following:
{| class="wikitable"
|-
! Style               !! HTML value     !! CSS value
|-
| A, B, C&nbsp;...    || <code>A</code> || <code>upper-alpha</code>
|-
| a, b, c&nbsp;...    || <code>a</code> || <code>lower-alpha</code>
|-
| I, II, III&nbsp;... || <code>I</code> || <code>upper-roman</code>
|-
| i, ii, iii&nbsp;... || <code>i</code> || <code>lower-roman</code>
|-
| 1, 2, 3&nbsp;...    || <code>1</code> || <code>decimal</code>
|}
CSS provides several other options not available as pure-HTML markup, including <code>none</code>, and options for [[CJK]], Hebrew, Georgian, and Armenian script.
</dd>
:<code>OL</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|ul|ul_tag}}{{XMLElement|ul|Unordered List|...}}
:An unordered (bulleted) list. The type of list item marker can be specified in an HTML attribute: {{nobr|{{code|lang=html|code=<ul type="foo">}}}}; or in a CSS declaration: {{nobr|{{code|lang=css|code=ul { list-style-type: foo; } }}}} – replacing <code><var>foo</var></code> with one of the following (the same values are used in HTML and CSS): <code>disc</code> (the default), <code>square</code>, or <code>circle</code>. '''Only''' the CSS method is supported in HTML5. CSS also provides <code>none</code>, and the ability to replace these bullets with custom images.
:<code>UL</code> existed in ''[[#HTMLTAGS|HTML Tags]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|li|li_tag}}{{XMLElement|li|List Item|...}}
:A list item in ordered (<code>ol</code>) or unordered (<code>ul</code>) lists.
:<code>LI</code> existed in ''[[#HTMLTAGS|HTML Tags]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|dir|dir_tag}}{{XMLElement|dir|Directory List|...|deprecated=1}}
:A directory listing. The original purpose of this element was never widely supported; deprecated in favor of {{code|lang=html|code=<ul>}}.
:<code>DIR</code> existed in ''[[#HTMLTAGS|HTML Tags]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; '''deprecated''' in [[#HTML401|HTML 4.0 Transitional]]; '''invalid''' in [[#HTML401|HTML 4.0 Strict]].

====Other block elements====
<!--linked from Template:Pre2-->

{{Anchor|address|address_tag}}{{XMLElement|address|Address|...}}
:Contact information for the document author.
:<code>ADDRESS</code> existed in ''[[#HTMLTAGS|HTML Tags]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{anchor|article|article_tag}}{{XMLElement|article|Article|...}}
:Used for articles and other similar content.
:'''Standardized''' in [[#HTML5|HTML5]].

{{anchor|aside|aside_tag}}{{XMLElement|aside|Aside|...}}
:Used for content in a document which is separate from the main page content, for example, sidebars or advertising.
:'''Standardized''' in [[#HTML5|HTML5]].

{{anchor|blockquote}} <!-- Linked from [[Wikipedia:Quotations]] -->
{{Anchor|blockquote|blockquote_tag}}{{XMLElement|blockquote|BlockQuotation|...}}
:A [[blockquote|block level quotation]], for when the quotation includes block level elements, e.g. paragraphs. The <code>cite</code> attribute (not to be confused with the [[#cite|{{tag|cite|o}}]] element) may give the source, and must be a fully qualified [[Uniform Resource Identifier]].
:The default presentation of block quotations in visual browsers is usually to indent them from both margins. This has led to the element being unnecessarily used just to indent paragraphs, regardless of semantics. For quotations not containing block level elements see the quote ([[#q|{{tag|q|o}}]]) element.
:<code>BLOCKQUOTE</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current. See [[blockquote element]] for more information.

{{Anchor|center|center_tag}}{{XMLElement|center|Centered Text|...|deprecated=1}}
:Creates a block-level center-aligned division. Deprecated in favor of [[#div|{{tag|div|o}}]] or another element with centering defined using style sheets.
:'''Standardized''' in [[#HTML32|HTML 3.2]]; '''deprecated''' in [[#HTML401|HTML 4.0]]; '''not supported''' in [[#HTML5|HTML5]].

{{Anchor|del|del_tag}}{{XMLElement|del|Deleted Section|...}}
:Marks a deleted section of content. This element can also be used as ''inline''.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{Anchor|div|div_tag}}{{XMLElement|div|Logical division|...}}
{{Main|Span and div}}
:A block-level logical division. A generic element with no semantic meaning used to distinguish a document section, usually for purposes such as presentation or behavior controlled by [[Cascading Style Sheets|style sheets]] or [[Document Object Model|DOM]] calls.
:Proposed in the [[#HTML30|HTML 3.0 Drafts]]; '''Standardized''' in [[#HTML32|HTML 3.2]]; still current.

{{anchor|figure|figure_tag}}{{XMLElement|figure|Figure|...}}
:Used to group images and captions, along with {{tag|figcaption|o}}.
:'''Standardized''' in [[#HTML5|HTML5]].

{{anchor|figcaption|figcaption_tag}}{{XMLElement|figcaption|Figure Caption|...}}
:A caption for an image. Always placed inside the {{tag|figure|o}} element.
:'''Standardized''' in [[#HTML5|HTML5]].

{{anchor|header|footer_tag}}{{XMLElement|footer|Footer|...}}
:Used for document footers. These might contain author or copyright information, or links to other pages.
:'''Standardized''' in [[#HTML5|HTML5]].

{{anchor|header|header_tag}}{{XMLElement|header|Header|...}}
:Used for document headers. These typically contain content introducing the page.
:'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|hr|hr_tag}}{{XMLElement|hr|Horizontal Rule|...|end=no}}
:A horizontal rule. Presentational rules can also be drawn with style sheets.
:'''Standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|ins|ins_tag}}{{XMLElement|ins|Inserted Section|...}}
:Marks a section of inserted content. This element can also be used as ''inline''.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{anchor|main|main_tag}}{{XMLElement|main|Main Content|...}}
:Contains the main content of a document.
:'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|menu|menu_tag}}{{XMLElement|menu|Menu|...|}}
:HTML 2.0: A menu listing. Should be more compact than a {{tag|ul|o}} list.
:<code>MENU</code> existed in ''[[#HTMLTAGS|HTML Tags]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; '''deprecated''' in [[#HTML401|HTML 4.0 Transitional]]; '''invalid''' in [[#HTML401|HTML 4.0 Strict]]; but then redefined in [[#HTML5|HTML5]].

{{anchor|nav|nav_tag}}{{XMLElement|nav|Navigation|...}}
:Used in navigational sections of articles (areas of webpages which contain links to other webpages).
:'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|noscript|noscript_tag}}{{XMLElement|noscript|JavaScript Fallback|...}}
:Replacement content for scripts. Unlike '''script''' this can only be used as a block-level element.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{Anchor|pre|pre_tag}}{{XMLElement|pre|PreFormattedText|...}}
:''Pre-formatted'' text. Text within this element is typically displayed in a [[non-proportional font]] exactly as it is laid out in the file (see [[ASCII art]]). Whereas browsers ignore [[Whitespace (computer science)|white-space]] for other HTML elements, in {{tag|pre}}, white-space should be rendered as authored. (With the CSS properties: {{code|lang=css|code={ white-space: pre; font-family: monospace; }<nowiki />}}, other elements can be presented in the same way.)  This element can contain any inline element except: [[#image|{{tag|image|o}}]], [[#object|{{tag|object|o}}]], [[#big|{{tag|big|o}}]], [[#small|{{tag|small|o}}]], [[#sup|{{tag|sup|o}}]], and [[#sub|{{tag|sub}}]].
:<code>PRE</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{anchor|section|section_tag}}{{XMLElement|section|Section|...}}
:Used for generic sections of a document. This is different from [[#div|{{tag|div|o}}]] in that it is only used to contain sections of a page, which the W3C defines as a group of content with a similar theme.
:'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|script|script_tag}}{{XMLElement|script|Script|...}}
:Places a script in the document. Also usable in the head and in inline contexts.  It may be used as {{tag|script|s}} with a <code>src</code> attribute to supply a URL from which to load the script, or used as {{tag|script}} around embedded script content.
::{{strong|Note:}} {{tag|script|o}} is not itself either a block or inline element; by itself it should not display at all, but it can contain instructions to dynamically generate either both block or inline content.
:'''Standardized''' in [[#HTML32|HTML 3.2]]; still current.

===Inline elements===

Inline elements cannot be placed directly inside the {{code|lang=html|code=<body>}} element; they must be wholly nested within block-level elements.<ref>{{citation|url=http://www.w3.org/TR/html401/struct/global.html#h-7.5.1 |title=HTML 4.01 |publisher=W3.org |date= |accessdate=2012-03-26}}</ref>

====Anchor====

{{Anchor|a|a_tag}}{{XMLElement|a|Anchor|...}}
:An anchor element is called an anchor because web designers can use it to "anchor" a URL to some text on a web page. When users view the web page in a browser, they can click the text to activate the link and visit the page whose URL is in the link.<ref>''HTML 4 for dummies'', 5th ed., 2005, by Ed Tittel, Mary C. Burmeister; p. 96.</ref>
:In HTML, an ''anchor'' can be either the ''origin'' (the [[anchor text]]) or the ''target'' (destination) end of a [[hyperlink]].
:With the attribute <code>href</code>,<ref>{{cite web|url=http://www.w3.org/Provider/ServerWriter.html|title=ServerWriter -- /Provider|website=www.w3.org}}</ref> the anchor becomes a hyperlink to either another part of the document or another resource (e.g. a webpage) using an external [[Uniform Resource Locator|URL]]. Alternatively (and sometimes concurrently), with the <code>name</code> or <code>id</code> [[HTML attributes]] set, the element becomes a link target. A [[Uniform Resource Locator]] (URL) can link to this target via a [[fragment identifier]], commonly referred to as a "# link". In HTML5, any element can now be made into a target by using the <code>id</code> attribute,<ref>{{cite web|url=http://w3.org/tr/html5/index.html#attributes-1|title=HTML 5.2|website=w3.org}}</ref> so using {{code|lang=html|code=<a name="foo">...</a>}} is not necessary, although this way of adding anchors continues to work.
: To illustrate: the header of a table of contents section on <samp>example.com</samp>'s homepage could be turned into a target by writing
:: {{code|lang=html|code=
<h2><a name="contents">Table of contents</a></h2>
}}
: Continuing with this example, now that the section has been marked up as a target, it can be referred to from external sites with a link like
:: {{code|lang=html|code=<a href="http://example.com#contents">see contents</a>}}
: or with a link on the same page like:
:: {{code|lang=html|code=<a href="#contents">contents, above</a>}}
:The attribute <code>title</code> may be set to give brief information about the link:
::{{code|lang=html|code=<a href="URL" title="additional information">link text</a>}}
:In most graphical browsers, when the cursor hovers over a link, the cursor changes into a hand with an extended index finger and the <code>title</code> value is displayed in a [[tooltip]] or in some other manner. Some browsers render [[Alt attribute|alt text]] the same way, although this is not what the specification calls for.
:<code>A</code> existed in ''[[#HTMLTAGS|HTML Tags]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

====Phrase elements====
{{Confusing|section|reason='''the section lacks a definition, gloss, or explanation of the term of art '[[phrase element]]'.''' Why are these particular elements grouped together? Why is 'Phrase elements' the name of this section? It all seems arbitrary|date=October 2018}}
=====General=====

{{Anchor|abbr|abbr_tag}}{{XMLElement|abbr|Abbreviation|...}}
:Marks an [[abbreviation]], and can make the full form available:
::{{code|lang=html|code=<abbr title="abbreviation">abbr.</abbr>}}
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{Anchor|acronym|acronym_tag}}{{XMLElement|acronym|Acronym|...|deprecated=1}}
:Similar to the {{code|lang=html|code=<abbr>}} element, but marks an [[acronym]]:
::{{code|lang=html|code=<acronym title="Hyper-Text Mark-up Language">HTML</acronym>}}
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current, '''not supported''' in [[#HTML5|HTML5]]. Recommended replacement is the 
 abbr tag.Page text.<ref>[https://www.w3schools.com/tags/tag_acronym.asp Acronym tag], acronym.</ref>

{{Anchor|dfn|dfn_tag}}{{XMLElement|dfn|Definition|...}}
:inline definition of a single term.
:<code>DFN</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was fully '''standardized''' in [[#HTML32|HTML 3.2]]; still current.

{{Anchor|em|em_tag}}{{XMLElement|em|Emphasis|...}}
:''Emphasis'' (conventionally displayed in italics)
:<code>EM</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|strong|strong_tag}}{{XMLElement|strong|Strong Emphasis|...}}
:'''strong emphasis''' (conventionally displayed bold).
:An [[voice browser|aural user agent]] may use different voices for emphasis.
:<code>STRONG</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

=====Computer phrase elements=====
These elements are useful primarily for documenting computer code development and user interaction through differentiation of source code ({{code|lang=html|code=<code>}}), variables ({{code|lang=html|code=<var>}}), user input ({{code|lang=html|code=<kbd>}}), and terminal or other output ({{code|lang=html|code=<samp>}}).

{{Anchor|code|code_tag}}{{XMLElement|code|Sourcecode|...}}
:A code snippet (<code>code example</code>). Conventionally rendered in a mono-space font.
:<code>CODE</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|kbd|kbd_tag}}{{XMLElement|kbd|Keyboard|...}}
:Keyboard – text to be entered by the user (<kbd>kbd example</kbd>).
:<code>KBD</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|samp|samp_tag}}{{XMLElement|samp|Sample|...}}
:Sample output – from a program or script: (<samp>samp example</samp>).
:<code>SAMP</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|var|var_tag}}{{XMLElement|var|Variable|...}}
:Variable (<var>var example</var>).
:<code>VAR</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

=====Presentation=====
As visual presentational markup only applies directly to visual browsers, its use is discouraged. Style sheets should be used instead. Several of these elements are deprecated or invalid in HTML 4 / XHTML 1.0, and the remainder are invalid in the current draft of [http://www.w3.org/TR/2005/WD-xhtml2-20050527/ XHTML 2.0]. The current draft of [http://www.w3.org/TR/html5/text-level-semantics.html HTML5], however, re-includes {{tag|s|o}}, {{tag|u|o}}, and {{tag|small|o}}, assigning new semantic meaning to each. In an [[HTML5]] document, the use of these elements is no longer discouraged, provided that it is semantically correct.

{{Anchor|b|b_tag}}{{XMLElement|b|Bold|...}} <!-- not deprecated in [[HTML 4.01]]; not included in [[XHTML 2.0]] which is in draft stage; now a semantic element in [[HTML5]] -->
:In [[HTML 4]], set font to '''boldface''' where possible. Equivalent CSS: {{code|lang=css|code={ font-weight: bold; } }}. The {{tag|b|o}} element usually has the same effect in visual browsers, as well as having more semantic meaning, under [[HTML 4.01]].
:In [[HTML5]], however, {{tag|b|o}} has its own meaning, distinct from that of {{tag|strong|o}}. It denotes "text to which attention is being drawn for utilitarian purposes without conveying any extra importance and with no implication of an alternate voice or mood."<ref name="html5-b-element">{{citation|url=http://developers.whatwg.org/text-level-semantics.html#the-b-element |title=4.6 Text-level semantics — The b element |publisher=Developers.whatwg.org |date= |accessdate=2012-03-26}}</ref>
:<code>B</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|i|i_tag}}{{XMLElement|i|Italic|...}} <!-- not deprecated in HTML 4.01; not included in XHTML 2.0 which is in draft stage; now a semantic element in HTML5 -->
:In [[HTML 4]], set font to ''italic'' where possible. Equivalent [[CSS]]: {{code|lang=css|code={ font-style: italic; } }}. Using {{tag|em}} has the same visual effect in most browsers, as well as having a semantic meaning as ''emphasis'', under [[HTML 4.01]]. (Purely typographic italics have many non-emphasis purposes, as HTML 5 more explicitly recognized.)
:In [[HTML5]], however, {{tag|i|o}} has its own semantic meaning, distinct from that of {{tag|em|o}}. It denotes "a different quality of text" or "an alternative voice or mood "e.g., a thought, a ship name, a [[Binomial nomenclature|binary species name]], a foreign-language phrase, etc."<ref name="html5-i-element">{{citation|url=http://developers.whatwg.org/text-level-semantics.html#the-i-element |title=4.6 Text-level semantics — The i element |publisher=Developers.whatwg.org |date= |accessdate=2012-03-26}}</ref>
:<code>I</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|u|u_tag}}{{XMLElement|u|Underlined|...}}
:In [[HTML 4]], <u>underlined</u> text. Equivalent CSS: {{code|lang=css|code={ text-decoration: underline; } }}. Deprecated in [[HTML 4.01]]. Restored in [[#HTML5|HTML5]].
:In [[HTML5]], the {{tag|u|o}} element denotes "a span of text with an unarticulated, though explicitly rendered, non-textual annotation, such as labelling the text as being a proper name in Chinese text (a Chinese proper name mark), or labelling the text as being misspelt."  The [[HTML5]] specification reminds developers that other elements are almost always more appropriate than {{tag|u|o}} and admonishes designers not to use underlined text where it could be confused for a hyper-link.<ref name="html5-u-element">{{citation|url=http://developers.whatwg.org/text-level-semantics.html#the-u-element |title=4.6 Text-level semantics — The u element |publisher=Developers.whatwg.org |date= |accessdate=2012-03-26}}</ref>
:<code>U</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', was '''standardized''' in [[#HTML32|HTML 3.2]] but was '''deprecated''' in [[#HTML401|HTML 4.0 Transitional]] and was '''invalid''' in [[#HTML401|HTML 4.0 Strict]]. '''Reintroduced''' in [[#HTML5|HTML5]].

{{Anchor|small|small_tag}}{{XMLElement|small|Small|...}}
:In [[HTML 4]], decreased font size (<small>smaller</small> text). Equivalent CSS: {{code|lang=css|code={ font-size: smaller; } }}
:In [[HTML5]], the {{tag|small|o}} element denotes "side comments such as small print."<ref name="html5-small-element">{{citation|url=http://developers.whatwg.org/text-level-semantics.html#the-small-element |title=4.6 Text-level semantics — The small element |publisher=Developers.whatwg.org |date= |accessdate=2012-03-26}}</ref>  This has caused some confusion with the {{tag|[[#aside|aside]]}} element.
:'''Standardized''' in [[#HTML32|HTML 3.2]]; still current.

{{Anchor|s|s_tag}}{{XMLElement|s|Strikethrough|...}}
:In [[HTML 4]], indicated strike-through text (<s>Strikethrough</s>) and was equivalent to {{tag|strike|o}}.
:In [[HTML5]], the {{tag|s|o}} element denotes information that is "no longer accurate or no longer relevant", and is not to be confused with {{tag|del|o}}, which indicates removal/deletion.<ref name="html5-s-element">{{citation|url=http://developers.whatwg.org/text-level-semantics.html#the-s-element |title=4.6 Text-level semantics — The s element |publisher=Developers.whatwg.org |date= |accessdate=2012-03-26}}</ref>
:<code>S</code> was '''deprecated''' in [[#HTML401|HTML 4.0 Transitional]] (having not appeared in any previous standard), and was '''invalid''' in [[#HTML401|HTML 4.0 Strict]]. '''Reintroduced''' in [[#HTML5|HTML5]], which instead deprecated {{tag|strike|o}}.

{{Anchor|big|big_tag}}{{XMLElement|big|Big|...|deprecated=1}}
:Increased font size (<big>bigger</big> text). Equivalent CSS: {{code|lang=css|code={ font-size: larger; } }}
:'''Standardized''' in [[#HTML32|HTML 3.2]]; '''not supported''' in [[#HTML5|HTML5]].

{{Anchor|strike|strike_tag}}{{XMLElement|strike|Strikethrough|...|}}
:Strike-through text (<s>Strikethrough</s>),  (Equivalent CSS: {{code|lang=css|code={ text-decoration: line-through; } }})
:<code>STRIKE</code> was standardized in [[#HTML32|HTML 3.2]]; '''deprecated''' in [[#HTML401|HTML 4.0 Transitional]]; '''invalid''' in [[#HTML401|HTML 4.0 Strict]].

{{Anchor|tt|tt_tag}}{{XMLElement|tt|Teletype|...|deprecated=1}}
:[[non-proportional font|Fixed-width]] font ({{mono|typewriter-like}}<!-- DO NOT use actual deprecated markup in this page; use CSS to simulate its output.-->), also known as [[teletype]], thus "tt". (Equivalent CSS: {{code|lang=css|code={ font-family: monospace; } }})
:<code>TT</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''Standardized''' in [[#HTML20|HTML 2.0]]; not supported<ref name="html5-tt-not-supported">{{citation|url=http://www.w3.org/TR/html5/obsolete.html#non-conforming-features |title=11 Obsolete features — HTML5 |publisher=W3.org |date= |accessdate=2012-03-26}}</ref> in HTML5. Possible replacements: [[#kbd|{{tag|kbd|o}}]] for marking user input, [[#var|{{tag|var|o}}]] for variables (usually rendered italic, and not with a change to monospace), [[#code|{{tag|code|o}}]] for source code, [[#samp|{{tag|samp|o}}]] for output.<ref name="html5-tt-not-supported" />
<!-- font description start -->
{{Anchor|font|font_tag}}{{XMLElement|font|Teletype|...|}}
:{{code|lang=html|code=<font [color=<var>color</var>] [size=<var>size</var>] [face=<var>face</var>]>...</font>}}
:Can specify the font color with the <code>color</code> attribute (note the American spelling), typeface with the <code>face</code> attribute, and absolute or relative size with the <code>size</code> attribute.
:Examples (all uses are deprecated, use CSS equivalents if possible):
:# {{code|lang=html|code=<font color="green">text</font>}} creates {{green|green text}}.
:# {{code|lang=html|code=<font color="#114499">text</font>}} creates <span style="color:#149;">text with [[Hex triplet|hexadecimal color]] #114499</span>.
:# {{code|lang=html|code=<font size="4">text</font>}} creates <span style="font-size:140%;">text</span> with size 4. Sizes are from 1 to 7. The standard size is 3, unless otherwise specified in the &lt;body> or other tags.
:# {{code|lang=html|code=<font size="+1">text</font>}} creates <span style="font-size:125%;">text with size 1 bigger than the standard.</span> {{code|lang=html|code=<font size="-1">text</font>}} is opposite.
:# {{code|lang=html|code=<font face="Courier">text</font>}} makes <span style="font-family:Courier;">text</span> with Courier font.
:Equivalent CSS for font attributes:
:*<code class="mw-highlight" dir="rtl"><span class="p">&lt;</span><span class="nt">font</span> <span class="na">size</span><span class="o">=</span><span class="s">"<var>N</var>"</span><span class="p">&gt;</span></code> corresponds to <code class="mw-highlight" dir="ltr"><span class="p">{</span><span class="nb">font-size</span><span class="o" style="color: #666;">:</span> <span class="nb"><var>Y</var><var>units</var></span><span class="p">}</span></code> (the HTML specification does not define the relationship between size <var>N</var> and unit-size <var>Y</var>, nor does it define a unit).
:*{{code|lang=html|code=<font color="red">}} corresponds to {{code|lang=css|code={ color: red; } }}
:*{{code|lang=html|code=<font face="Times New Roman">}} corresponds to {{code|lang=css|code={ font-family: 'Times New Roman', Times, serif; } }} – CSS supports a [[font stack]], of two or more alternative fonts.
:'''Standardized''' in [[#HTML32|HTML 3.2]]; '''deprecated''' in [[#HTML401|HTML 4.0 Transitional]]; '''invalid''' in [[#HTML401|HTML 4.0 Strict]]. Not part of HTML5.

====Span====

{{Anchor|span|span_tag}}{{XMLElement|span|Span|...|}}
{{Main|Span and div}}
:An inline logical division. A generic element with no semantic meaning used to distinguish a document section, usually for purposes such as presentation or behavior controlled by [[Cascading Style Sheets|style sheets]] or [[Document Object Model|DOM]] calls.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

====Other inline elements====

{{Anchor|br|br_tag}}{{XMLElement|br|Line Break|...|end=no}}
:A forced line break.
:'''Standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|bdi|bdi_tag}}{{XMLElement|bdi|Bidirectional Isolation|...|}}
:Isolates an inline section of text that may be formatted in a different direction from other text outside of it, such as user-generated content with unknown directionality.
:'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|bdo|bdo_tag}}{{XMLElement|bdo|Bidirectional Override|...|}}
:Marks an inline section of text in which the reading direction is the opposite from that of the parent element.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{Anchor|cite|cite_tag}}{{XMLElement|cite|Citation|...}}
:A citation or a reference for a quote or statement in the document.
:CITE existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.
:''Note:'' The HTML 5 specifications have been confusingly [[Fork (software development)|forked]],<ref name=finalars>{{cite web |url= https://arstechnica.com/information-technology/2014/10/html5-specification-finalized-squabbling-over-who-writes-the-specs-continues/ |title=HTML5 specification finalized, squabbling over specs continues |publisher=Ars Technica |date=29 October 2014 |access-date=29 October 2014}}</ref> including with regard to this element. In HTML 4 and earlier, {{tag|cite|o}} was for "a citation or a reference to other sources" without any particular limitations or requirements.<ref>{{cite web |title=9.2.1 Phrase elements: EM, STRONG, DFN, CODE, SAMP, KBD, VAR, CITE, ABBR, and ACRONYM |work=HTML 4.01 Specification |date=24 December 1999 |publisher=[[W3C]] |url= https://www.w3.org/TR/html401/struct/text.html#h-9.2.1 |access-date=26 July 2018}}</ref> The [[W3C]] HTML 5 spec uses a refinement of this idea, reflecting how the element has historically been used, but now requiring that it contain (but not be limited to) at least one of "the title of the work or the name of the author (person, people or organization) or an URL reference, or a reference in abbreviated form as per the conventions used for the addition of citation metadata."<ref>[[#HTML52|''HTML 5.2 W3C Recommendation'']], at [https://www.w3.org/TR/html52/textlevel-semantics.html#the-cite-element "§&thinsp;4.5.6. The cite element"].</ref> But the WHATWG spec only permits the element to be used around the title of a work.<ref>[[#WHATWGLS|''HTML Living Standard'']], at [https://html.spec.whatwg.org/multipage/text-level-semantics.html#the-cite-element "§&thinsp;4.5.6 The cite element"].</ref>  The W3C specs began with the broader definition, then switched to the very narrow one after WHATWG made this change. However, W3C reverted their own change in 2012, in response to negative developer-community feedback; the element was in broadly-deployed use with the broader scope, e.g., various blog and forum platforms wrap commenters' IDs and e-mail addresses in {{tag|cite}}, and people using the element for bibliographic citations were (and still are) routinely wrapping each entire citation in this element.
:Another problem with the element is that WHATWG recommends that it be italicized by default (thus almost all browsers do so), because it (in their view) is only for publication titles. By convention, however, only certain kinds of titles actually take italics, while others are expected to be put in quotation marks, and standards may actually vary by publishing context and language. Consequently, many website authors and admins use a site-wide stylesheet to undo this element's auto-italics.

{{Anchor|data|data_tag}}{{XMLElement|data|Data|...}}
:Links inline content with a machine-readable translation.
:'''Standardized''' in [[#HTML5|HTML5]].<ref>{{cite web|url=https://developer.mozilla.org/en-US/docs/Web/HTML/Element/data|title=&lt;data&gt;|website=MDN Web Docs}}</ref>

{{Anchor|del|del_tag}}{{XMLElement|del|Deleted|...}}
:Deleted text. Typically rendered as a [[strikethrough]]: <del>Deleted text.</del>
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{Anchor|ins|ins_tag}}{{XMLElement|ins|Inserted|...}}
:Inserted text. Often used to mark up replacement text for material struck with {{tag|del|o}} or {{tag|s|o}}. Typically rendered [[underline]]d: <ins>Inserted text.</ins>
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.
:Both {{tag|ins|o}} and {{tag|ins|del|o}} elements may also be used as block elements: containing other block and inline elements. However, these elements must still remain wholly within their parent element to maintain a well-formed HTML document. For example, deleting text from the middle of one paragraph across several other paragraphs and ending in a final paragraph would need to use three separate {{tag|ins|del|o}} elements. Two {{tag|ins|del|o}} elements would be required as inline elements to indicate the deletion of text in the first and last paragraphs, and a third, used as a block element, to indicate the deletion in the intervening paragraphs.

{{Anchor|mark|mark_tag}}{{XMLElement|mark|Mark|...}}
:Produces text that looks <mark>like this</mark>. Intended for highlighting relevant text in a quotation.
'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|q|q_tag}}{{XMLElement|q|Quote|...}}
:An inline quotation (for block level quotation see {{tag|[[#blockquote|blockquote]]|o}}). Quote elements may be nested.
:{{tag|q|o}} {{em|should}} automatically generate quotation marks in conjunction with style sheets. Practical concerns due to browser non-compliance may force authors to find workarounds.
:The <code>cite</code> attribute gives the source, and must be a fully qualified [[Uniform Resource Identifier|URI]].
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.
:{{strong|Note:}} Lengthy inline quotations may be displayed as indented blocks (as <code>block-quote</code>) using style sheets. For example, with a suitable CSS rule associated with <code>q.lengthy</code>: {{tag|q |attr=class="lengthy" |content=Lengthy quote here.}}

{{Anchor|rb|rb_tag}}{{XMLElement|rb|Ruby Annotation Base|...|}}
:Represents the base component of a [[Ruby character|ruby annotation]].
:'''Standardized''' in [[#HTML5|HTML5]].<ref>{{cite web|url=http://www.quackit.com/html/tags/html_rb_tag.cfm|title=HTML <rb> Tag|website=www.quackit.com}}</ref>

{{Anchor|rp|rp_tag}}{{XMLElement|rp|Ruby Fallback Parenthesis|...|}}
:Provides fallback parenthesis for browsers lacking [[Ruby character|ruby annotation]] support.
:'''Standardized''' in [[#HTML5|HTML5]].<ref>{{cite web|url=https://developer.mozilla.org/en-US/docs/Web/HTML/Element/rp|title=&lt;rp&gt;: The Ruby Fallback Parenthesis element|website=MDN Web Docs}}</ref>

{{Anchor|rt|rt_tag}}{{XMLElement|rt|Ruby Annotation Pronunciation|...|}}
:Indicates pronunciation for a character in a [[Ruby character|ruby annotation]].
:'''Standardized''' in [[#HTML5|HTML5]].<ref>{{cite web|url=https://developer.mozilla.org/en-US/docs/Web/HTML/Element/rt|title=&lt;rt&gt;: The Ruby Text element|website=MDN Web Docs}}</ref>

{{Anchor|rtc|rtc_tag}}{{XMLElement|rtc|Ruby Semantic Annotation|...|}}
:Semantic annotations for a [[Ruby character|ruby annotation]].
:'''Standardized''' in [[#HTML5|HTML5]].<ref>{{cite web|url=https://developer.mozilla.org/en-US/docs/Web/HTML/Element/rtc|title=&lt;rtc&gt;: The Ruby Text Container element|website=MDN Web Docs}}</ref>

{{Anchor|ruby|ruby_tag}}{{XMLElement|ruby|Ruby Annotation|...|}}
:Represents a [[Ruby character|ruby annotation]] for showing the pronunciation of East Asian characters.
:'''Standardized''' in [[#HTML5|HTML5]].<ref>{{cite web|url=https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ruby|title=&lt;ruby&gt;|website=MDN Web Docs}}</ref>

{{Anchor|script|script_tag}}{{XMLElement|script|Script|...}}
:Places a [[scripting language|script]] in the document. Also usable in the head and in block contexts.
::{{em|Note:}} {{tag|script|o}} is not itself either a block or inline element; by itself it should not display at all, but it can contain instructions to dynamically generate either both block or inline content.
:'''Standardized''' in [[#HTML32|HTML 3.2]]; still current.

{{Anchor|sub|sub_tag}}{{XMLElement|sub|Subscript|...}} and {{Anchor|sup|sup_tag}}{{XMLElement|sup|Superscript|...}}
:Mark <sub>[[subscript]]</sub> or <sup>[[superscript]]</sup> text. (Equivalent CSS: {{code|lang=css|code={ vertical-align: sub; } }} and {{code|lang=css|code={ vertical-align: super; } }}, respectively.)
:Both were proposed in the [[#HTML30|HTML 3.0 Drafts]]; '''Standardized''' in [[#HTML32|HTML 3.2]]; still current.

{{anchor|template|template_tag}}{{XMLElement|template|Template|...}}
:Code fragments to be copied by scripts.
:'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|time|time_tag}}{{XMLElement|time|Time|...|}}
:Represents a time on the 24-hour clock or a date on the [[Gregorian calendar]], optionally with time and timezone information. Also allows times and dates to be represented in a machine-readable format.
:'''Standardized''' in [[#HTML5|HTML5]].<ref>{{cite web|url=https://developer.mozilla.org/en-US/docs/Web/HTML/Element/time|title=&lt;time&gt;|website=MDN Web Docs}}</ref>

{{Anchor|wbr|wbr_tag}}{{XMLElement|wbr|Word Break Opportunity|...|end=no}}
:An optional word break.
:Was widely used (and supported by all major browsers) for years despite being non-standard until finally being '''standardized''' in [[#HTML5|HTML5]].

===Images and objects===

{{Anchor|applet|applet_tag}}{{XMLElement|applet|Java Applet|...|deprecated=xhtml}}
:Embeds a [[Java applet]] in the page. Deprecated in favor of {{tag|object|o}}, as it could only be used with Java applets, and had accessibility limitations.
:'''Standardized''' in [[#HTML32|HTML 3.2]]; '''deprecated''' in [[#HTML401|HTML 4.0 Transitional]]; '''invalid''' in [[#HTML401|HTML 4.0 Strict]]. As of 2011, still widely used as the implementations of the replacing {{tag|object|o}} are not consistent between different browsers.

{{Anchor|area|area_tag}}{{XMLElement|area|Area|...|end=no}}
:Specifies a [[Focus (computing)|focusable]] area in a {{tag|map|o}}.
:'''Standardized''' in [[#HTML32|HTML 3.2]]; still current.

{{anchor|audio|audio_tag}}{{XMLElement|audio|Audio|...}}
:Adds playable [[HTML5 audio]] to the page. The audio URL is determined using the <code>src</code> attribute. Supported audio formats vary from browser to browser.
:'''Standardized''' in [[#HTML5|HTML5]].

{{anchor|canvas|canvas_tag}}{{XMLElement|canvas|Canvas|...}}
:Adds a canvas whose contents can be edited with [[JavaScript]]. Frequently used for online games.
:'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|embed}}{{XMLElement|embed|Embed|...|}}
:Inserts a non-standard object (like applet) or external content (typically non-HTML) into the document. Deprecated in HTML 4 in favor of {{tag|object|o}}, but then was added back into the HTML5 specification<ref>[http://webdesign.about.com/od/htmltags/p/bltags_embed.htm Jennifer Kyrnin ] {{Webarchive|url=https://web.archive.org/web/20121102014318/http://webdesign.about.com/od/htmltags/p/bltags_embed.htm |date=2012-11-02 }} {{tag|embed|o}}</ref><ref>[https://www.w3schools.com/tags/tag_embed.asp W3Schools] about {{tag|embed|o}}</ref>

{{Anchor|img|img_tag}}{{XMLElement|img|Image|...|end=no}}
:Used by visual user agents to insert an [[image]] in the document. The <code>src</code> attribute specifies the image URL. The required [[Alt attribute|<code>alt</code> attribute]] provides alternative text in case the image cannot be displayed.<ref>The alt attribute's text cannot be styled with markup; as a result, other methods of alternative text presentation, such as [[Fahrner Image Replacement]], have been devised to accommodate situations in which the coder wishes styled text to be displayed if images are disabled in a user's browser.</ref> (Though <code>alt</code> is intended as alternative text, Microsoft [[Internet Explorer]] 7 and below render it as a [[tooltip]] if no <code>title</code> attribute is given.<ref>{{cite web | url=http://msdn.microsoft.com/en-us/library/cc288472.aspx#access | title=What's New in Internet Explorer 8 – Accessibility and ARIA | publisher=Microsoft | work=MSDN | accessdate=2009-07-22}}</ref> [[Safari (web browser)|Safari]] and [[Google Chrome]], on the other hand, do not display the alt attribute at all.)<ref>{{citation|url=https://bugs.webkit.org/show_bug.cgi?id=5566 |title=Bug 5566 – ALT attribute value sometimes not displayed when image is missing |publisher=Bugs.webkit.org |date= |accessdate=2012-03-26}}</ref>  The {{tag|img|s}} element was first proposed by [[Marc Andreessen]] and implemented in the [[Mosaic (web browser)|NSCA Mosaic]] web browser.<ref>{{citation|url=http://1997.webhistory.org/www.lists/www-talk.1993q1/0182.html |title=WWW-Talk Jan-Mar 1993: proposed new tag: IMG |publisher=1997.webhistory.org |date= |accessdate=2012-03-26}}</ref>
:<code>IMG</code> existed in ''[[#HTMLDRAFT12|HTML Internet Draft 1.2]]'', and was '''standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|map|map_tag}}{{XMLElement|map|Image Map|...|}}
:Specifies a client-side [[image map]].
:'''Standardized''' in [[#HTML32|HTML 3.2]]; still current.

{{Anchor|object|object_tag}}{{XMLElement|object|Object|...|}}
:Includes an [[Media Object|object]] in the page of the type specified by the <code>type</code> attribute. This may be in any [[MIME]]-type the user agent understands, such as an embedded HTML page, a file to be handled by a plug-in such as [[Macromedia Flash|Flash]], a [[Java (programming language)|Java]] [[applet]], a sound file, etc.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{Anchor|param|param_tag}}{{XMLElement|param|Object Parameter|...|end=no}}
:Originally introduced with {{tag|applet|o}}, this element is now used with {{tag|object|o}}, and should only occur as a child of {{tag|object|o}}. It uses [[HTML attributes]] to set a parameter for the object, e.g. width, height, font, background color, etc., depending on the type of object. An object can have multiple {{tag|param|s}} elements.
:'''Standardized''' in [[#HTML32|HTML 3.2]]; still current.

{{anchor|source|source_tag}}{{XMLElement|source|Source|...}}
:Specifies different sources for audio or video. Makes use of the <code>src</code> attribute in a way similar to the {{tag|video|o}} and {{tag|audio|o}} elements.
:'''Standardized''' in [[#HTML5|HTML5]].

{{anchor|track|track_tag}}{{XMLElement|track|Track|...}}
:Provides text tracks, like subtitles and captions, for audio and video.
:'''Standardized''' in [[#HTML5|HTML5]].

{{anchor|video|video_tag}}{{XMLElement|video|Video|...}}
:Adds a playable [[HTML5 video]] to the page. The video URL is determined using the <code>src</code> attribute. Supported video formats vary from browser to browser.
:'''Standardized''' in [[#HTML5|HTML5]].

===Forms===
{{Main|Form (HTML)}}

These elements can be combined into a form or in some instances used separately as user-interface controls; in the document, they can be simple HTML or used in conjunction with Scripts. HTML markup specifies the elements that make up a form, and the method by which it will be submitted. However, some form of scripts ([[server-side script|server-side]], client-side, or both) must be used to process the user’s input once it is submitted.

(These elements are either block or inline elements, but are collected here as their use is more restricted than other inline or block elements.)

{{Anchor|form|form_tag}}{{XMLElement|form|Form|...|atr={{XMLAttribute|action|Action|url|type=URL|need=required}}}}
:Creates a [[form (web)|form]]. The {{tag|form|o}} element specifies and operates the overall action of a form area, using the required <code>action</code> attribute.
:'''Standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|button|button_tag}}{{XMLElement|button|Button|...}}
:A generic form button which can contain a range of other elements to create complex buttons.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{anchor|datalist|datalist_tag}}{{XMLElement|datalist|Data List|...}}
:A list of <code>option</code>s for use in form elements.
:'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|fieldset|fieldset_tag}}{{XMLElement|fieldset|Fieldset|...}}
:A container for adding structure to forms. For example, a series of related controls can be grouped within a {{tag|fieldset|o}}, which can then have a {{tag|legend|o}} added in order to identify their function.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{Anchor|input|input_tag}}{{XMLElement|input|Input|...|end=no}}
:{{tag|input|o}} elements allow a variety of standard form controls to be implemented.
:'''Standardized''' in [[#HTML20|HTML 2.0]]; still current.

:'''Input Types:'''
:{{XMLAttribute|type|Field Type|checkbox|type=ENUM|need=implied}}
::A '''[[checkbox]]'''. Can be checked or unchecked.

:{{XMLAttribute|type|Field Type|radio|type=ENUM|need=implied}}
::A '''[[radio button]]'''. If multiple radio buttons are given the same name, the user will only be able to select one of them from this group.

:{{XMLAttribute|type|Field Type|button|type=ENUM|need=implied}}
::A general-purpose button. The element {{tag|button|o}} is preferred if possible (i.e., if the client supports it) as it provides richer possibilities.

:{{XMLAttribute|type|Field Type|submit|type=ENUM|need=implied}}
::A '''submit''' button.

:{{XMLAttribute|type|Field Type|image|type=ENUM|need=implied}}
::An '''image button'''. The image URL may be specified with the <code>src</code> attribute.

:{{XMLAttribute|type|Field Type|reset|type=ENUM|need=implied}}
::A '''reset button''' for resetting the form to default values.

:{{XMLAttribute|type|Field Type|text|type=ENUM|need=optional}}
::A '''one-line text input field'''. The <code>size</code> attribute specifies the default width of the input in character-widths. <code>max-length</code> sets the maximum number of characters the user can enter (which may be greater than size).

:{{XMLAttribute|type|Field Type|search|type=ENUM|need=implied}}
::A variation of <code>text</code> which produces a search bar.

:{{XMLAttribute|type|Field Type|password|type=ENUM|need=implied}}
::A variation of <code>text</code>. The difference is that text typed in this field is {{em|masked}} – characters are displayed as an asterisk, a dot, or another replacement. The password is still submitted to the server as [[plaintext]], so an underlying secure [[communication protocol]] like [[HTTPS]] is needed if confidentiality is a concern.

:{{XMLAttribute|type|Field Type|file|type=ENUM|need=implied}}
::A [[file select]] field (for uploading files to a server).

:{{XMLAttribute|type|Field Type|tel|type=ENUM|need=implied}}
::A variation of <code>text</code> for [[telephone numbers]].

:{{XMLAttribute|type|Field Type|email|type=ENUM|need=implied}}
::A variation of <code>text</code> for [[email addresses]].

:{{XMLAttribute|type|Field Type|url|type=ENUM|need=implied}}
::A variation of <code>text</code> for [[URLs]].

:{{XMLAttribute|type|Field Type|date|type=ENUM|need=implied}}
::A date selector.

:{{XMLAttribute|type|Field Type|time|type=ENUM|need=implied}}
::A time selector.

:{{XMLAttribute|type|Field Type|number|type=ENUM|need=implied}}
::A variation of <code>text</code> for numbers.

:{{XMLAttribute|type|Field Type|range|type=ENUM|need=implied}}
::Produces a slider for that returns a number, but the number is not visible to the user.

:{{XMLAttribute|type|Field Type|color|type=ENUM|need=implied}}
::A color picker.

:{{XMLAttribute|type|Field Type|hidden|type=ENUM|need=implied}}
::<code>hidden</code> inputs are not visible in the rendered page, but allow a designer to maintain a copy of data that needs to be submitted to the server as part of the form. This may, for example, be data that this web user entered or selected on a previous form that needs to be processed in conjunction with the current form. Not displayed to the user but data can still be altered client-side by editing the HTML source.

{{Anchor|isindex|isindex_tag}}{{XMLElement|isindex|Index|...|end=no|deprecated=1}}
:{{tag|isindex|s}} could either appear in the document head or in the body, but only once in a document.
:{{tag|isindex|s}} operated as a primitive HTML search form; but was {{lang|la|[[de facto]]}} obsoleted by more advanced HTML forms introduced in the early to mid-1990s. Represents a set of hyperlinks composed of a base URI, an [[ampersand]] and [[Percent-encoding|percent-encoded]] keywords separated by [[plus sign]]s.
:<code>ISINDEX</code> existed in ''[[#HTMLTAGS|HTML Tags]]''; '''standardized''' in [[#HTML20|HTML 2.0]]; '''deprecated''' in [[#HTML401|HTML 4.0 Transitional]]; '''invalid''' in [[#HTML401|HTML 4.0 Strict]].

{{anchor|keygen|keygen_tag}}{{XMLElement|keygen|Key pair generator|...|deprecated=1}}
:A key pair generator.
:'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|label|label_tag}}{{XMLElement|label|Label|...|atr={{XMLAttribute|for|For|id|type=ENUM|need=implied}}}}
:Creates a label for a form input, such as <code>radio</code>. Clicking on the label fires a click on the matching input.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{Anchor|legend|legend_tag}}{{XMLElement|legend|Legend|...}}
:A legend (caption) for a {{tag|fieldset|o}}.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{anchor|meter|meter_tag}}{{XMLElement|meter|Meter|...}}
:A meter which needs a <code>value</code> attribute. Can also have: <code>min</code>, <code>low</code>, <code>high</code>, and <code>max</code>.
:'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|option|option_tag}}{{XMLElement|option|Select List Option|...|atr={{XMLAttribute|value|Value|x|type=ANY|need=required}}}}
:Creates an item in a {{tag|select|o}} list.
:'''Standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|optgroup|optgroup_tag}}{{XMLElement|optgroup|Options Group|...|}}
:Identifies a group of {{tag|option|o}} elements in a {{tag|select|o}} list.
:'''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

{{anchor|output|output_tag}}{{XMLElement|output|Output|...}}
:The value of a form element.
:'''Standardized''' in [[#HTML5|HTML5]].

{{anchor|progress|progress_tag}}{{XMLElement|progress|Progress Bar|...}}
:A bar for showing the progress of an action.
:'''Standardized''' in [[#HTML5|HTML5]].

{{Anchor|select|select_tag}}{{XMLElement|select|Selection List|...|atr={{XMLAttribute|name|Name|xyz|type=NMTOKEN|need=implied}}}}
:Creates a selection list, from which the user can select a single option. May be rendered as a dropdown list.
:'''Standardized''' in [[#HTML20|HTML 2.0]]; still current.

{{Anchor|textarea|textarea_tag}}{{XMLElement|textarea|Multiline Textarea|...|atr={{XMLAttribute|rows|Rows|8|type=INT}}}}
:A multiple-line text area, the size of which is specified by <code>cols</code> (where a column is a one-character width of text) and <code>rows</code> [[HTML attributes]]. The content of this element is restricted to plain text, which appears in the text area as default text when the page is loaded.
:'''Standardized''' in [[#HTML20|HTML 2.0]]; still current.

===Tables===
The format of HTML Tables was proposed in the [[#HTML30|HTML 3.0 Drafts]] and the later RFC 1942 ''[[#HTMLTABLES|HTML Tables]]''. They were inspired by the [[CALS Table Model]]. Some elements in these proposals were included in HTML 3.2; the present form of HTML Tables was standardized in HTML 4. (Many of the elements used within tables are neither ''block'' nor ''inline'' elements.)

{{Anchor|table|table_tag}}{{XMLElement|table|Table|...|}}
:Identifies a table. Several [[HTML attributes]] are possible in HTML Transitional, but most of these are invalid in HTML Strict and can be replaced with style sheets. The <code>summary</code> attribute is informally required for accessibility purposes, though its usage is not simple.
:Proposed in the [[#HTML30|HTML 3.0 Drafts]]; '''Standardized''' in [[#HTML32|HTML 3.2]]; still current.
{{Anchor|tr|tr_tag}}{{XMLElement|tr|Table Row|...|}}
:Contains a row of cells in a {{tag|table|o}}.
:Proposed in the [[#HTML30|HTML 3.0 Drafts]]; '''Standardized''' in [[#HTML32|HTML 3.2]]; still current.
{{Anchor|th|th_tag}}{{XMLElement|th|Table Header Cell|...|}}
:A {{tag|table|o}} header cell; contents are conventionally displayed bold and centered. An [[aural]] user agent may use a louder voice for these items.
:Proposed in the [[#HTML30|HTML 3.0 Drafts]]; '''Standardized''' in [[#HTML32|HTML 3.2]]; still current.
{{Anchor|td|td_tag}}{{XMLElement|td|Table Data Cell|...|}}
:A {{tag|table|o}} data cell.
:Proposed in the [[#HTML30|HTML 3.0 Drafts]]; '''Standardized''' in [[#HTML32|HTML 3.2]]; still current.
{{Anchor|colgroup|colgroup_tag}}{{XMLElement|colgroup|Column Group|...|}}
:Specifies a column group in a {{tag|table|o}}.
:Proposed in [[#HTMLTABLES|HTML Tables]]; '''Standardized''' in [[#HTML401|HTML 4.0]]; still current.
{{Anchor|col|col_tag}}{{XMLElement|col|Table Column|...|}}
:Specifies a column in a {{tag|table|o}}.
:Proposed in [[#HTMLTABLES|HTML Tables]]; '''Standardized''' in [[#HTML401|HTML 4.0]]; still current.
{{Anchor|caption|caption_tag}}{{XMLElement|caption|Table Caption|...|}}
:Specifies a caption for a {{tag|table|o}}.
:Proposed in the [[#HTML30|HTML 3.0 Drafts]]; '''Standardized''' in [[#HTML32|HTML 3.2]]; still current.
{{Anchor|thead|thead_tag}}{{XMLElement|thead|Table Header|...|}}
:Specifies the header part of a {{tag|table|o}}. This section may be repeated by the user agent if the table is split across pages (in printing or other paged media).
:Proposed in [[#HTMLTABLES|HTML Tables]]; '''Standardized''' in [[#HTML401|HTML 4.0]]; still current.
{{Anchor|tbody|tbody_tag}}{{XMLElement|tbody|Table Body|...|}}
:Specifies a body of data for a {{tag|table|o}}.
:Proposed in [[#HTMLTABLES|HTML Tables]]; '''Standardized''' in [[#HTML401|HTML 4.0]]; still current.
{{Anchor|tfoot|tfoot_tag}}{{XMLElement|tfoot|Table Footer|...|}}
:Specifies the footer part of a {{tag|table|o}}. Like {{tag|thead|o}}, this section may be repeated by the user agent if the table is split across pages (in printing or other paged media).
:Proposed in [[#HTMLTABLES|HTML Tables]]; '''Standardized''' in [[#HTML401|HTML 4.0]]; still current.

==Frames==
{{Main|Framing (World Wide Web)}}

Frames allow a visual HTML Browser window to be split into segments, each of which can show a different document. This can lower bandwidth use, as repeating parts of a layout can be used in one frame, while variable content is displayed in another. This may come at a certain usability cost, especially in non-visual user agents,<ref>{{cite web|url=http://www.washington.edu/doit/are-frames-accessible|title=Are frames accessible?|quote=...frames do present additional usability challenges that are unique to users with disabilities, particularly those who use screen readers.}}</ref> due to separate and independent documents (or websites) being displayed adjacent to each other and being allowed to interact with the same parent window. Because of this cost, frames (excluding the {{tag|iframe|o}} element) are only allowed in HTML 4.01 Frame-set. Iframes can also hold documents on different servers. In this case the interaction between windows is blocked by the browser. Sites like [[Facebook]] and [[Twitter]] use iframes to display content (plugins) on third party websites. Google [[AdSense]] uses iframes to display banners on third party websites.

In HTML 4.01, a document may contain a {{tag|head|o}} and a {{tag|body|o}}} {{em|or}} a {{tag|head|o}} and a {{tag|frameset|o}}, but not both a {{tag|body|o}} and a {{tag|frameset|o}}. However, {{tag|iframe|o}} can be used in a normal document body.

{{Anchor|frameset|frameset_tag}}{{XMLElement|frameset|Frameset|...|deprecated=1}}
:Contains the set of {{tag|frame|s}} elements for a document. The layout of frames is given by comma separated lists in the <code>rows</code> and <code>cols</code> [[HTML attributes]].
:'''Standardized''' in [[#HTML401|HTML 4.0]] Frameset, '''obsolete''' in HTML5.
{{Anchor|frame|frame_tag}}{{XMLElement|frame|Frame|...|end=no|deprecated=1}}
:Defines a single frame, or region, within the {{tag|frameset|o}}. A separate document is linked to a frame using the <code>src</code> attribute inside the {{tag|frame|s}} element.
:'''Standardized''' in [[#HTML401|HTML 4.0]] Frameset, '''obsolete''' in HTML5.
{{Anchor|noframes|noframes_tag}}{{XMLElement|noframes|Frame Support Fallback|...|deprecated=1}}
:Contains normal HTML content for user agents that don't support {{tag|frame|s}} elements.
:'''Standardized''' in [[#HTML401|HTML 4.0]] Transitional, '''obsolete''' in HTML5.
{{Anchor|iframe|iframe_tag}}{{XMLElement|iframe|Inline Frame|...|}}
:An inline frame places another HTML document in a frame. Unlike an {{tag|object|s}} element, an {{tag|iframe|o}} can be the "target" frame for links defined by other elements, and it can be selected by the user agent as the focus for printing, viewing its source, and so on.
:The content of the element is used as alternative text to be displayed if the browser does not support inline frames.
:First introduced by Microsoft Internet Explorer in 1997, '''standardized''' in [[#HTML401|HTML 4.0]] Transitional, '''allowed''' in HTML5.

===<code>longdesc</code> attribute===
In [[HTML]], '''<code>longdesc</code>''' is an attribute used within the {{tag|img|s}}, {{tag|frame|s}}, or {{tag|iframe|o}} elements. It is supposed to be a [[URL]]{{refn|group=note|Strictly an [[Internationalized resource identifier|IRI]], not a URL; although URLs are a subset of IRIs.}} to a document that provides a '''long description''' for the image, frame, or iframe in question.<ref>{{cite web|url=http://www.w3.org/TR/REC-html40/struct/objects.html|title=Objects, Images, and Applets|publisher=W3C|accessdate=2008-12-20}}</ref> Note that this attribute should contain a URL, and {{em|not}} – as is commonly mistaken – the text of the description itself.

<code>longdesc</code> was designed to be used by [[screen reader]]s to display image information for computer users with [[accessibility]] issues, such as the blind or visually impaired, and is widely implemented by both web browsers and screen readers.<ref>{{cite web|url=http://www.w3.org/html/wg/wiki/ChangeProposals/InstateLongdesc/Implementation|title=InState Longdesc|accessdate=2011-09-05}}</ref>  Some developers object that
<ref>{{cite web|url=http://www.webaim.org/techniques/images/longdesc.php#longdesc|title=Creating Accessible Images|publisher=WebAim|accessdate=2008-12-20}}</ref> it is actually seldom used for this purpose because there are relatively few authors who use the attribute and most of those authors use it incorrectly; thus, they recommend deprecating <code>longdesc</code>.<ref>{{citation|url=http://wiki.whatwg.org/wiki/Longdesc_usage |title=Longdesc usage - WHATWG Wiki |publisher=Wiki.whatwg.org |date= |accessdate=2012-03-26}}</ref> The publishing industry has responded, advocating the retention of <code>longdesc</code>.<ref>{{cite web|url=http://www.w3.org/Bugs/Public/show_bug.cgi?id=13461|title=Bug 13461 - Commentary on Issue #30 (longdesc) from the Association of American Publishers |accessdate=2011-09-05}}</ref>

====Example====
<syntaxhighlight lang="html4strict">
<img src="Hello.jpg" longdesc="description.html">
</syntaxhighlight>
<br />
Content of <code>description.html</code>:
<syntaxhighlight lang="html4strict">
<br />
<p>This is an image of a two-layered birthday cake.</p>
...
</syntaxhighlight>

====Linking to the long description in the text====
Since very few graphical browsers support making the link available natively (Opera and iCab being the exceptions), it is useful to include a link to the description page near the {{tag|img|s}} element whenever possible, as this can also aid sighted users.

=====Example=====
<syntaxhighlight lang="html4strict">
<img src="Hello.jpg" longdesc="description.html" /> [<a href=
"description.html" title="long description of the image">D</a>]
</syntaxhighlight>

==Historic elements==
{{Main|Comparison of layout engines (Non-standard HTML)}}
The following elements were part of the early HTML developed by [[Tim Berners-Lee]] from 1989–91; they are mentioned in ''HTML Tags'', but deprecated in ''HTML 2.0'' and were never part of HTML standards.

{{Anchor|listing|listing_tag}}{{XMLElement|listing|HTML Listing|...|deprecated=1}}
:This element displayed the text inside the tags in a monospace font and without interpreting the HTML. The [[#HTML20|HTML 2.0]] specification recommended rendering the element at up to 132 characters per line.
:'''Deprecated''' in [[#HTML32|HTML 3.2]]; '''obsolete''' in [[#HTML5|HTML5]].<ref>{{cite web|url=https://developer.mozilla.org/en-US/docs/Web/HTML/Element/listing|title=&lt;listing&gt;|website=MDN Web Docs}}</ref>
{{Anchor|plaintext|plaintext_tag}}{{XMLElement|plaintext|Plaintext|...|deprecated=1|end=no}}
:{{tag|plaintext|s}} does not have an end tag as it terminates the markup and causes the rest of the document to be parsed as if it were [[plaintext]].
:{{tag|plaintext|s}} existed in ''[[#HTMLTAGS|HTML Tags]]''; '''deprecated''' in [[#HTML20|HTML 2.0]]; '''invalid''' in [[#HTML401|HTML 4.0]].
{{Anchor|xmp|xmp_tag}}{{XMLElement|xmp|HTML Example|...|deprecated=1}}
:This element displayed the text inside the tags in a monospace font and without interpreting the HTML. The [[#HTML20|HTML 2.0]] specification recommended rendering the element at 80 characters per line.
:'''Deprecated''' in [[#HTML32|HTML 3.2]]; '''obsolete''' in [[#HTML5|HTML5]].<ref>{{cite web|url=https://developer.mozilla.org/en-US/docs/Web/HTML/Element/xmp|title=&lt;xmp&gt;|website=MDN Web Docs}}</ref>
{{Anchor|nextid|nextid_tag}}{{XMLElement|nextid|NeXT ID|...|deprecated=1|end=no}}
:This element enabled NeXT web designing tool to generate automatic NAME labels for its anchors and was itself automatically generated.<ref>{{cite web|url=https://developer.mozilla.org/en-US/docs/Web/HTML/Element/nextid|title=&lt;nextid&gt;: The NeXT ID element (Obsolete)|website=MDN Web Docs}}</ref>
:{{tag|nextid|s}} existed in ''[[#HTMLTAGS|HTML Tags]]'' (described as obsolete); '''deprecated''' in [[#HTML20|HTML 2.0]]; '''invalid''' in [[#HTML32|HTML 3.2]] and later.

==Non-standard elements==
{{Main|Comparison of layout engines (Non-standard HTML)}}
This section lists some widely used obsolete elements, which means they are not used in [[Validator|valid]] code. They may not be supported in all user agents.

{{Anchor|blink}}{{XMLElement|blink|Blink|...|deprecated=1}}
:Causes text to blink. Introduced in imitation of the [[ANSI escape code]]s. Can be done with CSS where supported: {{code|lang=css|code={text-decoration: blink}<nowiki />}} (This effect may have negative consequences for people with [[photosensitive epilepsy]];<ref name="WCAG">{{cite web|url=http://www.w3.org/TR/WCAG10/|title=Web Content Accessibility Guidelines 1.0|first1=Wendy|last1=Chisholm|first2=Gregg|last2=Vanderheiden|first3=Ian|last3=Jacobs|publisher=World Wide Web Consortium|date=1999-05-05|accessdate=2010-07-20}}</ref> its use on the public Internet should follow the appropriate guidelines.)
:{{code|lang=html|code=<blink>}} originated in [[Netscape Navigator]] and is mostly recognized by its descendants, including [[Firefox]]; '''deprecated''' or '''invalid''' in [[#HTML20|HTML 2.0]] and later. Note that the replacement CSS tag, while standard, is not required to be supported.
{{Anchor|marquee}}{{XMLElement|marquee|Marquee|...|deprecated=1}}
:Creates scrolling text. Can be done with scripting instead. (This effect may have negative consequences for people with [[photosensitive epilepsy]];<ref name="WCAG" /> its use on the public Internet should follow the appropriate guidelines.) There are three options, including '''Alternate''', '''Scroll''' and '''slide'''. '''Scrolldelay''' can also be added.
:{{code|lang=html|code=<marquee>}} originated in [[Microsoft Internet Explorer]]; '''deprecated''' or '''invalid''' in [[#HTML20|HTML 4.01]] and later.
{{Anchor|nobr}}{{XMLElement|nobr|No Break|...|deprecated=1}}
:Causes text to not break at end of line, preventing word wrap where text exceeds the width of the enclosing object. Adjacent text may break before and after it. Can be done with CSS: {{code|lang=css|code={white-space: nowrap;}<nowiki />}}
:{{code|lang=html|code=<nobr>}} is a proprietary element which is recognized by most browsers for compatibility reasons; '''deprecated''' or '''invalid''' in [[#HTML20|HTML 2.0]] and later.
{{Anchor|noembed}}{{XMLElement|noembed|Embed Fallback|...|deprecated=1}}
:Specifies alternative content, if the embed cannot be rendered. Replaced by the content of the {{code|lang=html|code=<embed>}} or {{code|lang=html|code=<object>}} element.

==Comments==
{{Clear}}
;{{code|lang=html|code=<<nowiki />!-- A Comment -->}}
<br>
A [[Comment (computer programming)|comment]] in HTML (and related XML, SGML and SHTML) uses the same syntax as the [[SGML comment]] or [[XML comment]], depending on the doctype.

Unlike most HTML tags, comments do not nest.

The markup {{code|lang=html|code=<!<nowiki />--Xbegin<<nowiki />!--Y-->Xend-->}} will yield the comment {{samp|{{nobr|Xbegin&lt;!--Y}}}} and the text {{samp|{{nobr|Xend--&gt;}}}} after it, or sometimes just {{samp|Xend--&gt;}}, depending on browser.

Comments can appear anywhere in a document, as the HTML parser is supposed to ignore them no matter where they appear so long as they are not inside other HTML tag structures (i.e., they cannot be used next to attributes and values; this is invalid markup: <code>{{nobr|&lt;span id="x1"}}{{nobr|<--for}} "extension {{nobr|one"-->}} {{nobr|style="..."&lt;}}</code>).

Comments can even appear before the doctype declaration; no other tags are permitted to do this.

However, not all browsers and HTML editors are fully compliant with the HTML syntax framework and may do unpredictable things under some syntax conditions. Defective handling of comments only affects about 5% of all browsers and HTML editors in use, and even then only certain versions are affected by comment mishandling issues (Internet Explorer 6 accounts for most of this high percentage). 

There are a few compatibility quirks involving comments:
* Placing comments – or indeed any characters except for white-space – before the <code>doctype</code> will cause Internet Explorer 6 to use [[quirks mode]] for the HTML page. None of the <code>doctype</code> information will be processed.
* For compatibility with some pre-1995 browsers, the contents of {{tag|style|o}} and {{tag|script|o}} elements are still sometimes surrounded by comment delimiters, and CSS- and script-capable browsers are written to specifically ignore that comment markup as not actually a comment. This means that attempts to actually comment out CSS and script markup by change the elements inside the comment to not be recognized, e.g. <code>{{nobr|&lt;--}} {{nobr|[script]...}}[/script] {{nobr|--&gt;}}</code>.
* The [[BlueGriffon]] HTML editor, in versions 1.7.{{var|x}}, makes comments that are not embedded in the syntax structure; {{code|lang=html|code=<style> ... {comment tags} ...</style>}} will show up on-screen. Other HTML editors may have this same defect.

== Notes ==
{{Reflist|group=note|liststyle=lower-roman}}

==References==
{{reflist|35em}}

==Bibliography==
{{refbegin}}

===HTML standards===
;<span id="HTML20">HTML 2.0{{colon}}</span>
:{{cite web
  |last1=Berners-Lee |first1=Tim |author1-link=Tim Berners-Lee
  |last2=Connolly |first2=Dan |author2-link=Dan Connolly (computer scientist)
  |title=Hypertext Markup Language - 2.0 (RFC 1866)
  |publisher=[[IETF]]
  |date=November 1995
  |url=https://tools.ietf.org/html/rfc1866
  |access-date=2009-03-24}}
;<span id="HTML32">HTML 3.2{{colon}}</span>
:{{cite web
  |last=Raggett |first=Dave |author-link=Dave Raggett
  |title=HTML 3.2 Reference Specification
  |publisher=[[W3C]]
  |date=1997-01-14
  |url= http://www.w3.org/TR/REC-html32-19970114
  |access-date=2009-03-27}}
;<span id="HTML401">HTML 4.01{{colon}}</span>
:{{cite web
  |last=Raggett |first=Dave |author-link=Dave Raggett
  |last2=Le Hors |first2=Arnaud
  |last3=Jacobs |first3=Ian
  |title=HTML 4.01 Specification
  |publisher=[[W3C]]
  |date=1999-12-24
  |url= https://www.w3.org/TR/html4/
  |access-date=2009-03-24}}  ''(HTML 4.01 superseded [https://www.w3.org/TR/1998/REC-html40-19980424/ 4.0] (1998), which was never widely implemented, and all earlier versions. Superseded in turn on 2018-03-27 by [[#HTML52|HTML 5.2]])''
;<span id="XHTML10">XHTML 1.0{{colon}}</span>
:{{cite web
  |author=[[W3C]]
  |title=XHTML 1.0: The Extensible HyperText Markup Language (Second Edition)
  |version=Revised version
  |publisher=[[W3C]]
  |date=2002-08-01
  |orig-year=2000
  |url= https://www.w3.org/TR/xhtml1/
  |access-date=2009-03-24}}
;<span id="XHTML11">XHTML 1.1{{colon}}</span>
:{{cite web
  |editor1-last=Altheim |editor1-first=Murray
  |editor2-last=McCarron |editor2-first=Shane
  |editor3-last=Ishikawa |editor3-first=Masayasu
  |title=XHTML 1.1 - Module-based XHTML - Second Edition
  |version=Revised version
  |publisher=[[W3C]]
  |date=2010-11-23
  |orig-year=2001
  |url= https://www.w3.org/TR/xhtml11/
  |access-date=2018-07-26}} ''(Superseded on 2018-03-27 by HTML 5.2.)''
:<span id="XHTML11m"></span>{{cite web
  |editor1-last=Austin |editor1-first=Daniel
  |editor2-last=Peruvemba |editor2-first=Subramanian
  |editor3-last=McCarron |editor3-first=Shane
  |editor4-last=Ishikawa |editor4-first=Masayasu
  |editor5-last=Birbeck |editor5-first=Mark
  |editor6-last=Altheim |editor6-first=Murray
  |editor7-last=Boumphrey |editor7-first=Frank
  |editor8-last=Dooley |editor8-first=Sam
  |editor9-last=Schnitzenbaumer |editor9-first=Sebastian
  |editor10-last=Wugofski |editor10-first=Ted
  |title=XHTML™ Modularization 1.1 - Second Edition
  |version=Revised version
  |publisher=[[W3C]]
  |date=2010-07-29
  |orig-year=2006
  |url= https://www.w3.org/TR/xhtml-modularization/
  |access-date=2018-07-26}} ''(A more detailed version of the above. Also superseded on 2018-03-27 by [[#HTML52|HTML 5.2]].)''
;<span id="HTML52">W3C HTML 5.2{{colon}}</span>
:{{cite web
  |editor1-last=Faulkner |editor1-first=Steve
  |editor2-last=Eicholz |editor2-first=Arron
  |editor3-last=Leithead |editor3-first=Travis
  |editor4-last=Danilo |editor4-first=Alex
  |editor5-last=Moon |editor5-first=Sangwhan
  |editor6-last=Doyle Navara |editor6-first=Erika
  |editor7-last=O'Connor |editor7-first=Theresa
  |editor8-last=Berjon |editor8-first=Robin
  |title=HTML 5.2 W3C Recommendation
  |version=Revised version
  |publisher=[[W3C]]
  |date=2017-12-14
  |orig-year=2016
  |url= https://www.w3.org/TR/html52/
  |access-date=2018-07-26}} ''Supersedes all previous versions of HTML and XHTML, including [https://www.w3.org/TR/html51/ HTML 5.1].''
;<span id="WHATWGLS">WHATWG HTML5 Living Standard{{colon}}</span><!--Yes, WHATWG uses the run-together "HTML5" spelling.-->
:{{cite web
  |editor-first=Ian |editor-last=Hickson |editor-link=Ian Hickson
  |title=HTML Living Standard
  |version=One-page Version
  |publisher=[[WHATWG]]
  |date=2018-07-25
  |url= https://html.spec.whatwg.org/
  |access-date=2018-07-26}} ''Also available as a [https://html.spec.whatwg.org/multipage/ Multipage Version], and [https://html.spec.whatwg.org/dev/ Developer's Edition] (also multi-page, and minus details only of interest to browser vendors).''

===Other sources===

;''<span id="HTMLTAGS">HTML Tags{{colon}}</span>''
:{{cite web
  |last=Berners-Lee |first=Tim |author-link=Tim Berners-Lee
  |title=HTML Tags
  |date=1992-11-03
  |url= http://www.w3.org/History/19921103-hypertext/hypertext/WWW/MarkUp/Tags.html
  |access-date=2009-03-28}}  ''(Part of the first published description of HTML.)''
;''<span id="HTMLDRAFT12">HTML Internet Draft 1.2{{colon}}</span>''
:{{cite web
  |last1=Berners-Lee |first1=Tim |author1-link=Tim Berners-Lee
  |last2=Connolly |first2=Dan |author2-link=Dan Connolly (computer scientist)
  |title=Hypertext Markup Language (HTML)
  |date=June 1993
  |url= http://www.w3.org/MarkUp/draft-ietf-iiir-html-01.txt
  |access-date=2009-03-28}}
;''<span id="HTML30">HTML 3.0 Drafts{{colon}}</span>''
:{{cite web
  |last=Raggett |first=Dave |author-link=Dave Raggett
  |title=HyperText Markup Language Specification Version 3.0 (draft)
  |date=1995-03-24
  |url= http://www.w3.org/MarkUp/html3/CoverPage.html
  |access-date=2009-04-18}}  ''(This is the final draft of HTML 3.0, which expired without being developed further.)''
;''<span id="HTMLTABLES">HTML Tables{{colon}}</span>''
:{{cite web
  |last=Raggett |first=Dave
  |title=HTML Tables (RFC 1942)
  |publisher=[[IETF]]
  |date=May 1996
  |url= https://tools.ietf.org/html/rfc1942
  |accessdate = 2009-03-22}}
;<span id="XML10">XML 1.0{{colon}}</span>
:{{cite web
  |editor1-last=Bray |editor1-first=Tim |editor1-link=Tim Bray
  |editor2-last=Paoli |editor2-first=Jean |editor2-link=Jean Paoli
  |editor3-last=Sperberg-McQueen |editor3-first=C. Michael |editor3-link=Michael Sperberg-McQueen
  |editor4-last=Maler |editor4-first=Eve
  |editor5-last=Yergeau |editor5-first=François
  |title=Extensible Markup Language (XML) 1.0 (Fifth Edition)
  |publisher=[[W3C]]
  |date=2008-11-26
  |url= http://www.w3.org/TR/xml/
  |access-date=2009-03-20}}
;<span id="CSS1">CSS 1{{colon}}</span>
:{{cite web
  |last1=Lie |first1=Håkon Wium |author1-link=Håkon Wium Lie
  |last2=Bos |first2=Bert |author2-link=Bert Bos
  |title=Cascading Style Sheets, Level 1
  |version=Revised version
  |publisher=[[W3C]]
  |date=2008-04-11
  |orig-year=1996
  |url= http://www.w3.org/TR/CSS1/
  |access-date=2018-07-26}}
;<span id="CSS2.1">CSS 2.1{{colon}}</span>
:{{cite web
  |last1=Bos |first1=Bert |author1-link=Bert Bos
  |last2=Çelik |first2=Tantek |author2-link=Tantek Çelik
  |last3=Hickson |first3=Ian |author3-link=Ian Hickson
  |last4=Lie |first4=Håkon Wium |author4-link=Håkon Wium Lie
  |title=Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification
  |version=Revised version
  |publisher=[[W3C]]
  |date=12 April 2016
  |orig-year=2011
  |url= https://www.w3.org/TR/CSS2/
  |access-date=2018-07-26}} 
;CSS 3 and 4{{colon}}
:{{cite web
  |last1=Atkins |first=Tab, Jr.
  |last2=Eternad |first2=Elika J.
  |last3=Rivoal |first3=Florian 
  |title=CSS Snapshot 2017
  |at="§&thinsp;2. Cascading Style Sheets (CSS) – The Official Definition"
  |work=W3.org
  |publisher=[[W3C]]
  |date=31 January 2017
  |url= https://www.w3.org/TR/CSS/#css
  |access-date=2018-07-26}} ''(List of active specifications that have superseded CSS 2.1, as of the publication date.)''
:{{cite web
  |author=<!--Staff writer(s); no by-line.-->
  |title=CSS Current Status
  |work=W3.org
  |publisher=[[W3C]]
  |date=2018
  |url= https://www.w3.org/standards/techs/css#w3c_all
  |access-date=2018-07-26}} ''(CSS levels 3 and 4 are developed as independent modules, indexed at that page.)''
{{refend}}

==External links==
{{wikibooks | HyperText Markup Language | Tag List | all elements in HTML }}
* HTML 4.01 (Dec 24, 1999):  [http://www.w3.org/TR/html401/index/elements.html elements] and [http://www.w3.org/TR/html401/index/attributes.html attributes]
* {{vanchor|HTML5}} (Oct 28, 2014): [http://www.w3.org/TR/html5/index.html elements and attributes]

[[Category:HTML]]