# W3C Published articles for W3C. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## W3C Newsletter - October 2026 DevFeed: [W3C Newsletter - October 2026]() Original publisher: [Read original article]() Author: Dominique Hazaël-Massieux, W3C President and Interim CEO Published: 2026-11-05T10:57:00Z Content type: news Language: en Sources: [W3C]() Topics: [W3C](), [Web](), [meetings](), [Machine learning](), [web animation]() Tags: [2026](), [3](), [about](), [accelerated](), [adoption](), [ai](), [blogs](), [corporate](), [credentials](), [highlights](), [identity](), [improvements](), [information](), [infrastructure](), [more](), [newsletter](), [october](), [october-2026](), [progress](), [standardization](), [w3c](), [work]() ### AI overview At TPAC 2026 in Dublin, W3C reported broad participation and progress on AI, identity, and standards infrastructure. Discussions reached broad consensus on a proposed Agentic Web Working Group, whose draft charter would advance WebMCP ideas toward a Recommendation-track deliverable and include identity and delegation. The Web Machine Learning Working Group continued work on the WebNN API and heard reports of implementation and adoption. W3C also drafted an AI policy for Advisory Board review and may revisit policies for meeting transcripts and recordings. Infrastructure updates included activity pages for groups, plans to investigate Matrix as an alternative for real-time chat, and improved mailing-list archive navigation. Other milestones included a pilot to develop and maintain a WebMCP polyfill and an updated SVG2 Candidate Recommendation Snapshot. This newsletter highlights selected developments and does not claim to cover all TPAC discussions. ### Source excerpt W3C President and Interim CEO Dominique Hazaël-Massieux shares timely and notable highlights and information selected from the busy and prolific work last month at W3C such as TPAC 2026, AI @ W3C, progress on Identity and Credentials, further improvements to W3C infrastructure for standardization and more. ## An Empirical Evaluation of Signing and Verification Performance of Verifiable Credential Formats: A Cross-Language Benchmark of SD-JWT VC, W3C VCDM, and mdoc DevFeed: [An Empirical Evaluation of Signing and Verification Performance of Verifiable Credential Formats: A Cross-Language Benchmark of SD-JWT VC, W3C VCDM, and mdoc]() Original publisher: [Read original article]() Author: Naohiro Fujie (MIRAI Design Laboratory, ITOCHU Techno-Solutions Corporation, OpenID Foundation Japan), Shigeya Suzuki (Global Research Institute, Keio University) Published: 2026-11-03T05:00:00Z Content type: article Language: en Sources: [arXiv: Cryptography and Security]() Topics: [Benchmark](), [ECDSA](), [ed25519]() Tags: [benchmark](), [cross](), [cs-cr](), [cs-pf](), [evaluation](), [formats](), [jwt](), [performance](), [signing](), [vc](), [verification](), [w3c]() ### AI overview Across four environments, W3C VCDM was consistently slower than mdoc and SD-JWT VC for issuing, selectively presenting, and verifying a credential, while the relative ordering of mdoc and SD-JWT VC was not robust. In the Node.js cloud VM example disclosing 5 of 20 attributes, total times were 0.534 ms for W3C VCDM, 0.265 ms for mdoc, and 0.298 ms for SD-JWT VC. The authors attribute much of VCDM's gap to RDFC-1.0 canonicalization, performed six times per exchange; replacing it with JCS brought verification within 5% of SD-JWT VC in three environments and 12% in the fourth. Selective presentation also differs by cryptosuite: eddsa-rdfc-2022 re-signs the subset, whereas ecdsa-sd-2023 preserves the issuer signature but has higher reported issuance and derivation/verification costs. Production education schemas raised canonicalization costs 31-49-fold over a simple credential. Measurements stop at the issuer signature check. ### Source excerpt arXiv:2611.03493v1 Announce Type: new Abstract: We compare the signing and verification performance of three Verifiable Credential (VC) formats--SD-JWT VC; the W3C Verifiable Credentials Data Model 2.0 with a Data Integrity cryptosuite (W3C VCDM); and mdoc (ISO/IEC 18013-5)--over one scope: issue, present with selective disclosure, verify. Node.js, Go and Python implementations ran in four environments, one a cloud VM (N=2,000 across five runs; medians of each statistic and the spread). For an end-to-end exchange disclosing 5 of 20 attributes, the total (issue, present, verify) on Node.js in the cloud VM is 0.265 ms for mdoc, 0.298 ms for SD-JWT VC and 0.534 ms for W3C VCDM. The four span a factor of five in speed; across them W3C VCDM takes 1.73--2.04x mdoc and 1.57--1.79x SD-JWT VC--at least five times our 10% band--and the ordering survives unifying the algorithm on Ed25519 and P-256. The mdoc--SD-JWT VC difference is not robust: the totals differ by 12%, 28%, 19% and 10% in the four environments, and at verification mdoc is the slower in one of them. RDFC-1.0 canonicalization produces the gap: the cryptosuite canonicalizes twice per operation, so one exchange canonicalizes six times. We attribute that cost to the specification rather than to a library mainly by replacing RDFC-1.0 with JCS, which brings W3C VCDM verification to within 5% of SD-JWT VC in three environments and within 12% in the fourth; three implementations in three languages agree, though they share a lineage. Because eddsa-rdfc-2022 has no derivation step, presenting a subset re-signs it; ecdsa-sd-2023, which preserves the issuer signature, costs 3.4 ms to issue and 1.5--2.4 ms to derive and verify there. With production education schemas, canonicalization costs 31--49x a simple credential across the four, and blank node labeling is not the driver. The measured path ends at the issuer signature check. ## Historical www-talk archives made complete DevFeed: [Historical www-talk archives made complete]() Original publisher: [Read original article]() Author: Gerald Oskoboiny, Principal DevOps Engineer Published: 2026-10-28T14:07:00Z Content type: news Language: en Sources: [W3C]() Topics: [Self Hosted Archiving and Digital Preservation (DP)](), [Web](), [W3C](), [releases](), [Forms](), [web graphics]() Tags: [announce](), [announcement](), [apache](), [archive](), [blogs](), [bugs](), [cern](), [community](), [complete](), [consensus](), [content](), [contents](), [contribute](), [development](), [list](), [messages](), [october](), [systems](), [talk](), [the-web](), [w3c](), [web]() ### AI overview W3C completed its www-talk archives by reconstructing messages from 1993 through February 1995, a period previously missing because no reliable complete copy existed. The team analyzed and combined partial copies, reformatted them for its archive software, regenerated the web archive, and added redirects to preserve existing links. The restored messages offer a record of early Web development, including discussions of HTML forms and the IMG tag, browsers such as Mosaic and Lynx, CGI, robot identification and exclusion, security, and URI standards. The excerpt names notable threads but does not provide their full contents. ### Source excerpt W3C's archives of the www-talk mailing list are now complete, back to its creation in October 1991. This post lists some of the more interesting messages in the early development of the Web. ## W3C launches second pilot of program to support Open Source projects DevFeed: [W3C launches second pilot of program to support Open Source projects]() Original publisher: [Read original article]() Author: Ian Jacobs, Strategy Team Published: 2026-10-27T11:50:00Z Content type: news Language: en Sources: [W3C]() Topics: [W3C](), [polyfill](), [Open Source](), [open source maintenance]() Tags: [agentic](), [agents](), [assistive-technologies](), [blogs](), [community](), [coverage](), [declarative](), [developers](), [early-stage](), [events](), [experiment](), [feedback](), [governance](), [interoperability](), [javascript](), [lifecycle](), [npm](), [open-source](), [pilot](), [polyfill](), [w3c](), [webmcp]() ### AI overview W3C's second Open Source Program pilot is a polyfill for the incubating WebMCP API, intended to improve interoperability and let developers experiment while the specification evolves. WebMCP lets developers expose application functionality as JavaScript tools with natural-language descriptions and structured schemas for agents, browser agents, and assistive technologies. Initial goals are to publish the polyfill as an npm package, advance lifecycle events and declarative support, track specification changes, and maintain Web Platform Tests coverage. If WebMCP moves into standardization and native implementations provide interoperable support, the polyfill would be phased out. W3C also launched a Community Group to guide the program's growth and governance; participation is open without W3C Membership. ### Source excerpt In this blog post, Ian Jacobs, Strategy Team, introduces the second pilot of the W3C Open Source program: a polyfill for the WebMCP API. WebMCP is a new JavaScript interface that allows web developers to expose their web application functionality as "tools". ## Improved thread navigation in W3C's mailing list archives DevFeed: [Improved thread navigation in W3C's mailing list archives]() Original publisher: [Read original article]() Author: Gerald Oskoboiny, Principal DevOps Engineer Published: 2026-10-19T09:03:00Z Content type: article Language: en Sources: [W3C]() Topics: [W3C](), [State of the Web](), [interactive web design]() Tags: [blogs](), [browser](), [feature](), [github](), [html](), [implementation](), [improvements](), [infrastructure](), [javascript](), [navigation](), [open-source](), [open-source-software](), [software](), [source](), [systems](), [w3c]() ### AI overview W3C added an experimental thread panel and a flattened view to its mailing list archives, making it easier to navigate message threads. The implementation preserves static, cacheable archive pages and shared message URLs without requiring server side scripts. ### Source excerpt A new feature is available in W3C's mailing list archives, aiming to make it easier to read and navigate message threads. ## Announcing MCP support in Apigee hybrid: agentic tools that run in your own cluster DevFeed: [Announcing MCP support in Apigee hybrid: agentic tools that run in your own cluster]() Original publisher: [Read original article]() Author: Ayo Salawu; Sundar Ramamoorthy Published: 2026-10-15T02:28:36.906458Z Content type: release Language: en Sources: [Google Developers Blog]() Topics: [MSP MCP](), [AI Infrastructure](), [OpenAPI Specification](), [internal developer platform]() Tags: [apigee](), [infrastructure](), [kubernetes](), [mcp](), [openapi](), [security](), [traffic](), [w3c]() ### AI overview Apigee hybrid 1.17.0 adds MCP support with its data plane running inside a customer's Kubernetes cluster. OpenAPI specifications define discoverable tools, while traffic stays within the cluster and configuration is retrieved from the control plane. The release also describes tracing MCP calls across clients, Apigee, and backend services. ### Source excerpt Apigee hybrid 1.17.0 introduces native Model Context Protocol (MCP) support, enabling the MCP data plane to run directly within your own Kubernetes cluster. This architecture ensures that AI agent request traffic and tool execution remain entirely inside your infrastructure while pulling configuration updates from the control plane. Developers can expose OpenAPI 3.0.x specifications as discoverable MCP tools, leverage existing security policies and API products, and trace end-to-end requests using W3C trace context headers. ## A release gate for AI agent incidents DevFeed: [A release gate for AI agent incidents]() Original publisher: [Read original article]() Author: Morissa Schwartz Published: 2026-10-14T17:10:22Z Content type: article Language: en Sources: [SD Times]() Topics: [Agent Skills](), [human in the loop agent](), [User interface design](), [Access Control]() Tags: [accessibility](), [agents-in-production](), [ai-agents](), [authorization](), [deeper-look](), [deployment](), [nist](), [policy](), [w3c](), [web-content-accessibility]() ### AI overview The article proposes a four-part release gate for AI agents before they can act on production systems: preserve evidence behind consequential actions, name people who can intervene, test accessible recovery workflows, and define prohibited inferences from accommodation information. It recommends attaching inspectable evidence to release records and disabling actions with unresolved control gaps. ### Source excerpt Consider a hypothetical support agent that processes a cancellation request using an outdated policy. The message sounds helpful. The account update succeeds. The customer loses access, and the person reviewing the incident has to work out which policy the agent retrieved, who authorized the change, and how to restore the account. That sequence gives a... ... continue reading The post A release gate for AI agent incidents appeared first on SD Times. ## Introducing group activity pages DevFeed: [Introducing group activity pages]() Original publisher: [Read original article]() Author: Jean-Guilhem Rouel, Senior Principal DevOps Engineer Published: 2026-10-14T10:28:00Z Content type: news Language: en Sources: [W3C]() Topics: [Website](), [groupby](), [software-development]() Tags: [2026](), [blogs](), [pages](), [systems](), [that-s](), [w3c](), [work]() ### AI overview W3C has introduced beta activity pages that bring a group's recent work together month by month, including participation, meetings, publications, reports and GitHub activity. The pages show the latest three months, offer yearly archives and filters, and may later add faster GitHub updates, more data sources and an API. W3C is seeking feedback on the pages and their future uses. ### Source excerpt W3C groups now have an Activity page that shows, month by month, their charters, publications, meetings, participants and GitHub work in one place. The pages are in beta, and we would like your feedback. ## EPUB 3.4 adds roll layouts and updates accessibility and media support DevFeed: [EPUB 3.4 adds roll layouts and updates accessibility and media support]() Original publisher: [Read original article]() Author: Wendy Reid, W3C Publishing Maintenance Working Group Invited Expert Published: 2026-10-12T17:06:00Z Content type: release Language: en Sources: [W3C]() Topics: [Internationalization (i18n)](), [aria]() Tags: [a11y](), [accessibility](), [aria](), [blogs](), [digital-publishing](), [documentation](), [w3c]() ### AI overview W3C's Publishing Maintenance Working Group describes the candidate EPUB 3.4 update, including a vertical roll layout for digital comics, additional media types and codecs, accessibility metadata changes, and features marked outdated or deprecated. EPUBCheck 5.4.0 adds checks for the new specification. Existing EPUB files that conform to earlier versions remain compatible. ### Source excerpt The Publishing Maintenance Working Group at W3C has been quietly working on yet another update for the EPUB3 standard, and we're excited to share what we have been up to. Our goal is to not only maintain the EPUB standard, but do our best to keep it in line with the needs of industry, and this update does exactly that. Your existing books do not need to change, if they conform to previous EPUB versions, they will conform to EPUB 3.4. Content you create today will automatically conform as well. ## Cloudflare Traces Turns the Proxy Layer into OpenTelemetry Spans, with New Volume-Based Pricing DevFeed: [Cloudflare Traces Turns the Proxy Layer into OpenTelemetry Spans, with New Volume-Based Pricing]() Original publisher: [Read original article]() Author: Steef-Jan Wiggers Published: 2026-10-10T07:12:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [OpenTelemetry](), [tracing](), [Cloudflare](), [ai observability]() Tags: [ai](), [ai-ml-data-engineering](), [architecture](), [architecture-design](), [cloud](), [cloudflare](), [cloudflare-traces-open-beta](), [customer](), [development](), [devops](), [distributed-tracing](), [ml-data-engineering](), [news](), [observability](), [opentelemetry](), [traces](), [w3c]() ### AI overview Cloudflare has opened Traces in beta, adding automatic OpenTelemetry spans across proxy request processing, including security rules, transformations, caching, routing, Workers, and origin handling. It supports W3C trace context propagation, rule-based sampling, and OTLP export. Pricing will shift to ingestion and retention volume on December 1, 2026. ### Source excerpt Cloudflare has put Traces into open beta, extending automatic tracing from Workers to security rules, transformations, cache, routing and origin handling as OpenTelemetry spans. Traces accept and forward W3C traceparent headers, and Trace Rules allow targeted sampling. Pricing moves to ingestion and retention volume from December 1. By Steef-Jan Wiggers ## What's new in the W3C Website Design System DevFeed: [What's new in the W3C Website Design System]() Original publisher: [Read original article]() Author: Nicola Saunders, Front-End Lead Developer at Studio 24 Published: 2026-10-09T07:58:00Z Content type: release Language: en Sources: [W3C]() Topics: [Design system](), [User interface design](), [web design](), [human centric design]() Tags: [blogs](), [cms](), [css](), [css-custom-properties](), [design](), [design-system](), [github](), [systems](), [w3c](), [website]() ### AI overview The W3C Website Design System's September 2026 update revises typography, spacing, markup, cards, and list and table styles. It replaces Normalize.css with a smaller baseline stylesheet and removes constraints that made the system harder to use outside the CMS. The changes aim to make the system more flexible and its markup simpler. ### Source excerpt A significant update to the W3C Website Design System was published at the end of September 2026. Here's what changed and why. ## W3C Newsletter - September 2026 DevFeed: [W3C Newsletter - September 2026]() Original publisher: [Read original article]() Author: Dominique Hazaël-Massieux, W3C President and Interim CEO Published: 2026-10-02T10:01:00Z Content type: news Language: en Sources: [W3C]() Topics: [W3C](), [AI-enhanced product development](), [Web Accessibility (a11y)](), [Web]() Tags: [2026](), [accessibility](), [ai](), [ai-agents](), [blogs](), [corporate](), [newsletter](), [september-2026](), [w3c]() ### AI overview The September 2026 W3C newsletter reports on governance, AI and web standards work, accessibility, an open-source program pilot, and upcoming TPAC discussions. It highlights proposals for web pages and applications to support LLMs and AI agents, WebDriver discussions on agent-driven browsers and testing, and progress on WCAG 3.0. ### Source excerpt W3C President and Interim CEO Dominique Hazaël-Massieux shares timely and notable highlights and information selected from the busy and prolific work last month at W3C. ## Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments DevFeed: [Stateless MCP Removes Session Affinity Requirements for AWS Server Deployments]() Original publisher: [Read original article]() Author: Leela Kumili Published: 2026-09-25T12:58:00Z Content type: news Language: en Sources: [InfoQ]() Topics: [Model Context Protocol](), [cloud-infrastructure](), [autoscaling](), [session affinity](), [Routing (disambiguation)](), [AWS Lambda](), [Server](), [telemetry](), [tracing](), [retry](), [Security](), [context]() Tags: [ai](), [ai-architecture](), [ai-ml-data-engineering](), [architecture-design](), [aws](), [aws-lambda](), [aws-stateless-mcp](), [deployment](), [development](), [distributed-systems](), [distributed-tracing](), [frameworks](), [idempotency](), [infrastructure](), [load-balancer](), [load-balancing](), [mcp](), [microservices](), [ml-data-engineering](), [model-context-protocol](), [model-context-protocol-mcp](), [news](), [observability](), [opentelemetry](), [retries](), [routing](), [scaling](), [serverless](), [servers](), [session-affinity](), [w3c]() ### AI overview AWS explains that the latest Model Context Protocol specification removes protocol-level sessions, sticky-session requirements, and session storage for remote MCP servers. This enables independent request routing and simpler horizontal scaling, while shifting application state, retries, observability, and idempotency responsibilities to other layers. ### Source excerpt AWS details how the latest Model Context Protocol specification removes protocol-level sessions, sticky-session requirements, and session storage for remote MCP servers. The change enables independent request routing and simpler horizontal scaling while shifting application state, retries, observability, and idempotency concerns to other layers. By Leela Kumili ## Crafting WCAG 3 for more accessible user experiences DevFeed: [Crafting WCAG 3 for more accessible user experiences]() Original publisher: [Read original article]() Author: Shawn Lawton Henry, W3C Web Accessibility Initiative (WAI) Director Published: 2026-09-25T12:50:00Z Content type: opinion Language: en Sources: [W3C]() Topics: [Web Accessibility (a11y)](), [W3C](), [standard](), [Requirements](), [Website]() Tags: [accessibility](), [accessible](), [blogs](), [developers](), [requirements](), [standards](), [w3c](), [wcag](), [web-accessibility]() ### AI overview This post examines the challenges of developing WCAG 3, focusing on how accessibility standards must balance the needs of people with disabilities, practical implementation, regulatory requirements, and differing stakeholder priorities. ### Source excerpt In this post, W3C's Web Accessibility Initiative (WAI) Director Shawn Lawton Henry covers some of the stakes and challenges in developing W3C Accessibility Guidelines (WCAG) 3 that is under active development. ## 2026 Climate Weeks: W3C and Web Sustainability DevFeed: [2026 Climate Weeks: W3C and Web Sustainability]() Original publisher: [Read original article]() Author: Andrew Wright, W3C Sustainable Web Interest Group Invited Expert Published: 2026-09-22T12:40:00Z Content type: article Language: en Sources: [W3C]() Topics: [W3C](), [Web]() Tags: [accessibility](), [blogs](), [climate](), [digital-products](), [security](), [security-and-privacy](), [sustainability](), [w3c](), [web]() ### AI overview W3C's Sustainable Web Interest Group reports progress on the Web Sustainability Guidelines and their Impact Ratings. The guidelines provide actionable recommendations for environmentally sustainable digital products and services, while the ratings help readers prioritize guidance by its relative effects on people, the planet, and prosperity. The latest release also reflects accessibility, internationalization, security, and privacy review. ### Source excerpt W3C's Sustainable Web Interest Group shares updates about Web Sustainability Guidelines and Impact Ratings in time for Climate Week, with changes demonstrating impacts on People, Planet, and Prosperity and reflecting W3C's horizontal review process. ## W3C IRC bots now open source DevFeed: [W3C IRC bots now open source]() Original publisher: [Read original article]() Author: Gerald Oskoboiny, Principal DevOps Engineer Published: 2026-09-21T11:13:00Z Content type: article Language: en Sources: [W3C]() Topics: [Bot](), [IRC](), [Open Source](), [W3C](), [GitHub](), [meetings]() Tags: [blogs](), [bots](), [github](), [irc](), [logs](), [meetings](), [minutes](), [open-source](), [queues](), [systems](), [w3c]() ### AI overview W3C has released two long-running IRC bots, RRSAgent and Zakim, as open source projects on GitHub. RRSAgent records and publishes chat logs and meeting minutes, while Zakim manages meeting agendas and speaker queues. ### Source excerpt Two of W3C's IRC bots, RRSAgent and Zakim, are now open source. These bots help facilitate meetings coordinated on IRC, helping with chat logs, meeting minutes, agenda tracking and speaker queues. ## W3C, threat modeling, and the CRA: a report from GDC 2026 DevFeed: [W3C, threat modeling, and the CRA: a report from GDC 2026]() Original publisher: [Read original article]() Author: Giovanni Corti, from W3C Member Fondazione Bruno Kessler, participant of the W3C Security Interest Group (SING) Published: 2026-09-18T16:49:00Z Content type: article Language: en Sources: [W3C]() Topics: [W3C](), [cyber resilience act](), [Cybersecurity](), [standard](), [browser](), [Security](), [Threat Research]() Tags: [blogs](), [browser](), [cra](), [cybersecurity](), [eu-cyber-resilience-act](), [report](), [security](), [standard](), [w3c]() ### AI overview A W3C Security Interest Group member reports on integrating threat modeling into the revision of ETSI EN 304 617, a draft harmonized standard for browser cybersecurity under the EU Cyber Resilience Act. The article references W3C threat-modeling guidance and describes feedback intended to clarify product boundaries, security outcomes, and existing web security specifications. ### Source excerpt At GDC 2026, W3C Security Interest Group member Giovanni Corti shared how threat modeling was integrated into the revision of ETSI EN 304 617, the draft harmonized standard for browser cybersecurity under the EU Cyber Resilience Act, referencing the W3C Threat Modeling Guide and the Threat Model for the Web. ## Canvas2D: New QML canvas element using Qt Canvas Painter DevFeed: [Canvas2D: New QML canvas element using Qt Canvas Painter]() Original publisher: [Read original article]() Author: kaj.gronholm@qtcompany.onmicrosoft.com (Kaj Grönholm) Published: 2026-09-18T08:12:15Z Content type: article Language: en Sources: [Qt]() Topics: [Canvas](), [Qt](), [JavaScript](), [C++](), [web-standards]() Tags: [c-plus-plus](), [canvas](), [canvas-painter](), [canvas2d](), [dev-loop](), [gpu](), [graphics](), [javascript](), [qml](), [qt](), [qt-quick](), [stack-overflow](), [w3c]() ### AI overview This article introduces Canvas2D, a new QML canvas element in Qt 6.12 built on Qt Canvas Painter. It explains that Canvas2D uses JavaScript and GPU-backed rendering through QRhi, follows the W3C Canvas 2D Context API, and intentionally omits some HTML Canvas features to keep the API simpler and fast. ### Source excerpt In the earlier blog posts about Qt Canvas Painter we have looked at what it is, the new rendering features it brings, how fast it is compared to QPainter, and how path caching makes even a million line segments render smoothly. All of those earlier blog posts used the QCanvasPainter C++ API. At the end of the path caching post I teased that a QML element was coming, and it is here now: Canvas2D, available in Qt 6.12. ## W3C launches first pilot of program to support Open Source projects DevFeed: [W3C launches first pilot of program to support Open Source projects]() Original publisher: [Read original article]() Author: Ian Jacobs, Strategy Team Published: 2026-09-16T13:53:00Z Content type: release Language: en Sources: [W3C]() Topics: [Open Source](), [W3C](), [interoperability](), [dashboards](), [Web platform]() Tags: [blogs](), [dashboard](), [developers](), [interoperability](), [open-source](), [source](), [w3c]() ### AI overview W3C has launched the first pilot of a program supporting open source projects that advance web technology, adoption, and interoperability. The pilot centers on the Can I VC? compatibility dashboard for the W3C Verifiable Credentials ecosystem, with code contributed by Digital Bazaar. ### Source excerpt In this blog post, Ian Jacobs, Strategy Team, introduces the first pilot of a program allowing Open Source projects to mature within an ecosystem seeking to build a coherent open platform through processes and IPR policies designed to support interoperability, quality, and W3C values. ## Support the well-known change password URL with Appwrite Auth DevFeed: [Support the well-known change password URL with Appwrite Auth]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-16T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [passwords](), [Appwrite](), [Application Security](), [Web app](), [W3C]() Tags: [bitwarden](), [deployment](), [passwords](), [security](), [tutorial](), [tutorials](), [w3c]() ### AI overview This tutorial shows how to support the well-known change password URL in a TanStack Start app using Appwrite Auth. It explains the redirect, the change-password form for signed-out visitors, autocomplete hints, and deployment to Appwrite Sites. ### Source excerpt Password managers open /.well-known/change-password when they find a leaked or weak password. Add the redirect and a change password page backed by Appwrite Auth. ## OpenTelemetry proposes environment variables for context propagation across processes DevFeed: [OpenTelemetry proposes environment variables for context propagation across processes]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-09-11T11:01:22Z Content type: article Language: en Sources: [OpenTelemetry]() Topics: [context](), [tracing](), [OpenTelemetry](), [Process](), [CI/CD](), [data-processing]() Tags: [ci-cd](), [data-processing](), [environment-variables](), [opentelemetry](), [processes](), [spans](), [tracing](), [w3c]() ### AI overview The OpenTelemetry Specification has a release candidate for using environment variables to carry trace context and baggage between processes. The article explains how this can connect spans across workflow runners, shells, build tools, test processes, and similar workloads when protocol headers or message metadata are unavailable, and requests feedback before the specification becomes Stable. ### Source excerpt A trace does not always cross a network boundary. A workflow runner starts a shell, the shell launches a build tool, and the build tool starts test processes. Batch and data-processing systems create similar chains of child processes. Without a shared way to pass trace information across these boundaries, spans from each process can end up in separate traces. If context propagation is new to you, it is the mechanism that carries information from one service or process to the next. For tracing, this includes the trace and span identifiers that let new spans join the same trace. It can also carry baggage: application-defined key-value pairs that are passed to downstream work. ## A compilation of W3C in Japan's 30th anniversary events DevFeed: [A compilation of W3C in Japan's 30th anniversary events]() Original publisher: [Read original article]() Author: Naomi Yoshizawa Published: 2026-09-09T20:50:00Z Content type: article Language: en Sources: [W3C]() Topics: [W3C](), [Web](), [browser](), [coding-community](), [TCP/IP](), [protocols]() Tags: [2026](), [anniversary](), [blogs](), [browser](), [community](), [corporate](), [developer-community](), [events](), [japan](), [protocols](), [tcp-ip](), [w3c](), [web]() ### AI overview W3C Japan's 30th anniversary activities included a member event, a public exhibition, and the "Web Together" meetup for W3C members and Japan's web developer community. The meetup featured lightning talks and a panel reflecting on the web's history, value, challenges, and future. ### Source excerpt 2026 marks the 30th anniversary of the establishment of W3C in Japan. As part of these commemorative activities, W3C Japan held an event for W3C members in May, an exhibition for the general public in June and an event early September for W3C members and the web developer community in Japan. ## Evaluating a Success Criterion DevFeed: [Evaluating a Success Criterion]() Original publisher: [Read original article]() Author: Adrian Roselli Published: 2026-09-01T13:47:16Z Content type: article Language: en Sources: [Adrian Roselli]() Topics: [W3C](), [GitHub Issues](), [audit](), [Requirements](), [Pull Request](), [interface](), [GitHub](), [test]() Tags: [accessibility](), [audit](), [github](), [github-issues](), [pull-requests](), [requirements](), [standards](), [test](), [w3c](), [wai](), [wcag](), [web]() ### AI overview A practical process for evaluating WCAG Success Criteria when their intent or application is unclear. It recommends consulting current W3C normative and supporting documents, techniques, GitHub issues and pull requests, expert commentary, and testing outcomes. ### Source excerpt Sidney Paget illustration of Sherlock Holmes from Strand Magazine, December 1892, p.646, but I added papers from his March 1893 (p.281 of Strand Magazine) illustration and then two versions of the W3C logo to the front page. When performing a WCAG evaluation (or review or audit), it's easy to get... ## Feature Detecting "Undetectable" CSS Features with @supports named-feature() DevFeed: [Feature Detecting "Undetectable" CSS Features with @supports named-feature()]() Original publisher: [Read original article]() Author: Bramus! Published: 2026-08-27T21:31:42Z Content type: article Language: en Sources: [Bram.us]() Topics: [CSS](), [Web Development](), [Web platform](), [web-standards](), [layout]() Tags: [css](), [feature](), [feature-detection](), [flexbox](), [grid](), [implementation](), [original-content](), [w3c]() ### AI overview The article explains how the proposed CSS @supports named-feature() function can detect browser support for underlying implementation changes and interactions between existing properties. It uses Flexbox gap as the motivating example and discusses related CSS Working Group proposals. ### Source excerpt In CSS you can feature detect support for things like selectors, properties + values, and at-rules using @supports. But how do you feature detect a change to an underlying implementation, or two existing properties suddenly working together? Enter @supports named-feature(), a function designed to expose these specific capabilities without relying on hacky workarounds. [Next page]()