W3C Invites Implementations of Graphics-ARIA and Graphics-AAM

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 Graphics Module [GRAPHICS-ARIA-1.0] markup to platform accessibility APIs. It is intended for user agent developers responsible for accessibility in their user agent so that they can support the accessibility of graphics such as that created for [SVG] or [HTML52]. The implementation of this specification in user agents enables authors to produce more accessible graphics by conveying common graphics semantics to assistive technologies. It provides Accessibility API Mapping guidance for the roles defined in the WAI-ARIA Graphics Module [GRAPHICS-ARIA-1.0].

These documents are part of the WAI-ARIA suite described in the WAI-ARIA Overview.

W3C Invites Implementations of Encoding

The Internationalization Working Group invites implementations of an updated Candidate Recommendation of Encoding. The utf-8 encoding is the most appropriate encoding for interchange of Unicode, the universal coded character set. Therefore for new protocols and formats, as well as existing formats deployed in new contexts, this specification requires (and defines) the utf-8 encoding.

The other (legacy) encodings have been defined to some extent in the past. However, user agents 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 addresses those gaps so that new user agents do not have to reverse engineer encoding implementations and existing user agents can converge.

W3C Invites Implementations of the Web Authentication: An API for accessing Public Key Credentials Level 1

20 March 2018

The Web Authentication Working Group invites implementations of the Web Authentication: An API for accessing Public Key Credentials Level 1 Candidate Recommendation. This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given Relying Party, are created and stored on an authenticator by the user agent in conjunction with the web application. The user agent mediates access to public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to relying parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality

W3C Invites Implementations of the Sensor APIs

The Device and Sensors Working Group invites implementations of the Candidate Recommendation for six documents, namely:

• Generic Sensor API: Generic Sensor API defines a framework for exposing sensor data to the Open Web Platform in a consistent way. It does so by defining a blueprint for writing specifications of concrete sensors along with an abstract Sensor interface that can be extended to accommodate different sensor types.
• Ambient Light Sensor: Ambient Light Sensor defines a concrete sensor interface to monitor the ambient light level or illuminance of the device’s environment.
• Accelerometer: Accelerometer defines Accelerometer, LinearAccelerationSensor and GravitySensor interfaces for obtaining information about acceleration applied to the X, Y and Z axis of a device that hosts the sensor.
• Gyroscope: Gyroscope defines a concrete sensor interface to monitor the rate of rotation around the device’s local three primary axes.
• Magnetometer: Magnetometer defines a concrete sensor interface to measure magnetic field in the X, Y and Z axis.
• Orientation Sensor: Orientation Sensor defines a base orientation sensor interface and concrete sensor subclasses to monitor the device’s physical orientation in relation to a stationary three dimensional Cartesian coordinate system

W3C Invites Implementations of the Timed Text Markup Language 2 (TTML2)

The Timed Text Working Group invites implementations of the Timed Text Markup Language 2 (TTML2) Candidate Recommendation. This document specifies the Timed Text Markup Language (TTML), Version 2, also known as TTML2, in terms of a vocabulary and semantics thereof.

The Timed Text Markup Language is a content type that represents timed text media for the purpose of interchange among authoring systems. Timed text is textual information that is intrinsically or extrinsically associated with timing information.

First Public Working Draft: CSS Text Decoration Module Level 4

The CSS Working Group has published a First Public Working Draft of CSS Text Decoration Module Level 4. This module contains the features of CSS relating to text decoration, such as underlines, text shadows, and emphasis marks.

CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc.

ACT Rules Format 1.0 Working Draft Updated

An updated Working Draft of Accessibility Conformance Testing (ACT) Rules Format was published today by the Accessibility Guidelines Working Group (AG WG). This draft addresses all comments received on the previous draft. Most importantly, the “Selector” approach was replaced with “Applicability” and “Expectation” pairs, to make ACT Rules less procedural. This draft is accompanied by sample ACT Rules that implement this rules format. Read about the the Web Accessibility Initiative (WAI).

W3C Opens Technical Architecture Group (TAG) Special Election

5 March 2018

The W3C Advisory Committee having nominated three individuals, is invited today to vote until 2 April 2018 for one seat in the 2018 special election to the W3C Technical Architecture Group (TAG) per Process Document now granting an additional seat.

The TAG is a special working group within the W3C, chartered under the W3C Process Document, with stewardship of the Web architecture. Some aspects of its mission include

• to document and build consensus around principles of Web architecture and to interpret and clarify these principles when necessary;
• to resolve issues involving general Web architecture brought to the TAG;
• to help coordinate cross-technology architecture developments inside and outside W3C.

W3C Invites Implementations of the High Resolution Time Level 2

The Web Performance Working Group invites implementations of an updated Candidate Recommendation of High Resolution Time Level 2. This specification defines an API that provides the time origin, and current time in sub-millisecond resolution, such that it is not subject to system clock skew or adjustments.