WebXR Device API Specification

The WebXR device API is for accessing virtual reality (VR) and augmented reality (AR) devices, including sensors and head-mounted displays on the Web.

The WebXR Device API Specification is the repository of the Immersive Web Working Group.

Taking Part

1. Read the code of conduct
2. See if your issue is being discussed in the issues, or if your idea is being discussed in the proposals repo.
3. We will be publishing the minutes from the bi-weekly calls.
4. You can also join the working group to participate in these discussions.

Specifications

• WebXR Device API Specification: Main specification for JavaScript API for accessing VR and AR devices, including sensors and head-mounted displays.
• Explainer
• Input Explainer
• Privacy & Security Explainer
• Spatial Tracking Explainer

See also list of all specifications with detailed status in Working Group and Community Group.

Related Specifications

• Gamepad API Specification: Introduces a low-level JS API interface for accessing gamepad devices.

Legacy

• Legacy WebVR API Specification: Legacy WebVR API 1.1 specification for JavaScript API for accessing VR displays. Development of the WebVR API has halted in favor of being replaced the WebXR Device API. Several browsers will continue to support this version of the API in the meantime.
• Legacy Gamepad Extensions API Specification: Extends the Gamepad API to enable access to more advanced device capabilities.

Relevant Links

• Immersive Web Community Group
• WebXR Device API Specification
• WebXR on MDN
• Immersive Web Working Group Charter
• WebXR Input Profiles: WebXR Gamepad assets, source library, and schema to enable the correct display of XR input hardware in the virtual scene

Communication

• Immersive Web Working Group
• Immersive Web Community Group
• GitHub issues list: webxr
• public-immersive-web mailing list
• Legacy public-webvr mailing list archive

Maintainers

To generate the spec document (index.html) from the index.bs Bikeshed document:

make

Tests

For normative changes, a corresponding web-platform-tests PR is highly appreciated. Typically, both PRs will be merged at the same time. Note that a test change that contradicts the spec should not be merged before the corresponding spec change. If testing is not practical, please explain why and if appropriate file a web-platform-tests issue to follow up later. Add the type:untestable or type:missing-coverage label as appropriate.

License

Per the LICENSE.md file:

All documents in this Repository are licensed by contributors under the W3C Software and Document License.