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

This document defines APIs for a database of records holding simple values and hierarchical objects. Each record consists of a key and some value. Moreover, the database maintains indexes over records it stores. An application developer directly uses an API to locate records either by their key or by using an index. A query language can be layered on this API. An indexed database can be implemented using a persistent B-tree data structure.

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

This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Key storage is provided for both temporary and permanent keys. Access to keying material is contingent on the same origin policy. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications.

This document defines an interface definition language, Web IDL, that can be used to describe interfaces that are intended to be implemented in web browsers.

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

This specification defines an API that provides Web pages scripted access to geographical location information associated with the hosting device.

API that provides scripted access to raw mouse movement data while locking the target of mouse events to a single element and removing the cursor from view.

An API to control the device's vibrator.

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

This document defines an API for displaying simple notifications to the user.

This specification defines two mechanisms for communicating between browsing contexts in HTML document.

Defines events and interfaces for handling hardware agnostic pointer input from devices such as mouse, pen or touchscreen.

This specification defines an API for opening an HTTP connection for receiving push notifications from a server in the form of DOM events.

This document defines APIs for a database of records holding simple values and hierarchical objects.

This specification defines a client-side API to access metadata information related to media resources on the Web.

This document describes event types that can be used for monitoring the progress of an operation. It is primarily intended for contexts such as data transfer operations specified by XMLHTTPRequest [XHR], or Media Access Events [MAE].

An Application Programming Interface and a set of algorithms for programmatically transforming JSON-LD documents in order to make them easier to work with in programming environments like JavaScript, Python, and Ruby.

This specification defines an interface for web applications to access timing information related to navigation and elements. It is used by other specifications, like User Timing.

This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.

This specification defines an application programming interface (API) for widgets that provides, amongst other things, functionality for accessing a widget’s metadata and persistently storing data.

This specification defines a means for site developers to programmatically determine the current visibility state of the page in order to develop power and CPU efficient web applications.

This specification defines low-level events representing points of contact with a touch-sensitive surface.

Selectors, which are widely used in CSS, are patterns that match against elements in a tree structure [SELECT][CSS21]. The Selectors API specification defines methods for retrieving Element nodes from the DOM by matching against a group of selectors. It is often desirable to perform DOM operations on a specific set of elements in a document. These methods simplify the process of acquiring specific elements, especially compared with the more verbose techniques defined and used in the past.

This specification defines an interface that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.

This document provides an interface for web applications to access timing information related to navigation and elements.

This specification defines the ElementTraversal interface, which allows script navigation of the elements of a DOM tree, excluding all other nodes in the DOM, such as text nodes. It also provides an attribute to expose the number of child elements of an element. It is intended to provide a more convenient alternative to existing DOM navigation interfaces, with a low implementation footprint.

The Motion Sensors Explainer Note is an introduction to low-level and high-level motion sensors, their relationship, inner workings and common use-cases.

This specification defines a Media Source Extensions byte stream format specification based on the WebM container format.

This specification defines the byte stream formats for use with the Media Source Extensions specification.

This specification defines a Media Source Extensions byte stream format specification based on MPEG-2 Transport Streams.

This specification defines a Media Source Extensions byte stream format specification based on MPEG audio streams.

This specification defines a Media Source Extensions byte stream format specification based on the ISO Base Media File Format.

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.

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.

Navigation Error Logging defines an API to store and retrieve error data related to the previous navigations of a document.

Frame Timing helps web developers measure the performance of their applications by giving them access to frame performance data to facilitate smoothness measurements.

This document illustrates the use cases a mechanism to control the power-saving state of a device would enable on the Web platform.

This document reviews of the usage of type of network connectivity in existing mobile applications to determine what use cases a network information API would need to enable.

This document introduces a series of scenarios and a list of requirements guiding the work of the W3C Audio Working Group in its development of a web API for processing and synthesis of audio on the web.

This document describes privacy best practices for web applications, including those that might use device APIs.

These are the requirements intended to be met in the development of client-side APIs that enable the creation of Web Applications and Web Widgets that interact with devices services such as Calendar, Contacts, Camera, etc.

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

Page Visibility defines a means to programmatically determine the visibility state of a document. This can aid in the development of power and CPU efficient web applications.

The requestIdleCallback method is a more appropriate way for scheduling background tasks during times when the browser would otherwise be idle.

This specification describes a web API to allow merchants (i.e. web sites selling physical or digital goods) to easily accept payments from different payment methods with minimal integration. User agents (e.g. browsers) will facilitate the payment flow between merchant and user.

This specification defines a JavaScript interface that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.

This document specifies an API that allows web applications to request a wake lock. A wake lock prevents some aspect of the device from entering a power-saving state (e.g., preventing the system from turning off the screen).

This document defines a set of APIs that allow local media, including audio and video, to be requested from a platform, media to be sent over the network to another browser or device implementing the appropriate set of real-time protocols, and media received from another browser or device to be processed and displayed locally.

This specification defines an API extending the HTMLMediaElement that enables controlling remote playback of media from a web page onto remote playback devices such as connected TVs, projectors or audio-only speakers, attached using wired (HDMI, DVI, or similar) and wireless technologies (Miracast, Chromecast, DLNA, AirPlay, or similar).

This document defines a set of APIs that allow local media, including audio and video, to be requested from a platform, media to be sent over the network to another browser or device implementing the appropriate set of real-time protocols, and media received from another browser or device to be processed and displayed locally.

This document defines a set of JavaScript APIs that let a Web application manage how audio is rendered on the user audio output devices.

An API to enable web content to access external presentation-type displays and use them for presenting web content.

This specification defines the values for the KeyboardEvent.code attribute which is defined in DOM 3 Events.

This specification defines the values for the KeyboardEvent.key attribute which is defined in DOM 3 Events.

This specification defines an interface for web applications to access timing information related to HTML elements.

This specification defines the WebDriver API, a platform-and language-neutral interface that allows programs or scripts to introspect into, and control the behaviour of, a web browser.

This specification extends the High Resolution Time specification by providing methods to store and retrieve high resolution performance metric data.

This specification defines a new DOM event type that provides information about the battery status of the hosting device and associated auxiliary devices.

This specification defines an API that enables Web pages to use the Web Sockets protocol for two-way communication with a remote host.

This document defines a set of Javascript APIs that allow access to the statistical information about a PeerConnection.

This specification defines an interface to help web developers measure the performance of their applications by giving them access to high precision timestamps.

Defines a low-level interface that represents gamepad devices.

This document provides an explicit JavaScript API for interacting with WebAssembly.

This specification defines an API that provides scripted access to raw mouse movement data while locking the target of mouse events to a single element and removing the cursor from view. This is an essential input mode for certain classes of applications, especially first person perspective 3D applications and 3D modeling software.

The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware agnostic pointer input from devices including a mouse, pen, touchscreen, etc. For compatibility with existing mouse based content, this specification also describes a mapping to fire Mouse Events for other pointer device types.

The Payment Request API provides a standard way to initiate payment requests from Web pages and applications. User agents implementing that API prompt the user to select a way to handle the payment request, after which the user agent returns a payment response to the originating site. This specification defines capabilities that enable Web applications to handle payment requests.

Server Timing, part of the performance timeline metrics, provides API access to request-response cycle performance metrics communicated from the server to the user agent.

An API that provides Web applications with scripted access to server-sent application data.

This document provides an interface for web applications to access timing information related to navigation and elements.

Defines APIs to read screen orientation state and to lock the screen orientation to a specific state.

This specification enables applications to take advantage of persistent background processing, including hooks to enable bootstrapping of Web applications while offline.

Defines a low-level interface that represents gamepad devices.

This specification provides an API for representing file objects in web applications, as well as programmatically selecting them and accessing their data.

This specification defines accelerometer sensor interface for obtaining information about acceleration applied to the X, Y and Z axis of a device that hosts the sensor.

This specification defines a concrete sensor interface to monitor the rate of rotation around the device’s local three primary axes.

This specification defines a concrete sensor interface to measure magnetic field in the X, Y and Z axis.

The Generic Sensor API defines a framework and abstract Sensor interface to provide a consistent basis for writing for concrete sensor specifications. It is intended to be extended to accommodate different sensor types.

The Orientation Sensor API extends the Generic Sensor API to provide generic information describing the device’s physical orientation in relation to a three dimensional Cartesian coordinate system.

This specification defines a means to receive events that correspond to a light sensor detecting the presence of a light.

This document describes apis for clipboard operations such as copy/cut and paste, or drag and drop in web applications.

This document defines how a stream of media can be captured from a DOM element, such as a <video>, <audio>, or <canvas> element, in the form of a MediaStream [GETUSERMEDIA].

This specification defines additions to events for text and related input to allow for the monitoring and manipulation of default browser behavior in the context of text editor applications and other applications that deal with text input and text formatting. This specification builds on the UI events spec.

This specification defines additions to events for text and related input to allow for the monitoring and manipulation of default browser behavior in the context of text editor applications and other applications that deal with text input and text formatting. This specification builds on the UI events spec.

This specification defines APIs to select objects within a document.

This specification defines an API to grab still pictures from a capture device generating a video stream.

This document defines an API for recording audio and video streams.

This specification extends the Media Capture and Streams specification to allow a depth stream to be requested from 3D cameras.

This specification defines an interface for web applications to access the complete timing information for resources in a document.

This specification defines a means to receive events that correspond to a proximity sensor detecting the presence of a physical object.

This document defines how a user's display, or parts thereof, can be used as the source of a media stream using getOutputMedia, an extension to the Media Capture API [GETUSERMEDIA].

This specification describes a high-level JavaScript API for processing and synthesizing audio in web applications. The primary paradigm is of an audio routing graph, where a number of AudioNode objects are connected together to define the overall audio rendering. The actual processing will primarily take place in the underlying implementation (typically optimized Assembly / C / C++ code), but direct JavaScript processing and synthesis is also supported.

This specification defines an API that allows Web application authors to spawn background workers running scripts in parallel to their main page. This allows for thread-like operation with message-passing as the coordination mechanism.

This document collates the scenarios that are target use cases for the Media Capture API that enables access to media input capabilities for Web applications using Javascript.

This specification introduces and compares two client-side APIs for processing and synthesizing real-time audio streams in the browser.

This specification defines an API that provides the current time in sub-millisecond resolution and such that it is not subject to system clock skew or adjustments.

This specification adds the ability to retrieve a civic address, rather than coordinates, to the Geolocation API.

The FindText API specification describes an API for finding ranges of text in a document or part of a document, using a variety of selection criteria.

This specification defines several new DOM event types that provide information about the physical orientation and motion of a hosting device.

This specification defines a mechanism for an HTML document to discover and subsequently communicate with HTTP-based services advertised via common discovery protocols within a user's network.

Defines URL parsing, resolving, and canonicalizing as well as the URL API.

Defines an API for representing binary data in web applications as a Stream object.

The XMLHttpRequest specification defines an API that provides scripted client functionality for transferring data between a client and a server, one of the core components of “AJAX”.

The reporting API provides a generic reporting framework which allows Web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner.

Defines an API that provides Web applications with scripted access to an Input Method Editor

API to manage usage and availability of local storage resources

This document defines an API web page authors can use to write script-based animations where the user agent is in control of limiting the update rate of the animation.

This document specifies a runtime and security model for Web Applications. It describes how an application is defined through an application manifest, and how it can be installed, updated and packaged. It also specifies how such an application can be put into the background, be put back in the foreground or woken up. Finally, the document describes the security model for such applications. This includes the permission model and the different security rules that would apply.

This API provides interfaces to raw UDP sockets, TCP client sockets and TCP server sockets.

This specification defines a System Level API to provide access to the device alarm settings, which can schedule a notification or for an application to be started at a specific time. For example, some applications like alarm-clock, calendar or auto-update might need to utilize Alarm API to trigger particular device behaviors at specified time points.

This specification defines the app: URI scheme and rules for dereferencing an app: URI, which can be used to address resources inside a package (e.g., a packaged application). The dereferencing model relies on HTTP semantics to return resources in a manner akin to a HTTP GET request. Doing so allows this URI scheme to be used with other technologies that rely on HTTP responses to function as intended, such as [XHR].

This document identifies the permissions that are needed to use specific client-side APIs which grant access to sensitive data and operations.

This document defines an API for access to the hardware subsystem for near field communications (NFC). It permits Web pages to read and write NFC tags, to send and receive messages between NFC devices, and to handover to WiFi or Bluetooth.

A system level API for managing the user's contacts that are stored in the system's address book.

This specification defines an API to manage telephone calls. A typical use case of the Web Telephony API is the implementation of a 'Dialer' application supporting multiparty calls and multiple telephony services. A minimal structure for call history items is also defined.

This specification defines a System Level API which offers a simple interface to get access to mobile messaging services. A typical use case of the Messaging API is the implementation of a messaging client application that allows the user to send SMS and MMS messages as well as to access and manage the received SMS and MMS messages.

This specification defines an API to allow elements to be rendered fullscreen.

Defines an API to navigate file system hierarchies and sandboxed sections of a user's local filesystem.

This specification defines an API for writing to files from web applications.

The Network Information API provides an interface for Web Applications to access the underlying network information (connection info) of the device.

This specification defines an API that provides access to a user’s unified address book.

This specification defines an API to provide Web applications with access to various hardware properties of the system which they are running on, including battery status, current network bandwidth.

The Calendar API defines the high-level interfaces required to obtain read access to a user's calendaring service.

The Pick Media Intent defines a Web Intent that enables access to a user's media gallery from inside a Web application. It defines both an Intent action/type pair that selects this operation, and the format of the media data that is returned by services implementing this specification.

This specification defines an API that provides access to messaging functionality in the device, including SMS, MMS and email.

This specification extends the Web Intents service discovery and light-weight RPC mechanism for web applications by defining optional extensions to Web Intents enabled User Agents to discover and dynamically register local Web Intents Services.

Defines extensions to the Touch Events specification

The Selectors API specification defines methods for retrieving Element nodes from the DOM by matching against a group of selectors (as used in CSS).

This specification defines a service discovery and light-weight RPC mechanism for web apps called Web Intents.

This document defines DOM interfaces and markup used by client and service pages to create, receive, and reply to Web Intents messages, and the procedures the User Agent carries out to facilitate that process.

The RDF Interfaces Specification defines a set of standardized interfaces for working with RDF data in a programming environment.

RDF enables providers to publish various types of data on the Web in a unified format. This data intends to be machine-interpretable so that web developers can access it by programming languages in order to create applications for i.e., crawling, aggregating, summarizing, or highlighting contained information. While publishing RDF data on the web is vital to the growth of the Semantic Web, using the information to improve the collective utility of the Web is the true goal of the Semantic Web. To accomplish this goal, the RDF Application Programming Interface (RDF API) defines a set of standardized interfaces for working with RDF data in a web-based programming environment.

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.

This proposal makes HTML Streams the foundation for integrated Web media processing by creating a mixing and effects processing API for HTML Streams.

The Media Capture API enables access to the audio, image and video capture capabilities of the device through Javascript.

This document defines APIs for off-line serving of requests to HTTP resources using static and dynamic responses. It extends the function of application caches defined in HTML5.

This specification defines an API for storing data in databases that can be queried using a variant of SQL.