HTML element

Template:Html series
An **HTML element** is an individual component of an HTML document or web page, once this has been parsed into the Document Object Model. HTML is composed of a tree of HTML nodes, such as text nodes. Each node can have HTML attributes specified. Nodes can also have content, including other nodes and text. Many HTML nodes represent semantics, or meaning. For example, the `title` node represents the title of the document.

## Concepts

### Document vs. DOM

HTML documents are delivered as "documents". These are then parsed, which turns them into the Document Object Model (DOM) internal representation, within the web browser.

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 syntax errors. The parsing process was also required to "fix-up" these errors, as best it could. The resultant model was often not *correct* (i.e. it did not represent what a careless coder had originally intended), but it would at least be 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. HTML documents contain tags, but do not contain the elements. The elements are only generated *after* the parsing step, from these tags.

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. This is the case for many, *but not all*, elements within an HTML document.

As HTML is based on SGML, its parsing also depends on the use of a DTD, specifically an HTML DTD such as that for HTML 4.01. 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 *possible* (per the DTD), it is not generally a requirement that the document explicitly states that structure. As a simple example, the `<p>` start tag indicating the start of a paragraph element should be closed by a `</p>` end tag, indicating the end of the element. Also the DTD states that paragraph elements cannot be nested. The HTML document fragment:

`<p>Para 1 <p>Para 2 <p>Para 3`
can thus be inferred to be equivalent to:

`<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 *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.

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, behaviour beyond that point (i.e. screen rendering) is identical.

#### `%block;` vs. box

Part of this CSS presentation behavior is the notion of the "box model". This is applied to those elements that CSS considers to be "block" elements, set through the CSS `display: block;` declaration.

HTML also has a similar concept, although different, and the two are very frequently confused. `%block;` and `%inline;` are groups within the HTML DTD that group elements as being either "block-level" or "inline". This is used to define their nesting behavior: block-level elements cannot be placed into an inline context. 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, 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 `<ul><li> ...` are `%block;` 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.

## Overview

### Syntax

Template:Image frame
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 `p` element, would be written as

```
<p>In the HTML syntax, most elements are written ...</p>

```

However, not all of these elements *require* the end tag, or even the start tag, to be present. Some elements, the so-called *void elements* or  *empty elements*, do not have an end tag. A typical example is the `br` element, which represents a significant line break, such as in a poem or an address. A void element's behavior is predefined, and it cannot contain any content or other elements. For example, an address would be written as

```
<p>P. Sherman<br>42 Wallaby Way<br>Sydney</p>

```

When using an XHTML DTD, it is required to open and close the element with a single tag. To specify that it is a void element, a "/" is included at the **end** of the tag (not to be confused with the "/" at the **beginning** of a closing tag).

```
<p>P. Sherman<br/>42 Wallaby Way<br/>Sydney</p>

```

HTML attributes are specified inside the start tag. For example, the `abbr` element, which represents an abbreviation, expects a `title` attribute within its opening tag. This would be written as

```
<abbr title="abbreviation">abbr.</abbr>

```

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

**Void elements** only have a start tag, which contains any HTML attributes. They may not contain any children, such as text or other elements. Often they are place holders for elements which reference external files, such as the image (`<img />`) element. The attributes included in the element will then point to the external file in question.
Another example of a void element is the `<link />` element, for which the syntax is

```
<link rel="stylesheet" href="fancy.css" type="text/css">

```

This `<link />` element points the browser at a 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 trailing slash is required before the last angle bracket:

```
<link rel="stylesheet" href="fancy.css" type="text/css" />

```

**Raw text elements** are constructed with:

* a *start tag* (`<tag>`) 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>`. In some versions of HTML, the end tag is optional for some elements. The end tag is required in XHTML.

Template:Examples

**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>`) 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: `</tag>`.

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 doesn't include spaces (`name=value`), or it can be quoted with single or double quotes (`name='value'` or `name="value"`). In XML, those quotes are required. Boolean attributes, on the other hand, don't require a value to be specified. An example is the `checked` for checkboxes:

```
<input type=checkbox checked>

```

In the XML syntax, though, the name should be repeated as the value:

```
<input type="checkbox" checked="checked" />

```

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. 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 agents (e.g. web browsers) 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.

Subsequently, HTML 4.01 was rewritten in an XML-compatible form, 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 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 validating user agents).

At present, the status of elements is complicated by the existence of three types of HTML 4.01 / XHTML 1.0 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 2.0) contained four deprecated elements, one of which was invalid in HTML 3.2. All four are invalid in HTML 4.01 Transitional, which also deprecated a further ten elements. All of these, plus two others, are invalid in 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 Strict, but also includes the **Ruby markup** module.)

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). 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 sheets. A default style sheet is suggested as part of the CSS standard, giving a default rendering for HTML.

Behavior (interactivity) is also kept separate from content, and is handled by 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 <b> and <i>) 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.

External image files are incorporated with the **img** or **object** 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.) 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 **style** and **script**, with related HTML attributes, provide reference points in HTML markup for links to style sheets and scripts. They can also contain instructions directly.

* In the document head, **script** and **style** may either link to shared external documents, or contain embedded instructions. (The **link** element can also be used to link style sheets.)
* The *style attribute* is valid in most document body elements for inclusion of *inline style* instructions.
* *Event-handling attributes*, which provide links to scripts, are optional in most elements.
* **script** can occur at any point in the document body.
* For user agents which do not operate scripts, the **noscript** element provides alternative content where appropriate; however, it can only be used as a block-level element.

## Document structure elements

Template:XMLElement

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 HTML 2.0; still current.
Template:XMLElement

Container for processing information and metadata for an HTML document.
**Standardized** in HTML 2.0; still current.
(See document head elements for child elements.)
Template:XMLElement

Container for the displayable content of an HTML document.
**Standardized** in HTML 2.0; still current.
(See document body elements for child elements.)
## Document head elements

Template:XMLElement

Specifies a **base URL** for all relative `href` and other links in the document. Must appear before any element that refers to an external resource. HTML permits only one `base` element for each document. The `base` element has HTML attributes, but no contents.
A development version of **BASE** is mentioned in *HTML Tags*; **standardized** in HTML 2.0; still current.
Template:XMLElement

Specifies a base font size, typeface, and color for the document. Used together with `font` elements. Deprecated in favour of style sheets.
**Standardized** in HTML 3.2; **deprecated** in HTML 4.0 Transitional; **invalid** in HTML 4.0 Strict.
Template:XMLElement

**`isindex`** could either appear in the document head or in the body, but only once in a document. See Forms.
Template:XMLElement

Specifies links to other documents, such as *previous* and *next* links, or alternate versions. A common use is to link to external style sheets, using the form:
`<link rel="stylesheet" type="text/css" href="url" title="description\_of\_style">`
A less-common, but important, usage is to supply navigation hints consistently through use of microformats. Several common relationships are defined, that may be exposed to users through the browser interface rather than directly in the web page.
`<link rel="next" href="url">`
A document's `head` element may contain any number of `link` elements. The `link` element has HTML attributes, but no contents.
**LINK** existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current.
[[Meta element|Template:XMLElement]]

*Main article: 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, `meta` elements specify associative 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 *meta* element is defined by its attributes.
In one form, `meta` elements can specify HTTP headers which should be sent by a web server before the actual content, for example:
`<meta http-equiv="foo" content="bar">`
— this specifies that the page should be served with an HTTP header called `foo` that has a value `bar`.
In the general form, a `meta` element specifies `name` and associated `content` HTML attributes describing aspects of the HTML page. To prevent possible ambiguity, an optional third attribute, `scheme`, may be supplied to specify a semantic framework that defines the meaning of the key and its value: for example:
`<meta name="foo" content="bar" scheme="DC">`
In this example, the `meta` element identifies itself as containing the `foo` element, with a value of `bar`, from the DC or Dublin Core resource description framework.
**Standardized** in HTML 2.0; still current.
Template:XMLElement

Used for including generic objects within the document header. Though rarely used within a `head` element, it could potentially be used to extract foreign data and associate it with the current document.
**Standardized** in HTML 4.0; still current.
Template:XMLElement

Can act as a container for script instructions or link to an external script with the optional `src` attribute. Also usable in the document body to dynamically generate either both block or inline content.
**Standardized** in HTML 3.2; still current.
Template:XMLElement

Specifies a style for the document, usually in the form:
`<style type="text/css"> ... </style>`
Can either act as a container for style instructions or link to external style sheets – for example, in CSS, with `@import` directives of the form:
`<style> @import url; </style>`
**Standardized** in HTML 3.2; still current.
Template:XMLElement

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 engines’ web crawlers may pay particular attention to the words used in the title.

The `title` element must not contain other elements, only text. Only one `title` element is permitted in a document.
**TITLE** existed in *HTML Tags*, and was **standardized** in 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 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 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

Template:XMLElement

Creates a paragraph, perhaps the most common block level element.
`P` existed in *HTML Tags*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement
Template:XMLElement
Template:XMLElement
Template:XMLElement
Template:XMLElement
Template:XMLElement

Section headings at different levels. `<h1>` delimits the highest-level heading, `<h2>` the next level down (sub-section), `<h3>` for a level below that, and so on to `<h6>`. They are sometimes referred to collectively as `<h*n*>` 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 CSS. Heading elements are not intended merely for creating large or bold text—in fact, they should *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 *HTML Tags*, and were **standardized** in HTML 2.0; still current.
#### Lists

Template:XMLElement

A description list (a.k.a. association list), which consists of name–value groups, and was known as a definition list prior to HTML5. 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".
`DL` existed in *HTML Tags*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

A name in a description list (previously definition term in a definition list).
`DT` existed in *HTML Tags*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

A value in a description list (previously definition data in a definition list).
`DD` existed in *HTML Tags*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

An ordered (enumerated) list. The `type` 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. CSS: `list-style-type: foo`. HTML attribute: `<ol type="foo">`, in either case, replacing `foo` with one of the following:
* `A` for A, B, C...
* `a` for a, b, c...
* `I` for I, II, III...
* `i` for i, ii, iii...
* `1` for 1, 2, 3...

`OL` existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

An unordered (bulleted) list. Style sheets can be used to specify the list marker: `list-style-type: foo`. The default marker type is `disc`, other values are `square`, `circle` and `none`.
`UL` existed in *HTML Tags*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

A list item in ordered (**ol**) or unordered (**ul**) lists.
`LI` existed in *HTML Tags*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

A directory listing. The original purpose of this element was never widely supported; deprecated in favor of `<ul>`.
`DIR` existed in *HTML Tags*, and was **standardized** in HTML 2.0; **deprecated** in HTML 4.0 Transitional; **invalid** in HTML 4.0 Strict.
#### Other block elements

Template:XMLElement

Contact information for the document author.
`ADDRESS` existed in *HTML Tags*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

Used for articles and other similar content.
**Standardized** in HTML5.
Template:XMLElement

Used for content in a document which is separate from the main page content, for example, sidebars or advertising.
**Standardized** in HTML5.

Template:XMLElement

A block level quotation, for when the quotation includes block level elements, e.g. paragraphs. The `cite` attribute 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`) element.
`BLOCKQUOTE` existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current. See blockquote element for more information.
Template:XMLElement

Creates a block-level center-aligned division. Deprecated in favor of `<div>` or another element with centering defined using style sheets.
**Standardized** in HTML 3.2; **deprecated** in HTML 4.0; **not supported** in HTML5.
Template:XMLElement

Marks a deleted section of content. This element can also be used as *inline*.
**Standardized** in HTML 4.0; still current.
Template:XMLElement

*Main article: 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 behaviour controlled by style sheets or DOM calls.
Proposed in the HTML 3.0 Drafts; **Standardized** in HTML 3.2; still current.
Template:XMLElement

Used to group images and captions, along with `figcaption`.
**Standardized** in HTML5.
Template:XMLElement

A caption for an image. Always placed inside the figure element.
**Standardized** in HTML5.
Template:XMLElement

Used for document footers. These may contain author or copyright information, or links to other pages.
**Standardized** in HTML5.
Template:XMLElement

Used for document headers. These typically contain content introducing the page.
**Standardized** in HTML5.
Template:XMLElement

A horizontal rule. Presentational rules can also be drawn with style sheets.
**Standardized** in HTML 2.0; still current.
Template:XMLElement

Marks a section of inserted content. This element can also be used as *inline*.
**Standardized** in HTML 4.0; still current.
Template:XMLElement

Contains the main content of a document.
**Standardized** in HTML5.
Template:XMLElement

HTML 2.0: A menu listing. Should be more compact than a `<ul>` list.
`MENU` existed in *HTML Tags*, and was **standardized** in HTML 2.0; **deprecated** in HTML 4.0 Transitional; **invalid** in HTML 4.0 Strict; but then redefined in HTML5.
Template:XMLElement

Used in navigational sections of articles (areas of webpages which contain links to other webpages).
**Standardized** in HTML5.
Template:XMLElement

Replacement content for scripts. Unlike **script** this can only be used as a block-level element.
**Standardized** in HTML 4.0; still current.
Template:XMLElement

*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 white-space for other HTML elements, in `pre`, white-space should be rendered as authored. (With the CSS properties: `{white-space: pre; font-family: monospace;}`, other elements can be presented in the same way.) This element can contain any inline element except: image (`IMG`), object (`OBJECT`), big font size (`BIG`), small font size (`SMALL`), superscript (`SUP`), and subscript (`SUB`).
`PRE` existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

Used for generic sections of a document. This is different from `div` 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.
Template:XMLElement

Places a script in the document. Also usable in the head and in inline contexts.
Note: `SCRIPT` 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 HTML 3.2; still current.
### Inline elements

Inline elements cannot be placed directly inside the `body` element; they must be wholly nested within block-level elements.

#### Anchor

Template:XMLElement

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.
In HTML, an **anchor** can be either the origin (the anchor text) or the *target* (destination) end of a **hyperlink**.
With the attribute `href`, the anchor becomes a hyperlink to either another part of the document or another resource (e.g. a webpage) using an external URL. Alternatively (and sometimes concurrently), with the `name` or `id` HTML attributes set, the element becomes a **target**. A Uniform Resource Locator can link to this target via a fragment identifier. In HTML5, any element can now be made into a target by using the `id` attribute, so using `<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 `example.com` could be turned into a target by writing
`<h1 id="contents">Table of contents</h1>`
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
`<a href="http://example.com#contents">see contents</a>`
or with a link on the same page like:
`<a href="#contents">contents, above</a>`
The attribute `title` may be set to give brief information about the link:
`<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 `title` is displayed in a tooltip or in some other manner. Some browsers render alt text the same way, although this is not what the specification calls for.
`A` existed in *HTML Tags*, and was **standardized** in HTML 2.0; still current.
#### Phrase elements

##### General

Template:XMLElement

Marks an abbreviation, and can make the full form available:
`<abbr title="abbreviation">abbr.</abbr>`
**Standardized** in HTML 4.0; still current.
Template:XMLElement

Similar to the `abbr` element, but marks an acronym:
`<acronym title="Hyper-Text Mark-up Language">HTML</acronym>`
**Standardized** in HTML 4.0; still current, **not supported** in HTML5.
Template:XMLElement

inline definition of a single term.
`DFN` existed in *HTML Internet Draft 1.2*, and was fully **standardized** in HTML 3.2; still current.
Template:XMLElement

*Emphasis* (conventionally displayed in italics)
`EM` existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

**strong emphasis** (conventionally displayed bold).
An aural user agent may use different voices for emphasis.
`STRONG` existed in *HTML Internet Draft 1.2*, and was **standardized** in 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>), source code variables (<var>), user input (<kbd>), and terminal output (<samp>).

Template:XMLElement

A code snippet (`code example`). Conventionally rendered in a mono-space font.
`CODE` existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

Keyboard - text to be entered by the user (`kbd example`).
`KBD` existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

Sample output - from a program or script: (`samp example`).
`SAMP` existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

Variable (var example).
`VAR` existed in *HTML Internet Draft 1.2*, and was **standardized** in 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 XHTML 2.0. The current draft of HTML5, however, re-includes `
`, `<u>`, and `<small>`, 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.

Template:XMLElement

In HTML 4, set font to **boldface** where possible. Equivalent CSS: `{font-weight: bold}`. `<strong>...</strong>` usually has the same effect in visual browsers, as well as having more semantic meaning, under HTML 4.01.
In HTML5, however, `b` has its own meaning, distinct from that of `strong`. 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."
`B` existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

In HTML 4, set font to *italic* where possible. Equivalent CSS: `{font-style: italic}`. `<em>...</em>` usually has the same effect in visual browsers, as well as having more semantic meaning, under HTML 4.01.
In HTML5, however, `i` has its own semantic meaning, distinct from that of `em`. It denotes "a different quality of text" or "an alternative voice or mood"—e.g., a thought, a ship name, a binary species name, a foreign-language phrase, etc.
`I` existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

In HTML 4, underlined text. Equivalent CSS: `{text-decoration: underline}`. Deprecated in HTML 4.01. Restored in HTML5.
In HTML5, the `u` 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 `u` and admonishes designers not to use underlined text where it could be confused for a hyper-link.
`U` existed in *HTML Internet Draft 1.2*, was **standardized** in HTML 3.2 but was **deprecated** in HTML 4.0 Transitional and was **invalid** in HTML 4.0 Strict. **Reintroduced** in HTML5.
Template:XMLElement

In HTML 4, decreased font size (smaller text). Equivalent CSS: `{font-size: smaller}`
In HTML5, the `small` element denotes "side comments such as small print."
**Standardized** in HTML 3.2; still current.
Template:XMLElement

In HTML 4, indicated strike-through text (~~Strikethrough~~) and was equivalent to `strike`.
In HTML5, the `s` element denotes information that is "no longer accurate or no longer relevant", and is not to be confused with `del`, which indicates removal/deletion.
`S` was **deprecated** in HTML 4.0 Transitional (having not appeared in any previous standard), and was **invalid** in HTML 4.0 Strict. **Reintroduced** in HTML5.
Template:XMLElement

Increased font size (bigger text). Equivalent CSS: `{font-size: larger}`
**Standardized** in HTML 3.2; **not supported** in HTML5.
Template:XMLElement

Strike-through text (~~Strikethrough~~), (Equivalent CSS: `{text-decoration: line-through}`)
`STRIKE` was standardized in HTML 3.2; **deprecated** in HTML 4.0 Transitional; **invalid** in HTML 4.0 Strict.
Template:XMLElement

Fixed-width font (typewriter-like), also known as teletype. (Equivalent CSS: `{font-family: monospace;}`)
`TT` existed in *HTML Internet Draft 1.2*, and was **Standardized** in HTML 2.0; not supported in HTML5. Possible replacements: `<kbd>...</kbd>` for marking keyboard input, `<var>...</var>` for variables, `<code>...</code>` for computer code, `<samp>...</samp>` for computer output.
Template:XMLElement

`<font [color=colour] [size=size] [face=face]>...</font>`
Can specify the font colour with the `color` attribute (note the American spelling), typeface with the `face` attribute, and absolute or relative size with the `size` attribute.
Examples (all uses are deprecated, use CSS equivalents if possible):
1. `<font color="green">text</font>` creates Template:Green.
2. `<font color="#114499">text</font>` creates text with hexadecimal color #114499.
3. `<font size="4">text</font>` creates text with size 4. Sizes are from 1 to 7. The standard size is 3, unless otherwise specified in the <body> or other tags.
4. `<font size="+1">text</font>` creates text with size 1 bigger than the standard. `<font size="-1">text</font>` is opposite.
5. `<font face="Courier">text</font>` makes text with Courier font.

Equivalent CSS for font attributes:
* `<font size="N">` corresponds to `{font-size: Yunits}` (the HTML specification does not define the relationship between size N and unit-size Y, nor does it define a unit).
* `<font color="red">` corresponds to `{color: red}`
* `<font face="Courier">` corresponds to `{font-family: "Courier"}`

**Standardized** in HTML 3.2; **deprecated** in HTML 4.0 Transitional; **invalid** in HTML 4.0 Strict. Not part of HTML5.
#### Span

Template:XMLElement

*Main article: 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 behaviour controlled by style sheets or DOM calls.
**Standardized** in HTML 4.0; still current.
#### Other inline elements

Template:XMLElement

A forced line break.
**Standardized** in HTML 2.0; still current.
Template:XMLElement

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.
Template:XMLElement

Marks an inline section of text in which the reading direction is the opposite from that of the parent element.
**Standardized** in HTML 4.0; still current.
Template:XMLElement

A citation or a reference for a quote or statement in the document.
**CITE** existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

Links inline content with a machine-readable translation.
**Standardized** in HTML5.
Template:XMLElement

Deleted text. Typically rendered as a strikethrough: ~~Deleted text.~~
**Standardized** in HTML 4.0; still current.
Template:XMLElement

Inserted text. Often used to mark up replacement text for `<del>`'d text. Typically rendered underlined: Inserted text.
**Standardized** in HTML 4.0; still current.
Note, both `<ins>` and `<del>` 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 `<del>` elements. Two `<del>` elements would be required as inline element 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.
Template:XMLElement

Produces text that looks like this. Intended for highlighting relevant text in a quotation.
**Standardized** in HTML5.

Template:XMLElement

An inline quotation (for block level quotation see `blockquote`). Quote elements may be nested.
`<q>` *should* automatically generate quotation marks in conjunction with style sheets. Practical concerns due to browser non-compliance may force authors to find workarounds.
The `cite` *attribute* gives the source, and must be a fully qualified URI.
**Standardized** in HTML 4.0; still current.
Note: Lengthy inline quotations may be displayed as indented blocks (as `block-quote`) using style sheets. For example, with a suitable CSS rule associated with `q.lengthy`:
`<q class="lengthy">`An inline quotation of significant length (say 25 words, for example) goes here...`</q>`
Template:XMLElement

Represents the base component of a ruby annotation.
**Standardized** in HTML5.
Template:XMLElement

Provides fallback parenthesis for browsers lacking ruby annotation support.
**Standardized** in HTML5.
Template:XMLElement

Indicates pronunciation for a character in a ruby annotation.
**Standardized** in HTML5.
Template:XMLElement

Semantic annotations for a ruby annotation.
**Standardized** in HTML5.
Template:XMLElement

Represents a ruby annotation for showing the pronunciation of East Asian characters.
**Standardized** in HTML5.
Template:XMLElement

Places a script in the document. Also usable in the head and in block contexts.
Note: `<script>` 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 HTML 3.2; still current.
Template:XMLElement and Template:XMLElement

Mark subscript or superscript text. (Equivalent CSS: `{vertical-align: sub}` or `{vertical-align: super}`.)
Both were proposed in the HTML 3.0 Drafts; **Standardized** in HTML 3.2; still current.
Template:XMLElement

Code fragments to be copied by scripts.
**Standardized** in HTML5.
Template:XMLElement

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.
Template:XMLElement

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.
### Images and objects

Template:XMLElement

Embeds a Java applet in the page. Deprecated in favour of `<object>`, as it could only be used with Java applets, and had accessibility limitations.
**Standardized** in HTML 3.2; **deprecated** in HTML 4.0 Transitional; **invalid** in HTML 4.0 Strict. As of 2011, still widely used as the implementations of the replacing `<object>` are not consistent between different browsers.
Template:XMLElement

Specifies a focusable area in a `map`.
**Standardized** in HTML 3.2; still current.
Template:XMLElement

Adds playable HTML5 audio to the page. The audio URL is determined using the `src` attribute. Supported audio formats vary from browser to browser.
**Standardized** in HTML5.
Template:XMLElement

Adds a canvas whose contents can be edited with JavaScript. Frequently used for online games.
**Standardized** in HTML5.
Template:XMLElement
Inserts a non-standard object (like applet) or external content (typically non-HTML) into the document. Deprecated in HTML 4 in favor of the `object` tag, but then was added back into the HTML5 specification
Template:XMLElement

Used by visual user agents to insert an image in the document. The `src` attribute specifies the image URL. The required `alt` attribute provides alternative text in case the image cannot be displayed. (Though `alt` is intended as alternative text, Microsoft Internet Explorer 7 and below render it as a tooltip if no `title` is given. Safari and Google Chrome, on the other hand, do not display the alt attribute at all.) **img** was proposed by Marc Andreessen and implemented in the NSCA Mosaic web browser.
**IMG** existed in *HTML Internet Draft 1.2*, and was **standardized** in HTML 2.0; still current.
Template:XMLElement

Specifies a client-side image map.
**Standardized** in HTML 3.2; still current.
Template:XMLElement

Includes an object in the page of the type specified by the `type` 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 Flash, a Java applet, a sound file, etc.
**Standardized** in HTML 4.0; still current.
Template:XMLElement

Originally introduced with **applet**, this element is now used with, and should only occur as a child of **object**. It uses HTML attributes to set a parameter for the object, e.g. width, height, font, background colour, etc., depending on the type of object. An object can have multiple **param**s.
**Standardized** in HTML 3.2; still current.
Template:XMLElement

Specifies different sources for audio or video. Makes use of the `src` attribute in a way similar to the `video` and `audio` elements.
**Standardized** in HTML5.
Template:XMLElement

Provides text tracks, like subtitles and captions, for audio and video.
**Standardized** in HTML5.
Template:XMLElement

Adds a playable HTML5 video to the page. The video URL is determined using the `src` attribute. Supported video formats vary from browser to browser.
**Standardized** in HTML5.
### Forms

*Main article: 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, 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.)

Template:XMLElement

Creates a form. The **form** element specifies and operates the overall action of a form area, using the required **action** attribute.
**Standardized** in HTML 2.0; still current.
Template:XMLElement

A generic form button which can contain a range of other elements to create complex buttons.
**Standardized** in HTML 4.0; still current.
Template:XMLElement

A list of `option`s for use in form elements.
**Standardized** in HTML5.
Template:XMLElement

A container for adding structure to forms. For example, a series of related controls can be grouped within a **field-set**, which can then have a **legend** added in order to identify their function.
**Standardized** in HTML 4.0; still current.
Template:XMLElement

**input** elements allow a variety of standard form controls to be implemented.
**Standardized** in HTML 2.0; still current.
**Input Types:**
Template:XMLAttribute
A **checkbox**. Can be checked or unchecked.
Template:XMLAttribute
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.
Template:XMLAttribute
A general-purpose button. The element `<button>` is preferred if possible (i.e. if the client supports it) as it provides richer possibilities.
Template:XMLAttribute
A **submit** button.
Template:XMLAttribute
An **image button**. The image URL may be specified with the `src` attribute.
Template:XMLAttribute
A **reset button** for resetting the form to default values.
Template:XMLAttribute
A **one-line text input field**. The `size` attribute specifies the default width of the input in character-widths. `max-length` sets the maximum number of characters the user can enter (which may be greater than size).
Template:XMLAttribute
A variation of **text** which produces a search bar.
Template:XMLAttribute
A variation of **text**. The difference is that text typed in this field is *masked* — characters are displayed as an asterisk, a dot or another replacement. It should be noted, however, that the password is still submitted to the server as *clear text*, so an underlying secure transport layer like HTTPS is needed if confidentiality is a concern.
Template:XMLAttribute
A file select field (for uploading files to a server).
Template:XMLAttribute
A variation of **text** for telephone numbers.
Template:XMLAttribute
A variation of **text** for email addresses.
Template:XMLAttribute
A variation of **text** for URLs.
Template:XMLAttribute
A date selector.
Template:XMLAttribute
A time selector.
Template:XMLAttribute
A variation of **text** for numbers.
Template:XMLAttribute
Produces a slider for that returns a number, but the number is not visible to the user.
Template:XMLAttribute
A color picker.
Template:XMLAttribute
**hidden** 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.
Template:XMLElement

**`isindex`** could either appear in the document head or in the body, but only once in a document.
**Isindex** operated as a primitive HTML search form; but was 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-encoded keywords separated by plus signs.
**ISINDEX** existed in *HTML Tags*; **standardized** in HTML 2.0; **deprecated** in HTML 4.0 Transitional; **invalid** in HTML 4.0 Strict.
Template:XMLElement

A key pair generator.
**Standardized** in HTML5.
Template:XMLElement

Creates a label for a form input (e.g. radio button). Clicking on the label fires a click on the matching input.
**Standardized** in HTML 4.0; still current.
Template:XMLElement

A legend (caption) for a **fieldset**.
**Standardized** in HTML 4.0; still current.
Template:XMLElement

A meter which needs a **value** attribute. Can also have: min, low, high, max.
**Standardized** in HTML5.
Template:XMLElement

Creates an item in a `select` list.
**Standardized** in HTML 2.0; still current.
Template:XMLElement

Identifies a group of **option**s in a **select** list.
**Standardized** in HTML 4.0; still current.
Template:XMLElement

The value of a form element.
**Standardized** in HTML5.
Template:XMLElement

A bar for showing the progress of an action.
**Standardized** in HTML5.
Template:XMLElement

Creates a selection list, from which the user can select a single option. May be rendered as a dropdown list.
**Standardized** in HTML 2.0; still current.
Template:XMLElement

A multiple-line text area, the size of which is specified by `cols` (where a *col* is a one-character width of text) and `rows` 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 HTML 2.0; still current.
### Tables

The format of HTML Tables was proposed in the HTML 3.0 Drafts and the later RFC 1942 *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.)

Template:XMLElement
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 **summary** attribute is however informally required for accessibility purposes, though its usage is not simple.
Proposed in the HTML 3.0 Drafts; **Standardized** in HTML 3.2; still current.
Template:XMLElement
Contains a row of cells in a table.
Proposed in the HTML 3.0 Drafts; **Standardized** in HTML 3.2; still current.
Template:XMLElement
A table header cell; contents are conventionally displayed bold and centered. An aural user agent may use a louder voice for these items.
Proposed in the HTML 3.0 Drafts; **Standardized** in HTML 3.2; still current.
Template:XMLElement
A table data cell.
Proposed in the HTML 3.0 Drafts; **Standardized** in HTML 3.2; still current.
Template:XMLElement
Specifies a column group in a table.
Proposed in HTML Tables; **Standardized** in HTML 4.0; still current.
Template:XMLElement
Specifies a column in a table.
Proposed in HTML Tables; **Standardized** in HTML 4.0; still current.
Template:XMLElement
Specifies a caption for a table.
Proposed in the HTML 3.0 Drafts; **Standardized** in HTML 3.2; still current.
Template:XMLElement
Specifies the header part of a table. This section may be repeated by the user agent if the table is split across pages (in printing or other paged media).
Proposed in HTML Tables; **Standardized** in HTML 4.0; still current.
Template:XMLElement
Specifies a body of data for the table.
Proposed in HTML Tables; **Standardized** in HTML 4.0; still current.
Template:XMLElement
Specifies the footer part of a table. Like `<thead>`, this section may be repeated by the user agent if the table is split across pages (in printing or other paged media).
Proposed in HTML Tables; **Standardized** in HTML 4.0; still current.
## Frames

*Main article: 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, 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 `<iframe>` 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 `<head>` and a `<body>` *or* a `<head>` and a `<frameset>`, but not both a `<body>` and a `<frameset>`. However, `<iframe>` can be used in a normal document body.

Template:XMLElement
Contains the set of frame elements for a document. The layout of frames is given by comma separated lists in the `rows` and `cols` HTML attributes.
**Standardized** in HTML 4.0 Frameset, **obsolete** in HTML5.
Template:XMLElement
Defines a single frame, or region, within the `frameset`. A separate document is linked to a frame using the `src` attribute inside the `frame` element.
**Standardized** in HTML 4.0 Frameset, **obsolete** in HTML5.
Template:XMLElement
Contains normal HTML content for user agents that don't support frames.
**Standardized** in HTML 4.0 Transitional, **obsolete** in HTML5.
Template:XMLElement
An inline frame places another HTML document in a frame. Unlike an `object` element, an inline frame 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 iframes.
First introduced by Microsoft Internet Explorer in 1997, **standardized** in HTML 4.0 Transitional, **allowed** in HTML5.
### Longdesc

In HTML, **longdesc** is an attribute used within the image element, frame element, or iframe element. It is supposed to be a URL to a document that provides a **long description** for the image, frame, or iframe in question. Note that this attribute should contain a URL, and *not* as is commonly mistaken, the text of the description itself.

Longdesc was designed to be used by screen readers 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. Some developers object that
 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, and have used this argument to recommend dropping longdesc. The publishing industry has responded, advocating the retention of longdesc.

#### Example

```
<img src="Hello.jpg" longdesc="description.html">

```

Content of `description.html`:

```
</br>
<p>This is an image of a two-layered birthday cake.</p>
...

```

#### 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 `img` element whenever possible, as this can also aid sighted users.

##### Example

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

```

## Historic elements

*Main article: 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.

Template:XMLElement
This element displayed the text inside the tags in a monospace font and without interpreting the HTML. The HTML 2.0 specification recommended rendering the element at up to 132 characters per line.
**Deprecated** in HTML 3.2; **obsolete** in HTML5.
Template:XMLElement
**`plaintext`** 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 plain text.
`plaintext` existed in *HTML Tags*; **deprecated** in HTML 2.0; **invalid** in HTML 4.0.
Template:XMLElement
This element displayed the text inside the tags in a monospace font and without interpreting the HTML. The HTML 2.0 specification recommended rendering the element at 80 characters per line.
**Deprecated** in HTML 3.2; **obsolete** in HTML5.
Template:XMLElement
This element enabled NeXT web designing tool to generate automatic NAME labels for its anchors and was itself automatically generated.
`nextid` existed in *HTML Tags* (described as obsolete); **deprecated** in HTML 2.0; **invalid** in HTML 3.2 and later.
## Non-standard elements

*Main article: Comparison of layout engines (Non-standard HTML)*
This section lists some widely used obsolete elements, which means they are not used in valid code. They may not be supported in all user agents.

Template:XMLElement
Causes text to blink. Introduced in imitation of the ANSI escape codes. Can be done with CSS where supported: `{text-decoration: blink}` (This effect may have negative consequences for people with photosensitive epilepsy; its use on the public Internet should follow the appropriate guidelines.)
`blink` originated in Netscape Navigator and is mostly recognized by its descendants, including Firefox; **deprecated** or **invalid** in HTML 2.0 and later. Note that the replacement CSS tag, while standard, is not required to be supported.
Template:XMLElement
Creates scrolling text. Can be done with scripting instead. (This effect may have negative consequences for people with photosensitive epilepsy; 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.
`marquee` originated in Microsoft Internet Explorer; **deprecated** or **invalid** in HTML 4.01 and later.
Template:XMLElement
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: `{white-space: nowrap;}`
`nobr` is a proprietary element which is recognized by most browsers for compatibility reasons; **deprecated** or **invalid** in HTML 2.0 and later.
Template:XMLElement
Specifies alternative content, if the embed cannot be rendered. Replaced by the content of the `embed` or `object` element.
## Comments

`<!-- A Comment -->`

A 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 `<!--Xbegin<!--Y-->Xend-->` will yield the comment `Xbegin<!--Y` and the text `Xend-->` after it.

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.

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 (IE6 accounting for most of this high percentage). Even then only certain versions are affected by comment mishandling issues.

There are a few compatibility quirks involving comments:

* Placing comments – or indeed any characters except for white-space – before the doctype will cause Internet Explorer 6 to use quirks mode for the HTML page. None of its enclosed contents are processed.
* For compatibility with some pre-1995 browsers, the contents of `style` and `script` elements are still sometimes surrounded by comment delimiters.
* The BlueGriffon HTML editor, in versions 1.7.x makes comments that are not embedded in the syntax structure `<style> ... {comment tags} ...</style>` show up on screen. Other HTML editors may have this same defect.

## Notes

1. ↑ Document Object Model (DOM) Current Version. W3C (26 July 2016).
2. ↑ Definitions – Document tree. *Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification*. W3C (7 June 2011).
3. ↑ §3.2.1 Elements. *HTML 4.01 Specification*. W3C (24 December 1999).
4. ↑ §3.1 Introduction to SGML. *HTML 4.01 Specification*. W3C (24 December 1999).
5. ↑ HTML 4.01, §21, Document Type Definition. W3C (24 December 1999).
6. ↑ §1.3. XHTML and the HTML DOM. *Document Object Model (DOM) Level 2 HTML Specification*. W3C (9 January 2003).
7. ↑ 7.0 7.1 §7.5.3 Block-level and inline elements. *HTML 4.01 Specification*. W3C (24 December 1999).
8. ↑ Mark Newhouse (27 September 2002). CSS Design: Taming Lists. A List Apart.
9. ↑ XHTML 1.0 §4.2
10. ↑ XML 1.0 (The ability to produce additional elements is part of the *eXtensibility* in the acronym.)
11. ↑ XML 1.0 §5.1
12. ↑ XHTML 1.1 §A
13. ↑ HTML & CSS. W3C (2013).
14. ↑ Appendix D. Default style sheet for HTML 4. *Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification*. W3C (7 June 2011).
15. ↑ HTML 4.01 §14.1
16. ↑ Ferraiolo, J. Fujisawa, J, and Jackson, D (editors) (2003-01-14). Scalable Vector Graphics (SVG) 1.1 Specification, §2.3 *Options for using SVG in Web pages*. W3C. Retrieved on 2009-03-25.
17. ↑ HTML 4.01 §12.3
18. ↑ HTML 4.01 §14.3.2
19. ↑ HTML 4.01 §18
20. ↑ CSS §1.1
21. ↑ 4.4 Grouping content – HTML5. *HTML5: A vocabulary and associated APIs for HTML and XHTML – W3C Recommendation*. World Wide Web Consortium (28 October 2014). Retrieved on 16 August 2015.
22. ↑ Lists in HTML documents. *HTML 4.01 Specification – W3C Recommendation*. World Wide Web Consortium (24 December 1999). Retrieved on 2 May 2015.
23. ↑ W3C (5 April 2011). HTML5: A Vocabulary and Associated APIs for HTML and XHTML, W3C Working Draft..
24. ↑ *[citation needed]*
25. ↑ *HTML 4 for dummies*, 5th edition, 2005,
 By Ed Tittel, Mary C. Burmeister, p. 96.
26. ↑ hypertext reference
27. ↑ HTML5 attributes index
28. ↑ *[citation needed]*
29. ↑ *[citation needed]*
30. ↑ *[citation needed]*
31. ↑ *[citation needed]*
32. ↑ *[citation needed]*
33. ↑ 33.0 33.1 *[citation needed]*
34. ↑ https://developer.mozilla.org/en-US/docs/Web/HTML/Element/data
35. ↑ http://www.quackit.com/html/tags/html\_rb\_tag.cfm
36. ↑ https://developer.mozilla.org/en-US/docs/Web/HTML/Element/rp
37. ↑ https://developer.mozilla.org/en-US/docs/Web/HTML/Element/rt
38. ↑ https://developer.mozilla.org/en-US/docs/Web/HTML/Element/rtc
39. ↑ https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ruby
40. ↑ https://developer.mozilla.org/en-US/docs/Web/HTML/Element/time
41. ↑ Jennifer Kyrnin <embed>
42. ↑ W3Schools about <embed>
43. ↑ 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.
44. ↑ What's New in Internet Explorer 8 – Accessibility and ARIA. *MSDN*. Microsoft. Retrieved on 2009-07-22.
45. ↑ *[citation needed]*
46. ↑ *[citation needed]*
47. ↑ Are frames accessible?. “...frames do present additional usability challenges that are unique to users with disabilities, particularly those who use screen readers.”
48. ↑ Objects, Images, and Applets. W3C. Retrieved on 2008-12-20.
49. ↑ InState Longdesc. Retrieved on 2011-09-05.
50. ↑ Creating Accessible Images. WebAim. Retrieved on 2008-12-20.
51. ↑ *[citation needed]*
52. ↑ Bug 13461 - Commentary on Issue #30 (longdesc) from the Association of American Publishers. Retrieved on 2011-09-05.
53. ↑ https://developer.mozilla.org/en-US/docs/Web/HTML/Element/listing
54. ↑ https://developer.mozilla.org/en-US/docs/Web/HTML/Element/xmp
55. ↑ https://developer.mozilla.org/en-US/docs/Web/HTML/Element/nextid
56. ↑ 56.0 56.1 Web Content Accessibility Guidelines 1.0. World Wide Web Consortium (1999-05-05). Retrieved on 2010-07-20.

## Bibliography

### HTML standards

HTML 2.0:
Hypertext Markup Language - 2.0 (RFC 1866). IETF (November 1995). Retrieved on 2009-03-24.
HTML 3.2:
Dave Raggett (1997-01-14). HTML 3.2 Reference Specification. W3C. Retrieved on 2009-03-27.
HTML 4.01:
HTML 4.01 Specification. W3C (1999-12-24). Retrieved on 2009-03-24. *(HTML 4.01 is the updated form of HTML 4.0.)*
XHTML 1.0:
W3C (2000-01-26). XHTML 1.0: The Extensible HyperText Markup Language (Second Edition). W3C. Retrieved on 2009-03-24.
XHTML 1.1:
Altheim, M., and McCarron, S. (editors) (2001-05-31). XHTML 1.1 - Module-based XHTML. W3C. Retrieved on 2009-03-25.
### Other sources

*HTML Tags:*
Berners-Lee, T. (1992-11-03). HTML Tags. Retrieved on 2009-03-28. *(Part of the first published description of HTML.)*
*HTML Internet Draft 1.2:*
Hypertext Markup Language (HTML) (text) (June 1993). Retrieved on 2009-03-28.
*HTML 3.0 Drafts:*
Raggett, Dave (1995-03-24). HyperText Markup Language Specification Version 3.0 (draft). Retrieved on 2009-04-18. *(This is the final draft of HTML 3.0, which expired without being developed further.)*
*HTML Tables:*
Raggett, Dave (May 1996). HTML Tables (RFC 1942). IETF. Retrieved on 2009-03-22.
XML 1.0:
Bray, T, Paoli, J, Sperberg-McQueen, CM, Maler, E and Yergeau, F (editors) (2008-11-26). Extensible Markup Language (XML) 1.0 (Fifth Edition). W3C. Retrieved on 2009-03-20.
CSS:
Cascading Style Sheets, level 1 (revised 2008-04-11). W3C (2008-04-11). Retrieved on 2009-04-05.

## External links

Template:Wikibooks

* HTML 4.01 (Dec 24, 1999): elements and attributes
* Template:Vanchor (Oct 28, 2014): elements and attributes

Cite error: `<ref>` tags exist for a group named "note", but no corresponding `<references group="note"/>` tag was found