The Timed Text Working Group has published the DAPT Requirements as a Group Note. The document captures technical requirements for a profile of TTML2 for use in workflows related to dubbing and audio description of movies and videos, known as the Dubbing and Audio description Profile of TTML2 (DAPT).

The DAPT Requirements were previously published as a Draft Note in May 2022 and updated in October 2022.

The Accessibility Guidelines Working Group has published Guidance on Applying WCAG 2.2 to Mobile Applications (WCAG2Mobile) as a first Draft Note. WCAG2Mobile describes how Web Content Accessibility Guidelines (WCAG) 2.2 principles, guidelines, and success criteria can be applied to mobile applications, including native mobile apps, mobile web apps, and hybrid apps using web components inside native mobile apps.

The Accessibility Guidelines Working Group has published Web Content Accessibility Guidelines (WCAG) 2.1 as an updated W3C Recommendation, incorporating the changes since the 12 December 2024 Recommendation. The 6 May 2025 publication addresses minor technical issues from the previous publication.

The W3C Advisory Committee, having nominated ten individuals, is invited today to vote until 30 May 2025 to fill seven seats in the W3C Advisory Board (AB) election. Please, read the statements of the nominees.

Created in March 1998, the Advisory Board provides ongoing guidance to the W3C Team on issues of strategy, management, legal matters, process, and conflict resolution. The Advisory Board also serves the W3C Members by tracking issues raised between Advisory Committee meetings, soliciting Member comments on such issues, and proposing actions to resolve these issues. The Advisory Board manages the evolution of the Process Document. The Advisory Board hears appeals of Member Submission requests that are rejected for reasons unrelated to Web architecture. For several years, the AB has conducted its work in a public wiki.

The elected Members of the Advisory Board participate as individual contributors and not representatives of their organizations. Advisory Board participants use their best judgment to find the best solutions for the Web, not just for any particular network, technology, vendor, or user.

The Pointer Events Working Group has published Pointer Events Level 3 as W3C Candidate Recommendation. The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware-agnostic pointer input from devices including a mouse, pen, or touchscreen. For compatibility with existing mouse-based content, this specification also describes a mapping to fire Mouse Events for other pointer device types.

Comments are welcome via the GitHub issue by 27 May 2025.

The Devices and Sensors Working Group has published Compute Pressure Level 1 as W3C Candidate Recommendation. The Compute Pressure API provides a way for websites to react to changes in the CPU pressure of the target device, such that websites can trade off resources for an improved user experience.

Comments are welcome via the GitHub issue by 22 May 2025.

The Web Application Security Working Group has published the following two First Public Working Drafts:

• Web Cryptography Level 2: This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption. Additionally, it describes an API for applications to generate and/or manage the keying material necessary to perform these operations. Uses for this API range from user or service authentication, document or code signing, and the confidentiality and integrity of communications.
• Subresource Integrity: This specification defines a mechanism by which user agents may verify that a fetched resource has been delivered without unexpected manipulation.

The Private Advertising Technology Working Group has published a First Public Working Draft of Privacy-Preserving Attribution: Level 1. This specifies a browser API for the measurement of advertising performance. The goal is to produce aggregate statistics about how advertising leads to conversions, without creating a risk to the privacy of individual web users. This API collates information about people from multiple web origins, which could be a significant risk to their privacy. To manage this risk, the information that is gathered is aggregated using an aggregation service that is trusted by the user-agent to perform aggregation within strict limits. Noise is added to the aggregates produced by this service to provide differential privacy. Websites may select an aggregation service from the list of approved aggregation services provided by the user-agent.

Today the Web Applications Working Group published the following two documents as W3C Recommendations:

• UI Events KeyboardEvent key Values: This specification defines the key attribute values that must be used for KeyboardEvent’s key attribute, which is defined as part of the UI Events Specification.
• UI Events KeyboardEvent code Values: This specification defines the values for the KeyboardEvent.code attribute, which is defined as part of the UI Events Specification. The code value contains information about the key event that can be used to identify the physical key being pressed by the user.

The CSS Working Group has published a First Public Working Draft of CSS Gap Decorations Module Level 1. This module introduces several properties to add row and column gap decorations to container layout types such as grid and flex.

The World Wide Web Consortium (W3C) has published the Authorized Simplified Chinese Translation of the Ethical Web Principles, Web????.

This translation was developed by the W3C Team and underwent comprehensive review by the Chinese web community, following the Policy for Authorized W3C Translations. The policy is designed to achieve quality translations through a process that relies on transparency and community accountability, with W3C providing oversight of the process.

Translations enable broader adoption of W3C resources and serve worldwide audience across languages and cultures. Explore more W3C translations and learn how to contribute to translation efforts.

The W3C Advisory Board, in cooperation with the Vision Task Force, has updated the Group Note of Vision for W3C and now proposes advancing it to a W3C Statement.

The Vision for W3C articulates the values that underpin W3C’s mission, what W3C is, what it does and why that matters, and the principles by which it operates and makes decisions.

What is the web?

The World Wide Web was originally conceived as a tool for sharing information. It has evolved rapidly into a fundamental part of humanity, sparking major social change by providing and expanding access to knowledge, education, commerce and shopping, communication, social experiences, civic functions, entertainment, and more.

What is W3C?

The World Wide Web Consortium (W3C) was founded as an organization to provide a consistent architecture across the rapid pace of progress in the Web, and to build a common community to support its development.

W3C’s Vision for the Web:

• The Web is for all humanity.
• The Web is designed for the good of all people.
• The Web must be safe to use.
• There is one interoperable world-wide Web.

Vision for W3C:

The fundamental function of W3C is to provide an open forum where diverse voices from around the world and from different organizations and industries work together to evolve the web by building consensus on voluntary global standards for Web technologies.

W3C Members will review the Vision for W3C. The intent is for this document to eventually become a W3C Statement. It will continue to evolve.

The RDF-star Working Group has published a first Draft Note of RDF 1.2 Primer. This primer is designed to provide the reader with the basic knowledge required to effectively use RDF. It introduces the basic concepts of RDF and shows concrete examples of the use of RDF. Secs. 3-5 can be used as a minimalist introduction into the key elements of RDF. Changes between RDF 1.1 and RDF 1.2 are summarized in a separate document: What’s New in RDF 1.2.

The World Wide Web Consortium (W3C) published the Authorized Brazilian Portuguese Translation of Web Content Accessibility Guidelines (WCAG) 2.2, Diretrizes de Acessibilidade para Conteudo Web (WCAG) 2.2. The Lead Translation Organization for this Authorized Translation was Ceweb.br.

Other translations of accessibility resources — including non-technical and educational resources — are listed in All WAI Translations.

W3C Web Accessibility Initiative ( WAI) particularly encourages the development of Authorized Translations of WCAG 2.2 and other technical specifications to facilitate their adoption and implementation internationally. For information on developing an Authorized Translation, please see Policy for Authorized W3C Translations.

The Publishing Maintenance Working Group has published an updated EPUB 3.3 Recommendation. EPUB® 3 defines a distribution and interchange format for digital publications and documents. The EPUB format provides a means of representing, packaging, and encoding structured and semantically enhanced web content — including HTML, CSS, SVG, and other resources — for distribution in a single-file container. This specification defines the authoring requirements for EPUB 3 publications and represents the third major revision of the standard. The update includes a number of minor changes, primarily to clarify some details on the conformance requirements of EPUB 3 documents.

The Working Group has also published three First Public Working Drafts: EPUB 3.4, EPUB Reading Systems 3.4, and EPUB Accessibility 1.1.1. These drafts will eventually evolve into the next major version of the EPUB 3 standard (EPUB 3.4). For more information, please refer to the Publishing Maintenance Working Group Charter.

The CSS Working Group has published a First Public Working Draft of CSS Form Control Styling Level 1. This CSS Module defines various ways of styling form controls and their different parts.

The Web Editing Working Group has published a First Public Working Draft of ContentEditable, a collection of proposals developed by the group. Some of these proposals are further defined in EditContext API, which supersedes this document. The Working Group ceased work on this specification in 2022 prior to publishing a First Public Working Draft (FPWD). This FPWD is intended to archive the prior work. Following the publication of this FPWD the Working Group intends to publish this document as a Discontinued Draft and cease further work on it. This does not affect the definition of contenteditable=true, contenteditable=false and contenteditable=plaintext-only as they can be found in [ HTML]. Nor does it affect execCommand which is described in another unofficial draft document.

Today the Verifiable Credentials Working Group published the following seven documents as W3C Proposed Recommendations:

• Verifiable Credentials Data Model v2.0: A verifiable credential is a specific way to express a set of claims made by an issuer, such as a driver's license or an education certificate. This specification describes the extensible data model for verifiable credentials, how they can be secured from tampering, and a three-party ecosystem for the exchange of these credentials that is composed of issuers, holders, and verifiers. This document also covers a variety of security, privacy, internationalization, and accessibility considerations for ecosystems that use the technologies described in this specification.
• Verifiable Credential Data Integrity 1.0: This specification describes mechanisms for ensuring the authenticity and integrity of verifiable credentials and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs.
• Data Integrity EdDSA Cryptosuites v1.0: This specification describes Data Integrity cryptographic suites for use when creating or verifying a digital signature using the Ed25519 instantiation of the Edwards-Curve Digital Signature Algorithm (EdDSA).
• Data Integrity ECDSA Cryptosuites v1.0: This specification describes Data Integrity cryptosuites for use when generating a digital signature using the Elliptic Curve Digital Signature Algorithm (ECDSA).
• Securing Verifiable Credentials using JOSE and COSE: This specification defines how to secure credentials and presentations conforming to the Verifiable Credential data model with JSON Object Signing and Encryption, Selective Disclosure for JWTs, and CBOR Object Signing and Encryption (COSE). This enables the Verifiable Credential data model [VC-DATA-MODEL-2.0] to be implemented with standards for signing and encryption that are widely adopted.
• Controlled Identifiers v1.0: A controlled identifier document contains cryptographic material and lists service endpoints for the purposes of verifying cryptographic proofs from, and interacting with, the controller of an identifier.
• Bitstring Status List v1.0: This specification describes a privacy-preserving, space-efficient, and high-performance mechanism for publishing status information such as suspension or revocation of Verifiable Credentials through use of bitstrings.

The Data Shapes Working Group has published the following two First Public Working Drafts:

• SHACL 1.2 Core: This document defines the Core of the SHACL Shapes Constraint Language. SHACL is a language for validating RDF graphs against a set of conditions. These conditions are provided as shapes and other constructs expressed in the form of an RDF graph. RDF graphs that are used in this manner are called "shapes graphs" in SHACL and the RDF graphs that are validated against a shapes graph are called "data graphs". As SHACL shape graphs are used to validate that data graphs satisfy a set of conditions they can also be viewed as a description of the data graphs that do satisfy these conditions. Such descriptions may be used for a variety of purposes beside validation, including user interface building, code generation and data integration.
• SHACL 1.2 SPARQL Extensions: This document defines SPARQL-related extensions of the SHACL Shapes Constraint Language. While the Core part of SHACL defines the basic syntax of shapes and the most common constraint components supported by SHACL, the SPARQL-related extensions cover features that extend the expressiveness of Core by means of SPARQL. In particular, this document defines how constraints and constraint components can be defined using SPARQL.

Today the Accessible Rich Internet Applications Working Group published the following two documents as W3C Proposed Recommendations:

• Digital Publishing WAI-ARIA Module 1.1: Enabling users of assistive technologies to find their way through web content requires embedding semantic metadata about web document structural divisions. This is particularly important for structural divisions of long-form documents and goes along with embedding semantic metadata about web-application widgets and behaviors for assistive technologies. This specification defines a set of WAI-ARIA roles specific to helping users of assistive technologies navigate through such long-form documents. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview.
• Digital Publishing Accessibility API Mappings 1.1 defines how user agents map the Digital Publishing WAI-ARIA Module markup to platform accessibility APIs. It is intended for user agent developers responsible for accessibility in their user agent so that they can support the accessibility content produced for digital publishing.

The World Wide Web Consortium (W3C) published the Authorized French Translation of Web Content Accessibility Guidelines (WCAG) 2.2, Regles pour l’accessibilite des contenus Web (WCAG) 2.2. The Lead Translation Organization for this Authorized Translation was Access42.

Other translations of accessibility resources — including non-technical and educational resources — are listed in All WAI Translations.

W3C Web Accessibility Initiative ( WAI) particularly encourages the development of Authorized Translations of WCAG 2.2 and other technical specifications to facilitate their adoption and implementation internationally. For information on developing an Authorized Translation, please see Policy for Authorized W3C Translations.

The Web Real-Time Communications Working Group has published WebRTC: Real-Time Communication in Browsers as an updated W3C Recommendation. This document defines a set of ECMAScript APIs in WebIDL to allow media and generic application data to be sent to and received from another browser or device implementing the appropriate set of real-time protocols. This specification is being developed in conjunction with a protocol specification developed by the IETF RTCWEB group and an API specification to get access to local media devices.

The Portable Network Graphics (PNG) Working Group invites implementations of an updated Candidate Recommendation Snapshot of Portable Network Graphics (PNG) Specification (Third Edition). This document describes PNG (Portable Network Graphics), an extensible file format for the lossless, portable, well-compressed storage of static and animated raster images. PNG provides a patent-free replacement for GIF and can also replace many common uses of TIFF. Indexed-color, greyscale, and truecolor images are supported, plus an optional alpha channel. Sample depths range from 1 to 16 bits.

PNG is designed to work well in online viewing applications, such as the World Wide Web, so it is fully streamable with a progressive display option. PNG is robust, providing both full file integrity checking and simple detection of common transmission errors. Also, PNG can store color space data for improved color matching on heterogeneous platforms.

This specification defines two Internet Media Types, image/png and image/apng.

Comments are welcome via the GitHub issues by 13 May 2025.

The Timed Text Working Group has published Dubbing and Audio description Profiles of TTML2 as a W3C Candidate Recommendation. This document defines DAPT, a TTML-based file format for the exchange of timed text content in dubbing and audio description workflows.

Comments are welcome via GitHub issues by 8 April 2025.

Accessibility Roles and Responsibilities Mapping (ARRM) is published as a first draft Web Accessibility Initiative (WAI) resource. ARRM helps your team create more accessible digital products and services. ARRM provides an approach for defining roles, tasks, and responsibilities for meeting Web Content Accessibility Guidelines ( WCAG). If you would like to be involved in developing ARRM, we encourage you to join the ARRM Community Group.