The Authoring Tool Accessibility Guidelines Working Group (ATAG WG) has published a Proposed Recommendation of the Authoring Tool Accessibility Guidelines (ATAG) 2.0 and a Working Draft of Implementing ATAG 2.0. ATAG 2.0 provides guidelines for designing web content authoring tools that are both more accessible to authors with disabilities (Part A) and designed to enable, support, and promote the production of more accessible web content by all authors (Part B). Learn more about the Web Accessibility Initiative (WAI).
The Web Performance Working Group has published a Working Draft of Performance Timeline Level 2. This specification extends the High Resolution Time specification HR-TIME-2 by providing methods to store and retrieve high resolution performance metric data. Learn more about the Rich Web Client Activity.
The CSV on the Web Working Group has published a Candidate Recommendation for four documents:
Candidate Recommendation means that the Working Group considers the technical design to be complete, and is seeking implementation feedbacks on the documents. There are over 600 test cases and a separate document on how to use them and report on implementation results. The group is keen to get comments and implementation experiences on these specifications, either as issues on the Group’s GitHub repository or by posting to firstname.lastname@example.org.
The group expects to satisfy the implementation goals (i.e., at least two, independent implementations for each of the test cases) by October 30, 2015.
Learn more about the Data Activity.
The Web Performance Working Group has published a Working Draft of High Resolution Time Level 2. 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. Learn more about the Rich Web Client Activity.
The Device APIs Working Group has published a Group Note of Permissions for Device API Access. This document notes that work on this version of the specification has been discontinued and that further development of this specification is being performed by the Web Application Security Working Group which has published an updated version of the Permissions API.
The Tracking Protection Working Group has published a Last Call Working Draft of Tracking Compliance and Scope. This specification defines a set of practices for compliance with a user’s Do Not Track (DNT) tracking preference to which a server may claim adherence. Comments are welcome through 07 October. Learn more about the Privacy Activity.
The Protocols and Formats Working Group has published Updated Working Drafts of Accessible Rich Internet Applications (WAI-ARIA) 1.1, Core Accessibility API Mappings (Core-AAM) 1.1, and Accessible Name and Description: Computation and API Mappings 1.1 (AccName-AAM).
WAI-ARIA provides an ontology of roles, states, and properties that define accessible user interface elements. It is designed to improve the accessibility and interoperability of web content, particularly web applications.
Core-AAM describes how user agents should expose semantics of content languages to accessibility APIs across multiple content technologies (including much of WAI-ARIA), and serves as the basis for other specifications to extend the mappings to specific technologies.
AccName-AAM describes how user agents determine names and descriptions of accessible objects from web content languages and expose them in accessibility APIs.
Learn more from the call for review e-mail and read about the Web Accessibility Initiative (WAI).
The SVG Working Group has published a First Public Working Draft and one Working Draft.
SVG Paths is a specification that defines a syntax and DOM representation for paths, which are shapes that can be rendered in a document. Paths are primarily used for rendering shapes using the SVG ‘path’ element, but are also used by a number of other Web platform features, such as clipping paths and rendering in an HTML ‘canvas’.
Scalable Vector Graphics (SVG) 2 is a specification that 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.
Learn more about the Graphics Activity.
The Protocols and Formats Working Group, in coordination with the Digital Publishing Interest Group, published a First Public Working Draft of Digital Publishing WAI-ARIA Module 1.0. This specification extends WAI-ARIA 1.1 to define an ontology of roles, states, and properties specific to digital publishing. It facilitates automated processing and accessibility support by providing semantics that are not included in base languages such as HTML. It allows authors to convey structural information to assistive technologies, and to enable semantic navigation, styling, and interactive features used by readers. More information is available in the blog post
“ARIA and DPUB publish FPWD”. Learn more about the the Web Accessibility Initiative (WAI) and the Digital Publishing Activity.
The CSS Working Group and the SVG Working Group have published a working draft of Web Animations. This specification defines a model for synchronization and timing of changes to the presentation of a Web page. It also defines an application programming interface for interacting with this model and it is expected that further specifications will define declarative means for exposing these features.
Learn more about the Style Activity, and the Graphics Activity.