How Well Can 3D Accessibility Guidelines Support XR Development? An Interview Study with XR Practitioners in Industry
Daniel Killough, Tiger F. Ji, Kexin Zhang, Yaxin Hu, Yu Huang, Ruofei Du, Yuhang Zhao · 2026 · Proceedings of the 2026 CHI Conference on Human Factors in Computing Systems (CHI '26) · doi:10.1145/3772318.3790520
Summary
This study is the first systematic evaluation of how well existing 3D accessibility (a11y) guidelines transfer to extended reality (XR) development in industry. The authors conducted 25 semi-structured interviews (1.5–3 hours each) with XR practitioners spanning freelancers, startups, midsize companies, and big tech, with 2–9 years of XR development experience across Unity, Unreal, BabylonJS, Glitch, and custom engines. They compiled guidelines from six major resources — the Game Accessibility Guidelines (GAG), W3C XR Accessibility User Requirements (XAUR), Meta Quest Accessible VR Design, Accessible Player Experiences (APX), Xbox Accessibility Guidelines, and IGDA GASIG Top Ten — then selected 20 commonly-agreed guidelines (five each across motor, visual, cognitive, and speech & hearing disability groups). Each participant reviewed guidelines using a seven-step protocol: interpretation, feasibility, technical barriers, adaptations, and external support needs. Transcripts were thematically coded by two researchers with 100% inter-coder reliability on the final codebook. The framing treats guidelines not as compliance checklists but as 'transformation catalysts,' asking whether they are actionable, how practitioners interpret them in immersive contexts, and what additional support (toolkits, plugins, automated checking) would enable efficient a11y integration.
Key findings
Three research questions structured the findings. RQ1 (technical solutions and barriers): 17 of 25 practitioners had no formal XR a11y training, relying on online resources, personal projects, or on-the-job learning; practitioners nonetheless built inventive workarounds such as invisible 2D buttons overlaid on 3D objects to make mobile AR screen-reader-accessible. RQ2 (guideline interpretation): practitioners frequently found existing 3D guidelines ambiguous (especially visual/cognitive/hearing redundancy triads — Vis-1, Cog-2, SH-3), too broad (Cog-5 Hide Distractions), or incompatible with XR realities (Mot-5 Flexible Timing and Cog-4 Adjustable Speed conflicted with real-time training or multiplayer fairness). A three-tier priority emerged: Tier 1 (safety/legal, e.g., Avoid Flicker) — high importance and clarity; Tier 2 (platform-dependent, e.g., Resizable UI, Subtitle Settings) — moderate; Tier 3 (context-specific, e.g., Symbol Chat) — lowest motivation. Using a RACI matrix, designers held primary responsibility for 14 of 20 guidelines, developers for 6 (mostly system-level). RQ3 (needed support): 21 of 25 preferred platform-integrated tools over written guidelines, requesting open-source Unity/Unreal packages, automated a11y checkers, OpenXR-aligned components, XR-native alt-text metadata, and side-by-side accessible/inaccessible code examples.
Relevance
For anyone writing, updating, or implementing XR a11y guidance — W3C, IGDA GASIG, platform vendors (Meta, Microsoft, Apple), or internal engineering-standards teams — this paper is a direct mandate to rewrite 3D-era guidelines with XR-native concerns (spatial tracking, kinesthetic interaction, headset fit, locomotion, AR vs VR interaction differences) and to deliver them as code artefacts rather than prose. The RACI mapping and three-tier prioritisation offer a practical sequencing model for product teams retrofitting a11y into immersive roadmaps. Five concrete recommendations emerge: demonstrate feasibility via concrete XR examples; implement a11y early in design; address XR-specific constraints explicitly; ship platform-integrated plugins/packages under open licences; and frame guidelines as universal benefits rather than PWD-only accommodations. Limitations include a largely male participant pool, recruitment bias toward a11y-motivated practitioners, and the fact that the paper evaluates existing guidelines rather than validating new XR-specific ones — which the authors position as the necessary next step.
Tags: extended reality · virtual reality · augmented reality · XR · game accessibility · developer interviews · accessibility guidelines · practitioner study
Standards referenced: Game Accessibility Guidelines (GAG) · W3C XR Accessibility User Requirements (XAUR) · Meta Quest Accessible VR Design · Accessible Player Experiences (APX) · Xbox Accessibility Guidelines · IGDA GASIG Top Ten · WCAG 2.1