HTML element

Template:Html series

An HTML element is a type of HTML (HyperText Markup Language) document component, one of several types of HTML nodes (there are also text nodes, comment nodes and others).Template:Vague The first used version of HTML was written by Tim Berners-Lee in 1993 and there have since been many versions of HTML. The current de facto standard is governed by the industry group WHATWG and is known as the HTML Living Standard.

An HTML document is composed of a tree of simple HTML nodes, such as text nodes, and HTML elements, which add semantics and formatting to parts of a document (e.g., make text bold, organize it into paragraphs, lists and tables, or embed hyperlinks and images). Each element can have HTML attributes specified. Elements can also have content, including other elements and text.

Concepts

File:HTML element content categories.svg

HTML element content categories

Elements vs. tags

As is generally understood, the position of an element is indicated as spanning from a start tag and is terminated by an end tag.^[1] This is the case for many, but not all, elements within an HTML document. The distinction is explicitly emphasised in HTML 4.01 Specification:

Elements are not tags. Some people refer to elements as tags (e.g., "the P tag"). Remember that the element is one thing, and the tag (be it start or end tag) is another. For instance, the HEAD element is always present, even though both start and end HEAD tags may be missing in the markup.^[1]

Similarly the W3C Recommendation HTML 5.1 2nd Edition explicitly says:

Tags are used to delimit the start and end of elements in the markup. (...) The start and end tags of certain normal elements can be omitted, (...)
The contents of the element must be placed between just after the start tag (which might be implied, in certain cases) and just before the end tag (which again, might be implied, in certain cases).
— HTML 5.1 2nd Edition § 8.1.2. Elements § Tags

and:

Certain tags can be omitted.
NOTE:
Omitting an element's start tag (...) does not mean the element is not present; it is implied, but it is still there. For example, an HTML document always has a root <html> element, even if the string <html> doesn't appear anywhere in the markup.
— HTML 5.1 2nd Edition § 8.1.2.4. Optional tags

As HTML (before HTML5) is based on SGML,^[2] its parsing also depends on the Document Type Definition (DTD), specifically an HTML DTD (e.g. HTML 4.01^[3]^{[note 1]}). The DTD specifies which element types are possible (i.e. it defines the set of element types) and also 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), its explicit statement in any given document is not generally required. As a simple example, the <p> tag indicating the start of a paragraph element should be complemented by a </p> tag indicating its end. But since the DTD states that paragraph elements cannot be nested, an HTML document fragment <p>Para 1 <p>Para 2 <p>Para 3 is thus 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 this implication is based on the combination of the DTD and the individual document, it is not usually possible to infer elements from document tags alone but only by using an SGML—or HTML—aware parser with knowledge of the DTD. HTML5 creates a similar result by defining what tags can be omitted.^[4]

SGML vs. XML

SGML is complex, which has limited its widespread understanding and adoption. XML was developed as a simpler alternative. Although both can use the DTD 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.^{[note 2]}

HTML as used on the current web is likely to be either treated as XML, by being XHTML, or as HTML5; in either case the parsing of document tags into Document Object Model (DOM) elements is simplified compared to legacy HTML systems. Once the DOM of elements is obtained, behavior at higher levels of interface (example: screen rendering) is identical or nearly so.^{[note 3]}

`%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".^[6] This is used to define their nesting behavior: block-level elements cannot be placed into an inline context.^{[note 4]} 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,^[6] 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.^[7]

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.^[4] Some elements, the so-called void elements, do not have an end tag. A typical example is the <br> (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:

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

When using XHTML, it is required to open and close all elements, including void elements. This can be done by placing an end tag immediately after the start tag, but this is not legal in HTML 5 and will lead to two elements being created. An alternative way to specify that it is a void element, which is compatible with both XHTML and HTML 5, is to put a / 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>

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.^[8] 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.

Types of element

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

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

Template:Vanchor (also known as text or text-only elements) are constructed with:

a start tag (in the form <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.

An example is the <title> element, which must not contain other elements (including markup of text), only plain text.

Template:Vanchor (also sometimes called empty elements, single elements or stand-alone elements) only have a start tag (in the form <tag>), which contains any HTML attributes. They may not contain any children, such as text or other elements. For compatibility with XHTML, the HTML specification^[which?] allows an optional space and slash^{[citation needed]} (<tag /> is permissible). The slash is required in XHTML and other XML applications. Two common void elements are <br /> (for a hard line-break, such as in a poem or an address) and <hr /> (for a thematic break). Other such elements are often place-holders 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 <link />, 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. In the HTML syntax attributes do not have to be quoted if they are composed only of certain characters: letters, digits, the hyphen-minus and the period. When using the XML syntax (XHTML), on the other hand, all attributes must be quoted, and a spaced trailing slash is required before the last angle bracket:

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

Attributes

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 (attribute=value), or it can be quoted with single or double quotes (attribute='value' or attribute="value"). In XML, those quotes are required.

Boolean attributes, on the other hand, do not require a value to be specified. An example is the checked for checkboxes:

<input type=checkbox checked>

In the XML (and thus XHTML) syntax, though, a value is required, and the name should be repeated as the value:

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

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.^[9]

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).^[10]

In HTML 4.01 / XHTML 1.0, the status of elements is complicated by the existence of three types of 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.

HTML5 instead provides a listing of obsolete features to go along with the standardized normative content. They are broken down into "obsolete but conforming" for which implementation instructions exist and "non-conforming" ones that should be replaced.^[11]

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.)^[12]

A common source of confusion is the loose use of deprecated to refer to both deprecated and invalid status, and to elements that are expected to be formally deprecated in the 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).^[13] 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.^[14]

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.^[15]

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.)^[16] 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 style sheets and scripts.

In the document head, <style /> and <script /> may link to shared external documents, or <style>...</style> and <script>...</script> may contain embedded instructions. (The <link> element can also be used to link style sheets.)
<script /> or <script>...</script> can occur at any point in the document (head or body).
The style attribute is valid in most document body elements (e.g. <div>) 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 <noscript>...</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

Template:Glossary Template:Term Template:Defn Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Defn Template:Glossary end

Document head elements

Template:Glossary Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Glossary end

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 the content but which still forms part of the element. Padding 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.

Inline elements

Inline elements cannot be placed directly inside the <body> element; they must be wholly nested within block-level elements.^[17]

Anchor

Template:Glossary Template:Term Template:Defn Template:Defn Template:Glossary end

Phrase elements

Phrase elements are used for marking up phrases and adding structure or semantic meaning to text fragments. For example, the <em> and <strong> tags can be used for adding emphasis to text.

General

Template:Glossary Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Glossary end

Computer phrase elements

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

Template:Glossary Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Glossary end

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 <s>, <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:Term Template:Defn Template:Defn

Span

Template:Glossary Template:Term Template:Defn Template:Defn Template:Glossary end

Other inline elements

Template:Glossary Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Glossary end

Images and objects

Template:Glossary Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Glossary end

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:Glossary Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Glossary end

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:Glossary Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Glossary end

Frames

Main article: Frame (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,^[18] 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:Glossary Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Glossary end

`longdesc` attribute

In HTML, longdesc is an attribute used within the <img />, <frame />, or <iframe> elements. It is supposed to be a URL^{[note 5]} to a document that provides a long description for the image, frame, or iframe in question.^[19] This attribute should contain a URL, 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.^[20] Some developers object that^[21] 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 longdesc.^[22] The publishing industry has responded, advocating the retention of longdesc.^[23]

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

The following elements were part of the early HTML developed by Tim Berners-Lee from 1989 to 1991; they are mentioned in HTML Tags, but deprecated in HTML 2.0 and were never part of HTML standards.

Template:Glossary Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn Template:Glossary end

Non-standard elements

Template:Quote box Template:Quote box 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:Glossary Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Defn

Template:Term Template:Defn Template:Glossary end

Comments

Template:Glossary Template:Term Template:Defn Template:Glossary end

Notes

↑ 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.
↑ A macro-like feature of DTDs may still be used within XML.
↑ One minor difference is that XML, even after the DOM interface, is case-sensitive.^[5]
↑ However, see <object> for the inevitable exception.
↑ Strictly an IRI, not a URL; although URLs are a subset of IRIs.

References

↑ ^{Jump up to: 1.0} ^1.1 "§3 On SGML and HTML". HTML 4.01 Specification. W3C. 24 December 1999. §3.2.1 Elements. http://www.w3.org/TR/1999/REC-html401-19991224/intro/sgmltut.html#h-3.2.1.
↑ "§3 On SGML and HTML". HTML 4.01 Specification. W3C. 24 December 1999. §3.1 Introduction to SGML. http://www.w3.org/TR/1999/REC-html401-19991224/intro/sgmltut.html.
↑ "HTML 4.01, §21, Document Type Definition". W3C. 24 December 1999. http://www.w3.org/TR/1999/REC-html401-19991224/sgml/dtd.html.
↑ ^{Jump up to: 4.0} ^4.1 "HTML Standard § Optional tags". https://html.spec.whatwg.org/multipage/syntax.html#syntax-tag-omission.
↑ "§1. Document Object Model HTML". Document Object Model (DOM) Level 2 HTML Specification. W3C. 9 January 2003. §1.3. XHTML and the HTML DOM. http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109/html.html#ID-5353782642.
↑ ^{Jump up to: 6.0} ^6.1 "§7 The global structure of an HTML document". HTML 4.01 Specification. W3C. 24 December 1999. §7.5.3 Block-level and inline elements. http://www.w3.org/TR/1999/REC-html401-19991224/struct/global.html#h-7.5.3.
↑ Mark Newhouse (27 September 2002). "CSS Design: Taming Lists". A List Apart. http://alistapart.com/article/taminglists/.
↑ XHTML 1.0 §4.2
↑ XML 1.0 (The ability to produce additional elements is part of the eXtensibility in the acronym.)
↑ XML 1.0 §5.1
↑ WHATWGLS. § 15
↑ XHTML 1.1 §A
↑ "HTML & CSS". W3C. 2013. http://www.w3.org/standards/webdesign/htmlcss.
↑ "Appendix D. Default style sheet for HTML 4". Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification. W3C. 7 June 2011. http://www.w3.org/TR/CSS2/sample.html.
↑ HTML 4.01 §14.1
↑ "§2.3 Options for using SVG in Web pages". Scalable Vector Graphics (SVG) 1.1 Specification. W3C. 2003-01-14. http://www.w3.org/TR/2003/REC-SVG11-20030114/.
↑ HTML 4.01, W3C, http://www.w3.org/TR/html401/struct/global.html#h-7.5.1, retrieved 2012-03-26
↑ "Are frames accessible?". http://www.washington.edu/doit/are-frames-accessible. "...frames do present additional usability challenges that are unique to users with disabilities, particularly those who use screen readers."
↑ "Objects, Images, and Applets". W3C. http://www.w3.org/TR/REC-html40/struct/objects.html.
↑ "InState Longdesc". http://www.w3.org/html/wg/wiki/ChangeProposals/InstateLongdesc/Implementation.
↑ "Creating Accessible Images". WebAim. http://www.webaim.org/techniques/images/longdesc.php#longdesc.
↑ Longdesc usage - WHATWG Wiki, Wiki.whatwg.org, http://wiki.whatwg.org/wiki/Longdesc_usage, retrieved 2012-03-26
↑ "Bug 13461 - Commentary on Issue #30 (longdesc) from the Association of American Publishers". http://www.w3.org/Bugs/Public/show_bug.cgi?id=13461.

Bibliography

HTML standards

HTML 2.0Template:Colon: Template:Cite IETF
HTML 3.2Template:Colon: Raggett, Dave (1997-01-14). "HTML 3.2 Reference Specification". W3C. http://www.w3.org/TR/REC-html32-19970114.
HTML 4.01Template:Colon: Raggett, Dave; Le Hors, Arnaud; Jacobs, Ian (1999-12-24). "HTML 4.01 Specification". W3C. https://www.w3.org/TR/html4/. (HTML 4.01 superseded 4.0 (1998), which was never widely implemented, and all earlier versions. Superseded in turn on 2018-03-27 by HTML 5.2).
XHTML 1.0Template:Colon: "XHTML 1.0: The Extensible HyperText Markup Language (Second Edition)". Revised version. W3C. 2002-08-01. https://www.w3.org/TR/xhtml1/.
XHTML 1.1Template:Colon: Altheim, Murray; McCarron, Shane; Ishikawa, Masayasu, eds (2010-11-23). "XHTML 1.1 - Module-based XHTML - Second Edition". Revised version. W3C. https://www.w3.org/TR/xhtml11/. (Superseded on 2018-03-27 by HTML 5.2.); Austin, Daniel; Peruvemba, Subramanian; McCarron, Shane et al., eds (2010-07-29). "XHTML Modularization 1.1 - Second Edition". Revised version. W3C. https://www.w3.org/TR/xhtml-modularization/. (A more detailed version of the above. Also superseded on 2018-03-27 by HTML 5.2.)
W3C HTML 5.2Template:Colon: Faulkner, Steve; Eicholz, Arron; Leithead, Travis et al., eds (2017-12-14). "HTML 5.2 W3C Recommendation". Revised version. W3C. https://www.w3.org/TR/html52/. Supersedes all previous versions of HTML and XHTML, including HTML 5.1.
WHATWG HTML5 Living StandardTemplate:Colon: Hickson, Ian, ed (2018-07-25). "HTML Living Standard". One-page Version. WHATWG. https://html.spec.whatwg.org/. Also available as a Multipage Version, and Developer's Edition (also multi-page, with a search function and other gadgets, and minus details only of interest to browser vendors).

Other sources

HTML TagsTemplate:Colon: Berners-Lee, Tim (1992-11-03). "HTML Tags". http://www.w3.org/History/19921103-hypertext/hypertext/WWW/MarkUp/Tags.html. (Part of the first published description of HTML.)
HTML Internet Draft 1.2Template:Colon: Berners-Lee, Tim; Connolly, Dan (June 1993). "Hypertext Markup Language (HTML)". http://www.w3.org/MarkUp/draft-ietf-iiir-html-01.txt.
HTML 3.0 DraftsTemplate:Colon: Raggett, Dave (1995-03-24). "HyperText Markup Language Specification Version 3.0 (draft)". http://www.w3.org/MarkUp/html3/CoverPage.html. (This is the final draft of HTML 3.0, which expired without being developed further.)
HTML TablesTemplate:Colon: Template:Cite IETF
XML 1.0Template:Colon: Bray, Tim; Paoli, Jean; Sperberg-McQueen, C. Michael et al., eds (2008-11-26). "Extensible Markup Language (XML) 1.0 (Fifth Edition)". W3C. http://www.w3.org/TR/xml/.
CSS 1Template:Colon: Lie, Håkon Wium; Bos, Bert (2008-04-11). "Cascading Style Sheets, Level 1". Revised version. W3C. http://www.w3.org/TR/CSS1/.
CSS 2.1Template:Colon: Bos, Bert; Çelik, Tantek; Hickson, Ian; Lie, Håkon Wium (12 April 2016). "Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification". Revised version. W3C. https://www.w3.org/TR/CSS2/.
CSS 3 and 4Template:Colon: Atkins, Tab Jr.; Eternad, Elika J.; Rivoal, Florian (31 January 2017). "CSS Snapshot 2017". W3C. §2. Cascading Style Sheets (CSS) – The Official Definition. https://www.w3.org/TR/CSS/#css. (List of active specifications that have superseded CSS 2.1, as of the publication date.); "CSS Current Status". W3C. 2018. https://www.w3.org/standards/techs/css#w3c_all. (CSS levels 3 and 4 are developed as independent modules, indexed at that page.)

External links

Template:Wikibooks

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

[4] 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.

[6] A macro-like feature of DTDs may still be used within XML.

[8] One minor difference is that XML, even after the DOM interface, is case-sensitive.^[5]

[10] However, see <object> for the inevitable exception.

[23] Strictly an IRI, not a URL; although URLs are a subset of IRIs.

[HTML401_Elements-1] {Jump up to: 1.0} ^1.1 "§3 On SGML and HTML". HTML 4.01 Specification. W3C. 24 December 1999. §3.2.1 Elements. http://www.w3.org/TR/1999/REC-html401-19991224/intro/sgmltut.html#h-3.2.1.

[2] "§3 On SGML and HTML". HTML 4.01 Specification. W3C. 24 December 1999. §3.1 Introduction to SGML. http://www.w3.org/TR/1999/REC-html401-19991224/intro/sgmltut.html.

[W3C,_HTML_401_DTD-3] "HTML 4.01, §21, Document Type Definition". W3C. 24 December 1999. http://www.w3.org/TR/1999/REC-html401-19991224/sgml/dtd.html.

[whatwg-syntax-tag-omission-5] {Jump up to: 4.0} ^4.1 "HTML Standard § Optional tags". https://html.spec.whatwg.org/multipage/syntax.html#syntax-tag-omission.

[7] "§1. Document Object Model HTML". Document Object Model (DOM) Level 2 HTML Specification. W3C. 9 January 2003. §1.3. XHTML and the HTML DOM. http://www.w3.org/TR/2003/REC-DOM-Level-2-HTML-20030109/html.html#ID-5353782642.

[W3C,_HTML_4.01,_block_and_inline-9] {Jump up to: 6.0} ^6.1 "§7 The global structure of an HTML document". HTML 4.01 Specification. W3C. 24 December 1999. §7.5.3 Block-level and inline elements. http://www.w3.org/TR/1999/REC-html401-19991224/struct/global.html#h-7.5.3.

[11] Mark Newhouse (27 September 2002). "CSS Design: Taming Lists". A List Apart. http://alistapart.com/article/taminglists/.

[XHTML10-42-12] XHTML 1.0 §4.2

[13] XML 1.0 (The ability to produce additional elements is part of the eXtensibility in the acronym.)

[XML10-51-14] XML 1.0 §5.1

[15] WHATWGLS. § 15

[XHTML11-16] XHTML 1.1 §A

[17] "HTML & CSS". W3C. 2013. http://www.w3.org/standards/webdesign/htmlcss.

[18] "Appendix D. Default style sheet for HTML 4". Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification. W3C. 7 June 2011. http://www.w3.org/TR/CSS2/sample.html.

[HTML401-141-19] HTML 4.01 §14.1

[SVG11-23-20] "§2.3 Options for using SVG in Web pages". Scalable Vector Graphics (SVG) 1.1 Specification. W3C. 2003-01-14. http://www.w3.org/TR/2003/REC-SVG11-20030114/.

[21] HTML 4.01, W3C, http://www.w3.org/TR/html401/struct/global.html#h-7.5.1, retrieved 2012-03-26

[22] "Are frames accessible?". http://www.washington.edu/doit/are-frames-accessible. "...frames do present additional usability challenges that are unique to users with disabilities, particularly those who use screen readers."

[24] "Objects, Images, and Applets". W3C. http://www.w3.org/TR/REC-html40/struct/objects.html.

[25] "InState Longdesc". http://www.w3.org/html/wg/wiki/ChangeProposals/InstateLongdesc/Implementation.

[26] "Creating Accessible Images". WebAim. http://www.webaim.org/techniques/images/longdesc.php#longdesc.

[27] Longdesc usage - WHATWG Wiki, Wiki.whatwg.org, http://wiki.whatwg.org/wiki/Longdesc_usage, retrieved 2012-03-26

[28] "Bug 13461 - Commentary on Issue #30 (longdesc) from the Association of American Publishers". http://www.w3.org/Bugs/Public/show_bug.cgi?id=13461.

[1]

[2]

[3]

[note 1]

[4]

[note 2]

[note 3]

[6]

[note 4]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[15]

[16]

[17]

[18]

[note 5]

[19]

[20]

[21]

[22]

[23]

[5]

Concepts

Elements vs. tags

SGML vs. XML

%block; vs. box

Overview

Syntax

Types of element

Attributes

Element standards

Element status

Content vs. presentation and behavior

Document structure elements

Document head elements

Document body elements

Block elements

Basic text

Lists

Other block elements

Inline elements

Anchor

Phrase elements

General

Computer phrase elements

Presentation

Span

Other inline elements

Images and objects

Forms

Tables

Frames

longdesc attribute

Example

Linking to the long description in the text

Example

Historic elements

Non-standard elements

Comments

See also

Notes

References

Bibliography

HTML standards

Other sources

External links

`%block;` vs. box

`longdesc` attribute