Start with the business task
Imagine a product demonstration that lets a buyer explore equipment in an immersive scene. The useful outcome is understanding the equipment and deciding what to do next. Our suggested brief makes that outcome available through an ordinary web page too: labelled views, specifications, a comparison and a clear enquiry route. Agree which information and actions must remain available without a headset before building the scene.
Offer immersion when the environment supports it
The W3C WebXR Device API draft describes checking whether the desired session mode is supported, then offering an entry control and waiting for the user to activate it. Its support check is advisory: a positive result does not guarantee that a session will start. Our recommended flow handles a failed request with a clear explanation and keeps the standard demonstration available, preserving the selected product. W3C: WebXR Device API — application flow and session support.
Provide choices for content and controls
The W3C XR Accessibility User Requirements note discusses alternatives to motion-dependent interaction, text for important audio, customizable captions and clear start and stop controls. It is a research and requirements note, rather than a conformance checklist. Use it to inform discovery with intended users. Our proposed demonstration also provides keyboard-operable page controls, written explanations of significant visual details and a way to leave immersion without losing the task. W3C: XR Accessibility User Requirements — Working Group Note.
Test complete journeys in both modes
Write acceptance checks around a buyer journey: choose a configuration, inspect relevant details and request further information. Run it through the standard page and the immersive option. Include unavailable equipment, a rejected session request, interrupted viewing and a return to the page. Test the immersive experience on actual target hardware and involve users with relevant access needs. Record gaps and assign an owner before inviting a wider audience.
Measure understanding and completion
For a pilot, agree what evidence would justify further investment. Our suggested measures include successful task completion, unresolved questions, support requests and whether people can find the next step in either mode. Collect only the information needed for that review. A long session does not establish understanding. Use participant feedback alongside observed outcomes, and keep the standard page maintained as product information changes.