This specification defines an API for persistent data storage of key-value pair data in Web clients.

Defines the flat cartesian surface that is the context for the canvas element (for drawing).

RDFa Core is a specification for attributes to express structured data in any markup language. The embedded data already available in the markup language (e.g., XHTML) is reused by the RDFa markup, so that publishers don't need to repeat significant data in the document content.

RDFa Core 1.1 defines attributes and syntax for embedding semantic markup in Host Languages. This document defines one such Host Language. This language is a superset of XHTML 1.1, integrating the attributes as defined in RDFa Core 1.1.

RDFa Lite is a small subset of RDFa consisting of a few attributes that may be applied to most simple to moderate structured data markup tasks. While it is not a complete solution for advanced markup tasks, it does provide a good entry point for beginners.

This specification defines rules and guidelines for adapting the RDFa Core 1.1 and RDFa Lite 1.1 specifications for use in HTML5 and XHTML5. The rules defined in this specification not only apply to HTML5 documents in non-XML and XML mode, but also to HTML4 and XHTML documents interpreted through the HTML5 parsing rules.

This specification defines a longdesc attribute to link extended descriptions with images in HTML5-based content.

This specification defines the 5th major revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, new features are introduced to help Web application authors, new elements are introduced based on research into prevailing authoring practices, and special attention has been given to defining clear conformance criteria for user agents in an effort to improve interoperability.

Describes the syntax and interpretation of the CSS fragment that can be used in "style" attributes inside mark-up, e.g., in HTML, SVG and MathML.

This document defines data categories and their implementation as a set of elements and attributes called the Internationalization Tag Set (ITS) 2.0. ITS 2.0 is the successor of ITS 1.0; it is designed to foster the creation of multilingual Web content, focusing on HTML5, XML based formats in general, and to leverage localization workflows based on the XML Localization Interchange File Format (XLIFF). In addition to HTML5 and XML, algorithms to convert ITS attributes to RDFa and NIF are provided.

The XHTML Basic document type includes the minimal set of modules required to be an XHTML host language document type, and in addition it includes images, forms, basic tables, and object support. It is designed for Web clients that do not support the full set of XHTML features; for example, Web clients such as mobile phones, PDAs, pagers, and settop boxes. The document type is rich enough for content authoring.

XHTML Basic is designed as a common base that may be extended. The goal of XHTML Basic is to serve as a common language supported by various kinds of user agents.

This revision, 1.1, supercedes version 1.0 as defined in http://www.w3.org/TR/2000/REC-xhtml-basic-20001219. In this revision, several new features have been incorporated into the language in order to better serve the small-device community that is this language's major user:

1. XHTML Forms (defined in [XHTMLMOD])
2. Intrinsic Events (defined in [XHTMLMOD])
3. The value attribute for the li element (defined in [XHTMLMOD])
4. The target attribute (defined in [XHTMLMOD])
5. The style element (defined in [XHTMLMOD])
6. The style attribute (defined in [XHTMLMOD])
7. XHTML Presentation module (defined in [XHTMLMOD])
8. The inputmode attribute (defined in Section 5 of this document)

The document type definition is implemented using XHTML modules as defined in " XHTML Modularization" [XHTMLMOD].

XHTML 1.1 redefines XHTML 1.0 based on a modular design, with support for Ruby Annotation. This new edition corrects various bugs and introduces XML Schema modules.

XHTML-Print is member of the family of XHTML languages defined by the Modularization of XHTML [XHTMLMOD]. It is designed to be appropriate for printing from mobile devices to low-cost printers that might not have a full-page buffer and that generally print from top-to-bottom and left-to-right with the paper in a portrait orientation. XHTML-Print is also targeted at printing in environments where it is not feasible or desirable to install a printer-specific driver and where some variability in the formatting of the output is acceptable.

This specification defines the Second Edition of XHTML 1.0, a reformulation of HTML 4 as an XML 1.0 application, and three DTDs corresponding to the ones defined by HTML 4. The semantics of the elements and their attributes are defined in the W3C Recommendation for HTML 4. These semantics provide the foundation for future extensibility of XHTML. Compatibility with existing HTML user agents is possible by following a small set of guidelines.

"Ruby" are short runs of text alongside the base text, typically used in East Asian documents to indicate pronunciation or to provide a short annotation. This document proposes a set of CSS properties associated with the 'Ruby' elements. They can be used in combination with the Ruby elements of HTML.

This specification defines the HyperText Markup Language (HTML), the publishing language of the World Wide Web. This specification defines HTML 4.01, which is a subversion of HTML 4. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML (HTML 3.2 [HTML32] and HTML 2.0 [RFC1866]), HTML 4 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide.

HTML 4 is an SGML application conforming to International Standard ISO 8879 -- Standard Generalized Markup Language [ISO8879].

The document defines the Initialization Data formats for use with the Encrypted Media Extensions API.

This document defines the "keyids" Initialization Data format for use with the Encrypted Media Extensions API. It defines a stream format-independent format for specifying a list of key ID(s).

This document defines the "webm" Initialization Data format for use with the Encrypted Media Extensions API.

This document defines the "cenc" Initialization Data format for use with the Encrypted Media Extensions API. It is commonly used with the ISO Common Encryption ('cenc') Protection Scheme for ISO Base Media File Format Stream Format.

This document defines the stream formats for use with the Encrypted Media Extensions API.

This document defines the stream format for using ISO Base Media File Format content that uses the ISO Common Encryption ('cenc') protection scheme with the Encrypted Media Extensions API.

This document defines the stream format for using WebM content with the Encrypted Media Extensions API.

This document defines the application/xml+ttml media type and provides a registry of identified TTML processor profiles.

Aggregates requirements of a user with disabilities with respect to audio and video on the Web, providing background on user needs, alternative content technologies, and their application on the Web.

This is an extension to HTML which explicitly identifies a transcript linked to a media object such as audio or video.

This document contains author conformance requirements for use of the alt attribute in HTML5 and best practice guidance for authors of HTML documents on providing text alternatives for images.

HTML and RDFa (Resource Description Framework in Attributes) provides a set of markup attributes to augment visual information on the Web with machine-readable hints. In this Primer, we show how to express data using RDFa in HTML, and in particular how to mark up existing human-readable Web page content to express machine-readable data.

HTML microdata [MICRODATA] is an extension to HTML used to embed machine-readable data into HTML documents. Whereas the microdata specification describes a means of markup, the output format is JSON. This specification describes processing rules that may be used to extract RDF [RDF-CONCEPTS] from an HTML document containing microdata.

HTML 5 defines the fifth major revision of the core language of the World Wide Web, HTML. "HTML 5 differences from HTML 4" describes the differences between HTML 4 and HTML 5 and provides some of the rationale for the changes. This document may not provide accurate information as the HTML 5 specification is still actively in development. When in doubt, always check the HTML 5 specification itself. [HTML5]

The ruby markup model currently described in the HTML specification is limited in its support for a number of features, notably jukugo and double-sided ruby, as well as inline ruby. This specification addresses these issues by introducing new elements and changing the ruby processing model. Specific care has been taken to ensure that authoring remains as simple as possible.

This document captures the use cases and requirements for standardizing a solution for responsive images.

This specification defines a mechanism for machine-readable data to be embedded in HTML documents in an easy-to-write manner, with an unambiguous parsing model. It is compatible with numerous other data formats including RDF and JSON.

This document looks at a number of use cases involving ruby, and examines the pros and cons of a number of alternative approaches for meeting those use cases using the current HTML5 model, the XHTML Ruby Annotation model, and two other models. The aim is to clarify which use cases are supported by the existing markup models (HTML5 or XHTML), and where they are not, provide suggestions about how the markup model could be adapted to support those use cases. Implementers and standards developers can then take this background information and the suggestions in this document to specify and implement a comprehensive markup model for ruby in HTML5.

This document describes the HTML markup language and provides details to help producers of HTML content create documents that conform to the language. It is not the normative specification but intended for authors.

This document is a strict subset of the HTML5 specification that omits user-agent (UA) implementation details. It is targeted toward Web authors and others who are not UA implementors and who want a view of the HTML specification that focuses more precisely on details relevant to using the HTML language to create Web documents and Web applications.

This specification is an extension to the HTML5 specification. It defines an element to be used for the identification of the main content area of a document. The main element formalises the common practice of identification of the main content section of a document using the id values such as 'content' and 'main'. It also defines an HTML element that embodies the semantics and function of the WAI-ARIA landmark role=main.

This guide aims to help publishers and consumers of HTML data use it well. With several syntaxes and vocabularies to choose from, it provides guidance about how to decide which meets the publisher's or consumer's needs. It discusses when it is necessary to mix syntaxes and vocabularies and how to publish and consume data that uses multiple formats. It describes how to create vocabularies that can be used in multiple syntaxes and general best practices about the publication and consumption of HTML data.

The HLink module defined in this specification provides XHTML Family Members with the ability to specify which attributes of elements represent Hyperlinks, and how those hyperlinks should be traversed, and extends XLink use to a wider class of languages than those restricted to the syntactic style allowed by XLink.

XFrames is an XML application for composing documents together, replacing HTML Frames. By being a separate application from XHTML, it allows content negotiation to determine if the user agent accepts frames; by encoding the 'population' of frames in the URI, it allows framesets to be bookmarked.

The XHTML Role Attribute defined in this specification allows the author to annotate XML Languages with machine-extractable semantic information about the purpose of an element. Use cases include accessibility, device adaptation, server-side processing, and complex data description. This attribute can be integrated into any markup language based upon XHTML Modularization [XHTMLMOD].

The XHTML Access module defines an element that, when used in conjunction with other XHTML modules in XHTML Family Markup Languages, enables a more robust accessibility model than is presently possible.

XHTML Media Types recapitulates which media types can and should be used with the different flavors of XHTML, and under what conditions.

Offline Web Applications highlights the features in HTML 5 that address the challenge of building Web applications that work while offline.

This document describes XML Schemas for XHTML 1.0.

The XHTML+SMIL profile defines a set of XHTML abstract modules that support a subset of the SMIL 2.0 specification.

This specification defines the 5th major version, first minor revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, new features continue to be introduced to help Web application authors, new elements continue to be introduced based on research into prevailing authoring practices, and special attention continues to be given to defining clear conformance criteria for user agents in an effort to improve interoperability.

This specification extends the HTMLMediaElement interface to provide APIs for controlling playback of protected content

This specification extends the HTMLMediaElement interface to allow JavaScript to generate media streams for playback.

While encodings have been defined to some extent, implementations have not always implemented them in the same way, have not always used the same labels, and often differ in dealing with undefined and former proprietary areas of encodings. This specification attempts to fill those gaps so that new implementations do not have to reverse engineer encoding implementations of the market leaders and existing implementations can converge.

This specification defines HTML form enhancements that provide access to the audio, image and video capture capabilities of the device.

This specification defines the 5th major version, second minor revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, new features continue to be introduced to help Web application authors, new elements continue to be introduced based on research into prevailing authoring practices, and special attention continues to be given to defining clear conformance criteria for user agents in an effort to improve interoperability.

The Timed Text Markup Language is a content type that represents timed text media for the purpose of interchange among authoring systems and for distribution for example as a format to reference from an HTML element. Timed text is textual information that is intrinsically or extrinsically associated with timing information.

This specification defines WebVTT, the Web Video Text Tracks format. Its main use is for marking up external text track resources in connection with the HTML element. WebVTT files provide captions or subtitles for video content, and also text video descriptions [MAUR], chapters for content navigation, and more generally any form of metadata that is time-aligned with audio or video content.

Defines how user agents map HTML 5.1 elements and attributes to platform accessibility APIs. This promotes interoperable exposure of roles, states, properties, and events and helps to ensure that this information appears in a manner consistent with author intent.

This document is a practical guide for developers on how to add accessibility information to HTML elements using ARIA, a markup mechanism for making Web content and Web applications more accessible to people with disabilities.

SVG Integration defines how SVG documents must be processed when used in various contexts, such as CSS background images, HTML ‘iframe’ elements, and so on. These requirements include which features are restricted or disabled, such as scripting and animation.

An overview of usage scenarios and implementations demonstrating applications of the Internationalization Tag Set (ITS) 2.0. The usage scenarios are ranging from simple machine translation or human translation quality check to training for machine translation systems or automatic text analyis.

XForms for HTML provides a set of attributes and script methods that can be used by the tags or elements of an HTML or XHTML web page to simplify the integration of data-intensive interactive processing capabilities from XForms.

HTML 5 defines the fifth major revision of the core language of the World Wide Web, HTML. This document describes the set of guiding principles used by the HTML Working Group for the development of HTML5. The principles offer guidance for the design of HTML in the areas of compatibility, utility and interoperability.

A document that uses polyglot markup is document that is a stream of bytes that parses into identical document trees (with the exception of the xmlns attribute on the root element) when processed as HTML and when processed as XML. Polyglot markup that meets a well defined set of constraints is interpreted as compatible, regardless of whether they are processed as HTML or as XHTML, per the HTML5 specification.

This document maps HTML elements and attributes to accessibility API roles, states and properties on a variety of platforms.

This specification defines the 2D Context, Level 2 for the HTML canvas element. The 2D Context provides objects, methods, and properties to draw and manipulate graphics on a canvas drawing surface.

A new form encoding algorithm that enables the transmission of form data as JSON.

This is an addendum to the specification of HTML5 forms extending the abilities of configuring HTTP requests through HTML markup.

This document adds an additional public identifier that should be recognised by XHTML user agents and cause the HTML character entity definitions to be loaded.

When authors adapt their sites for high-resolution displays, they often need to be able to use different assets representing the same image. We address this need for adaptive, bitmapped content images by adding a srcset attribute to the img element.

The picture element is an image container whose source content is determined by one or more CSS media queries.

RDFa [RDFA-CORE] enables authors to publish structured information that is both human- and machine-readable. Concepts that have traditionally been difficult for machines to detect, like people, places, events, music, movies, and recipes, are now easily marked up in Web documents. While publishing this data is vital to the growth of Linked Data, using the information to improve the collective utility of the Web for humankind is the true goal. To accomplish this goal, it must be simple for Web developers to extract and utilize structured information from a Web document. This document details such a mechanism; an RDFa Application Programming Interface (RDFa API) that allows simple extraction and usage of structured information from a Web document.

HTML 5 Publication Notes is a companion document to the HTML 5 specification that gives more context about a given version of the drafts.

An XHTML+MathML+SVG profile is a profile that combines XHTML 1.1 [XHTML11], MathML 2.0 [MathML2] and SVG 1.1 [SVG11] together. This profile enables mixing XHTML, MathML and SVG in the same document using XML namespaces [XMLNS] mechanism, while allowing validation of such a mixed-namespace document. An XHTML 1.1 + MathML 2.0 + SVG 1.1 DTD driver is provided. An XHTML version of this document is conforming to this DTD.

The HTML Working Group is chartered with the development of an extensible, sub-settable version of HTML that is compatible with XML. It is also chartered with the development of some extensions to HTML - notably in the area of forms. This group's current activities commenced in August 1998, and the group was rechartered in June 2000. The purpose of this document is to describe the activities of the HTML Working Group, define general milestones for each sub-project, and outline the inter-dependencies among the various deliverables.