W3C

W3C News

TTML Profiles for Internet Media Subtitles and Captions 1.0.1 (IMSC1) is now a W3C Recommendation

The Timed Text Working Group has published TTML Profiles for Internet Media Subtitles and Captions 1.0.1 (IMSC1) as a W3C Recommendation. This document specifies two profiles of [TTML1]: a text-only profile and an image-only profile. These profiles are intended to be used across subtitle and caption delivery applications worldwide, thereby simplifying interoperability, consistent rendering and conversion to other subtitling and captioning formats. It is feasible to create documents that simultaneously conform to both [ttml10-sdp-us] and the text-only profile. The document defines extensions to [TTML1], as well as incorporates extensions specified in [ST2052-1] and [EBU-TT-D]. Both profiles are based on [SUBM].

Call for Review: Web Content Accessibility Guidelines (WCAG) 2.1 is a W3C Proposed Recommendation

The Accessibility Guidelines Working Group has published a Proposed Recommendation of Web Content Accessibility Guidelines (WCAG) 2.1. WCAG 2.1 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines will also often make Web content more usable to users in general.

Comments are welcome through 22 May 2018.

W3C Invites Implementations of Timed Text Markup Language 1 (TTML1) (Third Edition)

The Timed Text Working Group invites implementations of Timed Text Markup Language 1 (TTML1) (Third Edition) Candidate Recommendation. This document specifies Timed Text Markup Language (TTML), Version 1, also known as TTML1, 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. It is intended to be used for the purpose of transcoding or exchanging timed text information among legacy distribution content formats presently in use for subtitling and captioning functions. In addition to being used for interchange among legacy distribution content formats, TTML Content may be used directly as a distribution format, for example, providing a standard content format to reference from a <track> element in an HTML5 document, or a <text> or <textstream> media element in a [SMIL 2.1] document.

W3C Tutorials and Track on Web Conference 2018

WWW2018 logoThis year, W3C once again joins the Web Conference 2018, previously known as WWW2018 with W3C tutorials and track.

The W3C tutorials on Monday and Tuesday focus on Data Visualization, Media and Audio on the Web. The W3C Track on Friday invites conference attendees to talk to experts from W3C members and W3C team on topics including New Trends on the Web Platform, WebAssembly, WebXR, Web of Things, Social Web Protocols and the Foundations of Trust as well as Intelligent Search on the Web. A panel about the future of the Web will be hosted at the end of the W3C track and we expect active interaction with the audience on site with the recent hot topics they care about for the Web. Also, W3C will join the exhibition of the Web Conference and we welcome conference attendees to visit our booth.

Login with no password – Major Standards Milestone in Global Effort Towards Simpler, Stronger Authentication on the Web

illustration of the authentication flow in fido2W3C and the FIDO Alliance have achieved a major standards milestone in the global effort to bring simpler yet stronger web authentication to users around the world. The completion of the FIDO2 standardization efforts, the recent advancement of Web Authentication (WebAuthn) to Candidate Recommendation, –and the commitment of leading browser vendors to implement– enable users to login easily to online services with desktop or mobile devices with phishing-resistant security. WebAuthn, a standard web API to give users new methods to securely authenticate across sites and devices, has been developed in coordination with FIDO Alliance and is a core component of the FIDO2 Project along with FIDO’s Client to Authenticator Protocol (CTAP) specification, which enables an external authenticator, such as a security key or a mobile phone, to communicate strong authentication credentials locally over USB, Bluetooth or NFC to the user’s computer or tablet. Please, read the joint Press release and testimonials from W3C Members.

First Public Working Note of the Web of Things Protocol Binding Templates; updated WoT drafts

The Web of Things provides layered interoperability between Things by using the WoT Interfaces and enables applications to interact with and orchestrate connected Things at Web scale. The Web of Things (WoT) Working Group has published today:

  • A First Public Working Group Note of the Web of Things (WoT) Protocol Binding Templates. This document describes the initial set of design pattern and vocabulary extensions to the WoT Thing Description. Protocol Binding Templates consist of reusable vocabulary and design pattern extensions to the WoT Thing Description format that enable an application client to interact, using a consistent interaction model, with Things that expose diverse protocols and protocol usage. See the specification to discover how to contribute to this draft.
  • An updated Working Draft of the Web of Things (WoT) Thing Description. This specification describes a formal model and common representation for a Web of Things Thing Description, which describes the metadata and interfaces of Things, where a Thing is an abstraction of a physical entity that provides interactions to and participates in the Web of Things. In addition to physical entities, Things can also represent virtual entities. A Thing Description instance can be hosted by the Thing itself or hosted externally due to Thing’s resource restrictions (e.g. limited memory space) or when a Web of Things-compatible legacy device is retrofitted with a Thing Description.
  • An updated Working Draft of the Web of Things (WoT) Scripting API. This specification describes a programming interface representing the WoT Interface that allows scripts run on a Thing to discover and consume (retrieve) other Things and to expose Things characterized by Properties, Actions and Events. Scripting is an optional “convenience” building block in WoT and it is typically used in gateways that are able to run a WoT Runtime and script management, providing a convenient way to extend WoT support to new types of endpoints and implement WoT applications like Thing Directory.

W3C Advisory Committee Elects Technical Architecture Group

W3C TAG logoThe W3C Advisory Committee has elected Kenneth Rohde Christiansen (Intel Corporation) to fill the W3C Technical Architecture Group (TAG) additional seat created by the adoption of Process 2018. He joins co-Chairs Tim Berners-Lee, Daniel Appelquist (Samsung Electronics), Peter Linss (W3C Invited Expert), continuing participants David Baron (Mozilla Foundation), Hadley Beeman (W3C Invited Expert), Travis Leithead (Microsoft), Sangwhan Moon (Odd Concepts), Lukasz Olejnik (W3C Invited Expert), Alex Russell (Google), and staff contact Yves Lafon. The mission of the TAG is to 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, and to help coordinate cross-technology architecture developments inside and outside W3C. Learn more about the TAG.

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.