Discussion of current and upcoming work on the File System Standard, including the high-performance Access Handles API.

Low level device APIs in incubation address a range of needs in education, industrial, small business, and enterprise. Many peripherals people expect to work with computers have become available to web applications. Chrome, Edge, and Samsung browsers have enabled Bluetooth, HID, Serial, and USB. We will discuss the adoption & developer interest to date, answer questions, and discuss opportunities for the web to serve more needs.

Foundational parts of the HTML Standard, regarding navigation and session history, are being rewritten. Come find out why this is necessary, and what it means for your specs. If you've ever dealt with browsing contexts, iframes, etc., this might be relevant!

The abundance of privacy protection mechanisms (CORS, TAO & CORP to name a few) are great for protecting private user data, but make services jump through hoops when they want to serve resources that do not require privacy protection at all - public resources, such as free-for-all images on CDNs. This is an open discussion on how to make serving such content easier and more future proof.

An introduction to the Common Impact Data Standard (CIDS), including an overview of the impact measurement space, the social purpose ecosystem and the challenges that CIDS is designed to solve. We will discuss the technical specification and the possibility of a dedicated Working Group.

A fearless overview of current and prospective edge technologies application to enhance accessibility (including those highly controversial overlays)

Interop 2023 is opening up for proposals on September 15.

We will given an update on the group's work and share the 6 main reasons that children with disabilities will benefit from specific consideration in next-generation accessibility standards.

Introducing W3C member support activities to date and brainstorm what type of member support will be required at the new W3C to hear members' voices.

Very short presentation of the changes to the Web Monetization community specification draft and gather feedback.

Update on the Multicast Community Group activities: brief review of motivation and purpose, an overview of draft-jholland-quic-multicast and status on the aioquic implementation, and discussion of the path to browser adoption.

Short and long term, how should login to X with (an associated) Y work? e.g. login to instagram.com with facebook.com, audible.com with amazon.com, youtube.com with google.com and xbox.com/office.com with microsoft.com. Explicitly out of scope of the discussion: ccTLDs X/Y (e.g. login to example.ca with example.co.uk) and other FPS subsets.

A recurring theme in conversations with and surveys of Web developers is how less polished the developer experience is for the Web compared to e.g. native platforms. While some of this gap is unavoidable in a platform anchored in competing implementations of open standards, there is also likely room for a lot of improvements through better coordination of browser and dev tools providers. This breakout offers to identify such opportunities and will report on some early discussions around coordinated developer-targeting research (as was done with the MDN DNA survey) and increasing the understanding of the interoperable surface of the Web platform (as illustrated by the Interop 2022 effort)

Go over how User Agent breaking changes can have adverse effects on users due to the time needed for sites to adjust to the changes.

W3Cx is W3C's partnership with edX since 2015. This is where we offer MOOCs on core Web technologies. W3Cx’s catalog is composed of 7 MOOCs: in addition to the Front-End Web Developer program (5 courses on HTML5, CSS and JS), W3C produced “Introduction to Web Accessibility” (available until 31 December 2022) and “Introduction to Web Authentication” (new session to be launched on 8 Nov. 2022, in partnership with Yubico). edX/2U offer a leading global online learning platform. To date, we serve over 44 million learners with access to world-class education in partnership with more than 230 colleges, universities, and corporations. Our people and technology are powering more than 3,600 digital education offerings—from free courses to full degrees—and helping unlock human potential.

Presentation & tutorial on the ne Digital Accessibility Apprenticeship Program, funded, and governed by the U.S. Department of Labor.

IP address is a highly identifiable signal used for cross-site identity joining i.e. tracking users. How can we mitigate this privacy risk? Discuss relevant technologies

Explore when users exchange rich data through the copy and paste transfer mechanism.

Think about architectural models for allowing user accessibility choices while maintaining privacy and providing data to support product development, with reference to the video element in particular.

Innovation is the key to success in today's fast-paced, competitive marketplace. To be successful, companies must continuously create new and better products and services. But how can they do this? One answer is to embrace open standards. This Panel Session discusses Innovation best practices that allow companies to share knowledge, ideas, data, and code. We discuss strategies to promote collaboration and enable companies to leverage each other's Innovation Processes. Expert Speakers share enterprise success factors of adopting open standards to speed up the Innovation process, creating better products and services faster.

Discussion on a system where untrusted modular components can access private user data through policy protection and enforcement. Join us to play with prototypes and learn more!

The W3C Process requires adequate implementation experience to be able to transition a document beyond Candidate Recommendation. Some of the past transitions raised concerns about how this should be interpreted. This session is intended to help the community get a better grip on the 3 Big Is – interoperable, independent, implementation.

Present the current status of the Web of Things in the WoT IG/WG and CGs, and showcase a number of application demonstrations.

One of the largest developer pain points is styling/modifying the content of the controls/components that ship natively with the user-agent. Open UI will provide an update on the progress on new elements and primitives to improve this.

Some big changes to how cookies work in browsers make us rethink how Fetch and HTML integrate with the cookies RFC and whether more cookie behavior could be defined in browser land. Join us to learn about and discuss the future of cookies in standards!

A new web API for framing web content in a manner that's isolated from its embedder

The climate crisis requires urgent action to reduce energy usage and carbon emissions and there is varied interest in systematic work to make the Internet and the Web more sustainable.

Presentation of the W3C Accessibility Maturity Model First Public Working Draft.

Chromium folks have been working within the CSSWG to give developers an easy way to create page transitions. We'd like to show how it works, and get feedback from implementers, spec folks, and other interested parties.

The Antifraud CG will use this breakout for further discussion about ad and payments fraud on the Web that arises during the joint meeting of multiple groups on Tuesday; details to follow.

Some developers need stronger security guarantees than can be provided by HTTPS and platforms like Electron show that building apps with HTML, CSS and JavaScript but packaging them like native apps is a popular pattern. Are there opportunities for standardization?

API for capturing an Element as a video stream. Think HTMLCanvasElement.captureStream for an arbitrary type of Element.

What Open Web Docs is and how we document the Web on MDN.

Both Chromium and WebKit are prototyping support for text-based audio descriptions published as VTT. Come view a demo, discuss known issues, and share your feedback, opinions, and advice on this emerging technology.

The Web Components CG will facilitate a discussion with implementers and community members about filling browser gaps in agreed upon features and moving forward with the next wave of top priority features.

WAI-Adapt Content specification enables web content authors to support persons with various cognitive and learning disabilities, including users who need from more familiar icons (and other graphical symbols) in order to comprehend page content, require a simplified page in order to interact successfully, and/or communicate using symbolic languages generally known as Augmentative and Alternative Communications (AAC).

Discussion on Digital-twin services for Smart Cities specifilally about (1) what is already done by whom (SDOs, vendors, governments, etc.) in which area, (2) what is still missing for expected Web-based Smart Cities, and (3) who and how to lead the discussion to resolve the gaps.

Present the findings of the WebView CG & have an open discussion on further use-cases and challenges

BFCache provides a big performance win for navigation but there are obstacles to pages successfully being cached - Cache-Control: no-store header, unload handlers, in-the-wild telemetry for cache misses. This covers proposals for solving these.

Web3 means many things to many people. Some see Web3 as a collection of existing technology that is used to scam many newcomers of their wallet contents. Others see this as a means to a future state where the world's transactions are made on a distributed ledger or blockchain. In this session, we will be exploring what Web3 means to those building in the space and where the intersection of Internet standards might occur, if at all. Think of this as an exploratory conversation with participants in the field and those that are curious about the future of this technology.

CNAME records have a reputation as a tool to circumvent resource-blocking and specific privacy measures. However, if used properly, they can help websites integrate third-party services without requiring third-party cookies, providing a great privacy benefit. We want to discuss how browsers could support privacy-preserving usage of CNAMEs while preventing potential abuse. Joint session with a brief overview of chrome's proposed bounce tracking mitigations following the CNAME discussion.

A reflection of the apps that Project Fugu APIs have enabled, including a brief exploration of the present, the future of some of the enabling APIs, and our vision and dreams for the future.

Give short presentation of overview on Trusted Internet that makes arbitrary data verifiable on the Internet, discuss and gather feedback.

Brief overview of Interest Based Advertising use case and the proposed Topics API as a solution. Informational. Most of the discussion focused on Q/A and driving thorny issues forward.

A potentially outrageaous idea to move (some) document configuration out of HTTP header space into HTML, in a way that allows document authors to set configuration for their own documents, while (hopefully) avoiding most of the concerns around XSS / injection that existing mechanisms have.