W3C Breakouts Day 2025 calendar - Breakout Sessions

A breakout session to discuss how browser users can interact with ActivityPub-enabled people and objects on the Web. For example: following people, liking and commenting on text or images.

Goal(s):
Investigate how browser users can interact with ActivityPub-enabled people and objects on the Web and define next steps

Where do we stand with FedCM? We'll show you and talk about the roadmap for where we think things are going next.

Goal(s):
FedCM Update

This session will explore how to diversify the ecosystem of Web user agents by enabling profile applications to increase efficiency and optimize user experience on Web and WebView-based apps while maintaining compatibility with existing standards and the One-Web principle.

Background

In early January, W3C organized the WebAI and High-Performance Web Application Technology seminar for the Chinese community. One of the outcomes of the discussions was the launch of a new CG to support more variety and more performant Web user agents.

The CG aims to diversify the ecosystem of Web user agents by enabling profile standards to increase efficiency and optimize user experience on Web and WebView-based apps while maintaining compatibility with existing standards. Standard profiles and modularity might ease the design and implementation of lighter and more efficient engines for specific-scenario purposes when a full-fledged (embedded) browser is not required (e.g., MiniApps, WoT edge apps, and apps for wearables or constrained infotainment systems) and may serve as common ground for cross-platform development frameworks.

Package distribution strategies should be considered in conjunction with profile standards to ensure optimal content presentation across diverse platforms. Profile standards should be built with mobile-friendly features by default, ensuring a superior user experience and leveraging the unique capabilities of mobile devices.

The CG was titled High-Performance Baseline for Web Apps as a placeholder, but we know it could be misleading -also the initial description. In this breakout session, we would like to clarify the objectives and get the community's feedback to include these insights in the final chapter. The title, scope, and objectives will be discussed in this session.

Audience

This session welcomes vendors of embedded browsers, hybrid cross-platform app frameworks, JS engines, and others interested in exploring the modularity of the Web standards. We aim to collect use cases where standard profiles help enrich the Web ecosystem by opening new possibilities in unexplored scenarios and supporting innovation on the Web while protecting the principles of One-Web and interoperability.

We also want close alignment with other incubation groups working on similar topics (i.e., WebViews CG, WebDX,  WinterTC) and bi-directional conversations with core standardization groups for advice and pushing for new standardization requirements while avoiding fragmentation.

Check more information, including research on this explainer and on this blog post.

Goal(s):
Discuss potential objectives, scope, and interest from the community in this new incubation activity.

Website visitors often expect and seek familiar pages such as contact us, login, or shopping cart. But navigating websites can be a challenge, especially for users who find complex layouts and variable terminology difficult. Building on last year’s feedback, this session from WAI-Adapt Task Force introduces a fresh, semantic approach to navigation that leverages HTML link relation types to define such well known destinations on any page. We will also demo our updated browser extension which embodies this new strategy— simplifying navigation without compromising on design.

We will also facilitate discussion on open challenges identified by the Cognitive and Learning Disabilities Accessibility Task Force (COGA) regarding the clear presentation of destination types. For example, a help resource may be categorized as a “Virtual Advisor,” “Email Helpline,” or “Call Support.” The goal is to ensure that users can simply understand the nature of each option and set accurate expectations before engagement.

Goal(s):
Highlight the challenge; Showcase solutions; and Engage the community

W3C, in conjunction with the AB, is looking at its Events strategy. The Events strategy consists of aligning each event to the global objectives of the Consortium. Each event needs to fulfill a specific goal which serves W3C, their Members and the community.
Meetings are organized for specific reasons and goals. In general, meeting are organized for different purposes:

• Gather targeted stakeholders to move forward on some problematic
• Inform and explain
• Make decisions
• Create interactions between participants

We will focus this discussion on the AC meetings: The participation to these meetings has significantly decreased when the hybrid mode has been re-initiated in 2023, after the pandemic. The goal of the meeting may not be inline with the expectations anymore. We are then looking at restructuring this meeting and need to hear from our community.

Goal(s):
Gather feedback from the W3C Members and AC Reps to come up with a restructuring proposal

As a significant development since the release of AI & the Web W3C Team report, Machine Learning models, and in particular Large Language Models (LLMs), are increasing deployed to complement and sometimes radically transform how users interact with the Web.

In this session, after a quick introduction of the various ways these new AI agents are being surfaced today, we will have an open discussion on how this new paradigm may change the platform itself, and what (if anything) we should do as a community to prepare its potential impact on Web standards.

Goal(s):
Build shared understanding of impact of AI agents on the Web Platform

In the first episode we focused on high-level threats related to the Formal Objection received for the addition of the Digital Credentials API.

Considering that the W3C Council has overruled the Formal Objection, the Digital Credentials API is by design strongly linked to its Threat Model.

In this episode, we will therefore focus on a specific model about the step of Presenting Credentials on the Web, asking ourselves: What are we working on? What can go wrong? What are we going to do about it? Did we do a good job?

This breakout is intended to be a collaborative, working session. The focus will be on gaining consensus on threats and mitigations.

Goal(s):
The focus will be on gaining consensus on the mitigations.

As a member elected body, the Advisory Board has been playing a unique and important role in W3C community since 1998. It not only provides ongoing guidance to W3C Team on various topics, forms the Council with the TAG to handle formal objections, and also leads the development of several key W3C polices, such as Vision document, Process Document, Code of Conduct, etc.

With W3C Inc up and running as a new legal entity since Jan 1 2023, W3C has built its new governance structure. The W3C Board of Directors have ultimate authority on W3C's strategic direction and have fiduciary responsibility over W3C Inc as a whole.

Given this background, it is time for the Advisory Board to work with the W3C community and revisit its purpose.

Goal(s):
To seek members input about the purpose of the AB, the unique values that the AB can bring to the W3C community, the expectations/suggestions/comments for the AB.

A session to discuss scoped custom element registry:

• https://github.com/whatwg/html/issues/10854
• https://github.com/whatwg/dom/pull/1341

Goal(s):
Reaching a consensus on the spec PRs

The WebDX Community Group has done a lot of work in 2024 to increase the coverage of its web-features data. Now that the data roughly covers the entire web platform feature set, let's review the work done so far, the use cases that web-features, and Baseline, have unlocked, and let's open it up for discussion on the next important questions to tackle: how to maintain the web-features data over time, as the web platform evolves, keeping in mind web developers' best interest at heart.

Goal(s):
To update participants on WebDX, the work we've done so far, the use cases we've unlocked thanks to the data, and the open questions that are next for us to solve. To ask the audience for input into these open questions.

Discuss a proposal to extend Geolocation API to introduce the concepts of approximate and precise location data.

Sharing precise location information puts the user's privacy at risk as it can reveal sensitive information about the user's personal life such as home address, workplace, or place of worship. However, users may still wish to share location information to enable a more localized experience or facilitate a transaction. Approximate information about the user's location (for instance, a postal code) has a lower privacy risk and is typically sufficient for most applications. Extending Geolocation API to support approximate location would empower users to protect their location privacy and enable sites to request safer defaults when precise location is not needed.

Goal(s):
Introduce the proposal and get feedback

A session to discuss DOM parts

Goal(s):
Come to a consensus on a concrete next step

The MediaSource Extensions (MSE) spec has included in-band text tracks since the first published working draft, but that part of the spec have lacked browser adoption for a very long time.

Recently, WebKit has added experimental support for in-band text tracks in MSE. Work on this has highlighted a number of challenges in bytestream formats and the MSE specifications.

The purpose of this breakout session is to gather together, discuss those challenges and come to agreement on the direction to tackle them in the MSE specifications.

Goal(s):
Clarify some finer points about how in-band text tracks in MSE should work and define next steps for improvements in the specifications.

SVG has been around almost as long as the need for a web vector format has existed. Today, SVG browser support is passable, but there are gaps in that support and performance could be much better. It’s proposed as an Interop focus each year, and each year it gets turned down. What are the factors that make it so difficult to get implementor love for SVG, and how can we change things for the better?

Goal(s):
Brainstorm ways to change the narrative and overcome inertia

Session to talk about how we document web technologies and how we could create more positive feedback loops between specifications and technical docs (on MDN, and generally).

Goal(s):
Get technical writers and specification authors talking and discuss setting up a space where we could meet more frequently.

Collect feedback on the idea of setting up a W3C Documentation Community Group (Docs CG) as outlined in
https://docs.google.com/document/d/1rLt1wT_y7OF9VINVGFj9U5x2C_z9_3aZeOtMh-p_Qf8/edit

Today, each of the three main, open source browser engine projects have a steward organization which contribute, by far, the lion's share of the project's commits - 75-95%. They also take on the infrastructure around it, both physical an managerial. They decide how to allocate available resources. Other contributors add wildly varying levels of contributions, but in all cases it is dictated by them toward work that they decide.

But we are beginning to explore some other ideas involving pools of money: The Chromium Fund, Igalia's Open Prioritization and now whole engines like Servo and Ladybird. In this breakout session we'll discuss what we're exploring, questions that are arising and how to deal with new challenges.

Goal(s):
To discuss the challenges and brainstorm ideas toward greater collective ownership

For people who are blind or have low vision, identifying dynamic changes (non-user-initiated) in the content of a web app is very challenging. ARIA live regions are the only mechanism available today that communicate content changes down to the accessibility layer so that users can hear about them.

ARIA live regions are inconsistently implemented, have poor developer ergonomics, and are being used in ways that they weren't designed for (e.g., as a confirmation of action or notification-like API for changes unrelated to "live regions"). We propose an imperative notification API designed to replace the usage of ARIA live regions in scenarios where a visual "live region" isn't necessary.

This talk will provide an overview of the proposed solution, AriaNotify, what will be included in the first version of the API, and what functionality we are hoping to work with ATs to unblock improved notification handling for authors and end users.

Goal(s):
API Overview and Feedback

Scope

Explore web use cases, requirements and related issues for location-aware video cameras with additional sensors.

Background

Web Video Map Tracks (WebVMT) is a variant of WebVTT that is designed to synchronise location and sensor data with video for the web. This open format is aimed at users of drones, dash cams, body cameras and smartphones, and was published as a W3C/OGC Group Note in September 2023 by the Spatial Data on the Web WG.

Discussion

Understanding how web communities use geotagged video is key to identifying missing features and ensuring that users' requirements are properly addressed.

Participants are invited to:

• Highlight new use cases
• Suggest ideas for enhancements
• Discuss integration with web interfaces

Previous issues can be found in the WebVMT Community Group and more use cases are outlined in the W3C Group Note. Implementations based on these ideas have been prototyped in the OGC Testbeds to ensure that WebVMT features properly address community needs.

Goal(s):
Identify missing web requirements for geotagged video use cases with sensors.

A session to discuss Template Instantiation.

Goal(s):
Come to a consensus on a concrete next step