The  Web Applications Working Group  has published  Web Share API  as a W3C Recommendation. This specification defines an API for sharing text, links and other content to an arbitrary destination of the user’s choice. The available share targets are not specified here; they are provided by the user agent. They could, for example, be apps, websites or contacts.

  The  Web Applications Working Group  has published a First Public Working Draft of  Web Locks API . This document defines a web platform API that allows script to asynchronously acquire a lock over a resource, hold it while work is performed, then release it. While held, no other script in the origin can acquire a lock over the same resource. This allows contexts (windows, workers) within a web application to coordinate the usage of resources.

  The  Web Applications Working Group  has just published a Proposed Recommendation of  ARIA in HTML . This specification defines the authoring rules (author conformance requirements) for the use of  Accessible Rich Internet Applications (WAI-ARIA) 1.1  and  Digital Publishing WAI-ARIA Module 1.0  attributes on [ HTML ] elements. This specification’s primary objective is to define requirements for use with conformance checking tools used by authors (i.e., web developers). These requirements will aid authors in their development of web content, including custom interfaces/widgets, that makes use of ARIA to complement or extend the features of the host language [ HTML ].

17 December 2019 The  Web Applications Working Group  has published a First Public Working Draft of  Web Share API . This specification defines an API for sharing text, links and other content to an arbitrary destination of the user’s choice. The available share targets are not specified here; they are provided by the user agent. They could, for example, be apps, websites or contacts.

The  Accessible Rich Internet Applications Working Group  invites implementations of two documents: WAI-ARIA Graphics Module (Graphics-ARIA) : Assistive technologies need semantic information about the structures and expected behaviors of a document in order to convey appropriate information to persons with disabilities. This specification defines a WAI-ARIA 1.1 [WAI-ARIA-1.1] module of core roles specific to web graphics. These semantics allow an author to express the logical structure of the graphic to assistive technologies in order improve accessibility of graphics. Assistive technologies could then enable semantic navigation and adapt styling and interactive features, to provide an optimal experience for the audience. These features complement the graphics and document structure elements defined by HTML [HTML52] and SVG [SVG2]. Graphics Accessibility API Mappings (Graphics-AAM) : The Graphics Accessibility API Mappings defines how user agents map the WAI-ARIA Graphic...

7 October 2014 The Web Applications Working Group has published two documents today: A First Public Working Draft of Selection API . This document is a preliminary draft of a specification for the Selection API and selection related functionality. It replaces a couple of old sections of the HTML specification, the selection part of the old DOM Range specification. A Working Draft of Push API . The Push API provides webapps with scripted access to server-sent messages, for simplicity referred to here as push messages, as delivered by push services. A push service allows a webapp server to send messages to a webapp, regardless of whether the webapp is currently active on the user agent. The push message will be delivered to a Service Worker, which could then store the message’s data or display a notification to the user. This specification is designed to promote compatibility with any delivery method for push messages from push ...

11 February 2014 The Web Applications Working Group has published a W3C Recommendation of Progress Events . The Progress Events specification defines an event interface that can be used for measuring progress; e.g. HTTP entity body transfers. This specification is primarily meant to be used by other specifications. Learn more about the Rich Web Client Activity .

6 November 2013 The Web Applications Working Group has published four Working Drafts: Streams API . This specification provides an API for representing binary data and string data in web applications as a Stream object, as well as programmatically building and reading its contents. This includes a Stream, a StreamConsumeResult and a StreamReadType interfaces, extensions to XMLHttpRequest and to URL.createObjectURL and URL.revokeObjectURL. This API is designed to be used in conjunction with other APIs and elements on the web platform, notably: File, XMLHttpRequest, postMessage, and Web Workers. Quota Management API . This specification defines an API to manage usage and availability of local storage resources, and defines a means by which a user agent (UA) may grant Web applications permission to use more local space, temporarily or persistently, via various different storage APIs. Document Object Model (DOM) Level 3 Events Sp...

18 October 2013 The Web Applications Working Group has published a Group Note of Selectors API Level 2 . Selectors, which are widely used in CSS, are patterns that match against elements in a tree structure. The Selectors API specification defines methods for retrieving Element nodes from the DOM by matching against a group of selectors, and for testing if a given element matches a particular selector. It is often desirable to perform DOM operations on a specific set of elements in a document. These methods simplify the process of acquiring and testing specific elements, especially compared with the more verbose techniques defined and used in the past. Learn more about the Rich Web Client Activity .

15 August 2013 The Web Applications Working Group has published two Working Drafts: Push API . This specification defines a “Push API” that provides webapps with scripted access to server-sent notifications, for simplicity referred to here as push notifications, as delivered by push services. Push services are a way for application servers to send messages to webapps, whether or not the webapp is active in a browser window. Input Method Editor API . This specification defines an “IME API” that provides Web applications with scripted access to an IME (input-method editor) associated with a hosting user agent. Learn more about the Rich Web Client Activity .

04 July 2013 The Web Applications Working Group invites implementation of the Candidate Recommendation of Indexed Database API . 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. Learn more about the Rich Web Client Activity .

18 April 2013 The   Web Applications Working Group   has published a W3C Recommendation of   XML Digital Signatures for Widgets . This document defines a profile of the XML Signature Syntax and Processing specification to allow a widget package to be digitally signed. Authors and distributors can digitally sign a widget as a mechanism to ensure continuity of authorship and distributorship. A user agent, or other validation system, can use a digital signature to verify the data integrity of the files within a widget package and to confirm the signing key(s). Learn more about the   Rich Web Client Activity .

06 December 2012 The Web Applications Working Group published three Working Drafts : The Screen Orientation API . The Screen Orientation API's goal is to provide an interface for web applications to be able to read the screen orientation state, to be informed when this state changes and to be able to lock the screen orientation to a specific state. XMLHttpRequest . The XMLHttpRequest specification defines an API that provides scripted client functionality for transferring data between a client and a server. DOM4 , published in co-operation with the Web Hypertext Application Technology Working Group . DOM defines the event and document model the Web platform uses. The DOM is a language- and platform neutral interface that allows programs and scripts to dynamically access and update the content and structure of documents. Learn more about the Rich Web Client Activity .

27 November 2012 The Web Applications Working Group has published a W3C Recommendation of Packaged Web Apps (Widgets) - Packaging and XML Configuration (Second Edition) . This specification standardizes a packaging format and metadata for a class of software known commonly as packaged apps or widgets. Unlike traditional user interface widgets (e.g., buttons, input boxes, toolbars, etc.), widgets as specified in this document are full-fledged client-side applications that are authored using technologies such as HTML and then packaged for distribution. Examples range from simple clocks, stock tickers, news casters, games and weather forecasters, to complex applications that pull data from multiple sources to be "mashed-up" and presented to a user in some interesting and useful way. Learn more about the Rich Web Client Activity .

18 October 2012 The Web Applications Working Group has published the First Public Working Draft of Push API . This specification defines a “Push API” that provides webapps with scripted access to server-sent application data, for simplicity referred to here as "Push messages" as delivered by "Push services". Push services are a way for application servers to send messages to webapps, whether or not the webapp is active in a browser window. The specific method to be used by a webapp is either selected by the user through selecting a Web Intent Push Service provider, or by the browser. The Push API is defined to promote compatibility with any underlying delivery method. Learn more about the Rich Web Client Activity .

06 September 2012 The Web Applications Working Group has published a Last Call Working Draft of Document Object Model (DOM) Level 3 Events Specification . This specification defines the Document Object Model Events Level 3, a generic platform- and language-neutral event system which allows registration of event handlers, describes event flow through a tree structure, and provides basic contextual information for each event. The Document Object Model Events Level 3 builds on the Document Object Model Events Level 2. Comments are welcome through 27 September. Learn more about the Rich Web Client Activity .

09 August 2012 The Web Applications Working Group has published a Last Call Working Draft of The WebSocket API . This specification defines an API that enables Web pages to use the WebSocket protocol (defined by the IETF) for two-way communication with a remote host. Comments are welcome through 30 August. Learn more about the Rich Web Client Activity

28 June 2012 The Web Applications Working Group has published a Working Draft of Selectors API Level 2 . Selectors, which are widely used in CSS, are patterns that match against elements in a tree structure. The Selectors API specification defines methods for retrieving Element nodes from the DOM by matching against a group of selectors, and for testing if a given element matches a particular selector. It is often desirable to perform DOM operations on a specific set of elements in a document. These methods simplify the process of acquiring and testing specific elements, especially compared with the more verbose techniques defined and used in the past. Learn more about the Rich Web Client Activity .

14 June 2012 The Web Applications Working Group has published a Working Draft of Document Object Model (DOM) Level 3 Events Specification . This specification defines the Document Object Model Events Level 3, a generic platform- and language-neutral event system which allows registration of event handlers, describes event flow through a tree structure, and provides basic contextual information for each event. The Document Object Model Events Level 3 builds on the Document Object Model Events Level 2. Learn more about the Rich Web Client Activity .