W3C

W3C News

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

The Timed Text Working Group invites implementations of an updated Candidate Recommendation of Timed Text Markup Language 2 (TTML2). 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.

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 [HTML 5.2] document, or a <text> or <textstream> media element in a [SMIL 3.0] document.

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

The Timed Text Working Group invites implementations of an updated Candidate Recommendation of Timed Text Markup Language 1 (TTML1) (Third Edition). 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.

New version of the Roadmap of Web Applications on Mobile

icon representing mobile life-cycleW3C has published a new version of its Roadmap of Web Applications on Mobile, an overview of the various technologies developed in W3C that increase the capabilities of Web applications, and how they apply more specifically to the mobile context.

The contents of the roadmap have been updated to follow the evolution of the Web platform since April 2018. See the Change history for details. Most of these updates focused on mechanisms that allow mobile web applications to tweak performance settings and gain finer-grained control over the browser’s default behavior. In particular, new exploratory work and technologies in progress mentioned in the Performance and Tuning page include:

  • the CSS Animation Worklet API to create scripted animations in a dedicated thread,
  • the CSS contain property to indicate that an element’s subtree is independent of the rest of the page,
  • the proposed CSS overscroll-behavior property to control the behavior of a scroll container when its scrollport reaches the boundary of its scroll box,
  • the Event Timing Web Perf API to measure the latency of events triggered by user interaction,
  • the Identifiers for WebRTC’s Statistics API to monitor the performance of the network and media pipeline in peer-to-peer scenarios, and
  • Priority Hints to let developers signal the priority of each resource they need to download.

The roadmap did not mention WebDriver, recently published as a W3C Recommendation, a key technology for mobile web developers as it enables automated testing across browsers and devices. This was an oversight, fixed in this new version.

The implementation info rendered in tables now also embeds information from the MDN Browser Compatibility Data project. A new “partial” badge also indicates that an implementation may be incomplete, either because it is, or because implementation data is not complete enough to assess support of the entire specification.

Sponsored by Beihang University, this project is part of a set of roadmaps under development in a GitHub repository to document existing standards, highlight ongoing standardization efforts, point out topics under incubation, and discuss technical gaps that may need to be addressed in the future. New versions will be published on a quarterly basis, or as needed depending on progress of key technologies of the Web platform. We encourage the community to review them and raise comments, or suggest new ones, in the repository’s issue tracker.

W3C Invites Implementations of Scalable Vector Graphics (SVG) 2

The SVG Working Group invites implementations of an updated Candidate Recommendation of Scalable Vector Graphics (SVG) 2. This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 2. SVG is a language based on XML for describing two-dimensional vector and mixed vector/raster graphics. SVG content is stylable, scalable to different display resolutions, and can be viewed stand-alone, mixed with HTML content, or embedded using XML namespaces within other XML languages. SVG also supports dynamic changes; script can be used to create interactive documents, and animations can be performed using declarative animation features or by using script. This version of SVG builds upon SVG 1.1 Second Edition by improving the usability and precision of the language. The Changes appendix lists all of the changes that have been made since SVG 1.1 Second Edition.

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

The Web Authentication Working Group invites implementations of an updated Candidate Recommendation of Web Authentication: An API for accessing Public Key Credentials Level 1. 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 WebAuthn 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 Staff Judy Brewer is the 2018 ACM SIGACCESS Award honoree

Portrait of Judy BrewerOn 25 July the ACM has announced W3C’s Judy Brewer as the recipient of the 2018 SIGACCESS Award for Outstanding Contributions to Computing and Accessibility.

The SIGACCESS Award for Outstanding Contributions to Computing and Accessibility recognizes individuals who have made significant and lasting contributions to the development of computing technologies that improve the accessibility of media and services to people with disabilities. This award recognizes members of the community for long-term accomplishments or those who have made a notable impact through a significant innovation.

Judy Brewer is Director of the Web Accessibility Initiative (WAI) at the World Wide Web Consortium (W3C), and a Principal Research Scientist at MIT’s Computer Science and Artificial Intelligence Lab. For the past 21 years, under Judy’s leadership, WAI has developed key accessibility standards, prominent amongst which are the Web Content Accessibility Guidelines (WCAG), the Authoring Tool Accessibility Guidelines (ATAG), User Agent Accessibility Guidelines (UAAG), and Accessible Rich Internet Applications (WAI-ARIA).

As part of the award, Judy has been invited to present a keynote talk at the ASSETS Conference on October 22nd. Read more about about the SIGACCESS Award, about WCAG and WAI.

W3C Invites Implementations of TTML Profiles for Internet Media Subtitles and Captions 1.1

The Timed Text Working Group invites implementations of an updated Candidate Recommendation of TTML Profiles for Internet Media Subtitles and Captions 1.1. This specification defines two profiles of [ttml2-20180628]: 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. This specification improves on [ttml-imsc1.0.1] by supporting contemporary practices, while retaining compatibility with [ttml-imsc1.0.1] documents. Relative to [ttml-imsc1.0.1], any addition or deprecation of features are summarized at Appendix L. Summary of substantive changes (non-normative).

WAI-ARIA Authoring Practices 1.1 Working Group Note Updated

The Accessible Rich Internet Applications Working Group has published an updated Working Group Note of WAI-ARIA Authoring Practices 1.1. WAI-ARIA Authoring Practices 1.1 was previously published as a Working Group Note in December 2017, to accompany the WAI-ARIA 1.1 Recommendation. Since then, the group has added an additional design pattern and examples, and improved the quality of many of the other design patterns and examples, to improve the support for WAI-ARIA 1.1. Separately, as recently announced, WAI-ARIA Authoring Practices 1.2 is under development, which includes the improvements in this document plus additional features specific to WAI-ARIA 1.2. Each version of WAI-ARIA Authoring Practices is specific to the corresponding version of WAI-ARIA. Read about the Accessible Rich Internet Applications Working Group and the Web Accessibility Initiative (WAI).

First Public Working Drafts: WAI-ARIA 1.2, Core-AAM 1.2, and ARIA Practices 1.2

The Accessible Rich Internet Applications Working Group has published First Public Working Drafts of Accessible Rich Internet Applications 1.2 (WAI-ARIA), Core Accessibility API Mappings 1.2 (Core-AAM), and WAI-ARIA Authoring Practices 1.2 (ARIA APG). WAI-ARIA 1.2 continues development of the technology after ARIA 1.1 was completed in December 2017. This version focuses primarily on providing roles to match features of HTML, which is needed by technologies such as Web Components and Accessible Object Model. Core-AAM 1.2 provides accessibility API mappings for these new roles, and ARIA Practices 1.2 describes recommended authoring patterns for these new roles. For more information, see the blog post Accessible Rich Internet Applications 1.2. Read about the Accessible Rich Internet Applications Working Group and the Web Accessibility Initiative (WAI).