In response to demand from developers in our community wanting to interact with W3C’s data, we have developed an API. Through it we are making available public data on Specifications, Groups, Organizations and Users. We are providing a JSON format initially with alternate formats in the works and we will be expanding what information we expose over time. For more information please see the project page on Github.

The Accessible Rich Internet Applications Working Group, in coordination with the Digital Publishing Interest Group, have published an updated 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 to allow authors to convey structural information to assistive technologies, and to enable semantic navigation, styling, and interactive features used by readers.

This version includes new roles, changes the prefix for role names from “dpub” to “doc”, and refines the properties for roles previously defined. The document was previously published by the Protocols and Formats Working Group.

Learn more from the call for review e-mail and read about the Web Accessibility Initiative (WAI) and the Digital Publishing Activity.

The Accessible Rich Internet Applications Working Group has published Updated Working Drafts of:

• Accessible Rich Internet Applications (WAI-ARIA) 1.1
• Core Accessibility API Mappings (Core-AAM) 1.1
• Accessible Name and Description: Computation and API Mappings 1.1 (AccName-AAM)
• SVG Accessibility API Mappings 1.0 (SVG-AAM)
• WAI-ARIA Authoring Practices 1.1

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. The Accessibility API Mappings describe how user agents should expose semantics of content languages to accessibility APIs across multiple content technologies, including languages incorporating WAI-ARIA as well as features specific to HTML and SVG. WAI-ARIA Authoring Practices recommends approaches to help web application developers make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. These documents were previously published by the Protocols and Formats Working Group. SVG-AAM is jointly published with the SVG Working Group.

Learn more from the call for review e-mail and read about the Web Accessibility Initiative (WAI).

The HTML Working Group has published a W3C Recommendation of W3C DOM4. DOM defines a platform-neutral model for events and node trees. DOM4 adds Mutation Observers as a replacement for Mutation Events.

The XSLT Working Group invites implementation of the Candidate Recommendation of XSL Transformations (XSLT) Version 3.0. This specification defines the syntax and semantics of XSLT 3.0, a language designed primarily for transforming XML documents into other XML documents. The primary purpose of the changes in this version of the language is to enable transformations to be performed in streaming mode, where neither the source document nor the result document is ever held in memory in its entirety. Another important aim is to improve the modularity of large stylesheets, allowing stylesheets to be developed from independently-developed components with a high level of software engineering robustness.

A draft redesign of How to Meet WCAG 2.0: A customizable quick reference to Web Content Accessibility Guidelines (WCAG) 2.0 requirements (success criteria) and techniques was published yesterday by the Education and Outreach Working Group (EOWG) and the Web Content Accessibility Guidelines (WCAG) Working Group (WCAG WG). It is intended to replace the current How to Meet WCAG 2.0: A customizable quick reference. We welcome comments on the user interface and the filtering by 2 December, preferably via GitHub, or alternatively via e-mail to wai-eo-editors@w3.org. Read about the Web Accessibility Initiative (WAI).

The CSV on the Web Working Group has published a Proposed Recommendation for four documents:

• Model for Tabular Data and Metadata on the Web—an abstract model for tabular data, and how to locate metadata that enables users to better understand what the data holds; this specification also contains non-normative guidance on how to parse CSV files
• Metadata Vocabulary for Tabular Data—a JSON-based format for expressing metadata about tabular data to inform validation, conversion, display and data entry for tabular data
• Generating JSON from Tabular Data on the Web—how to convert tabular data into JSON
• Generating RDF from Tabular Data on the Web—how to convert tabular data into RDF

Comments are welcome through 15 December.