This year, the meeting will be hybrid with the main in-person hub in Vancouver, Canada, and remote event attendees.
Questions about accessibility requirements will be found at the end of this form, as well as information and questions about meals, accessibility, vaccine status and travel requirements for an in-person participation.
The Privacy Interest Group (PING) monitors ongoing privacy issues that affect the Web, investigates potential areas for new privacy work, and provides guidelines and advice for addressing privacy in standards development, including privacy considerations in specifications.
PING will have a short meeting on the first morning of TPAC to help coordinate our outreach to other group meetings throughout the week and to discuss the privacy review process and how to improve it.
This is a hybrid meeting: some will attend in person and some remotely. Remote participation details are included in this event page.
We're planning to run a hands-on, not-so-structured workshop, where WG participants can get their proverbial hands dirty and play around debugging various webperf issues using various browser's developer and browser-developer tools! Join us!!
The Improving Web Advertising BG will meet at TPAC, 13 September, with remote and on-site (Vancouver, Canada) participation. Remote participation will be via zoom, to integrate with on-site facilities.
We will review how intelligent personal assistants can interoperate in a similar fashion to web pages. There are 1,000's of intelligent personal assistants in existence, but there are no standards that enable them to interoperate -- each is based on a proprietary platform. Our group is proposing a common architecture and interfaces to promote interoperability. We'll talk about the documents that we've prepared so far and get your feedback. Find out how interoperable intelligent agents can benefit you.
We'll take a break at 9:30.
Hello WG,
Like we previously discussed and agreed, we will have our TPAC hybrid WG meeting from 10 am to 4 pm, split in two sessions with the lunch break between noon and 2 pm PDT.
Please see agenda below, additional agenda+ suggestions are welcome.
Please note that all in-person TPAC participants are expected to comply with the following health & safety requirements.
Moderated Round Table discussion with subject matter experts on the intersections of standards, information architecture, research, accessibility, inclusion, identity, privacy, and security in convergence environments
Virtual meeting on Zoom
Requires logging on to an authenticated Zoom account
Dial in is not available
Waiting room is enabled
PATCG will meet at 13:30 to 15:30 local Vancouver time.
This is a CG event, so involvement is open, according to W3C rules. If you would like to attend the remote event you will need to register for a W3C account and register for this specific event in advance.
The Zoom link will be added to the agenda. See that link below.
In TPAC2022, SemInd will introduce its overall goal. its architecture, and the plan for the first year of development.
The SemInd group will present its perspective regarding the semantification of insdustries, industrial machines, sensors, actuators, and systems.
MathML Core -- this is focused on defining a subset of MathML that is both widely used relatively easily implementable in current browsers. Igalia has worked with Google and developed MathML in Chromium to the point that they have filed an "Intent to Ship" request
MathML 4 -- this is a cleanup of the MathML 3 spec to align with Core and also to enhance the accessibility of MathML.
The meeting is focused on the MathML 4 recommendation.
We will give 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.
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.
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. Presentation Slides
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.
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!
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.
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)
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
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!
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.
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.
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.
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.
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 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.
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!
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 potentially outrageous 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.
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.
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.
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.
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.
– Pacific Daylight Time
Location: Grand D — North Tower Grand Ballroom Level
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).
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.
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.
Location: Pavilion foyer - 3rd floor (indoor space), Fountain Square - Lobby Level (outdoor space) - The food station will be in the indoor space only. Drinks will be available both in the indoor and outdoor space.
Day 1 of Immersive Web Group meetings agenda is below. Additionally, we will have the WebRTC joint meeting on September 13th, in the afternoon. We are working on getting the exact time for the meeting.
13:30 - 14:30 (60 min) Charter & progress review (deck)
In this section we will review the scope of work and deliverables sections of our charter, discuss potential modifications to these sections, survey progress made on deliverables, and discuss next steps.
14:30 - 14:40 (10 min) Break
14:40 - 15:30 (20 min) User script manager support in MV3
15:00 - 15:20 (20 min) Offscreen Documents for Manifest V3 or Limited Event Pages for MV3
15:20 - 15:30 (10 min) Make extension APIs browser neutral