W3C - News

• Authorized Translation of WCAG 2.2 in Brazilian Portuguese

  The World Wide Web Consortium (W3C) published the Authorized Brazilian Portuguese Translation of Web Content Accessibility Guidelines (WCAG) 2.2, Diretrizes de Acessibilidade para Conteúdo 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.

• Updated W3C Recommendation: EPUB 3.3

  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.

• First Public Working Draft: CSS Form Control Styling Level 1

  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.

• First Public Working Draft: ContentEditable

  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.

• Seven Proposed Recommendations published by the Verifiable Credentials Working Group

  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.

• First Public Working Drafts: SHACL 1.2 Core and SHACL 1.2 SPARQL Extensions

  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.

• DPub-ARIA 1.1 and DPub-AAM 1.1 are W3C Proposed Recommendations

  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.

• Authorized Translation of WCAG 2.2 in French

  The World Wide Web Consortium (W3C) published the Authorized French Translation of Web Content Accessibility Guidelines (WCAG) 2.2, Règles pour l’accessibilité 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.

• Updated W3C Recommendation: WebRTC: Real-Time Communication in Browsers

  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.

• Updated Candidate Recommendation: Portable Network Graphics (PNG) Specification (Third Edition)

  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.