<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
  <channel>
    <language>en</language>
    <title>W3C - News</title>
    <description>W3C News</description>
    <pubDate>Fri, 23 Oct 2026 15:11:01 +0000</pubDate>
    <generator>Laminas_Feed_Writer 2 (https://getlaminas.org)</generator>
    <link>https://www.w3.org/news/</link>
    <atom:link rel="self" type="application/rss+xml" href="https://www.w3.org/news/feed/"/>
    <item>
      <title>W3C and the State of the Web in the AI Era</title>
      <description><![CDATA[This W3C paper from the Strategy Team is intended to foster discussion in the technical community at TPAC — the most important W3C community event of the year — about how the W3C technical agenda for the web needs to evolve based on the rise of AI agents. It is part of building a consistent, coherent shared vision for evolving the web, starting with AI.]]></description>
      <pubDate>Wed, 21 Oct 2026 09:56:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/w3c-and-the-state-of-the-web-in-the-ai-era/</link>
      <guid>https://www.w3.org/news/2026/w3c-and-the-state-of-the-web-in-the-ai-era/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>W3C's VP Technical Strategy, Philippe Le Hegaret wrote "<a href="https://www.w3.org/2026/10/w3c-and-state-of-web-in-ai-era.html">W3C and the State of the Web in the AI Era</a>", a document putting together the observations and findings of the <a href="https://www.w3.org/staff/strat/">W3C Strategy Team</a> about how the W3C technical agenda for the web needs to evolve based on the rise of AI agents. It is part of building a consistent, coherent <a href="https://www.w3.org/Member/bod/strategy/#goal-4-build-a-consistent-coherent-shared-vision-for-evolving-the-web">shared vision for evolving the web</a>, starting with AI.&nbsp;</p><p>W3C needs to position itself as the venue where AI and web stakeholders discuss the risks and opportunities of this evolution of web user agents to develop responsible technology standards that align with W3C’s vision for the web. <a href="https://www.w3.org/TR/w3c-vision/#vision-web">W3C’s core vision</a> is to develop the web for all humanity: we have to keep humanity at the center of the web while allowing AI agents to act on their behalf.</p><p>This paper is intended to foster discussion in the technical community at TPAC — the most important W3C community event of the year.&nbsp;</p><p>In addition to outlining our understanding of how current and emerging AI technologies intersect with the W3C's roadmap this document can help <a href="https://www.w3.org/news-events/tpac/2026/">TPAC 2026</a> participants prepare for the many discussions on the agentic web that will take place in group meetings, a mini-Workshop, and breakouts. This paper does include some early recommendations that we expect to socialize during TPAC and we seek community feedback.</p><p>This report will be presented during the <a href="https://www.w3.org/events/meetings/f002d43a-d39c-447b-bf85-e99d87a11cfa/">Web and AI Interest Group session on 29 October</a> and feedback is also welcome to <a href="https://lists.w3.org/Archives/Public/public-webai/">public-webai@w3.org</a> and the <a href="https://github.com/w3c/webai-roadmap/issues">w3c/webai-roadmap repository</a>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>First Public Working Draft: Animation Triggers</title>
      <description><![CDATA[Defines CSS properties and an API for creating mechanisms that affect animation playback, based on DOM events resulting from user interaction, or on entry/exit of ranges on animation timelines.]]></description>
      <pubDate>Tue, 20 Oct 2026 05:55:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/first-public-working-draft-animation-triggers/</link>
      <guid>https://www.w3.org/news/2026/first-public-working-draft-animation-triggers/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/css">CSS Working Group</a> has published a First Public Working Draft of <a href="https://www.w3.org/TR/2026/WD-animation-triggers-1-20261020/">Animation Triggers</a>. It defines CSS properties and an API for creating mechanisms that affect animation playback, based on DOM events resulting from user interaction, or on entry/exit of ranges on animation timelines.&nbsp;</p><p><a href="https://www.w3.org/TR/CSS/">CSS</a> is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, etc.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>First Draft Notes: Verifiable Credential Threat Models</title>
      <description><![CDATA[The Verifiable Credentials Working Group has published a series of W3C Working Group Note Drafts for threat models.]]></description>
      <pubDate>Thu, 08 Oct 2026 08:32:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/first-draft-notes-verifiable-credential-threat-models/</link>
      <guid>https://www.w3.org/news/2026/first-draft-notes-verifiable-credential-threat-models/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/vc">Verifiable Credentials Working Group</a> has published a series of W3C Working Group Note Drafts for threat models. All identify and analyze security and privacy threats specific to their respective recommendation-track documents:</p><ul><li><a href="https://www.w3.org/TR/2026/DNOTE-vc-recognized-entities-threat-model-1.0-20261008/">Recognized Entities Threat Model v1.0</a></li><li><a href="https://www.w3.org/TR/2026/DNOTE-vc-data-integrity-threat-model-1.1-20261008/">Data Integrity Threat Model v1.1</a></li><li><a href="https://www.w3.org/TR/2026/DNOTE-vc-barcodes-threat-model-1.0-20261008/">Verifiable Credential Barcodes Threat Model v1.0</a></li><li><a href="https://www.w3.org/TR/2026/DNOTE-vc-render-method-threat-model-1.0-20261008/">Verifiable Credentials Render Method Threat Model v1.0</a></li><li><a href="https://www.w3.org/TR/2026/DNOTE-vcalm-threat-model-1.0-20261008/">VCALM Threat Model v1.0</a></li></ul><p>The working group welcomes comments via GitHub repository issues; the respective repository URL-s can be found in the header of each document.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>W3C issues press release about developing Verifiable Credential Barcodes</title>
      <description><![CDATA[In a press release we present the concept of real-time revocation that is being developed in the W3C Verifiable Credentials Barcodes specification to protect physical documents.]]></description>
      <pubDate>Wed, 07 Oct 2026 17:50:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/w3c-issues-press-release-about-developing-verifiable-credential-barcodes/</link>
      <guid>https://www.w3.org/news/2026/w3c-issues-press-release-about-developing-verifiable-credential-barcodes/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>Recently the data theft of approximately 160 million drivers licenses from the US and Canada was reported and unfortunately, identity thieves will use this data to impersonate victims. Real-time revocation is needed to protect individuals against identity theft. The future of physical document security is being decided as we speak. W3C Verifiable Credential Barcodes are the solution — and the technology is open and free for all to use. The Verifiable Credential Barcodes technology we are building in the W3C Verifiable Credentials Working Group is already protecting millions of people from identity theft and fraud, with the potential to protect billions more. We want to make sure that government organizations and policymakers know that there is a free and open solution to this problem that is being designed for the public good.</p><p>Learn more in our press release: <a href="https://www.w3.org/press-releases/2026/data-breaches-identity-theft-and-revocation-a-real-world-case-study-on-why-w3c-is-developing-verifiable-credential-barcodes/">Data breaches, identity theft, and revocation: a real-world case study on why W3C is developing Verifiable Credential Barcodes</a>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Updated Candidate Recommendation: Scalable Vector Graphics (SVG) 2</title>
      <description><![CDATA[The SVG Working Group published Scalable Vector Graphics (SVG) 2 as a Candidate Recommendation Snapshot and invites implementations.]]></description>
      <pubDate>Tue, 06 Oct 2026 10:21:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/updated-candidate-recommendation-scalable-vector-graphics-svg-2/</link>
      <guid>https://www.w3.org/news/2026/updated-candidate-recommendation-scalable-vector-graphics-svg-2/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/svg/">SVG Working Group</a> invites implementations of an updated Candidate Recommendation Snapshot of <a href="https://www.w3.org/TR/2026/CR-SVG2-20261006/">Scalable Vector Graphics (SVG) 2</a>.</p><p>This is a fresh version of SVG2 with corrections, clarifications and improvements for more interoperability, in particular in implementations in web browsers.</p><p>This specification defines the features and syntax for Scalable Vector Graphics (SVG) Version 2. SVG is a language based on XML for describing two-dimensional vector and mixed vector/raster graphics. SVG content is stylable, scalable to different display resolutions, and can be viewed stand-alone, mixed with HTML content, or embedded using XML namespaces within other XML languages. SVG also supports dynamic changes; script can be used to create interactive documents, and animations can be performed using declarative animation features or by using script.</p><p>To help the group continue its work in updating this widely-used technology, comments are welcome via <a href="https://github.com/w3c/svgwg/issues/">Github issues</a> by 1<strong> December 2026</strong>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Consortium Members elect Board of Directors</title>
      <description><![CDATA[World Wide Web Consortium Members have elected seven individuals to the World Wide Web Consortium, Inc. Board of Directors]]></description>
      <pubDate>Mon, 28 Sep 2026 12:47:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/consortium-members-elect-board-of-directors/</link>
      <guid>https://www.w3.org/news/2026/consortium-members-elect-board-of-directors/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>We are pleased to announce that W3C Consortium Members have elected the following seven people, listed in alphabetical order, to the World Wide Web Consortium, Inc. <a href="https://www.w3.org/groups/other/board/">Board of Directors</a>:</p><ul><li>Koichi Moriyama</li><li>Chris Needham</li><li>Theresa O'Connor</li><li>Florian Rivoal</li><li>Avneesh Singh</li><li>Léonie Watson</li><li>Hongru (Judy) Zhu</li></ul><p>They join Directors appointed by our current Partners: Dominique Hazaël-Massieux, Chunming Hu, Tatsuya Kurosaka (respectively by ERCIM, France; Beihang University, China; and WCAP, Japan); and Tim Berners-Lee who acts as a non-voting Board member.</p><p>All Board terms are for two years, starting 30 September 2026 until 30 September 2028.</p><p>We thank the 12 <a href="https://www.w3.org/2026/08/bod-nominations.html">candidates</a> who ran in this election.</p><p>The W3C Board of Directors is the governing body of the Consortium. The Board has ultimate authority on its strategic direction, has legal obligations and fiduciary responsibility over W3C as a whole. Directors are formally responsible for the correct running of the organization; this is generally characterized in three broad “fiduciary” duties: (1) a duty of care (to exercise good business judgment of a reasonable person with their experience); (2) duty of loyalty (to serve the best interest of the organization); and (3) a duty of obedience (in accordance with all applicable laws and rules). W3C Board of Directors seats are non-paid positions. Learn more about the <a href="https://www.w3.org/2024/06/w3c-board-of-directors-skills-description.html">W3C Board of Directors responsibilities</a>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>W3C Workshop Report: The Future of ODRL</title>
      <description><![CDATA[W3C is pleased to announce the report from the W3C Workshop on the Future of ODRL, held in July 2026 in London, UK, and online.]]></description>
      <pubDate>Thu, 24 Sep 2026 11:13:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/w3c-workshop-report-the-future-of-odrl/</link>
      <guid>https://www.w3.org/news/2026/w3c-workshop-report-the-future-of-odrl/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>W3C is pleased to announce the <a href="https://www.w3.org/2026/ODRLWS/report.html">report</a> from the <a href="https://www.w3.org/2026/ODRLWS/index.html">W3C Workshop on the Future of ODRL</a>, held in July 2026 in London, UK, and online.</p><p>Bringing together participants from standards organizations, industry, academia and the broader policy, data and rights communities, the workshop covered media, core semantics, banking and finance, data spaces, legal and regulatory applications, and new language features. It was explicitly positioned as a turning point for ODRL.</p><p>The emerging vision is considerably broader than simply producing another revision of the ODRL vocabulary. There was consensus to establish a new W3C ODRL Working Group set to work on ODRL 3.0 as a foundation for machine-readable, interoperable and increasingly machine-actionable policies, capable of operating across sectors and integrating with complementary standards for identity, provenance, legal information, data spaces and digital contracts.</p><p>The workshop’s outcomes can be distilled into the following principal recommendations:</p><ol><li>Establish the new W3C ODRL 3.0 Working Group</li><li>Start with use cases and explicit requirements</li><li>Strengthen the formal semantics of ODRL</li><li>Define conformance for policy-processing software</li><li>Develop a comprehensive conformance test suite</li><li>Adopt modular and potentially multi-level conformance</li><li>Improve usability</li><li>Position ODRL as an interoperability layer</li><li>Investigate integration with complementary standards</li></ol><p>The workshop's closing discussion confirmed that the workshop chairs would draft a Working Group charter. The intention is to socialize the charter at <a href="https://www.w3.org/news-events/tpac/2026/">TPAC 2026</a> in Dublin, with the objective of moving into the next phase of ODRL 3.0 by the end of 2026.</p><p>W3C thanks JP Morgan Chase for hosting the workshop; thanks the <a href="https://www.w3.org/2026/ODRLWS/index.html#program-committee">Program Committee</a>, the <a href="https://www.w3.org/2026/ODRLWS/agenda.html">workshop speakers</a>, and all participants for making this event successful.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>First Public Working Draft: Bitstring Status List v1.1</title>
      <description><![CDATA[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.]]></description>
      <pubDate>Thu, 24 Sep 2026 08:28:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/first-public-working-draft-bitstring-status-list-v1-1/</link>
      <guid>https://www.w3.org/news/2026/first-public-working-draft-bitstring-status-list-v1-1/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/vc">Verifiable Credentials Working Group</a> has published a First Public Working Draft of <a href="https://www.w3.org/TR/2026/WD-vc-bitstring-status-list-1.1-20260924/">Bitstring Status List v1.1</a>. 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.</p><p>Feedback is welcome via <a href="https://github.com/w3c/vc-bitstring-status-list/">GitHub</a>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Group Note Draft: Verifiable Credentials Data Model Threat Model v2.1</title>
      <description><![CDATA[This document describes a threat model for the Verifiable Credentials Data Model specification.]]></description>
      <pubDate>Thu, 24 Sep 2026 08:12:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/group-note-draft-verifiable-credentials-data-model-threat-model-v2-1/</link>
      <guid>https://www.w3.org/news/2026/group-note-draft-verifiable-credentials-data-model-threat-model-v2-1/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/vc">Verifiable Credentials Working Group</a> has published the first draft of a Group Note titled <a href="https://www.w3.org/TR/2026/DNOTE-vc-data-model-threat-model-2.1-20260924/">Verifiable Credentials Data Model Threat Model v2.1</a>. This document describes a threat model for the <a href="https://www.w3.org/TR/vc-data-model/">Verifiable Credentials Data Model specification</a>. It identifies and analyzes security and privacy threats specific to ecosystems in which issuers issue verifiable credentials to holders, who in turn present verifiable presentations to verifiers.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Authorized Translations of WCAG 2.2 and 2.1 in French updated</title>
      <description><![CDATA[W3C has published the updated Authorized French Translations of Web Content Accessibility Guidelines (WCAG) 2.2 and 2.1.]]></description>
      <pubDate>Tue, 22 Sep 2026 08:40:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/authorized-translations-of-wcag-2-2-and-2-1-in-french-updated/</link>
      <guid>https://www.w3.org/news/2026/authorized-translations-of-wcag-2-2-and-2-1-in-french-updated/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The World Wide Web Consortium (W3C) has published updated Authorized French Translations of Web Content Accessibility Guidelines (WCAG):</p><ul><li><a href="https://www.w3.org/Translations/WCAG22-fr-20260922/">Règles pour l’accessibilité des contenus web (WCAG) 2.2</a></li><li><a href="https://www.w3.org/Translations/WCAG21-fr-20260922/">Règles pour l’accessibilité des contenus web (WCAG) 2.1&nbsp;</a></li></ul><p>The Lead Translation Organization for these authorized translations was <a href="https://access42.net">Access42</a>.&nbsp;</p><p>Other translations of accessibility resources, including non-technical and educational resources, are listed in <a href="https://www.w3.org/WAI/translations/">All WAI Translations</a>.&nbsp;</p><p>W3C Web Accessibility Initiative (<a href="https://www.w3.org/WAI/">WAI</a>) 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 <a href="https://www.w3.org/2005/02/TranslationPolicy">Policy for Authorized W3C Translations</a>.</p><p>Translations enable broader adoption of W3C resources and serve worldwide audience across languages and cultures. Explore more <a href="https://www.w3.org/Translations/">W3C translations</a> and learn <a href="https://www.w3.org/Consortium/Translation/">how to contribute to translation efforts</a>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>First Public Working Draft: SHACL 1.2 Inference Rules</title>
      <description><![CDATA[This document defines the Inference Rules support of the SHACL Shapes Constraint Language (SHACL).]]></description>
      <pubDate>Thu, 17 Sep 2026 09:39:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/first-public-working-draft-shacl-1-2-inference-rules/</link>
      <guid>https://www.w3.org/news/2026/first-public-working-draft-shacl-1-2-inference-rules/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/data-shapes">Data Shapes Working Group</a> has published a First Public Working Draft of <a href="https://www.w3.org/TR/2026/WD-shacl12-inference-rules-20260917/">SHACL 1.2 Inference Rules</a>. This document defines the Inference Rules support of the SHACL Shapes Constraint Language (SHACL). While the Core part of SHACL focuses on the basic syntax of shapes and constraint validation of data graphs, the SHACL Inference Rules cover features that can be used to infer new triples from existing triples in the data graph.</p><p>Feedback is welcome via <a href="https://github.com/w3c/data-shapes/">GitHub</a>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>First Public Working Draft: Web Authentication: An API for accessing Public Key Credentials Level 4</title>
      <description><![CDATA[This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users.]]></description>
      <pubDate>Tue, 15 Sep 2026 06:07:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/first-public-working-draft-web-authentication-an-api-for-accessing-public-key-credentials-level-4/</link>
      <guid>https://www.w3.org/news/2026/first-public-working-draft-web-authentication-an-api-for-accessing-public-key-credentials-level-4/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/webauthn/">Web Authentication Working Group</a> has published a First Public Working Draft of <a href="https://www.w3.org/TR/2026/WD-webauthn-4-20260915/">Web Authentication: An API for accessing Public Key Credentials Level 4</a>. This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality. See <a href="https://www.w3.org/TR/2026/WD-webauthn-4-20260915/#changes-since-l3">changes since Web Authentication Level 3</a>.</p><p>Feedback is welcome via <a href="https://github.com/w3c/webauthn/issues">GitHub issues</a>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>W3C opens 2026 community survey</title>
      <description><![CDATA[W3C opens an 8-minute survey until 30 September and seeks community-wide input to get to know our community better, investigate needs, and understand how we can improve.]]></description>
      <pubDate>Fri, 04 Sep 2026 10:29:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/w3c-opens-2026-community-wide-survey/</link>
      <guid>https://www.w3.org/news/2026/w3c-opens-2026-community-wide-survey/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>Following on the success of the surveys of the W3C community over the last few years, we are conducting the W3C 2026 survey to get to know our community better, investigate needs, and understand how we can improve.</p><p>Further to the 2025 survey, we already implemented changes that W3C Members benefit from, such as quarterly onboarding calls and monthly newsletters, to name only a few.</p><p>This year's survey is being run through SurveyMonkey and should take about 8 minutes to complete. It is available to members as well as those who are part of the larger W3C community. Answers are anonymous.</p><ul><li>Links for W3C Members:<ul><li><a href="https://www.surveymonkey.com/r/FFXQNHL">Chinese</a></li><li><a href="https://www.surveymonkey.com/r/8F55Y7K">English</a></li><li><a href="https://www.surveymonkey.com/r/7KFXNFB">Japanese</a></li></ul></li><li>Links for the larger W3C community:<ul><li><a href="https://www.surveymonkey.com/r/83CQVX9">Chinese</a></li><li><a href="https://www.surveymonkey.com/r/FFGP6DL">English</a></li><li><a href="https://www.surveymonkey.com/r/FF9V2DH">Japanese</a></li></ul></li></ul><p>The survey closes on <strong>30 September 2026</strong>. We look forward to hearing from you!</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Web Authentication: An API for accessing Public Key Credentials Level 3 is now a W3C Recommendation</title>
      <description><![CDATA[This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users.]]></description>
      <pubDate>Tue, 25 Aug 2026 06:44:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/web-authentication-an-api-for-accessing-public-key-credentials-level-3-is-now-a-w3c-recommendation/</link>
      <guid>https://www.w3.org/news/2026/web-authentication-an-api-for-accessing-public-key-credentials-level-3-is-now-a-w3c-recommendation/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/webauthn/">Web Authentication Working Group</a> is pleased to publish <a href="https://www.w3.org/TR/2026/REC-webauthn-3-20260825/">Web Authentication: An API for accessing Public Key Credentials Level 3</a> as a W3C Recommendation.</p><p>This specification defines an API enabling the creation and use of strong, attested, scoped, public key-based credentials by web applications, for the purpose of strongly authenticating users. Conceptually, one or more public key credentials, each scoped to a given WebAuthn Relying Party, are created by and bound to authenticators as requested by the web application. The user agent mediates access to authenticators and their public key credentials in order to preserve user privacy. Authenticators are responsible for ensuring that no operation is performed without user consent. Authenticators provide cryptographic proof of their properties to Relying Parties via attestation. This specification also describes the functional model for WebAuthn conformant authenticators, including their signature and attestation functionality.&nbsp;</p><p>Level 3 is the successor to Web Authentication Level 2. New features will be developed in Level 4.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Patent Advisory Group recommends continuing work on Open Screen Application Protocol</title>
      <description><![CDATA[W3C launches a Patent Advisory Group (PAG) to resolve issues in the event a patent has been disclosed that may be essential, but is not available under the W3C Royalty-Free licensing terms.]]></description>
      <pubDate>Mon, 24 Aug 2026 13:19:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/patent-advisory-group-recommends-continuing-work-on-open-screen-application-protocol/</link>
      <guid>https://www.w3.org/news/2026/patent-advisory-group-recommends-continuing-work-on-open-screen-application-protocol/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/2025/06/secondscreen-pag/">Second Screen Working Group Patent Advisory Group</a> (PAG), launched in September 2025, has published a <a href="https://www.w3.org/2025/06/secondscreen-pag/report.html">report</a> recommending that W3C continue work on the Open Screen Application Protocol. W3C <a href="https://www.w3.org/policies/patent-policy/#sec-Exception">launches a PAG</a> to resolve issues in the event a patent has been disclosed that may be essential, but is not available under the <a href="https://www.w3.org/policies/patent-policy/#sec-Requirements">W3C Royalty-Free licensing terms</a>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>First Public Working Draft: The Profiles Vocabulary</title>
      <description><![CDATA[The Profiles Vocabulary is an RDF vocabulary created to allow the machine-readable description of profiles of specifications for information resources.]]></description>
      <pubDate>Thu, 20 Aug 2026 05:44:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/first-public-working-draft-the-profiles-vocabulary/</link>
      <guid>https://www.w3.org/news/2026/first-public-working-draft-the-profiles-vocabulary/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/dx">Dataset Exchange Working Group</a> has published today a First Public Working Draft of <a href="https://www.w3.org/TR/2026/WD-dx-prof-1.0-20260820/">The Profiles Vocabulary</a>. The Profiles Vocabulary is an RDF vocabulary created to allow the machine-readable description of profiles of specifications for information resources. It can be used to describe profile hierarchies wherein profiles of specifications may themselves have profiles indicated. It can also be used to link together multiple profile resources that make up a profile - guidelines, validation tools, schemas, term lists and so on - and it allows for those profile resources to be described with formats, roles, and digital artifacts.</p><p style="text-align:center;">The namespace for PROF terms is <code>http://www.w3.org/ns/dx/prof/</code> .<br>The PROF vocabulary, defined in OWL and encoded in RDF Turtle, is available at <a href="https://www.w3.org/TR/2026/WD-dx-prof-1.0-20260820/rdf/prof.ttl">prof.ttl</a> .</p><p>Feedback is welcome via <a href="https://github.com/w3c/dx-prof/">GitHub w3c/dx-prof</a>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Group Note Draft: Web Sustainability Guidelines (WSG) Impact Ratings</title>
      <description><![CDATA[This document describes the impact ratings provided alongside Web Sustainability Guidelines (WSG).]]></description>
      <pubDate>Tue, 18 Aug 2026 07:59:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/group-note-draft-web-sustainability-guidelines-wsg-impact-ratings/</link>
      <guid>https://www.w3.org/news/2026/group-note-draft-web-sustainability-guidelines-wsg-impact-ratings/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/ig/sustainableweb">Sustainable Web Interest Group</a> has published the first draft of a Group Note titled <a href="https://www.w3.org/TR/2026/DNOTE-wsg-ir-20260818/">Web Sustainability Guidelines (WSG) Impact Ratings</a>. The Web Sustainability Guidelines (<abbr title="Web Sustainability Guidelines">WSG</abbr> ) <a href="https://w3c.github.io/sustainableweb-impact">Impact Measurement</a> resource defines a framework for assessing the impact of <abbr title="Web Sustainability Guidelines">WSG</abbr> guidelines across three categories: people, planet, and prosperity. Each guideline is assigned an impact rating (indeterminate, low, medium, or high) and a timeframe (short, medium, or long) indicating when the impact is expected to be observed.</p><p>These inputs are used to calculate an impact score for each guideline. The score helps organisations compare guidelines and prioritise actions based on relative impact and timeframe. Higher scores indicate higher impact achieved over a shorter timeframe. The resulting scores are included in the resource.</p><p>Where quantitative measurement is not possible, ratings are based on available research and expert input. Each guideline includes a rationale for its ratings and timeframe, and where appropriate, suggested metrics to support evaluation.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Updated W3C Recommendation: ARIA in HTML</title>
      <description><![CDATA[This specification defines the authoring rules (author conformance requirements) for the use of Accessible Rich Internet Applications (WAI-ARIA) 1.2 and Digital Publishing WAI-ARIA Module 1.1 attributes on [HTML] elements.]]></description>
      <pubDate>Tue, 11 Aug 2026 15:19:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/updated-w3c-recommendation-aria-in-html/</link>
      <guid>https://www.w3.org/news/2026/updated-w3c-recommendation-aria-in-html/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/aria/">Accessible Rich Internet Applications Working Group</a> has published <a href="https://www.w3.org/TR/2026/REC-html-aria-20260811/">ARIA in HTML</a> as an updated W3C Recommendation. This specification defines the authoring rules (author conformance requirements) for the use of <a href="https://www.w3.org/TR/wai-aria-1.2/">Accessible Rich Internet Applications (WAI-ARIA) 1.2</a> and <a href="https://www.w3.org/TR/dpub-aria-1.1/">Digital Publishing WAI-ARIA Module 1.1</a> attributes on [<a href="https://www.w3.org/TR/2026/REC-html-aria-20260811/#bib-html">HTML</a>] elements. This specification's primary objective is to define requirements for use with conformance checking tools used by authors (i.e., web developers). These requirements will aid authors in their development of web content, including custom interfaces and widgets, which make use of ARIA to complement or extend the features of the host language [<a href="https://www.w3.org/TR/2026/REC-html-aria-20260811/#bib-html">HTML</a>].</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>W3C invites implementations of Decentralized Identifier Resolution (DID Resolution) v1</title>
      <description><![CDATA[This document describes the process of obtaining a DID document and accompanying metadata for a specific DID.]]></description>
      <pubDate>Thu, 06 Aug 2026 09:16:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/w3c-invites-implementations-of-decentralized-identifier-resolution-did-resolution-v1/</link>
      <guid>https://www.w3.org/news/2026/w3c-invites-implementations-of-decentralized-identifier-resolution-did-resolution-v1/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/did">Decentralized Identifier Working Group</a> has published a W3C Candidate Recommendation Snapshot of <a href="https://www.w3.org/TR/2026/CR-did-resolution-1.0-20260806/">Decentralized Identifier Resolution (DID Resolution) v1</a>. Decentralized identifier (DID) resolution is the process of obtaining a DID document and accompanying metadata for a specific DID. The process takes a DID and a set of resolution options as its input and returns a DID document and associated metadata about the resolved document and the resolution request. A resolved DID document is a set of information which enables cryptographically verifiable interactions with the DID subject, including mechanisms such as cryptographic public keys.</p><p>Comments are welcome via <a href="https://github.com/w3c/did-resolution/issues/">GitHub issues</a> by <strong>3 September 2026</strong>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Group Note: Further Aligning W3C's Program of Technical Work with Human Rights</title>
      <description><![CDATA[In this document, the Advisory Board lists examples of how human rights and technical standards setting map to each other, points to existing W3C work in this area, and provides concrete proposals to further the alignment between the W3C’s technical work and human rights.]]></description>
      <pubDate>Tue, 04 Aug 2026 09:16:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/group-note-further-aligning-w3cs-program-of-technical-work-with-human-rights/</link>
      <guid>https://www.w3.org/news/2026/group-note-further-aligning-w3cs-program-of-technical-work-with-human-rights/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The W3C <a href="https://www.w3.org/groups/other/ab">Advisory Board (AB)</a> published a Group Note of <a href="https://www.w3.org/TR/2026/NOTE-furthering-human-rights-20260804/">Further Aligning W3C's Program of Technical Work with Human Rights</a>. There is a clear link between human rights and technical standards setting. In this position paper, the AB lists examples of how the two map, points to existing W3C work in this area, and provides concrete proposals to further the alignment between the W3C’s technical work and human rights.</p><p>This document summarizes the AB’s current thinking, as of 4 August 2026. This Group Note is endorsed by the AB, but is not endorsed by W3C itself nor its Members.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>W3C Invites Implementations of WebTransport</title>
      <description><![CDATA[This document defines a set of ECMAScript APIs in WebIDL to allow data to be sent and received between a browser and server.]]></description>
      <pubDate>Thu, 30 Jul 2026 08:25:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/w3c-invites-implementations-of-webtransport/</link>
      <guid>https://www.w3.org/news/2026/w3c-invites-implementations-of-webtransport/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/webtransport/">WebTransport Working Group</a> has published <a href="https://www.w3.org/TR/2026/CR-webtransport-20260730/">WebTransport</a> as a W3C Candidate Recommendation Snapshot. This document defines a set of ECMAScript APIs in WebIDL to allow data to be sent and received between a browser and server. This specification is being developed in conjunction with protocol specifications developed by the IETF WEBTRANS Working Group.</p><p>Comments are welcome via <a href="https://github.com/w3c/webtransport/issues/">Github issues</a> by <strong>30 October 2026</strong>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Group Note Draft: Verifiable Credentials Overview v1.1</title>
      <description><![CDATA[The family of W3C Recommendations for Verifiable Credentials, described in this overview document, provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.]]></description>
      <pubDate>Thu, 30 Jul 2026 08:20:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/group-note-draft-verifiable-credentials-overview-v1-1/</link>
      <guid>https://www.w3.org/news/2026/group-note-draft-verifiable-credentials-overview-v1-1/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/vc/">Verifiable Credentials Working Group</a> has published the first draft of a Group Note titled <a href="https://www.w3.org/TR/2026/DNOTE-vc-overview-1.1-20260730/">Verifiable Credentials Overview v1.1</a>. 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, government-issued passports enable us to travel between countries, and trade authorities issue certificates containing various informations on a product. The family of W3C Recommendations for Verifiable Credentials, described in this overview document, provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Group Note Draft: EPUB Accessibility 1.2 Explainer</title>
      <description><![CDATA[The EPUB Accessibility 1.2 Explainer provides information on how to understand and evaluate the accessible publications conformance requirements of EPUB Accessibility 1.2 against reflowable EPUB publications.]]></description>
      <pubDate>Thu, 30 Jul 2026 08:17:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/group-note-draft-epub-accessibility-1-2-explainer/</link>
      <guid>https://www.w3.org/news/2026/group-note-draft-epub-accessibility-1-2-explainer/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/pm/">Publishing Maintenance Working Group</a> has published the first draft of a Group Note titled <a href="https://www.w3.org/TR/2026/DNOTE-epub-a11y-explain-12-20260730/">EPUB Accessibility 1.2 Explainer</a>, which provides information on how to understand and evaluate the accessible publications conformance requirements of <a href="https://www.w3.org/TR/epub-a11y-12/">EPUB Accessibility 1.2</a> against reflowable EPUB publications.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Group Note: WCAG Evaluation Methodology (WCAG-EM) 2.0</title>
      <description><![CDATA[This document describes a methodology with a step-by-step process to evaluate how well digital products conform to Web Content Accessibility Guidelines (WCAG) 2.]]></description>
      <pubDate>Thu, 23 Jul 2026 13:08:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/group-note-wcag-evaluation-methodology-wcag-em-2-0/</link>
      <guid>https://www.w3.org/news/2026/group-note-wcag-evaluation-methodology-wcag-em-2-0/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/ag/">Accessibility Guidelines Working Group</a> has published <a href="https://www.w3.org/TR/2026/NOTE-wcag-em-2-20260723/">WCAG Evaluation Methodology (WCAG-EM) 2.0</a> as a Group Note. This document describes a methodology with a step-by-step process to evaluate how well digital products conform to <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG) 2</a>.&nbsp;</p><p>It provides technology-agnostic guidance to define the evaluation scope, explore the target product, select a representative <a href="https://www.w3.org/TR/2026/NOTE-wcag-em-2-20260723/#dfn-sample-set">sample set</a> from products, evaluate the selected sample set, and report the evaluation findings. This procedure is suitable for use in different evaluation contexts, including self-assessment and third-party evaluation.&nbsp;</p><p>This document does not define feature-specific instructions, as the WCAG success criteria and <a href="https://www.w3.org/WAI/standards-guidelines/wcag/docs/">supporting documents</a> cover those. It also does not define additional WCAG 2 requirements, nor does it replace or supersede them in any way.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>W3C Invites Implementations of EPUB 3.4, EPUB Reading Systems 3.4 and EPUB Accessibility 1.2</title>
      <description><![CDATA[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.]]></description>
      <pubDate>Tue, 21 Jul 2026 09:26:00 +0000</pubDate>
      <link>https://www.w3.org/news/2026/w3c-invites-implementations-of-epub-3-4-epub-reading-systems-3-4-and-epub-accessibility-1-2/</link>
      <guid>https://www.w3.org/news/2026/w3c-invites-implementations-of-epub-3-4-epub-reading-systems-3-4-and-epub-accessibility-1-2/</guid>
      <category><![CDATA[news]]></category>
      <content:encoded><![CDATA[                            <p>The <a href="https://www.w3.org/groups/wg/pm/">Publishing Maintenance Working Group</a> invites implementations of the following three Candidate Recommendation Snapshots:</p><ul><li><a href="https://www.w3.org/TR/2026/CR-epub-34-20260721/">EPUB 3.4</a>: 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 fourth major revision of the standard.</li><li><a href="https://www.w3.org/TR/2026/CR-epub-rs-34-20260721/">EPUB Reading Systems 3.4</a>: This specification defines the conformance requirements for EPUB 3 reading systems — the user agents that render EPUB publications.</li><li><a href="https://www.w3.org/TR/2026/CR-epub-a11y-12-20260721/">EPUB Accessibility 1.2</a>: This specification specifies content conformance requirements for verifying the accessibility of EPUB® Publications. It also specifies accessibility metadata requirements for the discoverability of EPUB publications.</li></ul><p>Comments are welcome via <a href="https://github.com/w3c/epub-specs/issues/">GitHub issues</a> by <strong>19 October 2026</strong>.</p>
                ]]></content:encoded>
      <slash:comments>0</slash:comments>
    </item>
  </channel>
</rss>
