TPAC/2025/Demos and Group updates

An opportunity to discover what W3C groups are working on and how that works intersect with other Web technologies.
The group updates and demos are provided as pre-recorded videos. These videos will be shared online from the TPAC 2025 website and published via W3C's YT channel (@W3COfficial).

2025 Timeline

BEFORE SEPTEMBER 28th: Please indicate the name(s) of the volunteer(s) to mcf@w3.org

Please include a title, a description, the W3C group behind the relevant technical work, and the contact person responsible for getting the video recorded.

BEFORE OCTOBER 24th: Please send the recorded videos to mcf@w3.org
OCTOBER 27 - NOVEMBER 7: Videos published on TPAC 2025 videos webpage and on W3C's YT channel.

Confirmed Group Updates and/or Demos

W3C i18n activity update
- by Fuqiao Xue, Senior Principal Internationalization Specialist
- Description: The W3C Internationalization (I18n) Activity works to ensure the web is truly global, supporting all languages, scripts, and cultures. Recent efforts include expanding type samples, advancing layout work for Chinese, Japanese, and Mongolian, adding tests for scripts like Chinese and Tibetan, and publishing new educational resources. Outreach is growing through translations, articles, and video content. We invite wider community participation to help build a web that works for everyone.
Audio Working Group Updates 2025
- by Hongchan Choi (Google), and the Web Audio WG
- Description: The Audio Working Group advanced two key specifications in 2025. The Web Speech API was transferred from the WICG, with Chrome shipping its implementation and Firefox beginning theirs; spec work focused on on-device recognition and TAG privacy feedback. For the core Web Audio API, the AudioContext interrupted state was specified and entered a Chromium Origin Trial. The group also initiated a new Playout Statistics API and continued collaboration with the Web Performance WG on high-resolution time in worklets.
Credentials on the Web
- by Simone Onofri, W3C Senior Principal Security Specialist
- Description: Simone demonstrates how a Digital Credentials API lets users securely share verified data from a wallet. The browser asks to trust the site, connects to the wallet, and shares credentials like a driver’s license. This enables trusted, user-consented data exchange, including for government-issued IDs.
Navigation Capturing for PWAs
- by Dibyajyoti Pal (Google), and the WebApps WG
- Description: Navigation capturing in Progressive Web Apps (PWAs) offers a significant performance advantage by eliminating the delay associated with opening a new browser tab and loading a page. This results in a faster and more seamless user experience, as seen with applications like Google Chat, which substantially reduced navigation latency by avoiding new app launches. By handling navigation within the app itself, PWAs can feel more responsive and integrated, much like a native application. For more details, please refer to https://developer.chrome.com/docs/capabilities/pwa-navigation-management.
Predictable App Updating
- by Dibyajyoti Pal (Google), and the WebApps WG
- Description: Predictable app updating aims to provide developers with consistent control over PWA updates, minimizing user interruptions and wasting of network resources through redundant icon downloads. Non security sensitive fields are silently updated, while an UX is shown for security-sensitive changes, and only triggering icon updates when the icon URL changes, similar to Cache-Control:Immutable behavior. This approach seeks to bridge the gap between PWAs and native apps by making the update process more deterministic and user-friendly.
Web of Things Community Group 2025 update
- by the WoT CG
- Description: The Web of Things expanded significantly this year, releasing new tutorials, hosting meetups, and growing its Discord group by over 50%. Highlights included WoT Week, which showcased demos and collaborations across domains like smart homes and industry. Centered on open-source principles, the community continues to evolve through global contributions and invites newcomers to join via GitHub or Discord.
Demo of Incremental Font Transfer
- by Garret Rieger, and the Web Fonts WG
- Description: This video demonstrates incremental font transfer working in browser to load fonts via a web assembly polyfill. Incremental Font Transfer is a new way to transfer fonts that allows for only the needed data from the original font to be loaded on demand. It will reduce transfer sizes for web fonts while maintaining full rendering correctness. Of particular note it is able to significantly reduce transfer sizes for Chinese, Japanese, and Korean fonts which are currently difficult to use without IFT due to large file sizes. The specification is currently a candidate recommendation snapshot and can be viewed here: https://www.w3.org/TR/IFT/. The demo shown in the video can be tried out here: https://garretrieger.github.io/ift-demo/
Geotagged Traffic Video Analysis with WebVMT
- by Rob Smith (Away Team) and OGC/Spatio-temporal Data on the Web Working Group
- Description: Demonstration using roadside video footage with GeoPose to analyse traffic using WebVMT in a web browser, including vehicle tracking, data synchronization with video, multi-device data aggregation, wrong-way traffic identification and forensic speed calculation.
Maritime & Aerial Geotagged Video Analysis with WebVMT
- by Rob Smith (Away Team) and OGC/Spatio-temporal Data on the Web Working Group
- Description: Demonstrations using geotagged MISB and smartphone video footage to improve data quality with WebVMT analysis in a web browser, including multi-sensor aggregation, augmented AIS tracking of maritime vessels, camera orientation and enhanced image cognition.)
Media Metadata Interoperability Across Industries
- by Hiroki Endo (NHK), and the Media Content Metadata Japanese CG
- Description: This demo showcases metadata interoperability across publishing, broadcasting, and other media services, using real-world metadata from each sector.

Best Practices for Recording Videos

Plan the content

identify the story
- demos: what problem is being newly solved? what impact can we expect from the proposed solution?
- group updates: what is the group? what impact does it seek to have and is actually having on the Web?
make it accessible - follow the accessibility considerations when planning, scripting, storyboarding well before hitting the record button
plan for a short video - aim for 2 minutes if possible for a demo, 3 minutes for a group update
- think of the demo as a teaser for a deeper technical dive, NOT the deep technical dive itself
- if part of the process being demonstrated is slow or a bit long, plan on showing an abbreviated or accelerated version of the process
write up what you plan to say, keeping acronyms and jargon to a minimum, and explain it when using it
- demos: show and tell - plan on describing orally what is happening in the demo
if you plan on showing code, prepare it so that it can be shown with a large font and clear contrasted colors, and focused on the most relevant code
if you plan on showing slides, see guidance on preparing them
end the script with indications on where to follow up for people interested in more details or in getting involved

Test your setup

ensure your audio setup is clear and crisp
if you plan on video-recording yourself speaking:
- ensure your face will be well-lit, with the camera at eye level
- ensure the background in front of which you'll record yourself is not distracting
- memorize as much of your script as possible, or use a teleprompter to read your script while looking at the camera
- if recording from a mobile device, record in landscape mode

Shooting the video

Speak clearly and slowly. No need to rush.
especially if reading from your script, make sure to keep your tone lively - imagine you're telling an exciting story to a colleague
if you're recording a screen, remove any distracting elements (irrelevant windows and tabs, notifications); if possible, zoom and highlight the most relevant elements
If you're video-recording yourself speaking, leave a few seconds before and after you start speaking in recording mode to allow for editing

Submitting the video

Once you're happy with the resulting video, please share it with mcf@w3.org using one of the on-line systems for sharing large files (e.g. Wormhole, Google Drive, Smash, etc.)
If you read from a script, please share it with us as it will help with captioning as well.
If you screen-recorded slides, please share them as well.