Edition

Edition 1: Doors, depth and the first frame

Published · 10 stories

Welcome to the first edition. This week we keep returning to thresholds: the moment a page becomes a place, the first frame a headset draws, and the door a keyboard user needs to find. Stories, sources and people in this sample edition are fictional.

  1. Lead Immersive WebAccessibility

    The doorway problem: why immersive sites need thresholds

    An essay arguing that immersive pages should announce themselves before they envelop you: a visible threshold, a clear way out, and a moment to choose how to enter. The author collects examples from galleries, games and documentation sites.

    Mesh & MeaningSaskia Oyelaran-Pike

    Original article at Mesh & Meaning
  2. AccessibilityWebXR

    Keyboard-only navigation for a WebXR gallery, built and tested

    A detailed build log for an imaginary gallery that can be explored entirely with a keyboard in its inline mode, including focus order between artworks and a spoken room description.

    Accessible HorizonsPriya Lindqvist-Ode

    Original article at Accessible Horizons
  3. 3D on the Web

    A field guide to glTF compression: Draco, meshopt and when to skip both

    A practical comparison of geometry compression options for web scenes, with decode-time measurements on low-end phones and a short decision table for when uncompressed meshes are simply faster.

    Polygon LedgerNoor Halvorsen

    Original article at Polygon Ledger
  4. Research & StandardsAccessibility

    Measuring cybersickness in the browser with a five-minute protocol

    Researchers propose a short, self-administered comfort questionnaire that runs inside a WebXR session, so teams can collect comparable comfort data without a lab.

    Open Immersive ReviewDr. Lucía Brandt-Okafor

    Original article at Open Immersive Review
  5. Research & StandardsImmersive Web

    How long until a page feels present? Time-to-immersion as a metric

    A lab note proposing a page-level metric that measures from navigation to the first stable, head-tracked frame, and arguing it should sit beside the familiar web performance metrics.

    Kestrel Lab NotesDr. Aurelio Kim-Sato

    Original article at Kestrel Lab Notes
  6. Accessibility

    Subtitles, sign language avatars and the limits of automation

    Deaf practitioners interviewed for this piece welcome better captions in immersive media but warn that automated signing avatars are not a substitute for human interpreters.

    Accessible HorizonsTeodor Achebe-Lind

    Original article at Accessible Horizons
  7. Research & StandardsWebXR

    Input profiles registry adds twelve controllers and a deprecation policy

    The registry that maps controllers to models and button layouts gains new entries and, for the first time, a written policy for retiring profiles of discontinued hardware.

    Standards Watch QuarterlyStandards Watch staff

    Original article at Standards Watch Quarterly
  8. WebXRImmersive Web

    Inside a weekend game jam where every entry had to run in a browser headset

    Forty teams, one rule: ship a link, not an app. The report follows three teams through two sleepless nights and the hardware lending table that made it possible.

    The Spatial DispatchMateo Ferreira-Holm

    Original article at The Spatial Dispatch
  9. 3D on the Web

    Depth of field without the blur tax: a WebGPU post-processing recipe

    A compute-shader approach to depth of field that keeps the effect under two milliseconds on integrated graphics, with the full shader and a fallback for older devices.

    Polygon LedgerRafael Domingo-Ishii

    Original article at Polygon Ledger
  10. 3D on the Web

    Lumen Engine 4.1: progressive scene loading and a smaller runtime

    The engine release splits its runtime into optional modules and streams scenes in priority order, so the first interactive frame arrives before every texture has loaded.

    Lumen Engine BlogLumen Engine team

    Original article at Lumen Engine Blog