The Web Application Security Working Group has published a Working Draft of Content Security Policy Pinning. This document defines a new HTTP header that allows authors to instruct user agents to remember (“pin”) and enforce a Content Security Policy for a set of hosts for a period of time. Learn more about the Security Activity.

The group also published a Working Draft of Upgrade Insecure Requests. This document defines a mechanism which allows authors to instruct a user agent to upgrade a priori insecure resource requests to secure transport before Fetching them. Learn more about the Security Activity.

The HTML5 Image Description Extension (longdesc) was published today as a Recommendation by the HTML Working Group, with the approval of the Protocols and Formats Working Group. This extension for HTML5 adds a longdesc attribute that is used to provide links to detailed descriptions of images, and is part of W3C’s work to ensure that the Open Web Platform is accessible to people with disabilities. Learn more about the HTML Activity and the WAI Technical Activity.

The Web Content Accessibility Guidelines (WCAG) Working Group today published updates of two Notes that accompany WCAG 2.0: Understanding WCAG 2.0 and Techniques for WCAG 2.0. This is not an update to WCAG 2.0, which is a stable document. The WCAG guidelines and success criteria are designed to be broadly applicable to current and future web technologies, including dynamic applications, mobile, digital television, etc. The supporting resources published today provide specific guidance — including code examples, resources, and tests — and are updated periodically to cover current practices for meeting WCAG. For an introduction to the WCAG documents, see the WCAG Overview. Read about the Web Accessibility Initiative (WAI).

SVG Accessibility API Mappings 1.0 (SVG-AAM) was published today as a First Public Working Draft by the Protocols and Formats Working Group and SVG Working Group. This specification allows SVG authors to create accessible rich internet applications, including charts, graphs, and other drawings. It provides SVG-specific guidance to define how the SVG user agent must respond to keyboard focus, native SVG features, and role, state, and property attributes provided in web content via WAI-ARIA . SVG-AAM is the first technology-specific module that provides accessibility API mapping support for features in WAI-ARIA 1.1; other technology-specific mappings will follow. Learn more about the Interaction Domain and the Web Accessibility Initiative (WAI).

Mobile Accessibility: How WCAG 2.0 and Other W3C/WAI Guidelines Apply to Mobile was published today as a First Public Working Draft by the Mobile Accessibility Task Force, a joint Task Force of the Web Content Accessibility Guidelines Working Group (WCAG WG) and the User Agent Accessibility Guidelines Working Group (UAAG WG). This document describes how WCAG 2.0 principles, guidelines, and success criteria apply to mobile web content, mobile web apps, native apps, and hybrid apps using web components inside native apps. It provides guidance on mobile accessibility issues — such as small screen size, touch target size, zoom, gestures — and how they relate to WCAG 2.0. It links to a list of existing WCAG Techniques that apply to mobile.

The document also highlights the relevance of UAAG 2.0 and ATAG 2.0 in the mobile context, and links to UAAG 2.0 mobile accessibility examples. This document provides informative guidance, and does not set requirements. It may become a W3C Working Group Note, or the information may be integrated into WCAG Techniques and Understanding WCAG. (It will not impact WCAG 2.0 itself; WCAG 2.0 is a stable standard that does not change.) For information on W3C WAI’s broader work related to mobile accessibility, see Mobile Accessibility. Learn more about the Web Accessibility Initiative (WAI).

The Cascading Style Sheets (CSS) Working Group has published a Working Draft of CSS Basic User Interface Module Level 3 (CSS3 UI). This specification describes user interface related selectors, properties and values that are proposed for CSS level 3 to style HTML and XML (including XHTML). It includes and extends user interface related features from the selectors, properties and values of CSS level 2 revision 1 and Selectors specifications. It uses various selectors, properties and values to style basic user interface elements in a document. Learn more about the Style Activity.

The Pointer Events Working Group has published a W3C Recommendation of Pointer Events. The Pointer Events specification defines a unified set of events and interfaces for device-neutral pointer input, such as a mouse, touchscreen, and pen-tablet, including capabilities for handling pointer pressure, contact geometry, and tilt; it also defines a mapping to traditional mouse events. This specification provides additional functionality not available in the related Touch Events specification; for more information on the relationship between these two specifications, see the Touch Events Community Group. Learn more about the Rich Web Client Activity.

The Data on the Web Best Practices Working Group has published a First Public Working Draft of Data on the Web Best Practices, to encourage and enable the continued expansion of the Web as a medium for the exchange of data. Data should be discoverable and understandable by humans and machines. Where data is used in some way, whether by the originator of the data or by an external party, such usage should also be discoverable and the efforts of the data publisher recognized. In short, following these best practices will facilitate interaction between publishers and consumers.

The group also published today a Group Note of Data on the Web Best Practices Use Cases & Requirements with scenarios of how data is commonly published on the Web and how it is used. This document also provides a set of requirements derived from these use cases that will be used to guide the development of the Best Practices document and also two new vocabularies: Quality and Granularity Description, and Data Usage Description. Learn more about the Data Activity.