An AR or VR experience succeeds when people can understand it, control it, and leave it comfortably. A striking scene is only part of that work. Designers also decide how much movement is required, which senses carry essential information, and whether a person can use the experience with their preferred controls.
Accessibility should influence the first prototype. It is much easier to offer an alternative to a gesture when the underlying action has been clearly defined than after every interaction depends on that gesture. The following approach applies to educational demonstrations, product visualizations, exhibitions, and other spatial experiences, with implementation details adapted to the chosen platform.
Start with the task and the available choices
Write the experience as a set of outcomes: identify an object, inspect a feature, compare two states, or complete a lesson. Then list the actions currently required to reach each outcome. Look for dependencies on standing, walking, hearing, speaking, precise reaching, or seeing subtle differences. Each dependency is a design question worth testing.
The W3C’s XR Accessibility User Requirements describes a broad range of user needs, including customization, alternative modalities, and navigation. It is a Working Group Note that can inform your design alongside applicable standards and platform guidance. Use the needs to ask concrete questions about your own flow rather than treating a settings menu as proof that the whole experience is accessible.
Make setup useful before immersion begins
Explain what the experience contains and which controls are available before the user enters it. Let people choose a seated configuration, captions, input preferences, and motion options from an accessible starting screen. Keep those choices available later, because someone may discover a preference only after trying the scene.
Give the first task a short, repeatable practice step. A model inspection might begin with “Select the wheel” before introducing rotation and exploded views. Show the result of the action clearly, allow another attempt, and let experienced users skip the practice. Avoid making successful completion of a demanding tutorial the only route to the settings that would make it usable.
Keep movement under the user’s control
Review every camera movement and scene transition. Ask whether it serves the task, whether the user initiated it, and whether a simpler transition would communicate the same change. Avoid surprise movement through the scene. Where virtual travel is required, evaluate options such as teleportation, incremental turning, or an overview from which users choose their destination.
Support the platform’s reduced-motion preference and provide a clear control for optional animation. A rotating product can pause at a useful angle; a moving background can become still. Preserve the information conveyed by a transition through labels or state changes. The VR hologram guide explains how viewpoint and immersion differ from viewing a model on a conventional screen.
Place content where people can use it
Frequent actions should be reachable without repeated overhead movement, extended arm holds, or sustained awkward head positions. Allow important panels and objects to be repositioned or brought into a usable area. A seated mode should adapt the interaction layout, rather than merely moving the virtual camera lower.
Depth placement also deserves testing on the target hardware. Microsoft’s mixed-reality guidance discusses the relationship between apparent depth, display focus, and comfort, with measurements specific to its devices. Use the chosen platform’s guidance instead of applying one distance to every headset. Keep essential reading and controls stable, and test transitions between nearby and distant content with actual users.
Offer alternatives for essential actions
Define actions independently of input devices. “Select this item” can potentially be invoked through a controller, keyboard, switch-compatible interface, voice command, or another supported method. Which alternatives are practical depends on the platform, but the whole route through the experience needs attention: entering, changing settings, performing tasks, and exiting.
Review controls that require two hands, simultaneous button presses, rapid repetition, or precise timing. Offer remapping and adjustable timing where supported. Make a held action available as a toggle when appropriate. For dwell selection, show the pending action and provide a way to cancel it. Test alternative controls through complete tasks so users do not reach a later step that unexpectedly requires the original gesture.
Design text for the viewing conditions
Use readable type, clear spacing, and strong separation from the background. A transparent panel that looks elegant in a studio screenshot may become difficult to read against a busy room. Check text in the actual scene and allow its size or presentation to change. Avoid distributing essential instructions across several distant surfaces.
Keep labels concise and provide longer explanations in a stable reading view. Use words, shapes, or patterns alongside color when identifying states. Let people return to instructions without restarting the task. Test whether increased text size clips controls or covers the object being discussed; enlarging text is useful only when the surrounding layout continues to work.
Make sound and visual events understandable
Provide captions for spoken content and meaningful non-speech sounds. Identify the speaker when necessary and include directional information when location carries meaning. Give people control over caption size and placement, and check whether captions remain readable while an object moves or the user turns.
Review every essential cue that exists only in sound or only in an animation. A successful selection can have a visible state change as well as an audio response. A warning sound needs an understandable visual equivalent. If spatial audio guides someone toward an object, supply another way to find that object. Keep background audio adjustable so it does not compete with instructions or assistive output.
Give spatial objects meaningful descriptions
A rendered object needs more than a mesh and material if assistive technology must identify it. Provide a meaningful name, role, state, and supported actions through the platform’s accessibility mechanisms. A button labeled “Show interior” communicates more than a control named after its internal asset file.
For a complex model, offer an ordered list of significant parts and a text explanation of their relationships. Let users select a named part from that list and receive the same relevant information available visually. For browser-delivered material, an accessible page with descriptions, diagrams, and controls can provide another useful route. See the hologram browser guide for the wider presentation options.
Respect the physical setting
For AR, plan around the environment as well as the screen. Give clear guidance for placing content and make recovery understandable when tracking is unavailable. Avoid arranging essential interactions where users would need to reach through furniture or move toward an obstacle. Follow the device’s setup and boundary guidance.
Offer a way to recenter or relocate content without a complicated search. Explain what the person can do if the scene appears in an unsuitable position. The AR hologram overview covers how virtual content relates to real surroundings. Test in several representative spaces instead of assuming the developer’s room reflects everyone’s environment.
Make pausing, leaving, and returning easy
Keep a clear pause and exit path available throughout the experience. A person should be able to stop without finishing a timed task or waiting for an animation. Save progress where appropriate and explain what will happen when they return. Avoid penalizing people for taking breaks or changing their access settings.
Test interruption deliberately: open the settings halfway through a task, change the input method, pause a narration, and resume. Confirm that focus, captions, selected objects, and instructions return to a coherent state. A reliable return path is part of the experience, particularly in public demonstrations where staff and visitors may interrupt a session.
Test with people and record the limits
Include people with different access needs early enough to change the design. Ask participants to use the configurations that work for them, and make the testing arrangement itself accessible. Combine observation with standards-based review; a successful session with one participant cannot establish that every user need is covered.
Record each issue as a task, starting condition, observed barrier, and proposed change. Retest the affected flow after a fix. Publish clear information about supported controls and known limitations so people can decide how to participate. Comfortable, accessible XR grows from these repeatable decisions: give users choices, preserve the information across those choices, and verify that the complete journey works.
