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 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.
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).
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.
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.
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.
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.
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.
The CSS Working Group published the CSS Snapshot 2024 as a Group Note. This document collects together into one definition all the specifications that together form the current state of Cascading Style Sheets (CSS) as of 2024. The primary audience is CSS implementers, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate.
When the first CSS specification was published, all of CSS was contained in one document that defined CSS Level 1. CSS Level 2 was defined also by a single, multi-chapter document. However for CSS beyond Level 2, the CSS Working Group chose to adopt a modular approach, where each module defines a part of CSS, rather than to define a single monolithic specification. This breaks the specification into more manageable chunks and allows more immediate, incremental improvement to CSS.
Since different CSS modules are at different levels of stability, the CSS Working Group has chosen to publish this profile to define the current scope and state of Cascading Style Sheets as of 2024.
W3C is working on a deconstructed mini-workshop series to review proposals aimed at combating misinformation on the web. Based on discussions at TPAC 2024 (Originator Profile and Content Authenticity) and in the W3C Strategy Team, there is clear interest in investigating how several proposals in this space can contribute and what standardization support they might need.
The Credible Web Community Group will host this deconstructed mini-workshop series to discuss a project framework for assessing tooling in the authentic web ecosystem. The first session, scheduled for 12 March 2025, will review the framework and discuss how to move proposals to interoperable standards to combat misinformation on the web.
Attendance is free for all participants and is open to the public, whether or not W3C members.
Following the W3C Technical Architecture Group (TAG)'s election results, the W3C Team has chosen and the Advisory Board and Technical Architecture Group have ratified the following appointment to the TAG for the 2025-2027 term: Lola Odelola (unaffiliated W3C Invited Expert)
Among the individuals the W3C Team considered, Lola particularly stands out due to her connections with the developer community and her involvement in making web development available to under-represented parts of the community. Lola also has experience in W3C Working Groups and is an open source contributor.
Per W3C Process Document regarding TAG appointments, this procedure follows a public call for nominations which together with nominations from the W3C Team and Members surfaced a list of several traditional and non-traditional candidates. The Team considered what each on the list would bring to the TAG. In addition to the aspects mentioned in Process, the Team considered cultural diversity and gender diversity.
The Team is confident Lola Odelola brings robust complementary skills to the TAG and thanks her for offering her time to do the important TAG work of stewarding the Web architecture.
About the W3C TAG
The TAG was created in 2001 as a special W3C working group, chartered to steward the Web architecture. To do so, it fulfills 3 missions:
to document and build consensus around principles of Web architecture and to interpret and clarify these principles when necessary;
to resolve issues involving general Web architecture brought to the TAG;
to help coordinate cross-technology architecture developments inside and outside W3C.
The TAG is part of the Horizontal Review Process and reviews a large number of specifications done at W3C and outside, even during their early stage.
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.
Comments are welcome via GitHub issues by 28 February 2025.
The Decentralized Identifier Working Group has published a First Public Working Draft of Decentralized Identifiers (DIDs) v1.1. This document specifies the DID syntax, a common data model, core properties, serialized representations, DID operations, and an explanation of the process of resolving DIDs to the resources that they represent.
Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. They may refer to any subject and have been designed so that they may be decoupled from centralized registries, identity providers, and certificate authorities, so as to enable the controller of a DID to prove control over it without requiring permission from any other party.
The Accessible Platform Architectures (APA) Research Questions Task Force (RQTF) published Collaboration Tools Accessibility User Requirements as a W3C Group Note. The document covers accessibility user needs, requirements, and scenarios for collaborative content creation and development tools. The solutions identified in this document are intended to influence the evolution of future accessibility guidelines, technical specifications, or features of collaboration tools and assistive technologies. They are also relevant to software developers who contribute to developing the collaborative experience.
The Publishing Maintenance Working Group has proposed corrections to the W3C Recommendation of EPUB 3.3. 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 publications and represents the third major revision of the standard.
Proposed corrections are marked in the document. Comments, including implementation experience, are welcome via GitHub through 10 March 2025.
The GPU for the Web Working Group invites implementations of the first Candidate Recommendation Snapshots for the following documents:
WebGPU: Graphics Processing Units, or GPUs for short, have been essential in enabling rich rendering and computational applications in personal computing. WebGPU is an API that exposes the capabilities of GPU hardware for the Web. The API is designed from the ground up to efficiently map to (post-2014) native GPU APIs.
WebGPU Shading Language, also known as WGSL for short: An application using the WebGPU API uses WGSL to express the programs, known as shaders, that run on the GPU. The shading language is tailored for parallel execution and usage on the Web.
Comments are welcome via GitHub issues by 28 February 2025.
The CSS Working Group has published the First Public Working Draft of CSS Display Module Level 4. This module describes how the CSS formatting box tree is generated from the document element tree and defines the display property that controls it.
The CSS Working Group has published the First Public Working Draft of CSS Multi-column Layout Module Level 2. This specification describes multi-column layouts in CSS, a style sheet language for the web. Using functionality described in the specification, content can be flowed into multiple columns with a gap and a rule between them.
Verifiable Credentials Data Model v2.0: Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.
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 a Data Integrity cryptographic suite for use when creating or verifying a digital signature using the twisted Edwards Curve Digital Signature Algorithm (EdDSA) and Curve25519 (ed25519).
Data Integrity ECDSA Cryptosuites v1.0: This specification describes a Data Integrity Cryptosuite 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 (JOSE), Selective Disclosure for JWTs, and CBOR Object Signing and Encryption (COSE) [RFC9052]. This enables the Verifiable Credential data model to be implemented with standards for signing and encryption that are widely adopted.
Comments are welcome via the GitHub issues by 19 January 2025.
The W3C Advisory Committee has elected the following people to fill four seats on the W3C Technical Architecture Group (TAG) starting 1 February 2025: Hadley Beeman, Marcos Caceres, Sarven Capadisli and Xiaocheng Hu. They join continuing TAG participants, Daniel Appelquist, Matthew Atkinson, Dapeng (Max) Liu, Tristan Nitot, Martin Thomson and Jeffrey Yasskin. Tim Berners-Lee is an emeritus member of the TAG and Yves Lafon continues as staff contact. Many thanks to the 7 candidates, and thanks for contributions to the TAG to the departing participants, Amy Guy, Peter Linss (who in addition held the role of TAG co-chair for many years), Theresa O'Connor and Lea Verou, whose terms end at the end of January 2025.
The TAG is a special group within the W3C, chartered under the W3C Process Document, with stewardship of the Web architecture. The mission of the TAG is to build consensus around principles of Web architecture and to interpret and clarify these principles when necessary, to resolve issues involving general Web architecture brought to the TAG, and to help coordinate cross-technology architecture developments inside and outside W3C. The Members of the TAG participate as individual contributors, not as representatives of their organizations. TAG participants use their best judgment to find the best solutions for the Web, not just for any particular network, technology, vendor, or user. Learn more about the TAG.