TPAC/2022/Demos and Group updates

From W3C Wiki
< TPAC‎ | 2022

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 website.

For demos specifically, we will also organize a physical show-and-tell session during TPAC week for demo-ers that will be physically attending TPAC.

Timeline

  • July 11, 2022: Indicate your interest to record a group update and/or a demo to mcf@w3.org and dom@w3.org ; include a title, a description, the W3C group behind the relevant technical work, and the contact person responsible for getting the video recorded
  • August 26, 2022: Videos expected to be shared with mcf@w3.org and dom@w3.org
  • Beg of Sept, 2022: Videos uploaded to TPAC 2022 Web site

Proposed Demos

  1. Demonstration of Incremental Font Transfer
  2. A demonstration of math accessibility
    • by Richard Orme (Daisy Consortium)
    • Description: Although many people now understand the importance of making documents accessible, most people haven't seen what math accessibility is like. This video demonstrates math accessibility and also shows some configuration options that can tailor the experience to a user's needs.
  3. Is there a hope to exchange formulae through the clipboard?
    • by Paul Libbrecht (IUBH Internationale Hochschule GmbH)
    • Description: In the effort to define standardised encodings for mathematical formulæ, the Math Working Group has also defined how they should be named on the clipboard of operating systems. However, the W3C group’s definition has failed to reach web-browsers. However, there are hopes: proprietary formats appear to transpire from javascript’s clipboardData.setData() and a different approach is emerging with the clipboard’s pickling with the editing W3C group.
  4. That's now what I mean! Improving accessibility in MathML 4 by allowing authors to communicate their intent
    • by Neil Soiffer (W3C Invited Expert)
    • Description: While MathML has had great success at improving math accessibility, there is no way in MathML 3 to indicate that a superscript might not be a power or that (3,6) is not a point in the plane, but is the open interval from 3 to 6. MathML 4 proposes adding two accessibility-oriented attributes to solve this problem: "intent" and "arg".
  5. MathML-Core
    • by Brian Kardell (Igalia)
    • Description: MathML-Core is a new specification which carefully defines a subset of MathML 3 which is implemented in browsers and describes its platform integration with HTML, CSS, JavaScript and SVG.
  6. WebView CG Update
    • by Qing An (Alibaba Group)
  7. Learn how to integrate WebAuthn with an identity provider by trying out the WebAuthn Starter Kit
    • by Luke Walker and Cody Salas (Yubico)
    • Description: While people have become excited about passkeys, many developers are left unsure of the work needed to bring them into their applications. This demo will provide developers a resource where they can learn what is needed to adopt WebAuthn such as architecture considerations, user flows, and integrations with their identity provider.
  8. FIDO Multi-device Credentials in Action
    • by Christiaan Brand (Google) and Tim Cappalli (Microsoft)
  9. I18n update
    • by Fuqiao (W3C)
    • Description: The W3C Internationalization (i18n) Activity works with W3C working groups and liaises with other organizations to make it possible to use Web technologies around the world, regardless of language, writing system, or culture.

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

See also audio/video recording guidance

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, share it with mcf@w3.org and dom@w3.org using one of the on-line systems for sharing large files (e.g. Dropbox, WeTransfer, Google Drive, 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.