Fullscreen, audio & accessibility

3dCMS scenes aim to be welcoming out of the box, without you configuring anything.

• Fullscreen: a one-tap toggle for an immersive, chrome-free view.
• Audio on the visitor's terms: spatial sound has a clear mute button, and a muted visit loads no audio at all. Browsers require a tap before any sound plays, which is handled gracefully.
• Reduced motion: visitors who prefer less motion get a calmer experience. Camera flights land instantly instead of gliding, animated objects hold still at their resting pose, and particle emitters freeze their cloud in place rather than drifting. Navigation keeps working exactly the same.
• Moving without a mouse: W A S D pan the camera on every published scene, so a visitor who cannot use a pointing device can still move through the space. The ← → keys are left to page-stepping, which is what they do on a multi-page scene, so neither control means two different things depending on the scene.
• Keyboard & screen-reader friendly: the menus and search follow standard accessibility patterns. A page change announces the page's name ("Page 2 of 5: The Workshop"), not just its number, so a screen-reader visitor is told where they have arrived rather than how far along they are. A scene with video screens in it puts a real Play / Pause button for each one in the Menu, named after the screen, so a video isn't only reachable by clicking a shape in 3D space. A source that won't play says "video unavailable" and disables its button rather than sitting there looking clickable.
• Resilient loading: every published scene is normalized as it loads, so even a hand-edited or corrupted file can't wedge the viewer. An offline banner appears if the network drops, and a flaky load retries when the connection returns.
• When 3D isn't available: a visitor who can't see the scene gets a plain card and a link to the text version of the same page, never a blank rectangle. There are three cases and they read differently, because only one of them is worth retrying. WebGL turned off or blocked (a locked-down work laptop, a hardened privacy browser) says so. The renderer couldn't start, on a device without WebGL 2 or already out of graphics memory, says that and offers no reload button, because reloading fails the same way every time. The view was dropped mid-visit to reclaim memory, usually after the tab sat in the background, is the one that offers Reload: the scene comes back in a lighter version that asks less of the device, and the card says so before the visitor presses it.