BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.6.1//EN
CALSCALE:GREGORIAN
NAME:TPAC 2026 Calendar
X-WR-CALNAME:TPAC 2026 Calendar
LAST-MODIFIED:20261021T125618Z
BEGIN:VTIMEZONE
TZID:Europe/Dublin
BEGIN:STANDARD
DTSTART:20260329T010000
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
TZNAME:IST
END:STANDARD
BEGIN:STANDARD
DTSTART:20270328T010000
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
TZNAME:IST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20261025T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
TZNAME:GMT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:0e101aaf-9f0a-4386-b572-e63869c77771
DTSTAMP:20261021T034250Z
SUMMARY:Action Semantics for Agents: Protecting ARIA and Marking Risk in HT
 ML
DTSTART;TZID=Europe/Dublin:20261026T170000
DTEND;TZID=Europe/Dublin:20261026T180000
DESCRIPTION:https://www.w3.org/events/meetings/0e101aaf-9f0a-4386-b572-e638
 69c77771/\n\nAt last year's TPAC breakout on [Semantics for the Agentic We
 b](https://github.com/w3c/tpac2025-breakouts/issues/48)\, we asked whether
  the web needs a semantic layer for AI agents alongside ARIA for assistive
  technologies. Since then\, that question has turned into a real problem o
 n live sites. Several browser agents now tell web developers to add `aria-
 label` and `aria-description` attributes to buttons\, links\, and inputs s
 o agents can tell what a page does. Because ARIA overrides visible text an
 d feeds straight into screen readers\, stuffing prompts and agent instruct
 ions into accessibility attributes breaks the experience for screen reader
  users.\n\nAt the same time\, browser engines and web developers are debat
 ing how much of the agentic web should rely on existing HTML "as it is spo
 ken" versus new declarative markup or imperative tool APIs like [WebMCP](h
 ttps://github.com/webmachinelearning/webmcp). Many web interactions are si
 mple\, stateless actions where writing a JavaScript tool handler is overki
 ll\, but standard HTML and existing structured data don't always make it o
 bvious what a control does or whether an agent is safe to trigger it.\n\nA
 longside related sessions on [AI-friendly webpages](https://github.com/w3c
 /tpac2026-breakouts/issues/23)\, [declarative and imperative solutions](ht
 tps://github.com/w3c/tpac2026-breakouts/issues/24)\, and [extending WebMCP
 ](https://github.com/w3c/tpac2026-breakouts/issues/36)\, this session gets
  the accessibility\, HTML\, structured data\, and WebML communities in the
  same room to talk through concrete markup trade-offs:\n\n- **Keeping ARIA
  for accessibility:** Why are agent builders telling developers to overloa
 d `aria-label` when semantic HTML elements and forms already exist? Can be
 tter browser heuristics on standard HTML solve this\, or do developers nee
 d a simple way to describe controls for agents without breaking screen rea
 ders?\n- **Standard HTML and Schema.org vs. new attributes vs. imperative 
 tools:** For everyday page actions like search\, filtering\, and cart upda
 tes\, how far can standard HTML forms\, Schema.org Microdata\, and JSON-LD
  get us? Where is the clean handoff between declarative markup in the DOM 
 and registering JavaScript tools via `navigator.modelContext.registerTool`
 ?\n- **Safety hints and human-only controls:** Should HTML have a declarat
 ive way to mark the risk of an action\, like separating read-only navigati
 on from actions that change state\, spend money\, or always require a huma
 n click? And since careless or malicious sites can mislabel controls\, how
  should browsers and agents treat safety hints from a site?\n- **Working w
 ith existing browser signals:** How should agent semantics fit with featur
 es browsers already have\, like form autofill\, password managers\, and lo
 gin status APIs\, so developers don't have to describe the same flow three
  times?\n\n**Goal(s):**\nWork out how far standard HTML and existing struc
 tured data can go for everyday agent actions\, how to keep agent instructi
 ons out of ARIA\, and where declarative HTML hands off to imperative APIs 
 like WebMCP.\n\nAgenda\n\n- **First 10 minutes:** Quick recap of what we'v
 e seen since TPAC 2025\, including how agent docs are telling developers t
 o misuse ARIA and where standard HTML forms hit their limits.\n- **Next 15
  minutes:** Keeping ARIA for accessibility\, and comparing standard HTML\,
  Schema.org\, new HTML attributes\, and imperative WebMCP tools.\n- **Next
  20 minutes:** Marking safety boundaries in HTML\, from read-only actions 
 to state changes and controls that always need a person\, and how browsers
  should handle untrusted hints from sites.\n- **Final 15 minutes:** Where 
 browser engines\, accessibility leads\, and agent builders agree or disagr
 ee\, and where this work should live next.\n\n**Materials:**\n- [Session p
 roposal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/69)
STATUS:CONFIRMED
CREATED:20261013T144652Z
LAST-MODIFIED:20261021T034250Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Lansdowne Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:64686588-939d-4d6d-8781-30a69c264be2
DTSTAMP:20261021T034123Z
SUMMARY:Bringing Private Access Control Tokens to the Web
DTSTART;TZID=Europe/Dublin:20261026T170000
DTEND;TZID=Europe/Dublin:20261026T180000
DESCRIPTION:https://www.w3.org/events/meetings/64686588-939d-4d6d-8781-30a6
 9c264be2/\n\n[PACT](https://hacks.mozilla.org/2026/06/pact-anonymous-crede
 ntials-for-the-web/) is a [shared effort](https://www.cloudflare.com/en-gb
 /press/press-releases/2026/cloudflare-collaborates-with-leading-browsers-t
 o-develop-a-privacy-first-protocol-for-the-global-internet/) to develop a 
 privacy preserving protocol which can enable user-agents to bypass CAPTCHA
 s and block pages\, without compromising either user privacy or the effect
 iveness of sites' anti-abuse tooling.  \n\nIn this session we'll talk thro
 ugh the problem PACT is trying to solve\, the proposed solution\, and seek
  feedback on the approach from the community.\n\n**Goal(s):**\nShare persp
 ectives and concerns about PACT\n\nAgenda\n\n**Materials:**\n- [Session pr
 oposal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/29)
STATUS:CONFIRMED
CREATED:20261013T144450Z
LAST-MODIFIED:20261021T034123Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 09
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:c4735ea4-45e6-4b31-9689-d1072871f5d5
DTSTAMP:20261021T034121Z
SUMMARY:Cybernetic Avatar CG Discussion
DTSTART;TZID=Europe/Dublin:20261026T170000
DTEND;TZID=Europe/Dublin:20261026T180000
DESCRIPTION:https://www.w3.org/events/meetings/c4735ea4-45e6-4b31-9689-d107
 2871f5d5/\n\nCybernetic Avatars (CAs) are technologies that extend human c
 apabilities through remote\, robotic\, and digital embodiments\, enabling 
 people to interact with other people and environments beyond physical cons
 traints.\n\nFollowing the introductory discussion from our previous TPAC b
 reakout session\, this session will provide a brief recap of the Cyberneti
 c Avatar concept and share updates on our recent activities\, use cases\, 
 and validation efforts.\n\nIn particular\, we would like to explore the po
 ssibilities for implementing and supporting Cybernetic Avatar interactions
  through Web technologies and browser-based environments. Based on our cur
 rent use cases\, we will discuss potential technical requirements\, challe
 nges\, and opportunities for enabling Cybernetic Avatar systems to interac
 t through the Web.\n\nThe session is intended to be an open discussion wit
 h the community\, and we welcome perspectives on relevant Web technologies
 \, APIs\, architectures\, security\, accessibility\, and other considerati
 ons that may contribute to future Cybernetic Avatar implementations.\n\nAd
 ditional Chair: Masaaki Sato\n\n**Goal(s):**\nDiscuss Cybernetic Avatars a
 nd their possibilities on the Web.\n\nAgenda\n\n- Brief introduction and r
 ecap of Cybernetic Avatars\n- Updates on recent CACG activities\n- Overvie
 w of current use cases and validation efforts\n- Discussion on browser-bas
 ed implementation possibilities\n- Open discussion with participants\n\n**
 Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac20
 26-breakouts/issues/28)
STATUS:CONFIRMED
CREATED:20261013T144447Z
LAST-MODIFIED:20261021T034121Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 08
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:5ec70748-3fcf-411e-8a58-aaca280e05dd
DTSTAMP:20261021T034150Z
SUMMARY:Declarative partial updates and client side includes
DTSTART;TZID=Europe/Dublin:20261026T170000
DTEND;TZID=Europe/Dublin:20261026T180000
DESCRIPTION:https://www.w3.org/events/meetings/5ec70748-3fcf-411e-8a58-aaca
 280e05dd/\n\nLast year we [presented](https://github.com/w3c/tpac2025-brea
 kouts/issues/66) declarative partial updates - new HTML/JS ways to update 
 the document.\nWe see an opportunity to extend it in various ways\, and wo
 uld like to discuss with a wider audience!\n\nSpecifically:\n- allow fetch
 ing the update from an external URL `<template src>`\n- Built-in sanitizat
 ion `<template sanitize>`\n- Control whether the update buffers or streams
  `<template buffer>`\n\n**Goal(s):**\nGet feedback from a wider audience f
 or the new directions\n\nAgenda\n\n**Materials:**\n- [Session proposal on 
 GitHub](https://github.com/w3c/tpac2026-breakouts/issues/41)
STATUS:CONFIRMED
CREATED:20261013T144529Z
LAST-MODIFIED:20261021T034150Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 06
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:7c453896-507a-4276-9e57-ef2c46198154
DTSTAMP:20261021T034030Z
SUMMARY:Discovering topics of interest in W3C from group participation patt
 erns
DTSTART;TZID=Europe/Dublin:20261026T170000
DTEND;TZID=Europe/Dublin:20261026T180000
DESCRIPTION:https://www.w3.org/events/meetings/7c453896-507a-4276-9e57-ef2c
 46198154/\n\nThis session will center on the paper "[Who Shapes Web Standa
 rds? Uncovering the Main Topics of Interest in the W3C](https://doi.org/10
 .1145/3774905.3795481)". The paper investigates the main areas of interest
  of organizations participating in W3C by applying topic modeling to publi
 cly available data on member organizations' participation in W3C groups\, 
 using the number of representatives assigned to each group as a proxy for 
 organizational priorities.\n\nThe analysis identifies five major areas of 
 focus: Browser\, Ads & Privacy\; High Performance\; Credentials & Web of T
 hings\; Accessibility\; and Payments. It also shows that large enterprises
 \, particularly those based in the United States\, dominate participation 
 in browser development and advertising-related work\, while Japanese organ
 izations are more strongly represented in Web of Things activities.\n\nThe
  session will begin with a presentation by the paper's lead author\, follo
 wed by an open discussion with the audience. In addition to examining the 
 methodology and key findings\, participants will compare the results with 
 the firsthand experiences as W3C contributors\, providing valuable context
  for interpreting the analysis and fostering a deeper understanding of the
  dynamics that shape the development of Web standards.\n\n**Goal(s):**\nTh
 e goal of the session is to discuss the findings of the research on W3C wh
 ile fostering an exchange of perspectives between the researchers and W3C 
 contributors.\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](
 https://github.com/w3c/tpac2026-breakouts/issues/6)
STATUS:CONFIRMED
CREATED:20261013T144339Z
LAST-MODIFIED:20261021T034030Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Ulster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:9cda24fd-7cbb-46d1-8bea-99d595c01ce1
DTSTAMP:20261021T034119Z
SUMMARY:Dive into ARIA-AT
DTSTART;TZID=Europe/Dublin:20261026T170000
DTEND;TZID=Europe/Dublin:20261026T180000
DESCRIPTION:https://www.w3.org/events/meetings/9cda24fd-7cbb-46d1-8bea-99d5
 95c01ce1/\n\nARIA-AT is the test suite for testing browser features in scr
 een-reader settings. This is an important testing initiative happening at 
 the W3C for the advancement of an inclusive and accessible web. This sessi
 on will delve into how ARIA-AT works\, what makes it different from WPT\, 
 Test 262\, ACT and others\, how tests are constructed and run\, and more.\
 n\nWe'd love to encourage those who are involved in accessibility work\, t
 esting and support infrastructures (e.g. BCD\, WPT\, Baseline)\, and those
  generally interested in how we can test browser features against screen-r
 eaders.\n\n**Goal(s):**\nLearn more about ARIA-AT\n\nAgenda\n\n**Materials
 :**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-breako
 uts/issues/27)
STATUS:CONFIRMED
CREATED:20261013T144444Z
LAST-MODIFIED:20261021T034119Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Leinster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:4c78fd65-4e19-427e-9e1a-329506a0aea0
DTSTAMP:20261021T034214Z
SUMMARY:End-to-end Encrypted Messaging with ActivityPub
DTSTART;TZID=Europe/Dublin:20261026T170000
DTEND;TZID=Europe/Dublin:20261026T180000
DESCRIPTION:https://www.w3.org/events/meetings/4c78fd65-4e19-427e-9e1a-3295
 06a0aea0/\n\nThe Social Web Community Group has been working on end-to-end
  encrypted (E2EE) messaging in ActivityPub for more than 2 years. The E2EE
  Task Force has developed a community group report\, MLS over ActivityPub\
 , with two interoperable implementations. In this sessions\, we'll go over
  the E2EE work in SWICG and discuss next steps.\n\n**Goal(s):**\nShare inf
 ormation about E2EE messaging in ActivityPub and collect feedback for next
  steps\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https:/
 /github.com/w3c/tpac2026-breakouts/issues/52)
STATUS:CONFIRMED
CREATED:20261013T144604Z
LAST-MODIFIED:20261021T034214Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 01 and 02
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:2a205b4a-4c4e-416b-9318-5ad7d40ac09a
DTSTAMP:20261021T034145Z
SUMMARY:KYAPay: Verified Agent Identity and Payments for Ubiquitous Agentic
  Commerce on the Existing Web
DTSTART;TZID=Europe/Dublin:20261026T170000
DTEND;TZID=Europe/Dublin:20261026T180000
DESCRIPTION:https://www.w3.org/events/meetings/2a205b4a-4c4e-416b-9318-5ad7
 d40ac09a/\n\nThis breakout will continue the discussion on agentic commerc
 e for the Web we already started with [our session](https://github.com/w3c
 /ecommerce-for-humans-and-AI-Agents-workshop/issues/26) at the [W3C/GS1 Wo
 rkshop on E-Commerce for Humans and Agents](https://www.w3.org/2026/ecomme
 rce-agents/)\, which was followed by a productive breakout.  There\, works
 hop organizer Philippe le Hégaret suggested that we bring the ideas to TP
 AC to inform and receive feedback from the pertinent W3C working groups an
 d communities\, particularly in light of our work to standardize the under
 lying data structures and protocols at the IETF.\n\nWe want to frame the d
 iscussion around agentic commerce rather than e-commerce for agents: letti
 ng agents transact through the same Websites\, payment rails\, and brands 
 their human principals already use\, rather than a separate\, agent-only s
 urface that humans must configure in advance. We will discuss KYAPay\, whi
 ch uses a signed JWT that carries verified agent and human identity (KYA) 
 and payment credentials (PAY) so that the security infrastructure already 
 guarding merchant websites can tell legitimate\, human-authorized agents a
 part from malicious bots\, and so agents can pay across cards\, stablecoin
 s\, and (in future) banks. We have submitted it to the IETF OAuth working 
 group\, and it is already in production with a growing consortium includin
 g Experian\, Akamai\, F5\, Fastly\, Forter\, Imperva\, Cequence\, and Auth
 0\, among many others (see [kyapay.org](https://kyapay.org/)).\n\nOur main
  points will be:\n\n**Agents must be able to use the web ubiquitously\, li
 ke their human principals.** If humans must "set up" agent access in advan
 ce for each site\, we are back to the workflow automation that already exi
 sts\, and we lose the probabilistic discovery and serendipity that agents 
 and LLMs bring. This is why the goal should be agentic commerce on the exi
 sting web\, not a parallel agent-only surface that fragments the ecosystem
  and recreates that setup friction.\n\n**This is achievable now.** A brows
 er-use agent can already navigate\, browse\, and check out on a website wi
 th just a few prompts. Coupled with verified access via KYAPay\, which rem
 oves the complexity of bot evasion\, we see near 100% checkout rates.\n\n*
 *KYAPay gives every layer of defense one source of truth.** Bot managers\,
  fraud managers\, account-takeover protectors\, and CIAM solutions operate
  at the application layer. Today each makes its call in isolation\, so the
 ir verdicts on the same request can contradict one another. A single KYAPa
 y token lets all of them use the same verified identity and fraud signals\
 , so their decisions are more likely to be consistent than conflicting.\n\
 n**Layered\, extensible identity gives security infrastructure precise anc
 hors.** KYAPay's identity tiers distinguish the human principal\, the agen
 t platform/operator\, and the agent instance\, letting vendors block a sin
 gle principal or agent instance rather than banning an entire platform ove
 r one bad actor.\n\n**KYAPay complements OAuth.** Our KYA↔OAuth token ex
 change work with Okta and Ory lets agents log in on behalf of their human 
 principals\, opening up loyalty\, offers\, and other logged-in experiences
  merchants already offer humans. The protocol works today\, and the JWT ap
 proach interoperates with the APIs and agent-to-agent communication of tom
 orrow.\n\n**Idea for discussion:** Merchants can use KYAPay signals to sty
 le their existing pages for agents. Just as a "print" button uses CSS to r
 estyle a page for printing\, a merchant that receives a KYAPay token can r
 estyle its existing page for the agent. This reuses technology merchants h
 ave already mastered\, keeps interface ownership and brand with them (avoi
 ding the disintermediation they fear)\, preserves the fraud and good/bad-a
 ctor signals their models are built around\, and lets them optimize and it
 erate with familiar tools like A/B testing rather than carefully managed A
 PI-schema changes.\n\n**Goal(s):**\nWe would like to collaborate and white
 board actual end-to-end workflows that we collectively believe will work f
 or all. As a stretch goal\, I would like to identify partners who want to 
 prototype and/or help refine and standardize these capabilities.\n\nAgenda
 \n\n(TBD once session is accepted)\n\n**Materials:**\n- [Session proposal 
 on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/39)
STATUS:CONFIRMED
CREATED:20261013T144523Z
LAST-MODIFIED:20261021T034145Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 03
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:b8950833-f1dd-40f8-b452-74cc7983855b
DTSTAMP:20261021T034330Z
SUMMARY:New requirements for video metadata & timed data
DTSTART;TZID=Europe/Dublin:20261026T170000
DTEND;TZID=Europe/Dublin:20261026T180000
DESCRIPTION:https://www.w3.org/events/meetings/b8950833-f1dd-40f8-b452-74cc
 7983855b/\n\nDevelopment of [WebVMT](https://www.w3.org/TR/webvmt/) in the
  [OGC Testbed](https://www.ogc.org/apply/testbeds/) programme has identifi
 ed new requirements for static video metadata and dynamic timed data on th
 e web with guidance from [SDW WG](https://www.w3.org/groups/wg/sdw/)\, [ME
 IG](https://www.w3.org/groups/ig/me/) and [WICG DataCue](https://github.co
 m/WICG/datacue#web-incubator-cg-for-datacue). Scope has widened from a foc
 us on location to include timed data of any type in any format\, including
  binary\, and fixed video metadata.\n\nHTML cue (`TextTrackCue`) design ha
 s been progressively adapted to support these enhancements\, but the lates
 t proposals require significant changes to either modify the existing time
 d text scheduler (`TextTrack`) or propose an alternative scheduler that me
 ets the new requirements identified for handling timed data.\n\n**Goal(s):
 **\nIdentify missing requirements for video metadata and timed data on the
  web from the wider community\, and how best to integrate these requiremen
 ts with HTML.\n\nAgenda\n\n1. Gap analysis of timed data and video metadat
 a support in HTML (15 mins)\n 1. Discussion to identify additional require
 ments and integration options (30 mins)\n 1. Proposed next steps (10 mins)
 \n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/
 tpac2026-breakouts/issues/87)
STATUS:CONFIRMED
CREATED:20261015T132848Z
LAST-MODIFIED:20261021T034330Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 05
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:4690848b-ef1b-4c32-85e0-467632e66300
DTSTAMP:20261021T034301Z
SUMMARY:Open-World FedCM for Decentralized Social Networks
DTSTART;TZID=Europe/Dublin:20261026T170000
DTEND;TZID=Europe/Dublin:20261026T180000
DESCRIPTION:https://www.w3.org/events/meetings/4690848b-ef1b-4c32-85e0-4676
 32e66300/\n\nI would love to invite the Solid CG and the Social Web CG dev
 eloping Solid and ActivityPub to share the progress we have been making on
  open-world federations (federations where any identity providers can join
  without redeploying relying parties\, as opposed to closed-world federati
 ons where relying parties enumerate identity providers ahead of time) with
  (a) Email Verification and (b) the Atproto community.\n\n- Email Verifica
 tion\n  - https://developer.chrome.com/docs/identity/email-verification\n 
  - https://github.com/WICG/email-verification\n  - https://dickhardt.githu
 b.io/email-verification/draft-hardt-email-verification.html\n- Handle Veri
 fication\n  - https://atproto.com/blog/working-to-decentralize-fedcm\n  - 
 https://bsky.app/profile/did:plc:thaoj4hhvraos7y6v3yog7re/post/3mui4mejurc
 2x\n  - https://github.com/w3c-fedid/idp-registration\n\nMuch of this is s
 till very early and malleable\, so am hoping to have an open discussion:\n
 \n- How\, if at all\, is Solid and ActivityPub similar to email/handle ver
 ification?\n- How are they different?\n- Where are things at with Solid/Ac
 tivityPub? \n- Where are things at with FedCM and cross-browser implementa
 tion? Can extensions play a big role?\n\n**Goal(s):**\nShare and exchange 
 information\, interest and requirements\n\nAgenda\n\n**Materials:**\n- [Se
 ssion proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues
 /74)
STATUS:CONFIRMED
CREATED:20261013T144708Z
LAST-MODIFIED:20261021T034301Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Pembroke Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:59a6d1d1-d43f-45a6-9dac-57558cbaab2d
DTSTAMP:20261021T034112Z
SUMMARY:Agentic Web: declarative and imperative solutions
DTSTART;TZID=Europe/Dublin:20261027T153000
DTEND;TZID=Europe/Dublin:20261027T163000
DESCRIPTION:https://www.w3.org/events/meetings/59a6d1d1-d43f-45a6-9dac-5755
 8cbaab2d/\n\nThere are many ways that agents interface with web content. E
 ach browser engine is currently taking slightly different approaches\, but
  there's a lot of common ground/overlap too. For agents\, in coordination 
 with browsers\, to interface with the long tail of content\, they will nat
 urally need to deal with the messy HTML "as it is spoken" by the majority 
 of the web. At the same time\, alternative imperative approaches have been
  proposed\, but those could cause further fragmentation\, negatively impac
 t accessibility\, pose new privacy and security risks\, and entirely exclu
 de people who don't want to\, or can't\, use AI agents in the browsers.   
  \n\nThere are limitations and concerns about each approach\, so it would 
 be good to tease those out during this session to come to a shared underst
 anding.\n\n**Goal(s):**\nExplore the pros and cons of different approaches
 . Find a path forward to standardization.\n\nAgenda\n\n**Materials:**\n- [
 Session proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/issu
 es/24)
STATUS:CONFIRMED
CREATED:20261013T144436Z
LAST-MODIFIED:20261021T034112Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Lansdowne Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:35ce295a-42cd-4d56-beaa-4483863e21d8
DTSTAMP:20261021T034225Z
SUMMARY:AsyncContext across specifications
DTSTART;TZID=Europe/Dublin:20261027T153000
DTEND;TZID=Europe/Dublin:20261027T163000
DESCRIPTION:https://www.w3.org/events/meetings/35ce295a-42cd-4d56-beaa-4483
 863e21d8/\n\nEcma's TC39 has been developing [AsyncContext](https://github
 .com/tc39/proposal-async-context/) for a few years now: it's a new JS API 
 that allows implicit propagation of some JavaScript values across asynchro
 nous code. One if its main motivating use cases is being able to gather te
 lemetry data in frontend applications\, similarly to how it's already poss
 ible in Node.js and in many other programming languages.\n\nThere are a fe
 w other web specifications that are already exploring to build on top of A
 syncContext: what other features would AsyncContext be an useful building 
 block for? Should the web platform expose some information natively that i
 s propagated through async JS code? Does the proposal meet your needs as i
 t is\, or what do we need to change?\n\nPossible co-chair TBD: @mmocny\n\n
 **Goal(s):**\nMake sure that we are considering everybody's needs in the d
 esign of the AsyncContext specification\, and help spec authors figure out
  how to integrate with it.\n\nAgenda\n\n**Materials:**\n- [Session proposa
 l on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/58)
STATUS:CONFIRMED
CREATED:20261013T144619Z
LAST-MODIFIED:20261021T034225Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 05
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:0e2dd97c-1b12-4d02-ad62-994d5fbd5da1
DTSTAMP:20261021T034240Z
SUMMARY:DOM Localization
DTSTART;TZID=Europe/Dublin:20261027T153000
DTEND;TZID=Europe/Dublin:20261027T163000
DESCRIPTION:https://www.w3.org/events/meetings/0e2dd97c-1b12-4d02-ad62-994d
 5fbd5da1/\n\nUsers of the web are best served by being able to experience 
 it in their native languages. Currently\, localization of web content is a
 chieved with a multitude of custom solutions\, most of which are unable to
  express the full depth and breadth of human expressions in all languages.
  Introducing an easy-to-use but powerful standard localization solution wo
 uld improve the experience of all users\, in particular the vast majority 
 who do not speak English natively.\n\nDuring the past year\, [DOM Localiza
 tion](https://github.com/whatwg/proposal-dom-localization) has been accept
 ed as a Stage 1 WHATWG proposal\, and [Message Resources](https://github.c
 om/w3c/i18n-discuss/blob/gh-pages/explainers/message-resources.md) (the de
 finition of the underlying file format) has been accepted for incubation b
 y the W3C Internationalization WG.\n\nThis work has been previous discusse
 d at breakout sessions at past TPACs ([2023](https://www.w3.org/events/mee
 tings/4fd28161-058b-4daa-9618-d1893be9c39c/)\, [2025](https://www.w3.org/e
 vents/meetings/758666a3-cb69-443b-a93d-934fe9c17f7f/))\, and it builds on 
 [Unicode MessageFormat](https://www.unicode.org/reports/tr35/tr35-messageF
 ormat.html)\, now a part of Unicode's UTS 35 standard.\n\n**Goal(s):**\nCo
 llect comments on the proposals and recruit interests to work on the stand
 ards.\n\nAgenda\n\n(TBD)\n\n**Materials:**\n- [Session proposal on GitHub]
 (https://github.com/w3c/tpac2026-breakouts/issues/65)
STATUS:CONFIRMED
CREATED:20261013T144640Z
LAST-MODIFIED:20261021T034240Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 01 and 02
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:f600f69e-be95-4662-b719-7dca372725d2
DTSTAMP:20261021T034257Z
SUMMARY:Giving the user control over where AI models run in the browser
DTSTART;TZID=Europe/Dublin:20261027T153000
DTEND;TZID=Europe/Dublin:20261027T163000
DESCRIPTION:https://www.w3.org/events/meetings/f600f69e-be95-4662-b719-7dca
 372725d2/\n\nThis breakout session will explore the feasibility of giving 
 users control over computation placement of the AI models running in the b
 rowser. We will analyse the current friction points where web features cla
 sh with user privacy settings. \n\n**We will propose a lightweight experim
 ent:** could a shared vocabulary of locations (an "enum" of places) be the
  missing link that makes it technically viable for User Agents to enforce 
 user preferences without breaking existing web features?\n\nWe will also l
 ook at risks to the approach\, and how we might avoid a "Do Not Track 2.0"
  scenario - why a purely opt-in signal failed\, contrasting it with the po
 tential of an enforceable mechanism.\n\nChairs: Matthew Atkinson (Samsung 
 Electronics\,@matatk)\, Muadh Al Kalbani (Samsung Electronics\, @m-alkalba
 ni)\, Ehsan Toreini (Samsung Electronics\,@toreini)\n\n**Goal(s):**\nDiscu
 ss the problem and solution space around where models may run\, proposing 
 the shared vocabulary approach as one avenue to explore - supporting User 
 Agents to ensure that the user has control over this aspect of their priva
 cy.\n\nAgenda\n\n1.  **The Problem Landscape**\n    *   The tension betwee
 n developer needs (performance\, cost) and user privacy (data residency).\
 n    *   Why current OS-level toggles are invisible to the web and why "on
 -device" is too vague.\n    *   Key differences between this idea and DNT:
  Enforcement by the UA vs. a request to the server.\n\n2.  **The "Enum" Pr
 oposal: A Building Block\, not a Solution**\n    *   Introducing the conce
 pt of a shared vocabulary (`personal-secure`\, `personal`\, `remote`\, etc
 .).\n    *   How this "enum" acts as a contract between the feature and th
 e browser to make enforcement possible.\n    *   The Decision Logic: How t
 he UA intersects developer needs\, user preferences\, and device capabilit
 ies.\n    *   Distinguishing between the *vocabulary* and the *logic*.\n  
   * The "User Wins" Principle: Why the user's constraint takes precedence 
 and why clean refusal is better than silent degradation.\n\n4.  **Feasibil
 ity & Risks**\n    *   **Fingerprinting:** Does exposing a list of accepta
 ble places create a new vector?\n    *   **Adoption:** Can we actually get
  browser vendors and developers to agree on this list?\n\n5.  **Open Discu
 ssion & Next Steps**\n    *   Avoiding a DNT rehash.\n    *   Defining imm
 ediate next steps for a community review or incubation.\n\n**Materials:**\
 n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/
 issues/72)
STATUS:CONFIRMED
CREATED:20261013T144702Z
LAST-MODIFIED:20261021T034257Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 06
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:335b77c2-e557-496d-aefc-b0b8915ff650
DTSTAMP:20261021T034154Z
SUMMARY:How Can W3C Work Better with Policymakers?
DTSTART;TZID=Europe/Dublin:20261027T153000
DTEND;TZID=Europe/Dublin:20261027T163000
DESCRIPTION:https://www.w3.org/events/meetings/335b77c2-e557-496d-aefc-b0b8
 915ff650/\n\nOver the past year\, W3C has been increasing its efforts in p
 olicy engagement\, with the goal of supporting policy outcomes for "making
  the web work\, for everyone." Most of our focus has been on communication
  and coordination\, e.g.\, to serve as a reputable source of technical inf
 ormation for policy development. We'd like to ensure that our efforts in t
 his arena are effective\, and wanted to take time at TPAC to learn what we
  could try in the upcoming year(s) for better policy engagement. We'd love
  ideas from community members with experience and/or interest in policy\, 
 and would really appreciate diverse perspectives from different stakeholde
 rs to inform our work.\n\n**Goal(s):**\nHelp shape W3C's policy engagement
  work in 2027 (and beyond)\n\nAgenda\n\n**Materials:**\n- [Session proposa
 l on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/43)
STATUS:CONFIRMED
CREATED:20261013T144536Z
LAST-MODIFIED:20261021T034154Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Pembroke Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:42599eee-2b26-4758-b019-0578befc52cd
DTSTAMP:20261021T034248Z
SUMMARY:Mind the gaps: Where does the web platform fall short?
DTSTART;TZID=Europe/Dublin:20261027T153000
DTEND;TZID=Europe/Dublin:20261027T163000
DESCRIPTION:https://www.w3.org/events/meetings/42599eee-2b26-4758-b019-0578
 befc52cd/\n\nWeb standards work is good at gathering feedback on features 
 that already exist or solutions that have been proposed. It is much harder
  to learn what developers need before anyone writes a proposal\, e.g.\, th
 e gaps that lead to heavy workarounds\, inaccessible components\, and larg
 e libraries. \nThere have been efforts to address this. [The Web We Want](
 https://webwewant.fyi/) (2019 to 2024) collected developer ‘wants’\, b
 ut struggled with having an owner to triage and with getting ideas to peop
 le who could act on them. Similarly\, WICG gives people a place to incubat
 e proposals\, but still requires a lot of standards knowledge to participa
 te.\nIn recent interviews with authors of frameworks and libraries\, even 
 experienced standards advocates told us that they don’t know where to ra
 ise unmet needs. In this session\, we would like to explore what has and h
 asn’t worked and design a lightweight way to surface developer needs ear
 lier and route them to the group that can act on them.\n\n**Goal(s):**\nAg
 ree on a vendor-agnostic lightweight way to surface developer needs before
  proposals exist\, who triages them\, and how they reach the groups that c
 an act on them.\n\nAgenda\n\n- What we learned from past research initiati
 ves\n- Challenges and how to address them\n- Open discussion\n\n**Material
 s:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-break
 outs/issues/68)
STATUS:CONFIRMED
CREATED:20261013T144649Z
LAST-MODIFIED:20261021T034248Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Ulster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:5dd31a58-7bcb-4261-9f80-13f3ab0898a1
DTSTAMP:20261021T034312Z
SUMMARY:Phone Number Verification on the Web
DTSTART;TZID=Europe/Dublin:20261027T153000
DTEND;TZID=Europe/Dublin:20261027T163000
DESCRIPTION:https://www.w3.org/events/meetings/5dd31a58-7bcb-4261-9f80-13f3
 ab0898a1/\n\nTODO(goto): fill this up\n\n**Goal(s):**\nTODO\n\nAgenda\n\n*
 *Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2
 026-breakouts/issues/79)
STATUS:CONFIRMED
CREATED:20261013T144723Z
LAST-MODIFIED:20261021T034312Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 03
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:4fc603cd-0b87-4eec-a1be-d60ed1bf258e
DTSTAMP:20261021T034243Z
SUMMARY:Security by Design: From Threat Modeling to Security Considerations
DTSTART;TZID=Europe/Dublin:20261027T153000
DTEND;TZID=Europe/Dublin:20261027T163000
DESCRIPTION:https://www.w3.org/events/meetings/4fc603cd-0b87-4eec-a1be-d60e
 d1bf258e/\n\nHow can we make threat modeling practical for specification d
 evelopers?\n\nIn this hands-on session\, we'll use some W3C specifications
  to demonstrate how to build a lightweight threat model\, identify threats
  and responses\, and determine when the analysis is sufficiently complete.
 \n\nWe'll then show how to turn the findings\, including assumptions and r
 emaining threats\, into useful Security Considerations sections\, without 
 making the process unnecessarily complex.\n\nNote: Additional chairs to be
  confirmed.\n\n**Goal(s):**\nDemonstrate a simple\, repeatable approach to
  threat modeling and writing Security Considerations\, and gather feedback
  from specification editors.\n\nAgenda\n\n**Materials:**\n- [Session propo
 sal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/66)
STATUS:CONFIRMED
CREATED:20261013T144643Z
LAST-MODIFIED:20261021T034243Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Leinster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:f3acbf28-1251-48ef-b8f3-72e1b127c9cb
DTSTAMP:20261021T034207Z
SUMMARY:Web Speech API: On-Device Speech Recognition & Next-Generation Capa
 bilities
DTSTART;TZID=Europe/Dublin:20261027T153000
DTEND;TZID=Europe/Dublin:20261027T163000
DESCRIPTION:https://www.w3.org/events/meetings/f3acbf28-1251-48ef-b8f3-72e1
 b127c9cb/\n\nJoin the Chrome and Firefox teams to see recent advancements 
 in the [Web Speech API](https://webaudio.github.io/web-speech-api/) over t
 he past year. With the specification transitioning to the W3C Recommendati
 on track under the proposed [2026-2028 Audio Working Group Charter](https:
 //w3c.github.io/charter-drafts/2026/audio-wg.html) and both Chrome and Fir
 efox Nightly now supporting on-device speech recognition\, web-based speec
 h interaction is entering a new era of privacy\, low latency\, and cross-b
 rowser interoperability.\n\n**Goal(s):**\nDemonstrate multi-engine on-devi
 ce speech recognition and newly added capabilities\, and gather cross-WG f
 eedback on multilingual recognition\, speaker diarization\, audio timing\,
  and faster-than-realtime transcription.\n\nAgenda\n\n- Overview of recent
  Web Speech API standardization and multi-engine progress\n- Live demos of
  new capabilities in Chrome and Firefox Nightly\n- Open discussion & Q&A o
 n newly proposed features and future directions\n\n**Materials:**\n- [Sess
 ion proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/4
 9)
STATUS:CONFIRMED
CREATED:20261013T144555Z
LAST-MODIFIED:20261021T034207Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 09
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:00dd06fe-c11c-4f7d-b518-24d5e8303ab3
DTSTAMP:20261021T034125Z
SUMMARY:XML standardization at W3C
DTSTART;TZID=Europe/Dublin:20261027T153000
DTEND;TZID=Europe/Dublin:20261027T163000
DESCRIPTION:https://www.w3.org/events/meetings/00dd06fe-c11c-4f7d-b518-24d5
 e8303ab3/\n\nXML is still widely used and will continue to be so for many 
 years. There is interest within the user community both in continuing the 
 development of existing standards (XPath\, XSLT\, etc.) and creating new o
 nes (Invisible XML\, XProc\, etc.).  There are several community groups en
 gaged in XML-related activities along these lines (e.g.\, XSLT and XQuery 
 Extensions\, XProc\, and Invisible XML). Community Groups enable incubatio
 n\, but in some cases this is growing interest in standardization.  With t
 he XML Activity closed\, where and how and should XML-related community gr
 oups transition to Working Groups when they begin to design interoperable 
 standards?\n\n**Goal(s):**\nGauge support in the W3C community for creatin
 g a Working Group for new XML standardization activities.\n\nAgenda\n\n**M
 aterials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac202
 6-breakouts/issues/30)
STATUS:CONFIRMED
CREATED:20261013T144453Z
LAST-MODIFIED:20261021T034125Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 08
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:762f95b8-704c-400f-a281-36496081870b
DTSTAMP:20261021T034105Z
SUMMARY:Accessibility feedback for upcoming Open UI features
DTSTART;TZID=Europe/Dublin:20261028T090000
DTEND;TZID=Europe/Dublin:20261028T100000
DESCRIPTION:https://www.w3.org/events/meetings/762f95b8-704c-400f-a281-3649
 6081870b/\n\nThe OpenUI Community Group would like to present on upcoming 
 features\, specifically to talk about their impact on accessibility\, we'd
  also like to invite the ARIA Working Group to attend and provide feedback
 .\n\nSee https://github.com/openui/open-ui/issues/1510 for more.\n\n* ARIA
  chairs: @jnurthen\, @spectranaut\n* Open UI chairs: @gregwhitworth\, @kei
 thamus\, @mfreed7\n\n**Goal(s):**\nHighlight OpenUI work and discuss the i
 mpact to ARIA\n\nAgenda\n\nTBD\n\n**Materials:**\n- [Session proposal on G
 itHub](https://github.com/w3c/tpac2026-breakouts/issues/21)
STATUS:CONFIRMED
CREATED:20261013T144426Z
LAST-MODIFIED:20261021T034105Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Ulster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:d73989f3-9bba-4390-baf8-6da89c4c8632
DTSTAMP:20261021T034314Z
SUMMARY:Capitalization\, Titlecasing\, and Presentational Case Mapping
DTSTART;TZID=Europe/Dublin:20261028T090000
DTEND;TZID=Europe/Dublin:20261028T100000
DESCRIPTION:https://www.w3.org/events/meetings/d73989f3-9bba-4390-baf8-6da8
 9c4c8632/\n\nPresentational case mapping (capitalization and title casing)
  continues to be among the most-requested features in ECMA-402 (https://gi
 thub.com/tc39/ecma402/issues/294). However\, since we currently offer no u
 tility for this\, developers are left with i18n-unfriendly workarounds lik
 e `str[0].toUpperCase() + str.slice(1)`.\n\nTwo related but distinct probl
 ems in this space:\n\n- **Word and sentence capitalization transforms:** C
 SS provides `text-transform: capitalize`\, which titlecases the start of e
 very word while leaving trailing characters unchanged. However\, there is 
 no CSS transform for sentence casing ([w3c/csswg-drafts#8893](https://gith
 ub.com/w3c/csswg-drafts/issues/8893)) or editorial title casing ([w3c/cssw
 g-drafts#12526](https://github.com/w3c/csswg-drafts/issues/12526))\, and J
 avaScript currently has no titlecase mapping primitive at all ([tc39/ecma4
 02#294](https://github.com/tc39/ecma402/issues/294)). Naive JS workarounds
  fail on scripts where uppercase and titlecase differ (such as Georgian Mt
 avruli vs. Mkhedruli)\, digraphs like Dutch `IJ` (`IJsselmeer`)\, and lead
 ing punctuation.\n- **Contextual capitalization of localized strings:** CL
 DR stores display names\, month names\, and weekday names in middle-of-sen
 tence casing\, alongside `<contextTransforms>` data for standalone and UI 
 menu contexts. Because `Intl` formatters do not yet expose `DisplayContext
 ` ([tc39/ecma402#355](https://github.com/tc39/ecma402/issues/355))\, calli
 ng `Intl.DisplayNames` or `Intl.DateTimeFormat` to populate a UI menu or h
 eader produces lowercase strings in dozens of locales (e.g.\, `español de
  España`\, `français`\, `janvier`)\, and applying CSS `text-transform: c
 apitalize` produces incorrect results on multi-word names (`Español De Es
 paña`).\n\nWhen TC39-TG2 discussed https://github.com/tc39/ecma402/issues
 /294\, implementers suggested that although there are use cases for this d
 ata in JS\, we should coordinate with CSS WG and W3C i18n on a holistic de
 sign rather than designing JS and CSS features in isolation.\n\nIn this se
 ssion\, I would like to bring together those groups\, with a focus on CSS\
 , W3C i18n\, and TC39-TG2\, to align on terminology\, use cases\, and wher
 e each layer of the platform should provide building blocks versus high-le
 vel solutions.\n\n**Goal(s):**\nAlign across CSS\, W3C i18n\, and TC39-TG2
  on a cohesive Web Platform strategy for capitalization\, sentence/title c
 asing\, and contextual display transforms.\n\nAgenda\n\n- Overview of capi
 talization and titlecasing problems (character/segment titlecase\, sentenc
 e case\, start case\, editorial title case\, CLDR `DisplayContext`)\n- Cur
 rent gaps across CSS (`text-transform`)\, HTML (`autocapitalize`)\, and JS
  (`String.prototype` / `Intl`)\n- Discussion: What belongs in CSS vs. JS/E
 CMA-402 vs. userland libraries?\n- Next steps for CSS WG and TC39-TG2\n\n*
 *Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2
 026-breakouts/issues/80)
STATUS:CONFIRMED
CREATED:20261013T144726Z
LAST-MODIFIED:20261021T034314Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 05
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:f765d218-3e85-455a-9f35-672045a4658c
DTSTAMP:20261021T034139Z
SUMMARY:Extending WebMCP: Tool Granularity\, Composition\, and Agentic Step
 s
DTSTART;TZID=Europe/Dublin:20261028T090000
DTEND;TZID=Europe/Dublin:20261028T100000
DESCRIPTION:https://www.w3.org/events/meetings/f765d218-3e85-455a-9f35-6720
 45a4658c/\n\nWebMCP enables collaborative workflows in which users and age
 nts work within the same web interface. This session will (1) identify cha
 llenges encountered in implementing and using WebMCP tools\, and (2) explo
 re how the same set of WebMCP tools can be reused across collaborative and
  autonomous browsing tasks ranging from simple requests to complex\, multi
 -step workflows.\n\nWe will present selected results from prior work on ge
 nerating web tools\, integrating web tools into web agents\, and evaluatin
 g their effectiveness. These results highlight how tool design and tool-de
 finition exposure can affect task success and token usage\, and motivate f
 urther discussion of tool granularity\, tool composition\, and improvement
 s to the WebMCP interface. We will also discuss how WebMCP can support web
  tool execution that interleaves deterministic steps with agentic steps th
 at may use an LLM internally or draw on the user’s own agent for LLM-dep
 endent reasoning.\n\nThe central design question is how core WebMCP capabi
 lities can ensure generality\, interoperability\, and ease of use\, while 
 optional WebMCP capabilities provide well-defined support for different to
 ol granularities\, execution patterns\, and forms of tool–agent interact
 ion.\n\nWe propose to discuss the following topics:\n\n**Tool granularity 
 and selection.** Fine-grained\, single-function tools can serve small\, fo
 cused user requests and be reused across workflows. Larger tools can encap
 sulate workflows and reduce repeated agent decisions. Both large inventori
 es of small tools and numerous workflow-specific variants can increase con
 text and selection costs. How should tool definitions convey functional sc
 ope\, expected effects\, relationships to other tools\, and any agentic st
 eps\, so that an agent can choose the appropriate granularity for a reques
 t?\n\n**Dependent tool composition.** How can an agent plan multiple tool 
 calls in one decision\, using actual return values from earlier calls as i
 nput arguments for later calls without an intervening LLM call? What suppo
 rt is needed for discoverable output schemas\, references to return values
 \, input binding\, and validation? How should execution respond to errors\
 , cancellation\, navigation\, or changes in registered tools? Which respon
 sibilities belong in WebMCP and which belong in agent-side execution?\n\n*
 *Agentic steps using the user's own agent.** When a workflow requires LLM-
 dependent reasoning\, how can a tool request reasoning or a decision from 
 the user's own agent that invoked it\, and then continue execution? How ca
 n that agent apply the original task context and user-provided constraints
 ? What interfaces and lifecycle rules are needed to associate the request 
 with a pending tool execution\, suspend and resume execution\, and handle 
 cancellation or document unload? How should access to the agent's context 
 and capabilities be mediated?\n\n**Selective tool exposure and page observ
 ations.** How can tool registration and discovery be coordinated with sele
 ctive inclusion of tool definitions in the model context? How should agent
 s update their information when registered tools change or when user inter
 actions and application updates change the page context? What support is n
 eeded from applications\, browsers\, and agents to keep this information u
 seful while controlling context costs?\n\n**Page context and WebMCP's role
  alongside MCP.** How can WebMCP support tools whose availability and exec
 ution depend on the current document or live page state\, alongside tools 
 with broader application scope? Which page-context and lifecycle capabilit
 ies should be optional? How can shared UI\, existing client-side applicati
 on logic\, and browser-mediated execution support transitions between coll
 aborative workflows and autonomous task execution? What makes WebMCP usefu
 l beyond an MCP-only integration\, and how can the two work together?\n\n*
 *Goal(s):**\nIdentify and prioritize practical requirements for WebMCP int
 erface capabilities across different tool granularities\, composition patt
 erns\, and forms of tool–agent interaction.\n\nAgenda\n\n**Materials:**\
 n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/
 issues/36)
STATUS:CONFIRMED
CREATED:20261013T144513Z
LAST-MODIFIED:20261021T034139Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Pembroke Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:2b3e00a1-4e44-425b-a067-87e8d0e7d9da
DTSTAMP:20261021T034117Z
SUMMARY:Learn More About Joining TAG
DTSTART;TZID=Europe/Dublin:20261028T090000
DTEND;TZID=Europe/Dublin:20261028T100000
DESCRIPTION:https://www.w3.org/events/meetings/2b3e00a1-4e44-425b-a067-87e8
 d0e7d9da/\n\nThis is a session held by the TAG to inform potential nominee
 s for the 2026 election cycle what it's like to be a TAG member. It will b
 e an opportunity to ask questions\, better understand expectations and wor
 k load\, learn how we work\, and generally get a clearer view of how TAG p
 articipation works.\n\n**Goal(s):**\nTo understand how the TAG works and a
 nswer questions for those interested in running for election\n\nAgenda\n\n
 **Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac
 2026-breakouts/issues/26)\n\n**Attendance:**\nThis session is restricted t
 o TPAC registrants.
STATUS:CONFIRMED
CREATED:20261013T144442Z
LAST-MODIFIED:20261021T034117Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 01 and 02
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:bcc856d5-e42e-491d-8c5f-25151652555a
DTSTAMP:20261021T034152Z
SUMMARY:Making cross-document navigation feel more seamless
DTSTART;TZID=Europe/Dublin:20261028T090000
DTEND;TZID=Europe/Dublin:20261028T100000
DESCRIPTION:https://www.w3.org/events/meetings/bcc856d5-e42e-491d-8c5f-2515
 1652555a/\n\nCross-document navigations ("MPA" style) received a big boost
  in the last couple of years with cross-document view transitions.\n\nHowe
 ver\, this is incomplete! What do we do with the "uncanny valley" time bet
 ween starting a navigation and the next document being render-blocked?\n\n
 Brainstorming around multiple ideas in different stages of maturity:\n- tw
 o-phase view transitions\n- imperative `deferPageSwap`\n- Declarative Skel
 eton UI\n\n**Goal(s):**\nGet a good discussion about trade-offs for differ
 ent approaches from a broad audience\n\nAgenda\n\n**Materials:**\n- [Sessi
 on proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/42
 )
STATUS:CONFIRMED
CREATED:20261013T144533Z
LAST-MODIFIED:20261021T034152Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Leinster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:6787b150-b882-4b29-8189-eff85149baaa
DTSTAMP:20261021T034203Z
SUMMARY:Mitigating Shoulder Surfing via Progressively Enhanced Hardware-bas
 ed Rendering
DTSTART;TZID=Europe/Dublin:20261028T090000
DTEND;TZID=Europe/Dublin:20261028T100000
DESCRIPTION:https://www.w3.org/events/meetings/6787b150-b882-4b29-8189-eff8
 5149baaa/\n\nAs a community we are always developing ways to preserve and 
 enhance the user’s privacy. This often focuses on techniques that avoid\
 , or minimize\, the amount of user data that go over the wire. Another vec
 tor for privacy\, particularly in public places\, is the visual output fro
 m the user’s devices.\n\nSome devices have hardware rendering modes that
  make it harder for so-called ‘shoulder-surfing’ privacy compromises t
 o occur. We propose a simple spec - essentially an HTML attribute - to fla
 g potentially sensitive content for this rendering mode\, so that devices 
 may use it\, if they are able to.\n\nThis session will demonstrate how suc
 h a spec may work\, and will be a call for participation in developing the
  idea further.\n\n**Goal(s):**\nDemonstrate the potential of a simple Priv
 acy Screen spec\, and seek participation in the project.\n\nAgenda\n\n* De
 mo of how the spec may work in practice\, for content authors\, and users.
 \n* Short discussion on our implementation and conformance ideas.\n* Q&A\,
  next steps\n\n**Materials:**\n- [Session proposal on GitHub](https://gith
 ub.com/w3c/tpac2026-breakouts/issues/47)
STATUS:CONFIRMED
CREATED:20261013T144549Z
LAST-MODIFIED:20261021T034203Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 08
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:9d8e3079-033c-448a-be32-dbe89607f2d0
DTSTAMP:20261021T034050Z
SUMMARY:Modern real-time collaboration tooling for W3C
DTSTART;TZID=Europe/Dublin:20261028T090000
DTEND;TZID=Europe/Dublin:20261028T100000
DESCRIPTION:https://www.w3.org/events/meetings/9d8e3079-033c-448a-be32-dbe8
 9607f2d0/\n\nMany W3C groups continue to use IRC for real-time discussion 
 and meeting coordination. IRC has served W3C well\, particularly through i
 ntegrations with tools such as Zakim\, RRSAgent and GitHub bots\, but ther
 e are increasingly questions around whether it remains the best fit for ho
 w groups collaborate today.\n\nThis isn't a new question\, replacing or su
 pplementing IRC has been discussed within W3C for many years (see w3c/mode
 rn-tooling#16).\n\nRecent changes have brought the question up again. The 
 CSS Working Group recently lost its [publicly searchable IRC logs](https:/
 /github.com/w3c/csswg-drafts/issues/12054#issuecomment-3843634884)\, promp
 ting discussion about alternatives including IRCv3 and bridging the existi
 ng IRC channel to Matrix. Other W3C groups already use Matrix\, Slack and 
 other platforms alongside or instead of IRC.\n\n## Should we provide a com
 mon home?\n\nW3C groups currently use a variety of platforms for real-time
  collaboration\, including IRC\, Slack\, Discord\, Matrix and Zulip. In ma
 ny cases these have been adopted independently by individual Working Group
 s\, Community Groups or their members\, with groups sometimes responsible 
 for arranging hosting\, bots\, bridges or other infrastructure themselves.
 \n\nThis fragmentation can make participation harder: someone involved in 
 several W3C groups may need accounts and clients across several different 
 platforms\, each with different approaches to history\, search\, access an
 d moderation. It also means individual groups can end up solving the same 
 infrastructure problems independently\, or the burden [falls on individual
 s](https://github.com/w3c/csswg-drafts/issues/12054#issuecomment-284947451
 8) rather than the systems team.\n\nThis breakout would be an opportunity 
 to step back from any particular technical solution and discuss what W3C g
 roups actually need from real-time collaboration tooling.\n\nTopics could 
 include:\n\n- Persistent and searchable discussion history\n- Accessibilit
 y and ease of participation for new contributors\n- Integration with exist
 ing W3C meeting infrastructure (Zakim\, RRSAgent\, etc.)\n- Public partici
 pation versus access control and abuse prevention\n- Federation\, bridging
  and interoperability between platforms\n- Long-term hosting\, maintenance
  and ownership of collaboration infrastructure\n- Experiences from W3C gro
 ups already using Matrix\, Slack or other tools\n- Whether W3C should cont
 inue investing in IRC (including IRCv3)\, support additional platforms\, o
 r work towards a longer-term replacement\n\nIdeally\, we'd leave the sessi
 on with a clearer picture of common requirements\, what is working well fo
 r groups today\, and some potential next steps for experimentation or furt
 her work.\n\n**Goal(s):**\nclearer picture of common requirements for mode
 rn tooling\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](htt
 ps://github.com/w3c/tpac2026-breakouts/issues/14)
STATUS:CONFIRMED
CREATED:20261013T144404Z
LAST-MODIFIED:20261021T034050Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Lansdowne Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:14bb0ced-043f-48a7-8162-7a4fef923b5d
DTSTAMP:20261021T034229Z
SUMMARY:Originator Profile -- 2026 Progress Update
DTSTART;TZID=Europe/Dublin:20261028T090000
DTEND;TZID=Europe/Dublin:20261028T100000
DESCRIPTION:https://www.w3.org/events/meetings/14bb0ced-043f-48a7-8162-7a4f
 ef923b5d/\n\nOriginator Profile Collaborative Innovation Partnership (OP-C
 IP) has been implementing Originator Profile (OP) technology on websites t
 o demonstrate their authenticity and tamper-resistance. The effort is now 
 moving from proof-of-concept to real-world deployment.\n \n In FY2025\, 14
  media outlets and 2 local governments in Japan took part in our experimen
 t. We also successfully delivered OP-attached ads through an existing ad n
 etwork and displayed them on live websites.\n \n In this session\, we will
  share what we learned and discuss how these use cases can be extended to 
 other industries and regions.\n\n[OP-CIP introduction\n](https://originato
 r-profile.org/en-US/)\n[OP technology documents](https://docs.originator-p
 rofile.org/en/)\n\n**Goal(s):**\nTo help participants understand how OP wo
 rks in practice within a specific industry (media and public sectors)\, an
 d to discuss how this deployment can be expanded to other industries and r
 egions.\n\nAgenda\n\n1.Introduction and objectives : Session goal and over
 view of OP framework\n 2.Originator Profile in brief : How OP technology w
 orks?\n 3.FY2025 experiment results\n    3.1. Website implementation -- Pa
 rticipation of 14 media outlets and 2 local governments in Japan\n    3.2.
  OP-attached ads in live deployment: Distribution through an existing ad n
 etwork and display on live websites\n 4. Extending to other industries and
  regions \n 5. Open discussion\n\n**Materials:**\n- [Session proposal on G
 itHub](https://github.com/w3c/tpac2026-breakouts/issues/60)
STATUS:CONFIRMED
CREATED:20261013T144625Z
LAST-MODIFIED:20261021T034229Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 09
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:4b4bd185-84eb-4647-a091-1a59268c34b2
DTSTAMP:20261021T034059Z
SUMMARY:Web-based Digital Twins for Smart Cities
DTSTART;TZID=Europe/Dublin:20261028T090000
DTEND;TZID=Europe/Dublin:20261028T100000
DESCRIPTION:https://www.w3.org/events/meetings/4b4bd185-84eb-4647-a091-1a59
 268c34b2/\n\nThe Web-based Digital Twins for Smart Cities Interest Group (
 SCIG) would like to have annual joint discussion on related SDOs about our
  collaboration towards standards for Web-based Smart Cities as usual.\n\nA
 s the [group's Charter](https://www.w3.org/2024/06/smart-cities/) describe
 s\, SCIG's mission is working on the following:\n* identify and document u
 se cases and requirements that W3C specifications need to meet to support 
 various services within Smart Cities\,\n* obtain feedback from all stakeho
 lders on the usage of Web technologies for those services\,\n* gather expe
 rt input on important features for those services based on the Web technol
 ogy\,\n* and provide a forum for technical and business discussions relate
 d to those services.\n\nYou will learn the current best practices of cutti
 ng-edge standards for smart cities around possible framework and vocabular
 y ontologies\, and then see how Web standards could possibly counter the f
 ragmentation of existing smart city approaches.\n\n**Goal(s):**\nBased on 
 the [group's Charter](https://www.w3.org/2024/06/smart-cities/)\, we'll su
 mmarize the SCIG's discussion so far\, and ask the key stakholders from re
 lated SDOs about their standardization acitivies\, pain points and current
  best practices. Then we'll discuss what Web standards possibly could impr
 ove the fragmented situation.\n\nAgenda\n\n* Review the discussion so far\
 n* Get input from stakeholders about their work\, pain points and current 
 practices\n* Discuss what's still missing and what/how Web standards could
  help\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com
 /w3c/tpac2026-breakouts/issues/18)
STATUS:CONFIRMED
CREATED:20261013T144416Z
LAST-MODIFIED:20261021T034059Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 06
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:326deb6f-6b91-4fa5-8ec0-de1f0d036fa3
DTSTAMP:20261021T034317Z
SUMMARY:Where is (Web) Monetization going?
DTSTART;TZID=Europe/Dublin:20261028T090000
DTEND;TZID=Europe/Dublin:20261028T100000
DESCRIPTION:https://www.w3.org/events/meetings/326deb6f-6b91-4fa5-8ec0-de1f
 0d036fa3/\n\nAs we work towards a standard around Web Monetization\, we ar
 e opening this session to other efforts. We intend it to be a round table 
 of discussions and implementations. We will share more about:\n- State of 
 web Monetization ( stewarded by Interledger Foundatation)\n- Other impleme
 ntations x402\, MPP\n- Future challenges \n- Recommendations for Web Monet
 ization and other projects.\n\nThis session explores how Web Monetization 
 and the agentic web still share the same goal. Web Monetization set out to
  let browsers stream small\, automatic payments to creators as a third opt
 ion alongside ads and subscriptions\, and it is working now towards its na
 tive browser support. Generative AI answer engines and scraping agents now
  consume web content at scale without returning the clicks or revenue that
  used to flow back to creators\, turning a slow sustainability problem int
 o an acute one. Into that gap have stepped machine-native payment protocol
 s — x402 reviving HTTP's dormant 402 status code\, Google's AP2\, and in
 teroperable rails like Interledger's — built to let software pay for wha
 t it uses. The talk asks the W3C community to converge these two threads i
 nto one interoperable standard before competing protocols lock in a fragme
 nted default.\n\nNote: There may be co-Chairs representing the other techn
 ologies.\n\n**Goal(s):**\nDraft some future path of implementation for dif
 ferent Web Monetization streams\n\nAgenda\n\n1. Where Web Monetization is\
 n2. Why AI raises the stakes\n3. The agentic-payments wave\n4. Discussions
  and sharings\n4. Recommendations.\n\n**Materials:**\n- [Session proposal 
 on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/81)
STATUS:CONFIRMED
CREATED:20261013T144729Z
LAST-MODIFIED:20261021T034317Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 03
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:38d7b975-61b0-44ae-9d72-c68ed9876153
DTSTAMP:20261021T034114Z
SUMMARY:Agentic Web: permissions\, actions\, and alignment
DTSTART;TZID=Europe/Dublin:20261028T103000
DTEND;TZID=Europe/Dublin:20261028T113000
DESCRIPTION:https://www.w3.org/events/meetings/38d7b975-61b0-44ae-9d72-c68e
 d9876153/\n\nAI Agents acting on the user's behalf risk them being [misali
 gned](https://en.wikipedia.org/wiki/AI_alignment) with user intent and val
 ues. For anyone who has used the current generation of AI agents\, the ali
 gnment problem is very real when it comes to asking an agent to do even si
 mple tasks (i.e.\, inherent in all AI models is that they actively lie\, c
 heat\, deceive\, hallucinate\, exhibit bias\, or worse). \n\nHow do we des
 ign guardrails into web standards and APIs that can protect users from mis
 aligned AI agents? (i.e.\, where the user agent itself protects the user f
 rom misaligned agent). Though the agents can be helpful\, without user int
 ervention there's a real risk of AI systems going "off the rails" and inte
 ntionally or unintentionally doing reputable harm. \n\nHow can we make sur
 e that we build in checks and balances that AI agents cannot bypass: that 
 we always keep the human in the loop\, especially for critical actions?\n\
 n**Goal(s):**\nExplore the risk of the alignment problem to the web\n\nAge
 nda\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w
 3c/tpac2026-breakouts/issues/25)
STATUS:CONFIRMED
CREATED:20261013T144439Z
LAST-MODIFIED:20261021T034114Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Leinster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:76e95ad4-c74e-4ee9-9f0b-f5145fce7332
DTSTAMP:20261021T034110Z
SUMMARY:AI-friendly webpages
DTSTART;TZID=Europe/Dublin:20261028T103000
DTEND;TZID=Europe/Dublin:20261028T113000
DESCRIPTION:https://www.w3.org/events/meetings/76e95ad4-c74e-4ee9-9f0b-f514
 5fce7332/\n\nWith AI becoming ever more mainstream\, we want to begin the 
 conversation for defining what it means to be AI-friendly (implement WebMC
 P? Use JsonLD? etc) and whether there are things we might be able to provi
 de for free (lift existing attributes as declarative WebMCP? Use accessibi
 lity tree?)\n\n**Goal(s):**\nContinue the conversation from the AI agent w
 orkshop around building AI friendly websites and encouraging adoption of A
 I-friendly standards\n\nAgenda\n\n**Materials:**\n- [Session proposal on G
 itHub](https://github.com/w3c/tpac2026-breakouts/issues/23)
STATUS:CONFIRMED
CREATED:20261013T144433Z
LAST-MODIFIED:20261021T034110Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Ulster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:251b8098-0d74-452a-bf71-691652b58569
DTSTAMP:20261021T034238Z
SUMMARY:ArkWeb: Powering the Web on OpenHarmony
DTSTART;TZID=Europe/Dublin:20261028T103000
DTEND;TZID=Europe/Dublin:20261028T113000
DESCRIPTION:https://www.w3.org/events/meetings/251b8098-0d74-452a-bf71-6916
 52b58569/\n\nArkWeb is the web engine that powers **OpenHarmony**. It is a
  **Chromium-derived engine with a distinct feature set**\, its own release
  cadence\, and a growing set of contributions back to upstream web standar
 ds. This session introduces ArkWeb to the wider web community: where it is
  today\, what it adds beyond upstream Chromium\, how it is approaching AI-
 driven browsing\, and where it contributes to web standards. We want front
 -end developers and engine developers to know what ArkWeb is\, and to be a
 ble to participate in it.\n\n---\n\nOpenHarmony is an open source project 
 governed under the [OpenAtom Foundation](https://www.openatom.org/)\, with
  an ecosystem spanning phones\, tablets\, wearables\, and IoT devices. Its
  web engine\, ArkWeb\, is based on Chromium but is developed as a downstre
 am distribution rather than a downstream build: it carries its own platfor
 m integration layer\, its own security and privacy posture tuned to OpenHa
 rmony's application model\, and it **ships features that are not yet in up
 stream Chromium**.\n\nThat last point is the part most of the web communit
 y has not seen. Some of these additions are platform-specific (application
  lifecycle\, system ability integration\, distributed device scenarios). O
 thers are closer to the standard web surface and address gaps that the wid
 er community has also identified. We would like to walk through both categ
 ories candidly\, including where we think a feature belongs in a shared st
 andard rather than in one engine.\n\nThe session is deliberately an introd
 uction rather than a working meeting. The goal is for people who build for
  the web to leave with an accurate mental model of ArkWeb — what it is\,
  what it supports\, what it does not — and for engine and standards deve
 lopers to see concrete places where they could collaborate\, test against 
 ArkWeb\, or contribute. We are also interested in **hearing what the commu
 nity would need from us**: better conformance reporting\, participation in
  WPT\, presence in browser compatibility data\, or something else.\n\n**AI
  is a specific area where ArkWeb has been exploring actively**\, and where
  there is broad interest across browsers right now. We will describe our a
 pproach and be explicit about the open questions\, rather than presenting 
 it as a solved design.\n\n**Goal(s):**\nIntroduce the OpenHarmony ArkWeb e
 ngine to the web community\, and establish concrete paths for front-end an
 d engine developers to participate in and contribute to it.\n\nAgenda\n\n1
 . Overview of ArkWeb\n  - What ArkWeb is\, and where it sits in the OpenHa
 rmony architecture.\n  - Current status: engine version line\, release cad
 ence\, device coverage\, and how the engine is integrated with the OpenHar
 mony application model.\n  - Long-term goals for the engine and for the ec
 osystem around it.\n\n2. Features added beyond upstream Chromium\n  - Plat
 form-level additions driven by OpenHarmony requirements: application lifec
 ycle and process model\, system ability integration\, distributed and cros
 s-device scenarios\, and the ArkWeb public API surface.\n  - Web-facing ad
 ditions: which capabilities go beyond upstream today\, and how they are ex
 posed to authors.\n  - Where we think these belong long term — engine-sp
 ecific feature\, proposal for standardization\, or something in between.\n
 \n3. ArkWeb and AI\n  - What we have explored so far in agentic and AI-ass
 isted browsing.\n  - The read surface question: DOM\, accessibility tree\,
  or a purpose-built interface\, and the tradeoffs in privacy and stability
  for each.\n  - Action dispatch\, permission gating\, and how user consent
  is expressed.\n  - Open questions we have not resolved\, where we would l
 ike community input.\n\n4. Contribution to web standards\n  - Where ArkWeb
  participates today: spec work\, tests\, and compatibility data.\n  - Conf
 ormance and testing: our use of web-platform-tests and what we would need 
 in order to report results.\n  - Browser compatibility data: bringing ArkW
 eb into the ecosystem so that developers can see what is supported where.\
 n  - How the community can get involved\, and what we can commit to in ret
 urn.\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/
 w3c/tpac2026-breakouts/issues/64)
STATUS:CONFIRMED
CREATED:20261013T144637Z
LAST-MODIFIED:20261021T034238Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 01 and 02
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:f25640e1-5025-4d05-92de-e1bd4b41b656
DTSTAMP:20261021T034232Z
SUMMARY:Kickoff of the Content and Originator Authenticity CG
DTSTART;TZID=Europe/Dublin:20261028T103000
DTEND;TZID=Europe/Dublin:20261028T113000
DESCRIPTION:https://www.w3.org/events/meetings/f25640e1-5025-4d05-92de-e1bd
 4b41b656/\n\nWe have launched the Content and Originator Authenticity Comm
 unity Group (COA CG) and would like to start the discussion in person at T
 PAC. Everyone interested in the topic is welcome\, whether or not you have
  joined the group yet.\n[https://www.w3.org/community/coa-cg/](https://www
 .w3.org/community/coa-cg/)\n\nThe CG's mission is to serve as a hub for a 
 generalized authenticity architecture that fosters a vendor-neutral\, dece
 ntralized trust model for digital content on the web. It aims to provide t
 echnical guarantees for two things: (1) verifiable attestation of originat
 or identity attributes by third parties\, and (2) detection of content alt
 eration and tracking of content provenance. The group does not replace or 
 duplicate work in C2PA\, CAWG\, the OP community\, or other existing venue
 s. It focuses on the web-platform layer (URLs\, HTTP\, HTML\, and user age
 nts) where these technologies meet the web and each other. Privacy is a fi
 rst-class requirement: no mandatory verified identity\, and support for se
 lective disclosure and pseudonymous publication.\n\nWe plan to launch the 
 new group with three co-chairs\, to represent the wider community and ensu
 re impartial leadership.\n\nWho should attend: browser vendors and other u
 ser-agent implementers\; publishers and news organizations\; C2PA\, CAWG a
 nd OP participants\; Verifiable Credentials / DID experts\; web security a
 nd privacy experts (e.g.\, WebAppSec\, WICG\, Privacy WG)\; platform and A
 I service providers\; certification and attestation bodies\; and researche
 rs on trust and security indicators.\n\n**Goal(s):**\n1.Introduce the COA 
 CG's mission and scope to the wider W3C community and collect feedback. 2.
 Discuss the longer-term aim of building a shared understanding of how tech
 nologies in this field relate to each other. We'd like to hear participant
 s’ views. 3.Identify stakeholders and gather initial use cases\, concern
 s\, and gaps\, especially from user-agent implementers and privacy reviewe
 rs.\n\nAgenda\n\n1.Welcome and the CG's mission and scope\n2.Introduction 
 of Originator Profile technology\, for those new to it \n3.Perspectives fr
 om other stakeholders\n4.Open discussion: use cases\, gaps\, and prioritie
 s for the first work items (landscape and gap analysis\, use cases and req
 uirements\, web integration report)\n5.Chairs\, ways of working (public Gi
 tHub\, mailing list)\, and next steps\n\n**Materials:**\n- [Session propos
 al on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/61)
STATUS:CONFIRMED
CREATED:20261013T144628Z
LAST-MODIFIED:20261021T034232Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 09
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:f43c914a-a020-46c9-a0fc-91559aae32c5
DTSTAMP:20261021T034043Z
SUMMARY:New requirements for Timed Text\, enabled by AI
DTSTART;TZID=Europe/Dublin:20261028T103000
DTEND;TZID=Europe/Dublin:20261028T113000
DESCRIPTION:https://www.w3.org/events/meetings/f43c914a-a020-46c9-a0fc-9155
 9aae32c5/\n\nSee https://github.com/w3c/media-and-entertainment/issues/122
  for proposal\, context and approach.\n\nThis breakout would be an opportu
 nity for the [AIRFOT task force](https://www.w3.org/groups/tf/airfot/) of 
 the Media and Entertainment Interest Group to engage with W3C folk who wis
 h to contribute new\, or potential new\, requirements for Timed Text\, esp
 ecially those enabled or made cost-effective by the use of LLMs ("AI").\n\
 n**Goal(s):**\nGather new AI-related requirements for Timed Text\n\nAgenda
 \n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/
 tpac2026-breakouts/issues/11)
STATUS:CONFIRMED
CREATED:20261013T144354Z
LAST-MODIFIED:20261021T034043Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 05
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:316ef5c7-14bc-43f3-8588-c0952b2947bb
DTSTAMP:20261021T034259Z
SUMMARY:Prohibit HTTP Link header preload from subresources
DTSTART;TZID=Europe/Dublin:20261028T103000
DTEND;TZID=Europe/Dublin:20261028T113000
DESCRIPTION:https://www.w3.org/events/meetings/316ef5c7-14bc-43f3-8588-c095
 2b2947bb/\n\nThe HTTP `Link` header has functionality to initiate the reso
 urce preloading as the HTML `<link>` tag does. While preloading from main 
 documents is useful and has well-defined behaviors in the spec\, preloadin
 g from subresources is not used widely except for `rel=preconnect` nor def
 ined clearly in the spec. We propose prohibiting `Link` header preloading 
 (`prefetch`\, `preload`\, `modulepreload`\, etc.) from subresources.\n\nNo
 te: Until recently Chrome supported this feature but don't support it now.
  Other major browsers do not support this feature.\n\n**Goal(s):**\nGet fe
 edback from a wider audience for the new directions\n\nAgenda\n\n**Materia
 ls:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-brea
 kouts/issues/73)
STATUS:CONFIRMED
CREATED:20261013T144705Z
LAST-MODIFIED:20261021T034259Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 08
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:4d74f4d4-e065-4d71-8e7b-10ce91d6b150
DTSTAMP:20261021T034227Z
SUMMARY:Security and privacy considerations for peripherals
DTSTART;TZID=Europe/Dublin:20261028T103000
DTEND;TZID=Europe/Dublin:20261028T113000
DESCRIPTION:https://www.w3.org/events/meetings/4d74f4d4-e065-4d71-8e7b-10ce
 91d6b150/\n\nMozilla began prototyping peripherals APIs over a decade ago 
 as part of the FirefoxOS project. Chromium-based browsers have shipped API
 s for peripheral devices starting in 2017 with WebBluetooth\, followed by 
 WebUSB\, WebNFC\, WebSerial and WebHID. In 2026\, Mozilla shipped WebSeria
 l in Firefox. While these APIs have clear developer demand there have also
  been many concerns about their impact on user security and privacy. In th
 is session we will look at these concerns\, the mitigations that are curre
 ntly shipped and have a discussion about where the peripheral ecosystem ca
 n go from here.\n\n**Goal(s):**\nBuild an understanding of the current per
 ipheral landscape and how it interfaces with the web.\n\nAgenda\n\n**Mater
 ials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-br
 eakouts/issues/59)
STATUS:CONFIRMED
CREATED:20261013T144622Z
LAST-MODIFIED:20261021T034227Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 03
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:db76a8ad-e6d5-4d52-bfb7-9680f7a8b1d1
DTSTAMP:20261021T034308Z
SUMMARY:Towards an AI policy for W3C
DTSTART;TZID=Europe/Dublin:20261028T103000
DTEND;TZID=Europe/Dublin:20261028T113000
DESCRIPTION:https://www.w3.org/events/meetings/db76a8ad-e6d5-4d52-bfb7-9680
 f7a8b1d1/\n\nAI tools are used more and more across W3C groups and reposit
 ories. Many organizations have adopted\, or are in the process of adopting
 \, AI policies. What general stance\, specific provisions and guardrails s
 hould W3C adopt about the use of AI tools in W3C Standardization work?\n\n
 To seed the discussion\, I prepared an [initial draft AI policy](https://w
 ww.w3.org/2026/10/draft-ai-policy.html). It builds on the [Use of Large La
 nguage Models in Standards Work](https://www.w3.org/TR/llms-standards/) do
 cument published by the Advisory Board. This breakout will present the dra
 ft proposal\, invite feedback\, and seek convergence on the general direct
 ion and specific provisions that such a policy could set\, including:\n\n-
  Contributor responsibility\n- Contribution guidelines\n- Possible disclos
 ure requirements\n- Handling of policy violations\n\nInitial feedback and 
 suggestions are welcome through comments on this issue.\n\n**Goal(s):**\nS
 eek convergence on a possible AI policy for W3C\n\nAgenda\n\n**Materials:*
 *\n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-breakout
 s/issues/77)
STATUS:CONFIRMED
CREATED:20261013T144717Z
LAST-MODIFIED:20261021T034308Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Pembroke Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:e6db16a1-73dd-48a4-940a-94cfbb3f2826
DTSTAMP:20261021T034223Z
SUMMARY:W3C's Strategic Direction: Future of the Open Web
DTSTART;TZID=Europe/Dublin:20261028T103000
DTEND;TZID=Europe/Dublin:20261028T113000
DESCRIPTION:https://www.w3.org/events/meetings/e6db16a1-73dd-48a4-940a-94cf
 bb3f2826/\n\nThe Open Web is shrinking. This is due to unprecedented struc
 tural shifts: the explosion of LLM-generated content\, overwhelming LLM cr
 awling traffic and the rise of autonomous AI agents. The role W3C has play
 ed to date is no longer sufficiently supporting the long-term health of an
  open\, interoperable\, and human-centric web.\n\nSimultaneously\, W3C's v
 iability is at risk. Its value proposition has declined\, leading to a mul
 tiyear drop in membership and concerning expenditures relative to income.\
 n\nThis breakout session invites community members to critically examine t
 he W3C’s future strategic direction with the Board's [Strategy](https://
 www.w3.org/Member/bod/strategy/) as a starting point. We will confront cor
 e questions:\n\n1. How can W3C focus on high quality\, interoperable\, wor
 ld-relevant open web standards supported by user-impactful implementations
 ? What does W3C need to do and do well\, and (more importantly) what shoul
 d W3C de-prioritize?\n2. How can we evolve W3C's governance to facilitate 
 such continuous prioritization\, while staying aligned with our Vision and
  principles\, to ensure W3C's financial sustainability?\n3. W3C has lost e
 ngagement from the broader web community. Many consider open source projec
 ts either a replacement for or more important than open standards. How can
  W3C rebuild trust and relevance with the web community to work together t
 o evolve the web? For example\, how can W3C impact standards around emergi
 ng AI paradigms such as agentic web protocols?\n\nChairs: Chris Wilson\, T
 antek Çelik\n\n**Goal(s):**\nTo gather candid community perspectives\, su
 rface diverging priorities across stakeholders\, and synthesize key recomm
 endations for the W3C Board of Directors and Team to consider as part of o
 ngoing strategy and organizational evolution.\n\nAgenda\n\n**Materials:**\
 n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/
 issues/57)
STATUS:CONFIRMED
CREATED:20261013T144616Z
LAST-MODIFIED:20261021T034223Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Lansdowne Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:9078a773-7154-4c1f-8819-3d869b1f5766
DTSTAMP:20261021T034046Z
SUMMARY:Web Accessibility Evaluation Using AI agents
DTSTART;TZID=Europe/Dublin:20261028T103000
DTEND;TZID=Europe/Dublin:20261028T113000
DESCRIPTION:https://www.w3.org/events/meetings/9078a773-7154-4c1f-8819-3d86
 9b1f5766/\n\nAI agents are becoming an important tool for assessing compli
 ance with web accessibility standards. However\, some success criteria rem
 ain difficult to verify using traditional evaluation tools or even AI agen
 ts. We conducted a study to evaluate whether AI tools (LLMs and AI agents)
  can assess robust content\, such as video and blinking content. The resul
 ts were presented at the 23rd International Web for All Conference (W4A’
 26)\, the premier venue for web accessibility research\, on June 20th\, in
  Dubai\, United Arab Emirates.\n\nThis breakout session will demonstrate t
 he research findings\, showcase the tool we developed to consolidate the r
 esults\, and open the floor for discussion.\n\n- Paper: https://dl.acm.org
 /doi/10.1145/3800424.3800445\n- Tool: https://github.com/cewebbr/mastif\n-
  Video introducing the tool: https://www.youtube.com/watch?v=T47AmufeU10\n
 \n**Goal(s):**\nThe goal of this breakout session is to foster discussion 
 about the future of web accessibility compliance with AI\, exploring both 
 the opportunities and the limitations of using AI in this field.\n\nAgenda
 \n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/
 tpac2026-breakouts/issues/12)
STATUS:CONFIRMED
CREATED:20261013T144357Z
LAST-MODIFIED:20261021T034046Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 06
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:536282c3-f71c-45c0-989b-cbc65641c68e
DTSTAMP:20261021T034028Z
SUMMARY:Agent Security
DTSTART;TZID=Europe/Dublin:20261028T114500
DTEND;TZID=Europe/Dublin:20261028T124500
DESCRIPTION:https://www.w3.org/events/meetings/536282c3-f71c-45c0-989b-cbc6
 5641c68e/\n\nDiscuss agent security & get feedback on web platform securit
 y proposals.\n\n**Goal(s):**\nDiscuss agent security & get feedback on web
  platform security proposals.\n\nAgenda\n\n**Materials:**\n- [Session prop
 osal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/5)
STATUS:CONFIRMED
CREATED:20261013T144336Z
LAST-MODIFIED:20261021T034028Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Pembroke Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:9950f238-6c01-40e1-9cba-f187510ba741
DTSTAMP:20261021T034101Z
SUMMARY:Autofill CG - a year in review
DTSTART;TZID=Europe/Dublin:20261028T114500
DTEND;TZID=Europe/Dublin:20261028T124500
DESCRIPTION:https://www.w3.org/events/meetings/9950f238-6c01-40e1-9cba-f187
 510ba741/\n\nThe Autofill CG was formed after a successful breakout in las
 t year's TPAC. We wanted to come back to the TPAC crowd with updates on wh
 at we've been up to\, experimental results on our proposals and to continu
 e the conversation around autofill.\n\n**Goal(s):**\nAmplify the conversat
 ions around Autofill and standard proposals.\n\nAgenda\n\n**Materials:**\n
 - [Session proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/i
 ssues/19)
STATUS:CONFIRMED
CREATED:20261013T144419Z
LAST-MODIFIED:20261021T034101Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Ulster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:a32a4bf4-ee16-42b0-bab9-9ee8f61827fb
DTSTAMP:20261021T125618Z
SUMMARY:Building a W3C Open Source Program
DTSTART;TZID=Europe/Dublin:20261028T114500
DTEND;TZID=Europe/Dublin:20261028T124500
DESCRIPTION:https://www.w3.org/events/meetings/a32a4bf4-ee16-42b0-bab9-9ee8
 f61827fb/\n\nIn September W3C [announced](https://www.w3.org/blog/2026/w3c
 -launches-first-pilot-of-program-to-support-open-source-projects/) the fir
 st pilot project of a new [W3C Open Source Program](https://github.com/w3c
 -oss/open-source-program): the [CanIVC dashboard](https://github.com/w3c-o
 ss/canivc) contributed by Digital Bazaar. W3C is developing the program to
  support projects that foster the adoption and interoperability of Web tec
 hnology\, and to improve the operational side of W3C's standardization and
  incubation programs.\n\nAt this breakout session we'll share our experien
 ce leading up to the first pilot\, and how you can get involved in the nex
 t stage of program development in the [W3C Open Source Program CG](https:/
 /www.w3.org/groups/cg/w3c-open-source-program/). We also hope to hear from
  people who might want to bring open source projects to this program.\n\n*
 *Goal(s):**\nRaise awareness about the development of a W3C Open Source Pr
 ogram\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https://
 github.com/w3c/tpac2026-breakouts/issues/78)
STATUS:CONFIRMED
CREATED:20261013T144720Z
LAST-MODIFIED:20261021T125618Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Lansdowne Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:834374fb-61b0-4578-8c54-cf6534f5e6e3
DTSTAMP:20261021T034303Z
SUMMARY:Facilitating polyfillability beyond JS
DTSTART;TZID=Europe/Dublin:20261028T114500
DTEND;TZID=Europe/Dublin:20261028T124500
DESCRIPTION:https://www.w3.org/events/meetings/834374fb-61b0-4578-8c54-cf65
 34f5e6e3/\n\nAuthors often want to use new web platform features before th
 ey reach Baseline\, filling the gap in userland — whether that's called 
 a shim\, a polyfill\, a ponyfill\, or a fallback.\n\nBut polyfills[^1] are
  only attractive when their complexity is reasonable. Developers do not wa
 nt a polyfill at any cost\; beyond a certain level of complexity\, a polyf
 ill is as good as none.\n\nDone right\, polyfilling[^1] provides substanti
 al downstream value to end users\, [the Web Platform's primary constituent
 s](https://www.w3.org/TR/design-principles/#priority-of-constituencies): n
 ative features are typically more performant\, more accessible\, and more 
 i18nclusive\, and a good polyfill gets them to users sooner.\n\nHowever\, 
 not all kinds of web platform features are equally amenable to this:\n- **
 JS is leading the way.** Most JS features can be polyfilled well\, and usi
 ng them this way involves minimal or no additional friction.\n- **CSS is t
 he biggest gap.** Unknown syntax is ignored entirely\, so a CSS polyfill m
 ust re-implement the browser's stylesheet fetching and parsing *before* it
  gets to any actual polyfill logic. Even then\, a robust polyfill must rea
 ct to changes\, and the platform provides no primitives for that. We see o
 ver and over that even when CSS polyfills exist\, authors avoid them: they
  are perceived as complex\, large\, insufficiently robust\, and composing 
 poorly with tooling\, including other CSS polyfills.\n- **HTML sits in bet
 ween.** HTML features can be polyfilled reasonably well as a first approxi
 mation\, but limitations (e.g. parser behavior\, form association\, focus/
 a11y semantics\, shadow DOM boundaries) make these polyfills less robust a
 nd less performant than the native feature.\n\nThis session will explore:\
 n\n* What are the platform gaps preventing good polyfills\, and what is th
 e plan to address them? Are there any low-hanging fruits\, such as APIs th
 at would help with polyfilling without being polyfilling-specific?\n* How 
 does improving polyfillability shift incentives across the ecosystem? If n
 ew features deliver value earlier\, browsers have a stronger incentive to 
 be first to ship but less pressure to be last\, and the first implementati
 on gains more influence over the feature's eventual shape. How do we keep 
 premature polyfills from creating design lock-in without adding friction f
 or *appropriate* polyfilling?\n\n**Out of scope:** Whether individual feat
 ures should be designed around polyfillability. This session is about plat
 form-level primitives that make userland fallbacks possible\, not about co
 nstraining feature design.\n\n[^1]: "Polyfill" is used throughout for simp
 licity\; the discussion covers all patterns for using new web features wit
 h a userland fallback when unsupported\, including ponyfills\, shims\, and
  ad hoc fallbacks.\n\nNote: Additional Chairs TBD\n\n**Goal(s):**\nProduce
  a list of high-level platform gaps that would make userland polyfills/fal
 lbacks more viable across the platform\, and identify what in the [TAG's g
 uidance](https://www.w3.org/2001/tag/doc/polyfills/#risks-of-premature-pol
 yfilling) on premature polyfilling needs revisiting if polyfills become mo
 re viable.\n\nAgenda\n\nTBD\n\n**Materials:**\n- [Session proposal on GitH
 ub](https://github.com/w3c/tpac2026-breakouts/issues/75)
STATUS:CONFIRMED
CREATED:20261013T144711Z
LAST-MODIFIED:20261021T034303Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 05
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:618abc30-d38b-4210-ba45-6821d02a842e
DTSTAMP:20261021T034306Z
SUMMARY:FedCM Across Browsers: What Would It Take?
DTSTART;TZID=Europe/Dublin:20261028T114500
DTEND;TZID=Europe/Dublin:20261028T124500
DESCRIPTION:https://www.w3.org/events/meetings/618abc30-d38b-4210-ba45-6821
 d02a842e/\n\nFedCM is seeing increasing deployment by identity providers a
 nd relying parties\, alongside continued implementation and experimentatio
 n in Chromium. Current work also extends beyond the API's original relatio
 nship to third-party cookie deprecation\, including multi-IdP user experie
 nces\, decentralized identity-provider discovery and registration\, and re
 lated browser-mediated identity capabilities.\n\nAt the same time\, there 
 is not comparable implementation activity across the major browser engines
 .\n\nAs deployment and implementation continue\, that gap may become incre
 asingly significant. FedCM could develop into a widely used Web capability
  based largely on one browser-engine implementation\, even while substanti
 al architectural\, privacy\, security\, user-experience\, or product quest
 ions remain unresolved across the broader browser community.\n\nWe would l
 ike to use this breakout to establish a shared understanding of where FedC
 M is today and ask whether the growing implementation gap is a problem for
  the Web—and\, if so\, what might usefully be done about it.\n\nQuestion
 s for discussion include:\n\n- What problems does [FedCM](https://www.w3.o
 rg/TR/fedcm/) solve for the Web today\, independently of third-party cooki
 e deprecation?\n- How do newer uses—including multi-IdP experiences\, [d
 ecentralized IdP discovery and registration](https://atproto.com/blog/work
 ing-to-decentralize-fedcm)\, and related browser-mediated identity capabil
 ities such as [email verification](https://developer.chrome.com/docs/ident
 ity/email-verification)  affect that assessment?\n- What can we learn from
  current FedCM deployment and implementation experience?\n- Does increasin
 g deployment without corresponding implementation across browser engines c
 reate interoperability\, architectural\, or governance risks?\n- What conc
 erns or missing pieces currently limit interest from other browser engines
 ?\n- Are there changes to FedCM's architecture\, API\, privacy model\, sec
 urity model\, or user experience that would materially affect that assessm
 ent?\n- What evidence\, implementation experience\, research\, or interope
 rability work would help the broader community evaluate FedCM?\n- Is there
  a plausible path toward broader browser engagement\, and what could the F
 edCM community do to support it?\n\n#### Suggested pre-reading\n\nParticip
 ants may find the following useful background before the session:\n\n- [Fe
 derated Credential Management API](https://www.w3.org/TR/fedcm/)](https://
 www.w3.org/TR/fedcm/) — the W3C specification.\n- [Working to Decentrali
 ze FedCM](https://atproto.com/blog/working-to-decentralize-fedcm) — work
  supported by Bluesky exploring how FedCM and IdP registration could work 
 in decentralized environments where relying parties cannot start with a fi
 xed list of identity providers.\n- [Email Verification](https://developer.
 chrome.com/docs/identity/email-verification) — an experimental browser-m
 ediated approach to verifying control of an email address that builds on F
 edCM infrastructure and concepts.\n\nThe pre-reading is intended to establ
 ish a common understanding of the current work so that the session can foc
 us on areas of agreement\, disagreement\, and uncertainty rather than reco
 nstructing the history of the proposal.\n\n**Goal(s):**\nThe goal of this 
 session is to make sure that continued deployment does not substitute for 
 explicit discussion about whether FedCM is becoming a sound\, interoperabl
 e Web platform capability.\n\nAgenda\n\n**Materials:**\n- [Session proposa
 l on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/76)
STATUS:CONFIRMED
CREATED:20261013T144714Z
LAST-MODIFIED:20261021T034306Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 09
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:7bd40799-f6cc-4e82-90a6-e504f13ea1a7
DTSTAMP:20261021T034236Z
SUMMARY:Observability for on-device AI: tracing the Prompt API with OpenTel
 emetry
DTSTART;TZID=Europe/Dublin:20261028T114500
DTEND;TZID=Europe/Dublin:20261028T124500
DESCRIPTION:https://www.w3.org/events/meetings/7bd40799-f6cc-4e82-90a6-e504
 f13ea1a7/\n\nWith built-in AI APIs such as the Prompt API\, inference move
 s from the server into the browser\, and the telemetry that developers rel
 y on to debug and evaluate AI features goes with it. We present an open-so
 urce proof of concept that traces Prompt API calls with OpenTelemetry\, fo
 llowing the GenAI semantic conventions.\n\nWe then open three questions:\n
 \n1. Web Machine Learning: what observability signals should built-in AI A
 PIs expose natively?\n2. Distributed Tracing: how should one trace connect
  on-device inference to the backend in a hybrid gen ai app?\n3. Privacy: h
 ow can prompts\, tool calls and media be observed without exposing user da
 ta?\n\n**Goal(s):**\nGauge interest for observability\, trace propagation 
 and privacy questions that built-in AI APIs should address\n\nAgenda\n\nTB
 A\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c
 /tpac2026-breakouts/issues/63)
STATUS:CONFIRMED
CREATED:20261013T144634Z
LAST-MODIFIED:20261021T034236Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 08
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:7cbcb701-7df3-4fbc-ada4-5321a51fb7ea
DTSTAMP:20261021T034057Z
SUMMARY:Proposed Digital Policy Working Group Charter
DTSTART;TZID=Europe/Dublin:20261028T114500
DTEND;TZID=Europe/Dublin:20261028T124500
DESCRIPTION:https://www.w3.org/events/meetings/7cbcb701-7df3-4fbc-ada4-5321
 a51fb7ea/\n\nDiscussion and consensus-building for the new proposed Digita
 l Policy Working Group Charter that will extend and build on the success o
 f the W3C ODRL Recommendations.\n\nAfter a very successful [W3C ODRL Works
 hop in London](https://www.w3.org/2026/ODRLWS/agenda.html) where the commu
 nity discussed the future options of ODRL\, we will discuss a [draft chart
 er](https://w3c.github.io/odrl/w3c-wg-draft-charter-2026/dpwg-draft-charte
 r.html).\n\n**Goal(s):**\nConfirm the [draft charter](https://w3c.github.i
 o/odrl/w3c-wg-draft-charter-2026/dpwg-draft-charter.html) for the Digital 
 Policy Working Group.\n\nAgenda\n\n**Materials:**\n- [Session proposal on 
 GitHub](https://github.com/w3c/tpac2026-breakouts/issues/17)
STATUS:CONFIRMED
CREATED:20261013T144413Z
LAST-MODIFIED:20261021T034057Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 01 and 02
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:ae07ebcd-f27c-425e-b4c2-9c0203aabf1d
DTSTAMP:20261021T034201Z
SUMMARY:Storage capabilities for session resumption
DTSTART;TZID=Europe/Dublin:20261028T114500
DTEND;TZID=Europe/Dublin:20261028T124500
DESCRIPTION:https://www.w3.org/events/meetings/ae07ebcd-f27c-425e-b4c2-9c02
 03aabf1d/\n\nUsers don't like restarting their browser and losing state\, 
 and commonly maintain very long running sessions (weeks/months). Since upd
 ates\, including security patches\, typically don't apply to running proce
 sses\, this leaves such users exposed to known vulnerabilities for extende
 d periods of time long after patches have been released. In the world of a
 gentic scrutiny of open source codebases\, there are many recently patched
  vulnerabilities at any given time! We will discuss how browser vendors an
 d site authors can collaborate to close the "patch gap"\, with a specific 
 focus on web-exposed APIs for extending the scope of "session" across tab 
 restart.\n \nAlthough couched above in terms of browser restart\, resumabi
 lity has utility for history navigation\, reload\, resumed tabs\, OS resta
 rt\, etc.\n\nNote: Erik Anderson will chair the session.\n\n**Goal(s):**\n
 Gauge appetite for new session-linked or other short-term storage capabili
 ties\, and where site authors see pain points in providing seamless resuma
 bility.\n\nAgenda\n\n- Pain points for supporting resumption\, from perspe
 ctive of a web dev?\n- Proposal: [session-y/ref-counted storage](https://g
 ithub.com/WICG/storage-buckets/issues/44) (beyond Session Storage)\n- Prop
 osal: support for more types in History & Navigation APIs' state (for the 
 [tab resumption case](https://github.com/whatwg/html/issues/12809))\n\n**M
 aterials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac202
 6-breakouts/issues/46)
STATUS:CONFIRMED
CREATED:20261013T144546Z
LAST-MODIFIED:20261021T034201Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 06
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:2510f7a3-526a-4950-8e98-cb439003b382
DTSTAMP:20261021T034332Z
SUMMARY:Understanding media metadata use cases on the web
DTSTART;TZID=Europe/Dublin:20261028T114500
DTEND;TZID=Europe/Dublin:20261028T124500
DESCRIPTION:https://www.w3.org/events/meetings/2510f7a3-526a-4950-8e98-cb43
 9003b382/\n\n[WebVMT](https://www.w3.org/TR/webvmt/) is designed for all v
 ideo and audio use cases with additional information in any format\, inclu
 ding binary. That additional information is attached to the outside of the
  media file so it's easily accessible\, agnostic of video/audio encoding a
 nd metadata format\, and integrated with HTML cues for web apps.\n\nExampl
 e use cases include:\n * Displaying an animated map with footage from dron
 e cameras\, dash cams\, body cameras and smartphones.\n * Searching metada
 ta to quickly find relevant video content in a single file or in an online
  archive.\n * Accessing ID3 tags or synchronising MIDI data with an audio 
 file.\n * Annotating video for training and testing an image recognition a
 lgorithm.\n * Enhancing video with an AI-generated metadata stream to dete
 ct objects\, smiling faces or body poses.\n * Augmenting video with synchr
 onised datasets such as maritime\, flight or star trackers.\n\nBreakout se
 ssions offer an opportunity to engage with a broader audience to share ide
 as from [OGC's innovation programme](https://www.ogc.org/apply/testbeds/) 
 and identify new use cases from diverse web communities.\n\nJoin our discu
 ssion to discover how your media can be enriched with metadata on the web.
 \n\n**Goal(s):**\nFoster better understanding of how media metadata can be
  integrated with web apps\, find new use cases and identify additional req
 uirements for the web\n\nAgenda\n\n1. Short presentation of media metadata
  use cases and demos\, including OGC Testbed results (15 mins)\n 1. Group 
 discussion to identify new use cases and how these can be integrated with 
 HTML (30 mins)\n 1. Summary of new use cases and any additional requiremen
 ts identified (10 mins)\n\n**Materials:**\n- [Session proposal on GitHub](
 https://github.com/w3c/tpac2026-breakouts/issues/88)
STATUS:CONFIRMED
CREATED:20261015T132851Z
LAST-MODIFIED:20261021T034332Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 03
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:cf6e6793-c0f3-4636-8f49-d6cd8165191e
DTSTAMP:20261021T034205Z
SUMMARY:What is good AI training\, from an accessibility perspective?
DTSTART;TZID=Europe/Dublin:20261028T114500
DTEND;TZID=Europe/Dublin:20261028T124500
DESCRIPTION:https://www.w3.org/events/meetings/cf6e6793-c0f3-4636-8f49-d6cd
 8165191e/\n\nWe often find accessibility issues in AI output\, and a big p
 art of these issues may be resolved by improving the quality of the AI’s
  training. Problems include:\n\n* Generated pages and software code as ina
 ccessible as most of today's web\n\n* Under- or otherwise mis-representati
 on of people with disabilities\n\n* Failing to respond to the needs of the
  user.\n\n   * E.g. video description not taking into account a blind pers
 on’s needs\; caption summaries not taking into account the needs of some
 one hard of hearing.\n\n* Incorrect guidance on how to code accessible con
 tent\n\nIf we train AI on a largely inaccessible web\, we are liable to ge
 t inaccessible output as a result.\n\nThis session is proposed to demonstr
 ate some of these issues\, and to ask the question: how can we improve the
  situation? What could we do to increase the quality of input to AI system
 s\, such that we can expect better output?\n\n**Goal(s):**\nSuggestions fo
 r how we can improve the quality of training and thus output of AI systems
 \, from an accessibility perspective\n\nAgenda\n\n* Recap of some of the p
 roblems we have seen\, which we feel could be mitigated by better training
  (referencing documents from Research Questions TF\, the W3C Team\, and We
 b Machine Learning WG).\n\n* Blue-sky discussion around potential solution
 s. This may include social\, organizational\, and technical solutions (e.g
 . reinforcement learning\, the extent to which inference could help)\, or 
 other means.\n\n* Focusing on any that have general interest within the au
 dience\, which seem feasible.\n\n* Enumerating what would be needed to mak
 e them succeed\; particularly which groups we would need to get involved.\
 n\n* How would we measure success?\n\n* Planning next steps (interest in a
  CG\, or a symposium\, or other approach)\n\n**Materials:**\n- [Session pr
 oposal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/48)
STATUS:CONFIRMED
CREATED:20261013T144552Z
LAST-MODIFIED:20261021T034205Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Leinster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:85e1e0fb-5f85-4dce-83bf-ba137f848c09
DTSTAMP:20261021T034023Z
SUMMARY:Accessibility Compat Data: What is "supported"?
DTSTART;TZID=Europe/Dublin:20261028T140000
DTEND;TZID=Europe/Dublin:20261028T150000
DESCRIPTION:https://www.w3.org/events/meetings/85e1e0fb-5f85-4dce-83bf-ba13
 7f848c09/\n\nAccessibility Compat Data is expanding browser support data b
 y including accessibility support. ACD is using existing testing infra (WP
 T\, ARIA-AT) to inform developers about what is/isn't accessibility suppor
 ted. We've been working with folks in the Interop Accessibility group\, AR
 IA-AT\, Baseline and BCD owners with the goal of integrating accessibility
  support information into Baseline and BCD. This raises a number of questi
 ons:\n1. How do we evaluate support?\n2. How do we present support status 
 to developers?\n3. What do we do with web features that are currently Base
 line "widely available" or BCD "supported"\, but are not accessibility-sup
 ported?\n\nWe'd love to talk with browser vendors\, accessibility professi
 onals\, and developer advocates.\n\n**Goal(s):**\nCollaborate with browser
  vendors about making web features accessibility supported.\n\nAgenda\n\n*
 *Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2
 026-breakouts/issues/3)
STATUS:CONFIRMED
CREATED:20261013T144330Z
LAST-MODIFIED:20261021T034023Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Pembroke Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:542e02d7-1a1d-4345-b920-9576570d0537
DTSTAMP:20261021T034048Z
SUMMARY:Accessibility for “Manga”: Challenges and Discussions
DTSTART;TZID=Europe/Dublin:20261028T140000
DTEND;TZID=Europe/Dublin:20261028T150000
DESCRIPTION:https://www.w3.org/events/meetings/542e02d7-1a1d-4345-b920-9576
 570d0537/\n\nAccessibility conformance for ebooks is required in the world
  but standards or best practices for "Manga" contents are not yet provided
 .\nDPFJ (Digital Publishers Federation of Japan) started to discuss what k
 ind of accessibility conformance should be done for "Manga" contents for g
 lobal market.\nIn this session\, we will show the current strategy of acce
 ssibility for "Manga" contents from Japan with difficulties and issues.\n\
 nYukio Tomikura (Kodansha) is expected to participate.\n\n**Goal(s):**\nTh
 e goal of this breakout session is to explain the approach of accessibilit
 y for "Manga" contents from Japan and to obtain opinions and issues for th
 at through demos and discussions.\n\nAgenda\n\nTBD\n\n**Materials:**\n- [S
 ession proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/issue
 s/13)
STATUS:CONFIRMED
CREATED:20261013T144400Z
LAST-MODIFIED:20261021T034048Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Leinster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:1f92e260-1374-406a-9207-1620c7065277
DTSTAMP:20261021T034252Z
SUMMARY:Closing the Web "Appyness" Gap: Focus\, Selection\, and Vector Time
 lines
DTSTART;TZID=Europe/Dublin:20261028T140000
DTEND;TZID=Europe/Dublin:20261028T150000
DESCRIPTION:https://www.w3.org/events/meetings/1f92e260-1374-406a-9207-1620
 c7065277/\n\nOver the past few years\, we've shipped big UI features like 
 View Transitions\, Popover\, Anchor Positioning\, and customizable `<selec
 t>`. But when teams build multi-pane web apps\, creative tools\, or HTML-b
 ased browser interfaces\, they still run into small interaction gaps that 
 make web UI feel clunky next to native desktop and mobile apps.\n\nAlongsi
 de the broader app sessions on [cross-document navigation](https://github.
 com/w3c/tpac2026-breakouts/issues/42)\, [overscroll areas](https://github.
 com/w3c/tpac2026-breakouts/issues/7)\, and [Open UI accessibility](https:/
 /github.com/w3c/tpac2026-breakouts/issues/21)\, this session looks at thre
 e places where web apps still have to fight the browser with fragile JavaS
 cript hacks or heavy WebAssembly runtimes:\n\n- **Clicking toolbars and se
 condary controls without stealing focus:** In a desktop or mobile app\, cl
 icking a Bold button in a toolbar formats your text while keeping keyboard
  focus and the cursor inside the active editor. On the web\, clicking a bu
 tton pulls focus out of the editor unless developers intercept pointer eve
 nts and juggle focus in JavaScript\, which often breaks keyboard navigatio
 n and screen readers. Should HTML or Open UI have a declarative way to mar
 k controls that act on another focused region without stealing focus?\n- *
 *Keeping text selection visible when focus moves across inputs and panes:*
 * When you select text in an `<input>`\, `<textarea>`\, or embedded docume
 nt and then click into a find bar\, side panel\, or formatting toolbar\, t
 he selection highlight disappears even though the text is still selected u
 nderneath. On some operating systems\, clicking back in and dragging will 
 still drag that hidden selection\, while native apps just keep a dimmed hi
 ghlight visible so you can see what's selected. What do we need in CSS or 
 HTML so developers can keep inactive selections visible and styleable with
 out drawing fake highlight overlays in JavaScript?\n- **Scrubbing vector a
 nimations to interaction state without heavy runtimes:** Teams routinely s
 hip a 5MB Lottie WebAssembly player just to get smooth vector icon animati
 ons that can scrub to a specific point on a timeline or switch states on h
 over and click. Rather than standardizing a third-party runtime format\, w
 hat's missing in SVG and the Web Animations API that stops design tools fr
 om exporting scrubbable\, state-driven vector animations directly to the p
 latform?\n\nWe'll share brief examples from production web apps and HTML-b
 ased browser UI across engines\, and we'd love to hear which other small U
 I interaction gaps are causing the most pain for app developers.\n\n**Goal
 (s):**\nTalk through how to support non-focusing toolbar controls\, visibl
 e inactive text selections\, and scrubbable SVG timelines\, and figure out
  which pieces belong in Open UI\, CSS WG\, HTML\, and SVG WG.\n\nAgenda\n\
 n- **First 10 minutes:** Quick demos from multi-pane web apps and HTML-bas
 ed browser UI showing where focus handling\, disappearing text selections\
 , and vector timeline scrubbing fall short.\n- **Next 15 minutes:** Non-fo
 cusing controls and toolbars\, and how they should work with keyboard navi
 gation and assistive tech.\n- **Next 15 minutes:** Keeping text selections
  visible and styleable when focus moves to a toolbar\, find bar\, or side 
 panel.\n- **Next 15 minutes:** What SVG and the Web Animations API need so
  developers can scrub and control vector animations without shipping a 5MB
  WebAssembly runtime.\n- **Final 5 minutes:** Deciding which pieces belong
  in Open UI\, CSS WG\, HTML\, or SVG WG.\n\n**Materials:**\n- [Session pro
 posal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/70)
STATUS:CONFIRMED
CREATED:20261013T144655Z
LAST-MODIFIED:20261021T034252Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 09
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:ca79e680-e096-47d9-941e-43fe1707e161
DTSTAMP:20261021T034147Z
SUMMARY:Evolving the web browser and websites for Spatial Computing\, Digit
 al Twins\, Physical AI\, and Robotics
DTSTART;TZID=Europe/Dublin:20261028T140000
DTEND;TZID=Europe/Dublin:20261028T150000
DESCRIPTION:https://www.w3.org/events/meetings/ca79e680-e096-47d9-941e-43fe
 1707e161/\n\nSmart glasses and AI devices are giving computers access to t
 he physical world\, digital twins are mapping factories and entire cities\
 , physical AI is showing up in workplaces and homes\, and robots are leavi
 ng their fixed positions on the factory floor. Many of these products and 
 ecosystems are emerging within walled gardens. The Web lacks an integrated
  architecture for discovering and securely composing independently publish
 ed spatial services. Enterprises need open infrastructure for deploying th
 ese services across products and platforms. W3C is the organization that s
 hould lead the way by extending the open infrastructure that the web provi
 des to support spatial computing and connect the physical world with the v
 irtual.\n\nThis session covers the specific needs of metaverse infrastruct
 ure\, how the current web was not designed for spatial computing\, and the
  technical evolution needed to make the web ready to handle this significa
 nt transition\, including evolving the DOM and iframes\, solving for multi
 -origin\, geo-located content\, native rendering\, and updated security.\n
 \nThe web browser can and should evolve into both a 2D web browser and a 3
 D metaverse browser. Without this evolution\, the Web risks losing its rol
 e as the open platform for the next generation of computing.\n\nThe Open M
 etaverse Browser Initiative (OMBI)\, an open project at the Metaverse Stan
 dards Forum (MSF)\, is building an open-source browser engine called Sneez
 e. It discovers independently published spatial services by location and c
 omposes their content and logic in 3D around the user in real time\, with 
 interoperability and security as core design goals. Sneeze is designed to 
 run alongside existing browser engines (Blink\, WebKit\, and Gecko) for in
 cremental deployment\, with flexible compositing of live Web content withi
 n the 3D scene.\n\nMSF does not create standards\, so OMBI is bringing its
  proposed architecture and identified gaps to the relevant standards organ
 izations and believes the W3C should lead the charge.\n\nThe live demo wil
 l ground discussion of three areas:\n\n- **Extending the Web with spatial 
 browsing.** Sneeze uses WebAssembly\, and the project is evaluating Decent
 ralized Identifiers (DIDs) and Verifiable Credentials. The engine does not
  use WebXR\; it is a native spatial browser engine with a shared scene mod
 el\, location-based discovery\, and a service protocol.\n\n- **Securing sh
 ared 3D scenes.** The Web isolates content by origin. A 3D scene shared by
  many publishers needs isolation within one scene\, so OMBI proposes to id
 entify each publisher by the key that signs its content\, run its code in 
 its own WebAssembly sandbox\, and control access to its part of a unified 
 scene graph.\n\n- **Defining the open standards needed for interoperabilit
 y.** Scene representation\, service discovery and interaction\, and identi
 ty and security.\n\nOMBI also builds on standards from Khronos (glTF\, Ope
 nXR\, ANARI\, SPIR-V) and OGC (GeoPose)\, and uses emerging geolocation st
 andards. The session will demonstrate the [open-source Sneeze engine](http
 s://github.com/MetaversalCorp/Sneeze) in the Rubidium browser.\n\nPre-read
 ing is encouraged: see the [OMBI overview](https://metaverse-standards.org
 /open-metaverse-browser-initiative/). Slides will be linked in the agenda 
 before the session\, and attendees will receive a free copy of *The Spatia
 l Age*\, a book on this topic.\n\nNote that [Breakout #35 Web of Worlds](h
 ttps://github.com/w3c/tpac2026-breakouts/issues/35)\, is a separate and co
 mplementary MSF proposal for a network of linked\, addressable virtual wor
 lds.\n\n**Goal(s):**\nSeek W3C feedback on OMBI's proposed architecture\, 
 identify priority standards gaps\, and agree relevant groups and next step
 s for further discussion or incubation.\n\nAgenda\n\n1. Scope and motivati
 on (10 min)\n2. OMBI architecture (10 min)\n3. Live demo: Rubidium browser
  incorporating Sneeze (10 min)\n4. Standards used and gaps (10 min)\n5. Di
 scussion and next steps (20 min)\n\n**Pre-reading**\n- Slides: _link to be
  added before the session_\n\nMinutes will be taken on IRC. The presentati
 on may be recorded if nobody objects\; the discussion will not be recorded
 .\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c
 /tpac2026-breakouts/issues/40)
STATUS:CONFIRMED
CREATED:20261013T144526Z
LAST-MODIFIED:20261021T034147Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Ulster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:01c878c5-e6ff-43bf-845c-cc83abfa3e2a
DTSTAMP:20261021T034323Z
SUMMARY:Integrating WebMCP into WebExtensions
DTSTART;TZID=Europe/Dublin:20261028T140000
DTEND;TZID=Europe/Dublin:20261028T150000
DESCRIPTION:https://www.w3.org/events/meetings/01c878c5-e6ff-43bf-845c-cc83
 abfa3e2a/\n\nThe current draft of the [WebMCP specification](https://webma
 chinelearning.github.io/webmcp/) allows websites to register [tools](https
 ://webmachinelearning.github.io/webmcp/#intro) that an [agent](https://web
 machinelearning.github.io/webmcp/#agent) can discover and invoke.\n\nExten
 sions are currently one of the main ways that third party developers bring
  agentic features into web browsers. Such extensions work by scraping the 
 DOM\, generating an accessibility  tree based on the DOM\, capturing scree
 nshots of page content\, or driving the page through debugging and automat
 ion interfaces. WebMCP is an attractive alternative for these extensions\,
  as it could provide a structured\, site-sanctioned alternative. \n\nThis 
 session aims to collect requirements from extension developers and browser
  vendors\, and to check those requirements against WebMCP's current design
 . Questions we plan to work through:\n\n1. **Consuming site tools**\n	* Sh
 ould extensions be able to enumerate and invoke a page's tools without inj
 ecting a content script?\n	* Are any social considerations needed to expos
 e `navigator.modelContext` to `ISOLATED` world content scripts?\n	* Would 
 a dedicated extension API add sufficient value beyond calling the web API 
 from the page?\n2. **Providing tools**\n	* Should extensions be able to ex
 pose their own tools to the browser's agent?\n	* Should extensions be able
  to expose their own tools to websites?\n	* How does this relate to the if
 rame and embedding discussions in WebMCP? Are any design changes necessary
  to cover both use cases?\n3. **Permissions and trust**\n	* What (if any) 
 permissions should gate an extension’s access to WebMCP tools?\n	* Is a 
 new permission warranted?\n	* How (if at all) are users informed when an e
 xtension invokes a site's tools?\n4. **Lifecycle**\n	* How do event-driven
  background contexts (service workers\, event pages) interact with tool re
 gistration\, discovery\, and long-running invocations?\n	* Which events do
  extensions need when a page's tools change?\n5. **Gaps**\n	* What other u
 se cases should be considered before stabilizing  the API design?\n\nThis 
 is a community discussion\, not a group meeting. We especially want to hea
 r from extension developers building agentic or automation features\, WebM
 CP spec contributors\, and browser engineers working on both Web and WebEx
 tensions platforms.\n\n**Goal(s):**\nA shared list of extension use cases 
 and requirements for WebMCP. For each item\, identify whether it should be
  integrated into the WebMCP specification\, WebExtensions specification\, 
 or both. Identify owners for any follow-up issues\n\nAgenda\n\n- 5 min: In
 troductions\, scribe\, ground rules\n- 10 min: WebMCP primer (WebMCP spec 
 contributor)\n- 10 min: How extensions integrate with agents today\n- 30 m
 in: Requirements discussion (questions 1–5)\n- 5 min: Summary\, owners\,
  follow-up issues\n\n**Materials:**\n- [Session proposal on GitHub](https:
 //github.com/w3c/tpac2026-breakouts/issues/84)
STATUS:CONFIRMED
CREATED:20261013T144738Z
LAST-MODIFIED:20261021T034323Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Lansdowne Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:3cb480ca-4b87-4d37-ac9f-243bca8ce791
DTSTAMP:20261021T034158Z
SUMMARY:Let's Discuss Translator and Language Detector APIs
DTSTART;TZID=Europe/Dublin:20261028T140000
DTEND;TZID=Europe/Dublin:20261028T150000
DESCRIPTION:https://www.w3.org/events/meetings/3cb480ca-4b87-4d37-ac9f-243b
 ca8ce791/\n\nI would like to help facilitate a discussion around the [Tran
 slator and Language Detector APIs](https://webmachinelearning.github.io/tr
 anslation-api/) proposed by the WebML CG. \n\nIn particular\, we have had 
 some discussions within the Mozilla standards position repository\, and I 
 would like to gather folks to specifically discuss plain-text translator A
 PIs compared to a DOM-aware translator APIs. \n\n* https://github.com/mozi
 lla/standards-positions/issues/1015\n* https://github.com/webmachinelearni
 ng/translation-api/issues/60#issuecomment-5345000556\n\n**Goal(s):**\nFaci
 litate discussion and seek consensus on the shape and direction of transla
 tor APIs\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https
 ://github.com/w3c/tpac2026-breakouts/issues/45)
STATUS:CONFIRMED
CREATED:20261013T144543Z
LAST-MODIFIED:20261021T034158Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 06
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:d73ffc67-4b97-436e-93a4-71f3105d116c
DTSTAMP:20261021T034328Z
SUMMARY:Meaningful Data for AI & Humans with JSON-LD\, YAML-LD\, & CBOR-LD
DTSTART;TZID=Europe/Dublin:20261028T140000
DTEND;TZID=Europe/Dublin:20261028T150000
DESCRIPTION:https://www.w3.org/events/meetings/d73ffc67-4b97-436e-93a4-71f3
 105d116c/\n\n[JSON-LD](https://json-ld.org/) is an essential data format p
 owering SEO\, Social\, Credentials\, IoT\, Publishing\, and AI authenticit
 y. The JSON-LD is expanding to include YAML and CBOR based formats. [YAML-
 LD](https://www.w3.org/TR/yaml-ld-10/) provides a human and AI friendly fo
 rmat. [CBOR-LD](https://www.w3.org/TR/cbor-ld-10/) brings tight compressio
 n bringing JSON-LD documents into tight spaces (QR codes\, message queues\
 , etc.). Additionally\, JSON-LD's core specifications are growing to inclu
 de the latest graph super-powers arriving from the RDF 1.2 specifications.
  This breakout session will be an overview of the growing family and what'
 s ahead for the JSON-LD WG and CG.\n\n**Goal(s):**\nUpdate W3C Members on 
 the growing JSON-LD ecosystem.\n\nAgenda\n\n**Materials:**\n- [Session pro
 posal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/86)
STATUS:CONFIRMED
CREATED:20261015T132845Z
LAST-MODIFIED:20261021T034328Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 05
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:463a1e8a-851c-4363-b9fd-d562225a75d3
DTSTAMP:20261021T034026Z
SUMMARY:Portable Web Content Format: Build once and Instantly Run Apps\, Ga
 mes\, and Interactive Presentations on Any Device
DTSTART;TZID=Europe/Dublin:20261028T140000
DTEND;TZID=Europe/Dublin:20261028T150000
DESCRIPTION:https://www.w3.org/events/meetings/463a1e8a-851c-4363-b9fd-d562
 225a75d3/\n\nPortable Web Content Format enables apps\, games\, and intera
 ctive presentations built with web technologies to be packaged as self-con
 tained .pweb files that can be instantly opened and run on any device usin
 g a compatible viewer—even offline and without a web server.\n\nIn this 
 session\, we will \n\n- Introduce the format\n- Demonstrate its potential 
 use cases\n- Discuss its technical direction\n- Gather feedback from the W
 eb community.\n\n**Goal(s):**\nGather feedback\, identify related standard
 s\, refine PortableWeb’s technical direction\, and connect with potentia
 l contributors.\n\nAgenda\n\n- Introduce the format\n- Demonstrate its pot
 ential use cases\n- Discuss its technical direction\n- Gather feedback fro
 m the Web community.\n\n**Materials:**\n- [Session proposal on GitHub](htt
 ps://github.com/w3c/tpac2026-breakouts/issues/4)
STATUS:CONFIRMED
CREATED:20261013T144333Z
LAST-MODIFIED:20261021T034026Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 03
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:e94352d9-97c8-40ac-8518-535431f6b0b2
DTSTAMP:20261021T034216Z
SUMMARY:Private Groups in ActivityPub
DTSTART;TZID=Europe/Dublin:20261028T140000
DTEND;TZID=Europe/Dublin:20261028T150000
DESCRIPTION:https://www.w3.org/events/meetings/e94352d9-97c8-40ac-8518-5354
 31f6b0b2/\n\nActivityPub\, the social networking standard\, lets users fol
 low each other and receive a stream of content from their contacts. The So
 cial Web Community Group is currently extending the standard to support me
 mbership in groups\, including private groups.\n\n**Goal(s):**\nDiscuss Ac
 tivityPub support for groups\, solicit feedback\, and decide on next steps
 \n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https://githu
 b.com/w3c/tpac2026-breakouts/issues/53)
STATUS:CONFIRMED
CREATED:20261013T144607Z
LAST-MODIFIED:20261021T034216Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 01 and 02
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:9bc6bb51-4197-4ea7-bb94-36cd22b75fbf
DTSTAMP:20261021T034234Z
SUMMARY:Web-based Smart Education: Innovations and Global Perspectives
DTSTART;TZID=Europe/Dublin:20261028T140000
DTEND;TZID=Europe/Dublin:20261028T150000
DESCRIPTION:https://www.w3.org/events/meetings/9bc6bb51-4197-4ea7-bb94-36cd
 22b75fbf/\n\nThe arrival of AI is redrawing the talent bar for software en
 gineers: execution-level work is being commoditized\, while *judgment* —
  problem framing\, architecture\, trade-offs\, and accountability — beco
 mes the scarce\, valuable skill. For computing educators\, the question is
  no longer "how do we teach students to code faster\," but "how do we teac
 h the judgment that AI cannot supply."\n\nThis session shares a concrete\,
  classroom-proven answer: **Collective-Intelligence Co-education**\, a fiv
 e-dimensional framework (school–enterprise\, human–machine\, course–
 competition\, teacher–student\, inter-university) anchored on a single m
 eta-capability we call **Generalized System Capability = Systems Thinking 
 (ST) + Engineering Capability (EC)**. The framework is grounded in a 2026
 –2028 teaching-reform project at the Shenzhen Institute of Information T
 echnology (SZIIT)\, where a *Logic & Critical Thinking* general-education 
 course is being rebuilt so that AI output itself becomes the object of stu
 dent scrutiny.\n\nCrucially\, the medium of this reform is **the open Web*
 *. Instead of shipping a closed\, proprietary teaching app\, every learnin
 g artifact is a single\, self-contained HTML page built with plain HTML / 
 CSS / JavaScript / Canvas / SVG — no build step\, no framework\, openabl
 e in any modern browser and immediately shareable. Three interactive demos
  will be shown live:\n\n- **Eight Queens** — a step-by-step\, animated e
 xploration of backtracking search\;\n- **Feedforward Network · Hardcore T
 eardown** — a math-first\, interactive contrast of *why* a linear model 
 cannot solve XOR and how a hidden layer can\;\n- **Masked Multi-Head Self-
 Attention · Deep Dive** — an interactive\, quest-based walkthrough of t
 he causal mask inside a Transformer decoder\, including an error-vs-correc
 tion playground and a self-graded quiz.\n\nEach demo is designed not to *d
 emonstrate AI*\, but to *train judgment about AI*: students manipulate the
  model\, break it\, fix it\, and explain why.\n\nWe will also open a broad
 er conversation with the Web community on what comes next.\n\n**Goal(s):**
 \nThree concrete goals: 1) Share a working model. Present the Collective-I
 ntelligence Co-education framework and the Generalized System Capability (
 ST + EC) anchor\, with the SZIIT teaching-reform project as the case\, so 
 participants can reuse or adapt it. 2) Show the Web as the medium. Demonst
 rate the three interactive learning artifacts and argue for the open Web 
 — HTML/CSS/JS/Canvas/SVG\, zero build step — as the right substrate fo
 r AI-era computing education\, in contrast to proprietary or platform-lock
 ed teaching tools. 3) Seed collaboration. Identify shared interests with t
 he Web community and gauge appetite for follow-on work — e.g.\, a W3C Co
 mmunity Group or workshop on "Web for Smart Education\," open learning-art
 ifact formats\, or accessible interactive teaching components.\n\nAgenda\n
 \n1. Opening & framing — the talent bar in the AI era (4 min)\n2. The fr
 amework — Collective-Intelligence Co-education & Generalized System Capa
 bility (ST + EC) (7 min)\n3. Live demos — three Web-based interactive le
 arning artifacts (8 min)\n4. Open discussion — what the Web community ca
 n contribute\, and what a "Web for Smart Education" effort could look like
  (6 min)\n5. Wrap-up & next steps (5 min)\n\nThe agenda will be refined cl
 oser to the meeting.\n\n**Speaker:**\n\n- Name: Wang Yinfeng (王寅峰)\n
 - Role: Professor & Vice Dean\, School of Computer and Software\, Shenzhen
  University of Information Technology (SUIT)\, Shenzhen\, China\n- TPAC ro
 le: W3C Advisory Committee (AC) representative\, attending in person\n- Se
 ssion title: Web-based Smart Education: Innovations and Global Perspective
 s\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c
 /tpac2026-breakouts/issues/62)
STATUS:CONFIRMED
CREATED:20261013T144631Z
LAST-MODIFIED:20261021T034234Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 08
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:8371a85c-bb6e-413c-b84e-e41ef38d8089
DTSTAMP:20261021T034221Z
SUMMARY:Agents are redefining DX. [How] should web standards adapt?
DTSTART;TZID=Europe/Dublin:20261028T151500
DTEND;TZID=Europe/Dublin:20261028T161500
DESCRIPTION:https://www.w3.org/events/meetings/8371a85c-bb6e-413c-b84e-e41e
 f38d8089/\n\nThe [Web Platform's design principles](https://www.w3.org/TR/
 design-principles/) implicitly assume a human developer as the primary API
  consumer. As a growing share of web code is written by agents\, these ass
 umptions stop holding uniformly\, and some pull in opposite directions.\n\
 nQuestions this session will explore:\n\n- Should we take agent consumers 
 into account _at all_? The counterarguments are that agents are not unifor
 m — what is efficient for one model generation may not be for the next 
 — and the landscape is still volatile\, whereas Web APIs are permanent.\
 n- What does agent DX mean? Token efficiency? Robustness/correctness? What
  else?\n- Which existing design principles still hold for agents\, and whi
 ch actively hinder them?\n- What makes a Web API token-efficient\, both wh
 en writing code against it and when reading code that uses it?\n- What mak
 es a Web API *robust* for agents\, i.e. harder to misuse?\n- Where agent e
 rgonomics and human DX conflict\, how do we weigh them?\n- Evaluation: An 
 API's token cost is not an intrinsic property. An agent implementing an un
 familiar API spends tokens on lookup\, trial and error\, and correction\, 
 so a design that would be more token-efficient *at parity of familiarity* 
 measures as worse until training data catches up — which takes years. An
 y evaluation we run today privileges *familiar* over *better*. How do we s
 eparate the two\, and how do we evaluate API designs\, or design principle
 s\, given such a delayed feedback loop?\n\nNote: Additional Chairs TBD\n\n
 **Goal(s):**\nMake progress on the questions above and identify people int
 erested in exploring this further.\n\nAgenda\n\nTBD\n\n**Materials:**\n- [
 Session proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/issu
 es/56)
STATUS:CONFIRMED
CREATED:20261013T144613Z
LAST-MODIFIED:20261021T034221Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 03
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:9d8dc38e-cc24-46f8-8ba4-72cd1a471510
DTSTAMP:20261021T034218Z
SUMMARY:AI API - Advancing Higher Education and Career Pathways for Neurodi
 verse STEAMM Students
DTSTART;TZID=Europe/Dublin:20261028T151500
DTEND;TZID=Europe/Dublin:20261028T161500
DESCRIPTION:https://www.w3.org/events/meetings/9d8dc38e-cc24-46f8-8ba4-72cd
 1a471510/\n\n**What?**\n\nThe University of Michigan has engaged Helix Opp
 ortunity LLC in an Innovative Partnership to develop an AI Application Pro
 gramming Interface (API) for Neurodiverse STEAMM Students  for Advancing H
 igher Education and Career Pathways\n\n \n**Who?**\n\nHelix Opportunity is
  a leading edge innovator in digital transformation\, inclusive design\, a
 nd digital accessibility.\n\nThe University of Michigan has performed grou
 nd-breaking work on career readiness training for the neurodivergent popul
 ation.\n \n**Why?**\n\nThis project combines expertise that will bridge ga
 ps in the current AI ecosphere of product development\, reducing bias and 
 incorporating much needed insights from the disability population.\n \nHis
 torically\, disability data has been omitted in the development of AI whic
 h\nhas caused systemic algorithmic bias and discrimination. Current AI sys
 tems\nare largely trained on datasets that underrepresent or misrepresent 
 the\ndisability community. This results in technologies that perpetuate st
 ereotypes\,\ncreate accessibility barriers\, and make inaccurate or unfair
  decisions in critical\nareas like employment\, education\, and healthcare
 .\n\nThis project explores the development of AI technology specifically\n
 trained on large datasets of the world’s most vulnerable population\, as
 \ndescribed above\, to improve societal outcomes related to vocational\nre
 habilitation.\n\n**Goal(s):**\nInform the audience on cutting edge applica
 tions of AI in the disability inclusion space\n\nAgenda\n\nHelix Opportuni
 ty will discuss the following topics related to our work on this project:\
 n\n1. Project Overview\n\n3. System Architecture\n\n4. API Exploratory Act
 ivities\n\n5. Data Annotation\n\n**Materials:**\n- [Session proposal on Gi
 tHub](https://github.com/w3c/tpac2026-breakouts/issues/54)
STATUS:CONFIRMED
CREATED:20261013T151235Z
LAST-MODIFIED:20261021T034218Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 06
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:14e4e656-20d9-4342-9c78-24c6ef44ac2d
DTSTAMP:20261021T034132Z
SUMMARY:Do Agents Dream of Electric Sheep? AI Skill Workflows for Human Rev
 iew of Web Standards
DTSTART;TZID=Europe/Dublin:20261028T151500
DTEND;TZID=Europe/Dublin:20261028T161500
DESCRIPTION:https://www.w3.org/events/meetings/14e4e656-20d9-4342-9c78-24c6
 ef44ac2d/\n\n“Never send a human to do a machine’s job”. Agent Smith
  had a point in The Matrix\,  at least for part of a standards review.\n\n
 We are experimenting how AI can support human review of Web standards\, pa
 rticularly security review. Some parts of the review can be delegated to m
 achines\, other parts such as interpretation\, judgment\, and decisions ar
 e still on humans.\n\nWe have been building an experimental marketplace of
  portable AI skills to help W3C work. During a review\, a skill can help u
 s understand and model what a specification is building\, another can ask 
 what might go wrong and support threat modeling\, or comparing the specifi
 cation from its implementations. Others can gather and check evidence\, fa
 ct-check a claim\, suggest possible responses for a reviewer to consider\,
  or prepare draft review material.\n\nThere are not fire-and-forget skills
 . A human still has to challenge\, interpret\, check it and decide.\nThe w
 orkflow can also start before the horizontal review. A Working Group can u
 se these skills in earlier design phase\, as a security-by-design sparring
  partner rather. Sometimes the skills will produce useful questions\; some
 times they will produce poor ones or miss something entirely. Understandin
 g that boundary is part of the experiment.\n\nIn the breakout\, we will sh
 ow the skills currently available\, how they fit into the workflow\, and o
 ne concrete example of working with their output.\n\nThis brings us back t
 o the electric sheep. Think of these agents as electric sheep that can ran
 ge over information\, follow different paths\, and sometimes bring back so
 mething useful. We still need to shepherd them: understand where they went
 \, challenge what they found\, decide what matters\, and take responsibili
 ty for the review. The sheep do not replace the shepherds\, and maybe we a
 lso need electric sheepdogs.\n\n**Goal(s):**\nPresent and test a human-led
  workflow of portable AI skills for Web standards review\, and find partic
 ipants willing to experiment with it and help improve it.\n\nAgenda\n\n**M
 aterials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac202
 6-breakouts/issues/33)
STATUS:CONFIRMED
CREATED:20261013T144503Z
LAST-MODIFIED:20261021T034132Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Ulster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:75e59843-4fe7-48ab-a21a-b49718992308
DTSTAMP:20261021T034036Z
SUMMARY:Email Verification API
DTSTART;TZID=Europe/Dublin:20261028T151500
DTEND;TZID=Europe/Dublin:20261028T161500
DESCRIPTION:https://www.w3.org/events/meetings/75e59843-4fe7-48ab-a21a-b497
 18992308/\n\nThis is a follow-up to last year's [session](https://github.c
 om/w3c/tpac2025-breakouts/issues/77) with an overview of where things are 
 at and an update of the progress that we have made since last year\, speci
 fically:\n\n- Per [TAG's guidance](https://github.com/w3ctag/design-review
 s/issues/1169#issuecomment-3669406079)\, an update on [moving part of the 
 work to the IETF](https://www.ietf.org/archive/id/draft-hardt-email-verifi
 cation-01.html)\n- What we have learned with implementation and [deploymen
 t experience in Chrome](https://developer.chrome.com/blog/email-verificati
 on-protocol-origin-trial) and Gmail\n- The [browser API](https://wicg.gith
 ub.io/email-verification/) and integration with form filling (and open que
 stions we have)\n- An open invitation for participation from websites\, em
 ail providers\, browser vendors and protocol designers\n\n**Goal(s):**\nRa
 ise awareness\, find privacy/security/economic holes in the design and an 
 open invitation for participation\n\nAgenda\n\nTBD\n\n**Materials:**\n- [S
 ession proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/issue
 s/8)
STATUS:CONFIRMED
CREATED:20261013T144345Z
LAST-MODIFIED:20261021T034036Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 08
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:93be694f-489c-4a12-9415-bc7a5e3237e9
DTSTAMP:20261021T034156Z
SUMMARY:On-Device Generative UI Application Profile
DTSTART;TZID=Europe/Dublin:20261028T151500
DTEND;TZID=Europe/Dublin:20261028T161500
DESCRIPTION:https://www.w3.org/events/meetings/93be694f-489c-4a12-9415-bc7a
 5e3237e9/\n\nCurrent on-device Generative UI solutions present a trade-off
 : Web engines (e.g.\, Chromium) offer superior layout flexibility and LLM 
 compatibility but incur high performance costs and experience fragmentatio
 n. Native JSON routes (e.g.\, A2UI) are lightweight and performant but lac
 k flexibility for complex layouts and are prone to parsing errors. This pr
 oposal explores whether we can combine the best of both worlds to create a
  new\, efficient technical standard for Generative UI.\n\n- First\, at the
  **syntax layer**\, we propose a **Generative UI Baseline** to constrain t
 he syntax space\, prioritizing core features like flexible layouts like Fl
 exbox and Grid. This significantly would reduces LLM generation complexity
  and token consumption while preserving essential cross-device responsiven
 ess\, resolving syntax errors and layout adaptation issues at the source.\
 n\n- Second\, at the **engine layer**\, we envision a **Lightweight Web En
 gine** stripped of legacy baggage. This would reduce memory footprint and 
 cold-start latency by an order of magnitude\, enabling smooth streaming re
 ndering alongside LLM outputs within a minimal attack surface.\n\n- Finall
 y\, at the **rendering layer**\, we aim for **OS-Unified Rendering** by li
 nking the engine’s display lists directly into low-level OS graphics pip
 elines. This would eliminate off-screen compositing overhead\, allowing Ge
 nerative UI to natively leverage OS gesture physics\, font rendering\, and
  high refresh rates.\n\n**Goal(s):**\nCollect community’s feedback on th
 e technical and strategic feasibility of this approach\, aiming for optima
 l convergence with current Web standards and meaningful contribution to th
 e open web of the future.\n\nAgenda\n\n- Introduction to the proposal by @
 JingShen2012\n- Open discussion\n\n**Materials:**\n- [Session proposal on 
 GitHub](https://github.com/w3c/tpac2026-breakouts/issues/44)
STATUS:CONFIRMED
CREATED:20261013T144540Z
LAST-MODIFIED:20261021T034156Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 09
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:a275b20d-cdd5-4771-83a6-df48b8885a54
DTSTAMP:20261021T034032Z
SUMMARY:Overscroll Areas: drawer menus and bottom sheets
DTSTART;TZID=Europe/Dublin:20261028T151500
DTEND;TZID=Europe/Dublin:20261028T161500
DESCRIPTION:https://www.w3.org/events/meetings/a275b20d-cdd5-4771-83a6-df48
 b8885a54/\n\n[Declarative Overscroll Actions (Explainer)](https://open-ui.
 org/components/overscroll-actions.explainer/)\n\nThe web platform allows f
 or sophisticated scrolling experiences\, but it currently lacks a semantic
  way to utilize "overscroll" space (the area beyond the scroll or element 
 boundary).\n\nCommon UI patterns like drawer-menus (swiping past the edge 
 to reveal a menu) rely on complex nested scrollers or JavaScript gesture p
 olyfills. These workarounds are difficult to implement\, computationally e
 xpensive\, and often fail to provide accessible alternatives for non-touch
  users.\n\nWe propose a set of HTML attributes and CSS properties that dec
 laratively bind an element (the "overscroll content") to the scroll bounda
 ry of a container to support drawer-menu and bottom-sheet cases.\n\n**Goal
 (s):**\nExplain an upcoming feature and gather feedback.\n\nAgenda\n\n**Ma
 terials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2026
 -breakouts/issues/7)
STATUS:CONFIRMED
CREATED:20261013T144342Z
LAST-MODIFIED:20261021T034032Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Pembroke Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:98a7819d-2655-4c9e-83a5-f286394a327d
DTSTAMP:20261021T034052Z
SUMMARY:QUIC-based options for moving real-time data between peers
DTSTART;TZID=Europe/Dublin:20261028T151500
DTEND;TZID=Europe/Dublin:20261028T161500
DESCRIPTION:https://www.w3.org/events/meetings/98a7819d-2655-4c9e-83a5-f286
 394a327d/\n\nThe W3C WebTransport working group have recently extended our
  Charter to consider “ ..incubating mechanisms for peer-to-peer capabili
 ty”. To this end\, we are having two presentations on this topic\, follo
 wed by discussion time. The first would be a remote presentation by Jan-Iv
 ar Bruaroey from Mozilla on the concept of the leveraging the WebRTC hands
 hake to initialize a p2p connection\, prior to establishing a WebTransport
  connection. The second is an in-person presentation by Marten Seemann  on
  “[A p2p Vision for QUIC](https://seemann.io/posts/2024-10-26---p2p-quic
 /)”\, which offers an alternate approach of migrating a client-server co
 nnection to a peer. There will then be discussion time between participant
 s and the audience. \n\nThe WebTransport WG encourages all W3C TPAC partic
 ipants interested in QUIC-based options for moving real-time data between 
 peers to please attend.\n\n**Goal(s):**\nAssess interest in QUIC-based opt
 ions for moving real-time data between peers\n\nAgenda\n\nTBD\n\n**Materia
 ls:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-brea
 kouts/issues/15)
STATUS:CONFIRMED
CREATED:20261013T144407Z
LAST-MODIFIED:20261021T034052Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 05
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:e55792ae-2fe7-4bcc-a0a0-b18f94bff1f1
DTSTAMP:20261021T034134Z
SUMMARY:Report and follow-ups from the E-commerce for Humans and AI Agents
DTSTART;TZID=Europe/Dublin:20261028T151500
DTEND;TZID=Europe/Dublin:20261028T161500
DESCRIPTION:https://www.w3.org/events/meetings/e55792ae-2fe7-4bcc-a0a0-b18f
 94bff1f1/\n\nThe E-Commerce for Humans and AI Agents occurred on September
  8-9. The workshop discussed merchants' context and views\, legal accounta
 bility\, protocols and data infrastructure\, including trust and ownership
 . Using AI Agents\, Web browsers\, or some combination of both\, e-commerc
 e needs product data models and representations\, user intent/alignment\, 
 identity and authorization\, payment. A Web for humans and AI agents shoul
 d be part of the future of customer interactions.\n\n**Goal(s):**\nReporti
 ng on the workshop discussion and how to address the use cases\n\nAgenda\n
 \n1. Presentation of the workshop report\n2. Q&A / General Discussion\n\n*
 *Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2
 026-breakouts/issues/34)
STATUS:CONFIRMED
CREATED:20261013T144507Z
LAST-MODIFIED:20261021T034134Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 01 and 02
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:75b73c15-6d4e-4b60-abe0-f590cc349e39
DTSTAMP:20261021T034334Z
SUMMARY:The Browser as Universal Interpreter: A 30-Year-Old Idea Whose Time
  Has Come
DTSTART;TZID=Europe/Dublin:20261028T151500
DTEND;TZID=Europe/Dublin:20261028T161500
DESCRIPTION:https://www.w3.org/events/meetings/75b73c15-6d4e-4b60-abe0-f590
 cc349e39/\n\nFor three decades\, web accessibility has been pursued almost
  everywhere except the one place every user already stands: the browser. W
 e have asked authors to remediate\, assistive technologies to compensate\,
  and regulators to enforce — while the layer that renders the web to eve
 ry person has stayed largely on the sidelines of universal personalization
 .\n\nThis session makes the case that the browser is the natural home for 
 universal accessibility: a layer that could adapt any page to the individu
 al needs\, abilities\, language\, and preferences of the person using it\,
  rather than requiring every author and every assistive technology to carr
 y that burden separately. It is not a new idea — it was described in the
  research literature as early as 1996\, and the "accessible framework as p
 ersonal interpreter" concept predates the modern web.\n\nWhat is new is th
 at feasibility is no longer the open question. On-device AI now runs insid
 e the browser on ordinary consumer hardware\, and the browser has always b
 een able to reach into the page it renders — the accessibility tree\, th
 e DOM\, and the user's own style layer. A working prototype of a user-cont
 rolled "smart browser\," built on a five-year-old laptop\, already demonst
 rates the idea in practice. The pieces that were missing in 1996 are arriv
 ing.\n\nSo the question this breakout puts on the table is not whether bro
 wser-level personalization is possible\, but how to do it well. When a gen
 eral on-device AI interface was proposed for the web\, the engines and the
  W3C TAG raised specific\, documented concerns — interoperability\, user
  consent\, device cost\, fingerprinting\, and the viability of independent
  browsers. Those concerns are exactly the right starting point. A narrow\,
  user-controlled accessibility capability answers several of them by const
 ruction and turns the rest into design requirements. This session is where
  the people who would build it can work through those questions together.\
 n\nThis session is grounded in the research paper Web Browsers as a Pervas
 ive Accessibility Solution (Paciello). The "universal interpreter" lineage
  traces to the 1996 ASSETS paper (Laux\, McNally\, Paciello & Vanderheiden
 ) and the Pervasive Accessible Technology concept introduced by David Ston
 e at the 1991 World Congress on Technology for People with Disabilities.\n
 \n**Goal(s):**\nBuild shared understanding that the browser is a viable ac
 cessibility layer now that on-device AI has shipped and the browser alread
 y exposes the page it renders\; work through\, candidly and with the peopl
 e who would have to build it\, the documented concerns the engines and the
  W3C TAG have already raised about a general AI interface\, and how a narr
 ow\, user-controlled accessibility capability addresses them\; and identif
 y concrete next steps — what the major engines could prototype\, and wha
 t standards or coordination work at W3C would unblock it. Success is leavi
 ng the room with at least one committed follow-up (a community group discu
 ssion\, an explainer\, or a cross-vendor conversation).\n\nAgenda\n\n1. Fr
 aming talk (~10 min) — the case for the browser as the accessibility lay
 er: the 1996→2026 "universal interpreter" lineage\, what has now shipped
  (on-device AI in the browser\; the accessibility tree\, DOM\, and style l
 ayers the browser already controls)\, and a user-controlled smart-browser 
 prototype as an existence proof.\n2. Facilitated discussion (~35 min) — 
 working through the documented concerns from the engines' and the TAG's ow
 n reviews (interoperability\, consent\, device cost\, fingerprinting\, ind
 ependent-browser viability)\, and what a narrow\, user-controlled\, standa
 rdized accessibility capability would need to look like to meet them. Cost
  and business-case realities included.\n3. Next steps (~5 min) — capture
  concrete follow-ups and at least one committed action.\n\n**Materials:**\
 n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/
 issues/89)
STATUS:CONFIRMED
CREATED:20261016T131518Z
LAST-MODIFIED:20261021T034334Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Leinster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:1b48d206-3adc-48c5-a33d-188a9cc1b131
DTSTAMP:20261021T034130Z
SUMMARY:Web Sustainability Guidelines in the Wild
DTSTART;TZID=Europe/Dublin:20261028T151500
DTEND;TZID=Europe/Dublin:20261028T161500
DESCRIPTION:https://www.w3.org/events/meetings/1b48d206-3adc-48c5-a33d-188a
 9cc1b131/\n\nThe web sustainability landscape has been rapidly evolving\, 
 with organizations and implementers seeking to take on the challenge of cl
 imate responsibility. There is [tremendous interest and many implementatio
 ns](https://github.com/w3c/sustainableweb-ig/blob/main/campaign-toolkit.md
 ) of the WSG Draft and its [supporting materials](https://w3c.github.io/su
 stainableweb-ig/#work).\n\nThis breakout will explore:\n\n- The current im
 pact of the [Web Sustainability Guidelines](https://www.w3.org/TR/web-sust
 ainability-guidelines/)\n- How implementers are supporting conformity with
  the WSG\n- An open discussion of WSG tooling and implementations\n\n**Goa
 l(s):**\nExplore WSG related tooling\, and consider how the Sustainable We
 b IG can make implementation more viable.\n\nAgenda\n\nAgenda: TBD\n\n**Ma
 terials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2026
 -breakouts/issues/32)
STATUS:CONFIRMED
CREATED:20261013T144459Z
LAST-MODIFIED:20261021T034130Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Lansdowne Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:06bd3a4c-6389-42c3-8e8e-13a793512a00
DTSTAMP:20261021T034209Z
SUMMARY:Accessibility and Privacy
DTSTART;TZID=Europe/Dublin:20261028T163000
DTEND;TZID=Europe/Dublin:20261028T173000
DESCRIPTION:https://www.w3.org/events/meetings/06bd3a4c-6389-42c3-8e8e-13a7
 93512a00/\n\n***tl\;dr:** Let’s have a conversation about the intersecti
 on of modern Assistive Technologies\, adaptations\, proposed platform feat
 ures\, and the user’s privacy. We want the user to avoid being in a posi
 tion where the adaptations they need to afford them access are also a fing
 erprinting risk - especially one that highlights the use of Assistive Tech
 nology - or that such features can’t be added to the platform safely. Ca
 n we learn anything from past impasses in these areas\, to help us design 
 a future web that is both more adaptive\, as well as more privacy preservi
 ng?*\n\nUser Agents are there to protect their users. We have always taken
  care to design new features and APIs to\, as far as possible\, discourage
  detecting if the user is using Assistive Technology to access the web. Th
 e user’s privacy - especially in relation to such personal information -
  is extremely important.\n\nWhat an Assistive Technology actually *is*\, t
 hough\, can vary. It could be: a screen reader\; the use of dark mode\; or
  the desire to opt in to\, or out of\, specific fonts\, font sizes\, or ae
 sthetic features. A range of minor-to-moderate impairments exists\, and a 
 range of assistance - be that a ‘traditional’ Assistive Technology\, o
 r an adaptation provided by the OS or UA - exists to meet these needs\, an
 d to personalize the web for the user.\n\nThe use - or non-use - of those 
 features could increase fingerprinting surface\, especially if the sizes o
 f the populations using\, or opting out of\, a feature are very different 
 in size. As a result\, some features that might benefit some people can’
 t be developed and shipped\, due to the privacy risk. That’s a reasonabl
 e stance to take on a feature-by-feature basis\, but are there any pattern
 s we can learn from\, to inform changes that might make more such useful a
 daptive features possible in future?\n\n**Goal(s):**\nEstablish interest a
 nd next steps in assessing the balancing act here\, and how to involve the
  community in designs going forward.\n\nAgenda\n\n* Sourcing examples from
  the room of features or APIs we wanted to ship\, but decided not to on pr
 ivacy grounds?\n	* Of those\, which might have been beneficial to some use
 rs?\n	* Which could’ve been designed differently so users would not have
  felt the need to opt in or out?\n	* Which might benefit from further disc
 ussion with the people who would be affected by those changes?\n	* How can
  we as a community track the features that never come to be\, due to fores
 een privacy risks\, so we can look for patterns?\n* High-level questions\n
 	* How can we balance privacy and access? Could we give users\, or UAs\, w
 ays to measure and budget around privacy leakage? Or should we aim to make
  radical changes that would make that unnecessary?\n	* Should the user’s
  level of trust in a site dictate the level of adaptation that could be ap
 plied to it? How would the user come to trust a site that isn’t adapted 
 to their needs to begin with?\n* Technical questions\n	* Could we create a
  mode in which browsers could render alternative content in a way that is 
 harder for sites to detect?\n	* Could we design new features in such a way
  that people with disabilities won’t feel the need to turn them off?\n\n
 **Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac
 2026-breakouts/issues/50)
STATUS:CONFIRMED
CREATED:20261013T144558Z
LAST-MODIFIED:20261021T034209Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Leinster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:fcec3fd0-0d4c-47c6-8fb1-1fad2305627c
DTSTAMP:20261021T034021Z
SUMMARY:Ask i18n: Testing an AI-Assisted\, Citation-Grounded Interface for 
 Finding Internationalization Guidance
DTSTART;TZID=Europe/Dublin:20261028T163000
DTEND;TZID=Europe/Dublin:20261028T173000
DESCRIPTION:https://www.w3.org/events/meetings/fcec3fd0-0d4c-47c6-8fb1-1fad
 2305627c/\n\nAsk i18n is an experimental tool from the i18n WG exploring w
 hether an AI-assisted\, citation-grounded interface can make W3C Internati
 onalization guidance easier to find. It indexes W3C i18n sources\, retriev
 es relevant sections\, and presents answers based on that evidence\, with 
 visible citations and warnings when the evidence is weak.\n\nThis breakout
  will demonstrate the current system. The session will also ask what safeg
 uards and community oversight would be required\, whether other approaches
  would be better\, and whether further development is justified.\n\n- Site
 : https://ask-i18n.onrender.com/\n- GitHub repo: https://github.com/w3c/as
 k-i18n\n\n**Goal(s):**\nAssess whether it helps people find relevant W3C i
 18n guidance while keeping the underlying documents\, rather than the gene
 rated answer\, authoritative.\n\nAgenda\n\n1. The discovery problem\n1. Ho
 w the system works\n1. Live demonstration\n1. Discussion\n1. Summary and n
 ext actions\n\n**Materials:**\n- [Session proposal on GitHub](https://gith
 ub.com/w3c/tpac2026-breakouts/issues/2)
STATUS:CONFIRMED
CREATED:20261013T144327Z
LAST-MODIFIED:20261021T034021Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 01 and 02
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:31bdc343-1524-42d5-9456-a9278d5fa056
DTSTAMP:20261021T034143Z
SUMMARY:CG specification redesign and more program updates
DTSTART;TZID=Europe/Dublin:20261028T163000
DTEND;TZID=Europe/Dublin:20261028T173000
DESCRIPTION:https://www.w3.org/events/meetings/31bdc343-1524-42d5-9456-a927
 8d5fa056/\n\nAfter [beta testing](https://github.com/w3c/cg-program/tree/m
 ain/beta-2026) earlier this year\, we will demo updated designs for CG spe
 cifications and share progress on their implementation in respec and bikes
 hed.\n\nThe redesigned specifications include\, inline\, much more informa
 tion about the technology’s implementation and adoption status. We will 
 describe the [new metadata tooling](https://github.com/w3c/cg-spec-metadat
 a/tree/main)  that supports the inclusion of this dynamic usage guidance.\
 n\nWe will also share plans for current work on the next enhancements: pub
 lication tools and plans to host more CG specifications on w3.org.\n\n**Go
 al(s):**\nProvide the community with updates on the CG specification redes
 ign project and seek feedback\n\nAgenda\n\n* CG designs\n* Questions about
  tools (e.g.\, wordpress usage)\n\n**Materials:**\n- [Session proposal on 
 GitHub](https://github.com/w3c/tpac2026-breakouts/issues/38)
STATUS:CONFIRMED
CREATED:20261013T144519Z
LAST-MODIFIED:20261021T034143Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 06
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:66c3b674-298a-428a-a664-66afa7f73478
DTSTAMP:20261021T034103Z
SUMMARY:Furthering Human Rights at W3C
DTSTART;TZID=Europe/Dublin:20261028T163000
DTEND;TZID=Europe/Dublin:20261028T173000
DESCRIPTION:https://www.w3.org/events/meetings/66c3b674-298a-428a-a664-66af
 a7f73478/\n\nIn August of this year\, the Advisory Board published a posit
 ion statement\, [Further Aligning W3C's Program of Technical Work with Hum
 an Rights](https://www.w3.org/TR/furthering-human-rights/). Subsequently\,
  we have created a [Community Group](https://www.w3.org/community/threats-
 and-harms/) where we are starting to explore how to put some of this recom
 mendations into action. This will be a working session to present the AB p
 osition paper as well as the current status and activities of that group\,
  and to gather community feedback\, raise awareness of this topic and enga
 ge additional contributors.\n\n**Goal(s):**\nHighlight the work that has g
 one on so far with regard to Human Rights at W3C\, invite comment and ques
 tion\, and hopefully recruit participants for our ongoing efforts.\n\nAgen
 da\n\nWe will have a short overview of the UN report\, the work that has g
 one into it (including last year's workshops)\, the position paper publish
 ed by the Advisory Board\, and the work done so far by the community group
  and elsewhere in W3C. We will then open the floor to questions and discus
 sion.\n\n**Materials:**\n- [Session proposal on GitHub](https://github.com
 /w3c/tpac2026-breakouts/issues/20)
STATUS:CONFIRMED
CREATED:20261013T144422Z
LAST-MODIFIED:20261021T034103Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Pembroke Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:1ff677c7-64ed-4002-b835-4177f2099768
DTSTAMP:20261021T034336Z
SUMMARY:How should national identity systems improve interoperability?
DTSTART;TZID=Europe/Dublin:20261028T163000
DTEND;TZID=Europe/Dublin:20261028T173000
DESCRIPTION:https://www.w3.org/events/meetings/1ff677c7-64ed-4002-b835-4177
 f2099768/\n\nNational identity systems tend to provide a vertically integr
 ated solution\, including issuer\, holder and verifier. Interoperability r
 emains a key challenge across systems adopting W3C Verifiable Credentials.
 \n\nWith support from WCAP\, we held a Technical Interoperability Plugfest
  (TIP) for DIGITAL TRUST Thailand 2026 (See [related public information](h
 ttps://lists.w3.org/Archives/Public/public-vc-wg/2026Jun/0008.html)\, with
  agenda and methodology)\, with four system participants: MOSIP Inji\, TWD
 IW\, ETDA\, and Bhutan NDI.\n\nThis session will share our findings\, [pro
 posed interoperability task force in CCG](https://github.com/w3c-ccg/commu
 nity/issues/262)\, and initiate discussion on various topics\, e.g.\, How 
 could the W3C Digital Credentials API be integrated into this ecosystem?\n
 \n**Goal(s):**\nIdentify and discuss key issues to support ongoing discuss
 ions with other stakeholders\, such as solution providers and identity pro
 viders (e.g.\, government agencies).\n\nAgenda\n\n1. Presentation and Prop
 osed Discussion Topics (30 min)\n2. Open Discussion (30 min)\n\n**Material
 s:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-break
 outs/issues/91)
STATUS:CONFIRMED
CREATED:20261018T043014Z
LAST-MODIFIED:20261021T034336Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 08
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:745174a2-a4c0-4991-9542-e936946fa8de
DTSTAMP:20261021T034212Z
SUMMARY:Reimagining Modern Authoring Tools - ATAG 3.0
DTSTART;TZID=Europe/Dublin:20261028T163000
DTEND;TZID=Europe/Dublin:20261028T173000
DESCRIPTION:https://www.w3.org/events/meetings/745174a2-a4c0-4991-9542-e936
 946fa8de/\n\nGenerative AI has heavily impacted many areas of the web\, bu
 t one of the most impacted is authoring of content. Content of all kinds c
 an now be produced faster than ever before\, but without guardrails\, we a
 lready see the risks to users in terms of inaccessibility and harm. Genera
 tive AI has also made some accessibility use cases more available to disab
 led users such as automated captioning and on-demand image descriptions\, 
 but many tools have no consideration for accessible content authoring at t
 he time of creation. How do we balance the risks and the opportunities\, a
 nd how might we write a standard for authoring tools that creates the nece
 ssary guardrails while supporting a more accessible authoring environment?
  In this session we want to discuss the different possibilities\, concerns
 \, and the wild potential of authoring tools in the AI age as we prepare f
 or the development of ATAG 3.0.\n\n**Goal(s):**\nDiscuss possible use case
 s\, risks\, and opportunities for ATAG 3.0.\n\nAgenda\n\n**Materials:**\n-
  [Session proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/is
 sues/51)
STATUS:CONFIRMED
CREATED:20261013T144601Z
LAST-MODIFIED:20261021T034212Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 09
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:3e7f2228-a79c-4477-a163-ae2818dba074
DTSTAMP:20261021T034041Z
SUMMARY:Thinking outside the browser - More coordination for better web sta
 ndards for embedding
DTSTART;TZID=Europe/Dublin:20261028T163000
DTEND;TZID=Europe/Dublin:20261028T173000
DESCRIPTION:https://www.w3.org/events/meetings/3e7f2228-a79c-4477-a163-ae28
 18dba074/\n\nThe web is much more than browsers. Web standards are often d
 esigned and implemented first for browsers. If you look at embedding or di
 fferent contexts like WebViews\, MiniApps\, Isolated Web Apps\, JavaScript
  runtimes and more you sometimes find new challenges\, questions\, require
 ments or issues. \n\nThese areas have their own groups and communities tha
 t despite probably quite a few overlapping challenges and interests don't 
 really get to talk and coordinate much between each other.\n\nThis breakou
 t invites everyone to get to know each other and share issues\, past and f
 uture work.  We can start with a short introduction about your field of wo
 rk by one representative of each group/project:\n\n1. Please give a little
  introduction about you and your field of work\n2. Please tell us about th
 e things you would like to improve\n3. What did you or group so far?\n4. W
 hat are your plans for upcoming activities?\n\n(If you want leave your int
 roduction in this issue we can include it in the presentation that opens u
 p the breakout.)\n\n**After hearing about the interesting things and possi
 bly finding common interest we can discuss how to coordinate this.** We ha
 ve great discussions at TPAC but once a year is not enough to really move 
 things forward. Should we create new groups or formats to work better toge
 ther? Let's find out!\n\n**Goal(s):**\nA plan on how to do more and regula
 r coordination between browsers\, embedded contexts and more\n\nBring toge
 ther:\n\n* MiniApps\n* WebViews\n* Embedded Web Engines & Native Web Runti
 mes\n* Embeeded Browsers like WPE WebKit\n* Sub Apps API\n* TAG\n* more\n\
 nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https://github.c
 om/w3c/tpac2026-breakouts/issues/10)
STATUS:CONFIRMED
CREATED:20261013T144352Z
LAST-MODIFIED:20261021T034041Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Lansdowne Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:c5006576-f7f7-458b-a36c-ede6466f8965
DTSTAMP:20261021T034055Z
SUMMARY:W3C collaboration with the OPC Foundation
DTSTART;TZID=Europe/Dublin:20261028T163000
DTEND;TZID=Europe/Dublin:20261028T173000
DESCRIPTION:https://www.w3.org/events/meetings/c5006576-f7f7-458b-a36c-ede6
 466f8965/\n\nThe W3C has been collaborating with the OPC Foundation\, main
 tainer of the OPC UA Industrial Interoperability IEC Standard\, for many y
 ears now in two joint working groups\, namely the Web of Things Connectivi
 ty working group and the Web of Things Binding working group. This session
  will give an overview of the collaboration and its outcomes to date\, as 
 well as work in progress and future work.\n\n**Goal(s):**\nProvide an over
 view of the W3C collaboration with the OPC Foundation\n\nAgenda\n\n**Mater
 ials:**\n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-br
 eakouts/issues/16)
STATUS:CONFIRMED
CREATED:20261013T144410Z
LAST-MODIFIED:20261021T034055Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 03
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:4f37da9e-e00b-4e74-9333-bdbdda132676
DTSTAMP:20261021T034039Z
SUMMARY:Web of Things Live Demonstration
DTSTART;TZID=Europe/Dublin:20261028T163000
DTEND;TZID=Europe/Dublin:20261028T173000
DESCRIPTION:https://www.w3.org/events/meetings/4f37da9e-e00b-4e74-9333-bdbd
 da132676/\n\nThe Web of Things (WoT) WG/IG will run a [PlugFest from 25-27
  October](https://github.com/w3c/tpac2026-meetings/issues/55). This breako
 ut session will show the results of the PlugFest including live demos from
  different participants.\n\nYou will learn how WoT counters the fragmentat
 ion of the Internet of Things (IoT) by using and extending existing\, stan
 dardized Web technologies. By providing standardized metadata and other re
 -usable technological building blocks\, W3C WoT enables easy integration a
 cross IoT platforms and application domains.\n\n**Goal(s):**\npresenting l
 ive demos from the WoT PlugFest and learn\, e.g.\, Plug&Play device onboar
 ding with WoT\n\nAgenda\n\ntbd\n\n**Materials:**\n- [Session proposal on G
 itHub](https://github.com/w3c/tpac2026-breakouts/issues/9)
STATUS:CONFIRMED
CREATED:20261013T144349Z
LAST-MODIFIED:20261021T034039Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 05
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:524e7095-a968-4fb4-9b3e-0c06b65cb0c2
DTSTAMP:20261021T034255Z
SUMMARY:When Browsers Act for You: User Consent\, Consequential Actions\, a
 nd Agent Neutrality
DTSTART;TZID=Europe/Dublin:20261028T163000
DTEND;TZID=Europe/Dublin:20261028T173000
DESCRIPTION:https://www.w3.org/events/meetings/524e7095-a968-4fb4-9b3e-0c06
 b65cb0c2/\n\nAs AI agents move into the browser\, whether built in\, insta
 lled as extensions\, or calling new web APIs\, they're acting inside tabs 
 where the user is already signed in. That shift raises hard questions acro
 ss security\, privacy\, identity\, and competition.\n\nLast year's breakou
 ts on [Agentic Browsing and the Web's Security Model](https://github.com/w
 3c/tpac2025-breakouts/issues/25) and [Semantics for the Agentic Web](https
 ://github.com/w3c/tpac2025-breakouts/issues/48) started the conversation a
 round user agency versus site control. This year\, with early browser-agen
 t trials underway and related breakouts exploring [agent alignment](https:
 //github.com/w3c/tpac2026-breakouts/issues/25)\, [agent security](https://
 github.com/w3c/tpac2026-breakouts/issues/5)\, [anonymous credentials](http
 s://github.com/w3c/tpac2026-breakouts/issues/29)\, and [verified agent com
 merce](https://github.com/w3c/tpac2026-breakouts/issues/39)\, we want to d
 ig into three practical trade-offs around how the browser mediates between
  the user\, the agent\, and the site:\n\n- **Avoiding prompt fatigue witho
 ut losing user control:** Asking for permission before every tool call or 
 form submission just trains people to click "Allow" without reading\, like
  cookie banners. But we obviously can't let an agent buy things\, move mon
 ey\, or delete data in the background without asking. How do we support a 
 "gather\, then commit" flow where an agent can research and stage a task o
 n its own\, and the browser steps in for a real human check before anythin
 g final happens?\n- **Browser-owned checkpoints vs. in-page confirmation m
 odals:** If a website builds its own "Are you sure?" modal in HTML\, an ag
 ent driving the page can click that confirm button just like any other but
 ton. Where does the browser itself need to step in with confirmation UI th
 at an agent can't click past? And how should risk hints from a site\, like
  WebMCP's `readOnlyHint` or proposed hints for high-stakes actions\, conne
 ct with existing browser gates like Autofill\, Payment Request\, and WebAu
 thn when a site forgets or mislabels a hint?\n- **Balancing site defense w
 ith agent neutrality:** Websites and merchants reasonably want fraud prote
 ction\, rate limits\, and a way to shut off an agent that's misbehaving. A
 t the same time\, browser vendors and privacy groups worry that exposing w
 hich specific agent vendor is calling in client-side web APIs\, or requiri
 ng partner allowlists for in-tab actions\, makes it easy for sites to bloc
 k user-chosen agents in favor of commercial partners. How can we give site
 s practical ways to manage automated traffic and revoke bad agent runs\, l
 ike separate agent sub-sessions or privacy-preserving tokens\, without tur
 ning the browser into a gatekeeper for which assistant a user is allowed t
 o pick?\n\nWe'd like to get browser\, security\, privacy\, and identity fo
 lks together with site owners to talk through these trade-offs openly and 
 figure out what belongs in web specs versus what should be left to browser
  UI.\n\n**Goal(s):**\nWork toward shared principles across browsers\, secu
 rity and privacy groups\, and site owners on how in-browser agents should 
 handle user confirmation and site safety without causing prompt fatigue or
  locking users into partner-approved agents.\n\nAgenda\n\n- **First 10 min
 utes:** Walking through the three tensions we're seeing in early browser-a
 gent trials: prompt fatigue\, in-page versus browser-owned confirmation\, 
 and site defense versus agent neutrality.\n- **Next 15 minutes:** How brow
 sers should handle confirmation for high-stakes actions\, and how risk hin
 ts from sites fit with Autofill\, Payment Request\, and WebAuthn.\n- **Nex
 t 20 minutes:** Giving sites control over agent traffic without breaking a
 gent neutrality\, comparing verified agent ID proposals against separate a
 gent sub-sessions and privacy-preserving rate limiting.\n- **Final 15 minu
 tes:** Agreeing on shared principles for TAG\, WebAppSec\, and Privacy\, a
 nd separating what belongs in web specs from browser UX.\n\n**Materials:**
 \n- [Session proposal on GitHub](https://github.com/w3c/tpac2026-breakouts
 /issues/71)
STATUS:CONFIRMED
CREATED:20261013T144659Z
LAST-MODIFIED:20261021T034255Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Ulster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:cc2b0b80-f331-4e60-9757-e7f23da4ebf0
DTSTAMP:20261021T034246Z
SUMMARY:Integrating AI into W3C Work: Task Force Lessons and Peer Exchange
DTSTART;TZID=Europe/Dublin:20261029T170000
DTEND;TZID=Europe/Dublin:20261029T180000
DESCRIPTION:https://www.w3.org/events/meetings/cc2b0b80-f331-4e60-9757-e7f2
 3da4ebf0/\n\nThis session will be a discussion on the advantages and the p
 itfalls we have found when using artificial intelligence (AI)  in our rese
 arch work. We are also interested to find out how other groups are using A
 I. \n\nWe’ll explore how W3C task forces can integrate AI tools into sta
 ndards and research workflows while maintaining quality\, accessibility\, 
 and human oversight. It will include: \n\n- Practical examples of AI integ
 ration in drafting research modules on user testing\, triggers  and artifi
 cial intelligence (AI). \n- Challenges we have encountered and processes w
 e are implementing. \n- Cross-group discussion on how other groups are usi
 ng AI to help their work at the W3C and shared insights.\n\nThe Cognitive 
 and Learning Disabilities Accessibility Task Force (COGA) are hosting the 
 session. Everyone is welcome. You do not need a background in cognitive ac
 cessibility or AI to take part.\n\nLeonard Beasley will chair the session.
 \n\n**Goal(s):**\nShare experiences of using AI in W3C work\, including su
 ccesses and challenges and foster working together.\n\nAgenda\n\nWelcome a
 nd introductions (5 minutes). Choose a scribe. Share how to take part in I
 RC (#coga).\n What COGA research modules are (5 minutes). \nHow COGA is us
 ing AI to aid our W3C work (25 minutes). Covers challenges we have encount
 ered and processed we are implementing.\n\n- Update a draft -  Module on t
 riggers\n- New module - User Testing module: User Testing for Cognitive Ac
 cessibility.\n- Add a new section  - Draft: Artificial Intelligence and Al
 gorithms (including Social Media and Data).\n- Citations  and editing \n- 
 Problems we encountered \n- Processes we are using \n\nDiscussion / next s
 teps Next steps (25 minutes). How are you using AI to help your work at th
 e W3C?\n\n**Materials:**\n- [Session proposal on GitHub](https://github.co
 m/w3c/tpac2026-breakouts/issues/67)
STATUS:CONFIRMED
CREATED:20261013T144646Z
LAST-MODIFIED:20261021T034246Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 01 and 02
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:82ec7557-183d-4aa4-8474-92db40d4a43f
DTSTAMP:20261021T034141Z
SUMMARY:Pre-Kickoff Meeting for DID Methods WG (or\, conversely\, emergency
  WG Charter Triage Meeting!)
DTSTART;TZID=Europe/Dublin:20261029T170000
DTEND;TZID=Europe/Dublin:20261029T180000
DESCRIPTION:https://www.w3.org/events/meetings/82ec7557-183d-4aa4-8474-92db
 40d4a43f/\n\nPending approval of the charter\, this informal meeting could
  be a chance to:\n\n- recruit participants and other stakeholders (or spon
 sors!) from further afield than the DID WG community\n- present (and debat
 e potential modifications to) the draft evaluation criteria and process in
  anticipation of the first official meeting\n- chat with browser vendors a
 nd W3C members about the specific use-cases they might be interested in su
 pporting\, and how their requirements could be codified as mandatory or op
 tional factors in the evaluation process\n\n**Goal(s):**\nRecruit particip
 ants\, issue-openers\, and stakeholders for the upcoming new WG\n\nAgenda\
 n\n**Materials:**\n- [Session proposal on GitHub](https://github.com/w3c/t
 pac2026-breakouts/issues/37)
STATUS:CONFIRMED
CREATED:20261013T144516Z
LAST-MODIFIED:20261021T034141Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 08
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:416f3eab-169e-4d20-95dd-a238cddeedc8
DTSTAMP:20261021T034128Z
SUMMARY:The future of agentic web experiences
DTSTART;TZID=Europe/Dublin:20261029T170000
DTEND;TZID=Europe/Dublin:20261029T180000
DESCRIPTION:https://www.w3.org/events/meetings/416f3eab-169e-4d20-95dd-a238
 cddeedc8/\n\nThis session will explore a collective project that Microsoft
  is proposing for how we're looking to prioritize work on the web platform
 . Using real world user journeys and early benefits we've found. Based on 
 this we'll go over key categories that we believe warrant discovery\, inve
 stment and prioritization to have a holistic view of how the web should ev
 olve for agentic experiences with a human in the loop.\n\n**Goal(s):**\nAl
 ignment on a joint initiative to incubate key solutions\n\nAgenda\n\n1. Pr
 esentation for Future of Web Experiences including a review of a real prot
 otype in Edge to see real world value (30-40 mins) \n2. Call for support o
 f the effort as a collective project/effort to drive incubation\n3. Q&A / 
 General Discussion\n\n**Materials:**\n- [Session proposal on GitHub](https
 ://github.com/w3c/tpac2026-breakouts/issues/31)
STATUS:CONFIRMED
CREATED:20261013T144456Z
LAST-MODIFIED:20261021T034128Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Ulster Suite
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:89c55337-9199-460a-8176-84e7df2041fc
DTSTAMP:20261021T034319Z
SUMMARY:W3C group activity pages: presentation and feedback
DTSTART;TZID=Europe/Dublin:20261029T170000
DTEND;TZID=Europe/Dublin:20261029T180000
DESCRIPTION:https://www.w3.org/events/meetings/89c55337-9199-460a-8176-84e7
 df2041fc/\n\nThe W3C Systems team just released a new W3C group feature: [
 activity pages](https://www.w3.org/blog/2026/introducing-group-activity-pa
 ges/). These pages are meant to show what a group has been doing\, month b
 y month.\n\nFor an example\, see the [GPU for the Web activity page](https
 ://www.w3.org/groups/wg/gpu/activity/).\n\nThe goal of this session is to 
 present these new pages\, and gather feedback and ideas to improve this sy
 stem further.\n\n**Goal(s):**\nGather feedback and expectations on the new
  group activity pages\n\nAgenda\n\n1) Presentation\n2) Next steps\n3) Disc
 ussion\n\n**Materials:**\n- [Session proposal on GitHub](https://github.co
 m/w3c/tpac2026-breakouts/issues/82)
STATUS:CONFIRMED
CREATED:20261013T144732Z
LAST-MODIFIED:20261021T034319Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 06
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:812ab231-8d44-45ce-bf80-2234b422c84d
DTSTAMP:20261021T034019Z
SUMMARY:What's new in Pointer Events Level 3
DTSTART;TZID=Europe/Dublin:20261029T170000
DTEND;TZID=Europe/Dublin:20261029T180000
DESCRIPTION:https://www.w3.org/events/meetings/812ab231-8d44-45ce-bf80-2234
 b422c84d/\n\n[Pointer Events Level 3](https://www.w3.org/TR/pointerevents3
 /) has just recently gone to stable recommendation. In this session\, we'd
  like to give a short presentation and overview (with live demos) of Point
 er Events in general\, and what new features have been introduced in the l
 atest version of the specification.\n\n**Goal(s):**\nProvide an overview o
 f Pointer Events and the new features in Level 3\n\nAgenda\n\n* Presentati
 on and demos (approx. 25 mins)\n* Q&A\n\n**Materials:**\n- [Session propos
 al on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/1)
STATUS:CONFIRMED
CREATED:20261013T144324Z
LAST-MODIFIED:20261021T034019Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 05
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:8af67b37-ad60-4ef2-8082-e1da57f909b0
DTSTAMP:20261021T034341Z
SUMMARY:Learnings from implementing Spatialized HTML/CSS in WebSpatial
DTSTART;TZID=Europe/Dublin:20261030T083000
DTEND;TZID=Europe/Dublin:20261030T093000
DESCRIPTION:https://www.w3.org/events/meetings/8af67b37-ad60-4ef2-8082-e1da
 57f909b0/\n\nBuilding on the [TPAC 2025 WebSpatial breakout](https://githu
 b.com/w3c/tpac2025-breakouts/issues/22)\, this session shares implementati
 on experience to inform discussion of spatial capabilities for HTML\, CSS 
 and dynamic 3D API.\n\nWe’ll examine challenges and tradeoffs in spatial
  layout\, depth and transforms\, materials\, interaction events\, and comb
 ining 2D interfaces with 3D content. We’ll discuss how these capabilitie
 s can preserve existing web behavior and development patterns.\n\nCommunit
 y members are invited to compare approaches\, challenge assumptions\, and 
 identify areas for further experimentation and collaboration. Implementati
 on demos will ground a discussion of requirements and standards work.\n\n*
 *Goal(s):**\nIdentify concrete requirements\, open questions\, and follow-
 up work for spatialized HTML/CSS across the relevant web standards communi
 ties.\n\nAgenda\n\n1. Short presentation of existing spatial features in W
 ebSpatial (20 mins)\n2. Group discussion to review challenges of building 
 spatial features in other browsers (20 min)\n3. Summary of future developm
 ent and next steps (10 min)\n\n**Materials:**\n- [Session proposal on GitH
 ub](https://github.com/w3c/tpac2026-breakouts/issues/93)
STATUS:CONFIRMED
CREATED:20261021T034341Z
LAST-MODIFIED:20261021T034341Z
SEQUENCE:0
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 03
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:a70e4c41-5f8b-4b82-9fb6-d845a38f648c
DTSTAMP:20261021T034325Z
SUMMARY:Media for WoT
DTSTART;TZID=Europe/Dublin:20261030T083000
DTEND;TZID=Europe/Dublin:20261030T093000
DESCRIPTION:https://www.w3.org/events/meetings/a70e4c41-5f8b-4b82-9fb6-d845
 a38f648c/\n\nRecently\, the Web of Things WG (WoT-WG) has started to discu
 ss media handling capability for WoT as a possible use case [a\, b]\, and 
 the group would like to have joint discussion with the media experts inclu
 ding the Media and Entertainment IG (MEIG) during TPAC 2026.\n\nFor that p
 urpose\, the Chairs of the WoT-WG and the MEIG have been holding initial d
 iscussion about a possible breakout session on "Media for WoT" during TPAC
 . We think holding the discussion as an official TPAC breakout session wou
 ld be very useful\, because we'd like to invite all the experts from both 
 the WoT world and the media world. Also we'd like to hear from all the oth
 er related/interested people attending TPAC 2026 in Dublin.\n\n**NOTE:**\n
 I've been suggesting the WoT WG should think about media handling capabili
 ty for the WoT mechanism for years\, and really would like to see what is 
 still missing to make the Web Browser a WoT Thing and/or a WoT Consumer.\n
 \n[a] WoT minutes: https://pad.w3.org/p/2026-08-0506-wot-td-minutes\n[b] E
 xpand media streaming analysis proposal: https://github.com/w3c/wot-thing-
 description/pull/2213\n\n**Goal(s):**\nPresenting the initial proposal on 
 "Media for WoT"\, and gathering opinions/ideas about existing pain points 
 and possible use cases\n\nAgenda\n\n[DRAFT Agenda] \n* Media handling capa
 bility for WoT\n  * [Expand media streaming analysis proposal](https://git
 hub.com/w3c/wot-thing-description/pull/2213)\n  * Media with geolocation i
 nformation\, e.g.\, WebVMT\n  * Open discussion\n\n**Materials:**\n- [Sess
 ion proposal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/8
 5)
STATUS:CONFIRMED
CREATED:20261013T144741Z
LAST-MODIFIED:20261021T034325Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 06
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:1fd62b0c-bb75-4a6c-ad62-ec6ae817861f
DTSTAMP:20261021T034108Z
SUMMARY:The Agentic Web
DTSTART;TZID=Europe/Dublin:20261030T083000
DTEND;TZID=Europe/Dublin:20261030T093000
DESCRIPTION:https://www.w3.org/events/meetings/1fd62b0c-bb75-4a6c-ad62-ec6a
 e817861f/\n\nWhat could the Agentic Web look like? What do we need to do t
 o standardize it? \n\nMore details coming soon...\n\n**Goal(s):**\nDirecti
 ons for future work at the W3C around enabling the web to work well with A
 I agents.\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](http
 s://github.com/w3c/tpac2026-breakouts/issues/22)
STATUS:CONFIRMED
CREATED:20261013T144430Z
LAST-MODIFIED:20261021T034108Z
SEQUENCE:3
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Ground Floor - Lansdowne Room
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:437890c5-8be3-44d2-b5e8-d8cd2a69d847
DTSTAMP:20261021T034136Z
SUMMARY:Unleashing a Spatial Web: Mapping W3C Standards to Support a Web of
  Worlds
DTSTART;TZID=Europe/Dublin:20261030T083000
DTEND;TZID=Europe/Dublin:20261030T093000
DESCRIPTION:https://www.w3.org/events/meetings/437890c5-8be3-44d2-b5e8-d8cd
 2a69d847/\n\nThe Web already delivers spatial and immersive experiences - 
 via WebXR\, WebGPU\, WebAssembly\, real-time communications\, digital iden
 tity\, geospatial technologies\, 3D formats and the wider Web platform - *
 *but not yet an interoperable Web of linked spatial experiences\, the way 
 URLs and HTML link today's Web.**\n\n[The Metaverse Standards Forum (MSF) 
 Web of Worlds initiative](https://webofworlds.github.io/) frames this prob
 lem concretely. Instead of a new stack or 3D format\, it composes existing
  standards around three concepts:\n\n- **Open Spatial Worlds:** spatial ex
 periences that can be addressed\, linked and composed with Web technologie
 s\;\n- **Open Spatial Assets:** independently hosted 3D/spatial resources 
 that can be referenced and reused across experiences\;\n- **Open User Mani
 fests:** mechanisms for users to carry identity\, preferences\, avatars\, 
 assets and other user-controlled data between worlds.\n\n**Much of the nee
 ded infrastructure already exists across the Web Platform and other standa
 rds ecosystems.** The open questions are where existing standards suffice\
 , where integration or profiling is needed and where genuine gaps remain.\
 n\nChair note: TBD - jointly organised W3C / Metaverse Standards Forum ses
 sion. Additional facilitators from the MSF / Web3D Consortium to be confir
 med.\n\n**Goal(s):**\nCreate an initial mapping of W3C standards to suppor
 t a Web of Worlds - connecting concrete spatial Web requirements to existi
 ng standards\, relevant W3C groups and identify remaining gaps.\n\nAgenda\
 n\n1. Why a Web of Worlds?\n\n2. Web of Worlds in one picture\n \n3. What 
 the Web already provides\n \n4. Standards gap discussion\, in three parts:
 \n    - Linking\, Addressing & Locating the Spatial Web\n    - Spatial Com
 position\, Semantics & User-Agent Responsibilities\n    - Portable Identit
 y\, User Data & Preferences\n \n5. Testing against use cases\n \n6. Where 
 does the work belong?\n \n7. Next steps\n\n**Materials:**\n- [Session prop
 osal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/35)
STATUS:CONFIRMED
CREATED:20261013T144510Z
LAST-MODIFIED:20261021T034136Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 08
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:bf2da82d-6274-4475-a3de-09580309e44f
DTSTAMP:20261021T034339Z
SUMMARY:Visibility Security Model and CSS Styling Restrictions for Elements
DTSTART;TZID=Europe/Dublin:20261030T083000
DTEND;TZID=Europe/Dublin:20261030T093000
DESCRIPTION:https://www.w3.org/events/meetings/bf2da82d-6274-4475-a3de-0958
 0309e44f/\n\nCurrently declarative elements—such as `<usermedia>\, <came
 ra>\, <microphone>\, and <geolocation>`—ensuring a clear\, unambiguous s
 ignal of user intent is paramount.\n\nSo\, user agents should implement a 
 visibility security model and styling constraints (such as bounds on opaci
 ty\, sizing\, and contrast as in intentful activation draft https://wicg.g
 ithub.io/PEPC/usermedia-element-intentful-activation.html) to mitigate cli
 ckjacking and spoofing. However\, these rules often exist as browser-speci
 fic hints or loose guidelines rather than a formal web standard\, leading 
 to cross-browser inconsistencies and unexpected fallbacks. \n\nThis sessio
 n will focus on reaching an agreement regarding CSS restriction rules and 
 computed style bounds across browsers to ensure a consistent developer exp
 erience and predictable behavior.\n\nChairs: Thomas Nguyen (@tungnh28 )\, 
 Balazs Engedy (@engedy)\, Daniel Vogelheim (@otherdaniel)\n\n**Goal(s):**\
 nEvaluate whether to standardize styling restrictions and visibility bound
 s across browsers\, identify the right balance between layout flexibility 
 and security guarantees\, and collect feedback from browser vendors and we
 b devs.\n\nAgenda\n\n**Materials:**\n- [Session proposal on GitHub](https:
 //github.com/w3c/tpac2026-breakouts/issues/92)
STATUS:CONFIRMED
CREATED:20261020T173750Z
LAST-MODIFIED:20261021T034339Z
SEQUENCE:0
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 09
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
BEGIN:VEVENT
UID:469a460d-3729-4da6-9ca9-9163f9f52b85
DTSTAMP:20261021T034321Z
SUMMARY:What can go wrong with the new KSK and what W3C communities can do 
 to minimize the risks
DTSTART;TZID=Europe/Dublin:20261030T083000
DTEND;TZID=Europe/Dublin:20261030T093000
DESCRIPTION:https://www.w3.org/events/meetings/469a460d-3729-4da6-9ca9-9163
 f9f52b85/\n\nOn 11 October 2026 the DNS root is scheduled to switch to a n
 ew key-signing key\, KSK-2024. A validating resolver that does not trust t
 he new key may leave its users unable to reach sites under any top-level d
 omain. Validating resolvers are run by ISPs\, enterprises and others on us
 ers' behalf\, and users have little means to check their status.\n\nRead a
 lso [backgrounder](https://github.com/w3c-cg/aikr/blob/main/trust/ksk.md)\
 n\nFurther root key events are planned: revocation of KSK-2017 in 2027\, a
  proposed algorithm rollover to ECDSA between 2027 and 2029\, and a later 
 post-quantum root key. Meanwhile the Credentials CG has discussed rooting 
 DIDs in DNSSEC\, leading to [draft-ranjbar-dane-did-01](https://www.ietf.o
 rg/archive/id/draft-ranjbar-dane-did-01.html)\, so credentials and agent i
 dentities may come to depend on the same anchor.\n\nThe session follows on
  from the TPAC 2025 "Future of the Open Web" discussion and from a submiss
 ion to the Data Governance & Ownership mini-workshop ([w3c/tpac2026-miniwo
 rkshops#39](https://github.com/w3c/tpac2026-miniworkshops/issues/39)). It 
 opens with what the rollover showed\, then works through open questions:\n
 \n- Does a stale resolver block publishing as well as reading?\n- Can a re
 solver that was ready lose readiness after a reinstall or migration?\n- Ho
 w can a user\, support desk or agent tell a trust-anchor failure from an o
 rdinary outage?\n- Who is accountable when a resolver operator misses a ro
 llover?\n- Would DNS-bound credentials and agent identities fail closed be
 hind a stale resolver\, and how would a relying party learn why?\n- Which 
 W3C specifications inherit trust from the DNS root\, and do they say so?\n
 \nReferences: \n\n- [Cloudflare on the KSK-2024 rollover](https://blog.clo
 udflare.com/root-ksk-2024-rollover/)(https://blog.cloudflare.com/root-ksk-
 2024-rollover/)\n- [Credentials CG thread](https://lists.w3.org/Archives/P
 ublic/public-credentials/2026Jul/0041.html)(https://lists.w3.org/Archives/
 Public/public-credentials/2026Jul/0041.html) \n- [ICANN proposed algorithm
  rollover](https://www.icann.org/en/public-comment/proceeding/proposed-roo
 t-ksk-algorithm-rollover-03-02-2026)\n\nNote: The proponent of this breako
 ut session @starborn is not going to be attending in person\, and is creat
 ing this issue\, to raise awareness among w3c communities of the risks ari
 sing from the ney KSK key\, Individuals who care for the open web attendin
 g TPAC in person\, please come forward to co chair this breakout session o
 r please\, bring the topic up in relevant sessions that you may be organiz
 ing/attending\n\n**Goal(s):**\nAgree what W3C communities can do to reduce
  risks to users and agents from root key changes\, and whether the topic w
 arrants a W3C Workshop\, a TAG review request or joint work between the Cr
 edentials CG\, DID WG\, Autonomous Agents on the Web CG and AIKR CG.\n\nAg
 enda\n\n1. What the 11 October rollover showed (10 min)\n2. Risks to users
 ' read and write access (15 min)\n3. Identifiers\, credentials and agents 
 bound to DNS names (15 min)\n4. What W3C communities can do next (15 min)\
 n5. Actions and follow-up venue (5 min)\n\n**Materials:**\n- [Session prop
 osal on GitHub](https://github.com/w3c/tpac2026-breakouts/issues/83)
STATUS:CONFIRMED
CREATED:20261013T144735Z
LAST-MODIFIED:20261021T034321Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Second Floor - Room 05
CATEGORIES:TPAC 2026,Breakout Sessions
END:VEVENT
END:VCALENDAR