W3C

The Cascading Style Sheets (CSS) Working Group has published a Working Draft of Cascading Style Sheets Level 2 Revision 2 (CSS 2.2) Specification. This specification defines Cascading Style Sheets level 2. CSS is a style sheet language that allows authors and users to attach style (e.g. fonts and spacing) to structured documents (e.g. HTML documents and XML applications). By separating the presentation style of documents from the content of documents, CSS simplifies Web authoring and site maintenance.

The Web Performance Working Group has published a Working Draft of Reporting API 1. This document defines a generic reporting framework which allows web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner.

The Web Cryptography Working Group has published a Group Note of WebCrypto Key Discovery. This note describes a JavaScript API for discovering named, origin-specific pre-provisioned cryptographic keys for use with the Web Cryptography API. Pre-provisioned keys are keys which have been made available to the UA by means other than the generation, derivation, importation and unwrapping functions of the Web Cryptography API. Origin-specific keys are keys that are available only to a specified origin. Named keys are identified by a name assumed to be known to the origin in question and provisioned with the key itself. This note concerns only keys which have all three of these properties.

The Device APIs Working Group has published a Proposed Recommendation of Battery Status API. The Battery Status API specification defines a means for web developers to programmatically determine the battery status of the hosting device. Without knowing the battery status of a device, a web developer must design the web application with an assumption of sufficient battery level for the task at hand. This means the battery of a device may exhaust faster than desired because web developers are unable to make decisions based on the battery status. This specification defines an API that provides information about the battery status of the hosting device. Comments are welcome through 29 April.

Accessibility Requirements for People with Low Vision, developed by the Low Vision Accessibility Task Force (LVTF), was published today by the Web Content Accessibility Guidelines Working Group (WCAG WG). This document describes what people with low vision need for electronic content, tools, and technologies to be accessible. It includes an overview of low vision and describes specific user needs. It does not set technical requirements. It provides the background for planned future work on guidance for making web content, tools, and technologies accessible to people with low vision. Comments are welcome by 14 April 2016. Read about the Web Accessibility Initiative (WAI).

The Education and Outreach Working Group (EOWG) and the Web Content Accessibility Guidelines Working Group (WCAG WG) have published a new version of How to Meet WCAG 2.0: A customizable quick reference to Web Content Accessibility Guidelines (WCAG) 2.0 requirements (success criteria) and techniques. It provides a customizable view of WCAG 2.0 resources, including: Web Content Accessibility Guidelines (WCAG) 2.0 web standard, Techniques for WCAG 2.0 implementation guidance, and Understanding WCAG 2.0 supporting information. Information on these resources is provided in the WCAG Overview and The WCAG 2.0 Documents. This new version provides a significantly updated user interface and additional functionality to filter by Tags that are categorized under Developing, Interaction Design, Content Creation, and Visual Design. (The previous version is still available.) Learn more about the Web Accessibility Initiative (WAI).