Good Intentions, Real Barriers: Investigating Accessibility in XR Workflows

Creator: Mrunmai Abhyankar, The College of Texas at Austin

Editor Dylan Fox, Director of Operations, XR Entry

Government Abstract

This venture, carried out in collaboration with XR Entry and the Metaverse Requirements Discussion board (MSF), investigates why accessibility in eXtended Actuality (XR) usually breaks down between intention and execution—and what instruments or programs might assist bridge that hole. As XR applied sciences evolve, guaranteeing accessibility requires not simply consciousness, however sensible, embedded assist that matches real-world workflows.

Interviews with XR creators and accessibility specialists revealed a number of core challenges: accessibility is usually launched too late within the course of resulting from deadline stress or lack of possession, whereas current requirements like WCAG are seen as too complicated or web-centric for immersive environments. Groups additionally lack built-in instruments for testing and deciphering accessibility. There’s restricted shared language or construction for speaking accessibility wants throughout disciplines.

In response, I designed a tenet interface prototype (Determine 1) that makes pointers simpler to know, filter, and apply. The interface permits customers to discover categorized steering primarily based on person capacity, platform, or crew position, and presents success standards, sensible examples, and implementation suggestions in a transparent, accessible format. It goals to shift accessibility from a static guidelines to an lively, usable reference for inclusive XR design.

Purpose

To discover how accessibility is at the moment approached in XR design and improvement, establish the obstacles groups face in making use of pointers, and suggest an answer that makes these pointers simpler to search out, interpret, and implement in observe.

Analysis

I carried out 19 semi-structured interviews with a complete of 21 contributors:

• 10 XR creators (X1 – X10) — together with designers, builders, inventive technologists, and product managers working in spatial computing, XR platforms, and immersive content material.
• 11 accessibility specialists (A1 – A11) — together with consultants, researchers, advocates, and testers with deep expertise in incapacity entry, inclusive design, and coverage.

Interviews lasted 45–60 minutes and centered on:

• How accessibility at the moment matches into XR workflows (if in any respect)
• How groups interpret and apply accessibility steering
• What instruments, processes, or roles assist (or hinder) inclusive outcomes
• The place accountability and decision-making round accessibility truly sits

The objective was not simply to gather ache factors, however to know the underlying programs and crew dynamics shaping accessibility efforts in XR. The interview script may be present in Appendix A.

Evaluation

I used a structured approach utilizing a thematic matrix to current insights from stakeholder interviews (see Determine 2). By grouping related responses, it highlights recurring themes throughout contributors and brings consideration to key challenges and alternatives in XR accessibility. This strategy additionally permits for a transparent comparability between the views of XR creators and accessibility specialists. The sticky notes are color-coded to mirror the tone of participant quotes—purple for destructive, inexperienced for constructive, and yellow for impartial or factual statements. This visible system helps rapidly establish emotional cues and patterns throughout themes.

Key themes that emerged from this evaluation embody:

• Approaches to Accessibility – Variations in when and the way accessibility is built-in into XR improvement.
• Challenges Confronted – Technical, organizational, and information obstacles limiting accessibility implementation.
• Present Pointers – The position of present accessibility requirements, their limitations, and their applicability to XR.
• Perceived Want for XR Accessibility Pointers – The demand for structured sources, toolkits, and platform-level options.

Excessive v/s Low Precedence Approaches to Accessibility

Contributors confirmed a transparent divide in when accessibility is prioritized. Some groups incorporate it early within the design course of, treating it as foundational.

“You actually wish to take into consideration accessibility earlier than you begin design as a result of accessibility is just about unattainable to retrofit.” – X9

“I believe accessibility is just not one thing that you may incorporate in direction of the top. It’s one thing you begin working with from the very starting.” – X3

Others, nonetheless, strategy accessibility reactively—solely addressing it post-launch resulting from consumer calls for, restricted sources, or lack of understanding.

“Lots of that kind of stuff will get deprioritized as a result of, you already know, we are able to barely make the factor as is, not to mention add the accessibility, hitting the deadline.” – X7

XR creators specifically admitted to deprioritizing accessibility below deadline stress or resulting from inadequate information, whereas accessibility specialists expressed frustration with this strategy.

“It’s not that they’re not doing it as a result of they don’t like disabled folks. It’s that they simply didn’t give it some thought.” – X9

Just a few contributors reported constantly integrating accessibility from the start.

“Somebody needs to be [responsible for accessibility].” – X7

---

Perception: Many groups deal with accessibility as an afterthought resulting from deadlines, useful resource constraints, or lack of understanding.

---

Systematic Lack of Technical and Organizational Assist

Groups face each technical and organizational obstacles when making an attempt to implement accessibility. Many lack devoted accessibility roles, making possession unclear.

“The roles and obligations usually are not clarified relating to accessibility between, like, all of the completely different roles.” – A2

“We don’t essentially have a devoted accessibility engineer… we combine it into the traditional engineering course of.” – X6

Instruments and engines usually don’t assist accessible design out of the field, and cross-platform conflicts additional complicate implementation. Some options had been added by chance slightly than intention, pointing to an absence of systematic processes. Testing with customers is restricted for many contributors, and standards for cognitive accessibility stay particularly unclear, as famous by a number of accessibility specialists.

---

Perception: Lack of possession and tooling results in fragmented and inconsistent accessibility efforts.

---

Want for Clear and Sensible XR Pointers

Contributors broadly agreed that current pointers like WCAG (Net Content material Accessibility Pointers) are too complicated and web-centric to use cleanly to XR.

“WCAG is simply so obtuse to attempt to learn, it’s a must to actually perceive accessibility to even interpret it.” – A7

Whereas some groups try to make use of WCAG, many want inside, casual requirements primarily based on WCAG however are simpler to behave on. There’s a common understanding that pointers are essential, however their present kind is usually overwhelming or impractical.

“We’ll most likely want one thing like how WCAG works for conventional web sites.” – X2

“Unreal and Unity have accessibility pointers… however nothing that pulls every thing collectively.” – A1

A number of famous that necessities usually overlap or really feel ambiguous in XR contexts. Testing was emphasised even when formal requirements weren’t adopted carefully.

“There must be testing. There’s no substitute.” – X7

---

Perception: Groups want easier, XR-specific pointers which might be actionable and never web-centric.

---

Urge for food for Constructed-in Testing and System-Degree Instruments

There’s sturdy demand for XR-specific accessibility sources which might be simpler to make use of, extra visible, and context-aware. Contributors requested interactive guides, code examples, and toolkits tailor-made to their improvement environments.

“Having a extra standardized approach of labeling issues for non-developers could be actually useful.” – A4

Some recommended TLDRs or cheat sheets to decrease the barrier to understanding. A number of emphasised that pointers needs to be constructed into platforms and instruments, not left as exterior references.

“I believe placing extra give attention to platform-level or native-level accessibility is required” – X6

A common, agreed-upon customary was seen as ideally suited however tough to attain. Many contributors emphasised that accessibility challenges transcend simply instruments and requirements—it’s a multifaceted subject with no closing repair.

“Accessibility won’t ever be a ‘solved drawback’.” – A9

---

Perception: There’s sturdy demand for native, easy-to-use accessibility instruments inside XR platforms. 

---

Evaluation Abstract

Tensions between XR creators and accessibility specialists usually stemmed from differing expectations—creators favored built-in instruments and ready-made options that might assist them clear up accessibility challenges swiftly, whereas accessibility specialists wished clear, testable standards that might make it simpler to judge and audit XR experiences.

Each teams agreed that present instruments are missing, pointers are inadequate, and that testing with actual customers is important. There was a shared recognition that accessibility must be higher communicated and embedded throughout workflows. Enterprise priorities and tight timelines regularly push accessibility to the background. Total, contributors supported having clearer obligations, extra intuitive sources, and built-in infrastructure assist.

Pointers Interface Prototype

Objective & Context

The rules prototype was designed to assist designers, builders, and testers discover XR accessibility pointers extra simply. It addresses key challenges surfaced in stakeholder interviews, together with the shortage of a central useful resource, confusion round obligations, and the complexity of current requirements like WCAG.

Design References & Benchmarks

As a part of the early analysis and benchmarking course of, I seemed carefully at current accessibility sources to know how steering is at the moment structured and delivered. The Net Content material Accessibility Pointers (WCAG) supplied a complete however usually overwhelming mannequin. Its sidebar-based construction (Determine 3) was useful for organizing massive volumes of data, however its technical depth and web-specific framing made it tough to translate into XR contexts.

The Sport Accessibility Pointers (GAG), in distinction, undertake a extra approachable tone, presenting suggestions as clear, actionable statements (Determine 4). Whereas GAG loosely categorizes pointers by capacity (e.g., visible, motor, cognitive), it lacks a structured method to search or filter by way of them, which limits discoverability when utilized in sensible contexts. This lack of navigability echoed suggestions from contributors, a number of of whom described the present state of accessibility steering as “scattered” or “onerous to interpret in context.”

References to sources for current platforms like Unity’s accessibility package and Meta’s accessibility principles had been additionally reviewed, however fragmented constructions and lack of detailed sources in these sources validated the necessity for one thing extra cohesive and informative.

Interface Prototype

To deal with the gaps surfaced by way of interviews and benchmarking, I designed a pointers interface prototype that reframes pointers in a extra structured, approachable, and role-aware format. The objective was to make accessibility steering simpler to search out, perceive, and apply inside actual XR improvement workflows.

Construction & Categorization

The interface affords two main methods of navigating pointers:

• By Precept – Grouped in line with levels or features inside an XR expertise (e.g., Setup, Perceive, Navigate).
• By Capability – Grouped by incapacity classes reminiscent of Imaginative and prescient, Listening to, Motor, Cognitive, and Cross-modal.

Pointers had been deliberately allowed to seem in a number of teams to assist versatile discovery. Further filters embody Function (e.g., designer, developer, tester) and Platform, acknowledging gaps in accountability consciousness and platform-specific implementation points raised throughout interviews.

Navigation & Interplay

Customers can toggle between Capability and Precept tabs, which restructure the record of pointers accordingly. They will additionally use the common search bar to search out pointers by key phrase. Filters are positioned above the content material space, making them contextually seen and instantly related to the rule record. Clicking a tenet opens an in depth view, with title, description, success standards, accessibility relevance, and examples.

A future-facing function features a chat-based AI assistant, envisioned to assist customers ask questions and interpret pointers extra simply—particularly when not sure the way to apply them.

Design Iteration

The preliminary format adopted a three-panel grid with filters on the left, a listing of pointers within the middle, and detailed content material on the fitting (see Determine 5). Nonetheless, throughout casual critiques and walkthroughs, it turned clear that the location of filters in a aspect panel made it much less apparent that they had been instantly related to the record of pointers. Customers didn’t intuitively affiliate the filters with the content material they had been viewing, which affected usability and discoverability.

To deal with this, the format was restructured with filters positioned above the rule record, making their perform extra contextually seen and clearly tied to the content material. Tabs had been additionally launched to modify between categorization varieties (by Capability and by Precept), conserving the interplay easy and decreasing visible muddle.

The ultimate prototype (Determine 6) presents a cleaner, wiki-style interface that permits XR creators to browse, filter, and perceive accessibility pointers extra successfully. A devoted part “The way it helps completely different disabilities” was included to assist creators perceive the influence of every guideline, encouraging extra empathetic and knowledgeable decision-making.

Identified Limitations

• Some customers might wish to choose a number of talents, which factors to Capability doubtlessly being higher as a filter than a categorization.
• Edge case dealing with (e.g., filtering out a at the moment seen guideline) wants additional definition.
• The prototype has not been person examined, and suggestions from precise customers is important earlier than making selections about implementation.

Subsequent Steps

This analysis uncovered clear gaps in how accessibility pointers are understood, accessed, and carried out in XR workflows. The rules interface prototype is a foundational step towards making a extra usable, structured, and role-aware guideline system — however extra layers of exploration are wanted.

Shifting ahead, we might:

• Validate the IA and prototype by way of person testing with XR creators and accessibility specialists to make sure real-world relevance.
• Discover improvement of a shared guidelines or reporting device, enabling groups to trace, assign, and doc accessibility concerns collaboratively.
• Refine how pointers are introduced, doubtlessly shifting from static content material to extra interactive codecs (e.g., customizable views, resolution bushes, AI-supported interpretation).
•  Construct a platform-level technique for the way pointers, infrastructure, and tooling may be higher aligned — transferring from reactive documentation to embedded assist.
• Have a devoted examples part to assist creators discover particular examples of what has been accomplished earlier than and the way they will strategy a specific accessibility subject.
• Proceed shaping a unified, XR-specific customary, knowledgeable by lived practitioner experiences, that balances technical depth with sensible usability.

This work opens a pathway not only for organizing accessibility pointers extra successfully, however for serving to groups interpret and apply them with better readability and confidence. Because the MSF continues its work on growing standardized accessibility pointers for XR, this analysis affords useful perception into how completely different stakeholder teams navigate, perceive, and act on accessibility steering. The prototype supplies a basis for structuring and presenting pointers in methods which might be actionable throughout roles.

Conclusion

This analysis highlights the real-world hole between the intent to construct accessible XR experiences and the obstacles that make it tough in observe. Whereas many XR creators worth inclusion, challenges like unclear pointers, time constraints, and restricted collaboration with accessibility specialists usually get in the way in which.

The prototype developed as a part of this work affords a place to begin to handle a few of these gaps. By organizing current pointers in a clearer, extra navigable format and explicitly highlighting the roles and obligations, it helps creators in making accessibility selections earlier and extra confidently of their workflows. Whereas nonetheless exploratory, it lays the groundwork for future iterations and conversations, appearing as each a baseline and a provocation for rethinking how accessibility steering is delivered and utilized in XR. There’s nonetheless a lot to be accomplished however constructing shared understanding and instruments like these will help push the trade towards extra inclusive and sustainable design practices.

Appendix A: Interview Script

Interview Script: Understanding the present state of accessibility in XR

Stakeholders: XR Creators & A11y testers

Greetings and introduction

Hello <Participant title>, How are you doing as we speak?

Thanks for taking the time to speak to us as we speak!

My title is Mrunmai and I’m a UX researcher at XR Entry. My crew is working with the Accessibility Working Group of the Metaverse Requirements Discussion board on a venture to enhance accessibility in XR (digital and augmented actuality) and would like to be taught in regards to the challenges you face when creating or testing XR experiences or in any other case evaluating for accessibility. Your insights will assist make XR extra inclusive for all customers.

Please share your trustworthy ideas as we go alongside. Do keep in mind, there are not any proper or incorrect solutions!

Do you will have any questions for me earlier than we get began?

Earlier than we start, might I simply affirm that you just’re nonetheless okay with this session being recorded? [Wait for reply]

Superior! I’ll begin the recording now.

Thanks!

Questions

XR Creators

1. Are you able to inform me just a little about your background and expertise in XR?
2. What are the varieties of XR purposes you will have labored on? (e.g., VR, AR, MR, gaming, coaching, simulations)
3. What software program or instruments do you employ to design or develop XR experiences?
4. When designing XR experiences, what are the important thing components you prioritize?
5. At what stage within the improvement course of do you contemplate accessibility?
   1. [For Sr Devs] Has that modified over time?
6. When designing/growing XR experiences, have you ever ever wanted to think about accessibility? Was there any incident which prompted that?
   1. Which disabilities have you ever thought-about in your designs?
   2. How do you guarantee customers of various talents can work together together with your purposes?
7. Who in your group is answerable for accessibility? OR Who determines the precedence of accessibility-related duties, and who’s answerable for approving accessibility adjustments?
8. Do you will have any inside accessibility pointers or greatest practices particular to XR?
9. Are there any folks with seen disabilities in your crew/in your group? OR Have you ever ever labored with customers with disabilities when designing an XR expertise? What was that course of like?
10. Have you ever ever needed to adapt an current XR expertise to make it extra accessible? In that case, how did you strategy it?
11. Are you able to share a time when making an XR expertise accessible was difficult? OR Are there particular technical or design limitations that make accessibility more durable to implement in XR?
12. Are there accessibility necessities from purchasers, stakeholders, or laws that it’s a must to meet?
13. Are there any accessibility-related design patterns or frameworks you comply with?
    1. Have you ever used any current accessibility pointers when designing XR experiences? How useful or difficult was it?
14. Have you ever discovered these pointers useful, or do they current any challenges in sensible implementation?
15. What would make accessibility simpler to combine into your workflow?
16. How do you usually find out about new greatest practices or trade requirements in XR improvement?
17. Is accessibility additionally part of your QA checks?

Accessibility Testers

1. Are you able to inform me about your expertise with accessibility testing?
2. Have you ever examined XR purposes for accessibility? If sure, which varieties? (e.g., VR, AR, MR)
   1. What software program and {hardware} do you employ for accessibility testing in XR?
   2. Are you able to describe a latest expertise testing an XR product?
      1. How did you establish whether it is accessible?
      2. Do you comply with any particular accessibility testing pointers for XR? If sure, which of them?
      3. What are among the commonest accessibility points you’ve recognized in XR purposes?
      4. Have you ever come throughout any accessibility options in XR that had been well-executed?
      5. How do you usually doc or report accessibility points in XR?
      6. Are there any particular disabilities that XR purposes usually fail to accommodate?
3. What pointers do you apply relating to accessibility moreover WCAG?
   1. What would make your job as an accessibility tester simpler when evaluating interfaces and experiences past WCAG?
4. Do you employ any particular guidelines instruments for various interfaces (eg: internet, cell, XR, and so forth)?
   1. Are there any options you actually like about these instruments?
      1. Is there any device/function that you just discover tough to make use of?
5. What do you do when current accessibility pointers don’t instantly apply to the appliance you’re testing?
6. Is accessibility additionally part of your QA checks?
7. In case you might change one factor about the way in which accessibility is dealt with as we speak, what wouldn’t it be?

Closing/Thanks

These are all my questions for as we speak!

Thanks a lot for taking part on this screening session. Your opinions and ideas are essential and can assist us enhance the accessibility in XR interfaces.

Ask in the event that they wish to be a part of mailing record:

https://docs.google.com/forms/d/e/1FAIpQLSdZxYGXzfZumj_1xRu0J1V7gG3PLmCDj2GC8pB8SMAQB9rDRA/viewform

Is there the rest you’d like so as to add or any questions you will have for us at this level?

Superior! Thanks once more on your participation and sharing your opinions. Have an important day!

Appendix B: Full Quotes and Insights

Strategy to Accessibility

Participant	Sentiment	Perception
X2	Destructive	Business initiatives: ‘I believe it actually kicks in within the later levels.’
X2	Constructive	Analysis initiatives have extra liberty and feasibility to accommodate accessibility in XR
X5	Impartial	Extremely depending on consumer requirement – doesn’t proactively implement any accessibility options or comply with any pointers
X9	Impartial	As a marketing consultant, purchasers usually are not tremendous receptive of the suggestions on accessibility and search for fast fixes and enhancements
X4	Destructive	Know your viewers and cater the answer accordingly: Consumer Centric however not accessibility oriented
X8	Destructive	Focus extra on MVP then iterate to make it extra snug and accessible
X8	Destructive	‘I believe Business initiatives usually are not at all times making the choice to spend money and time for accessibility.’
X3	Constructive	The definition of accessibility adjustments when in context of XR
X8	Impartial	Created person persona after alpha launch and integrated accessibility in line with the persona
X9	Constructive	‘You actually wish to take into consideration accessibility earlier than you begin design as a result of accessibility is just about unattainable to retrofit’
X10	Constructive	‘I believe that accessibility is for everybody’
X4	Destructive	‘I’m extra centered on being a developer than a designer. In order that wasn’t my first go to factor at all times’
X5	Destructive	‘I’m a tech particular person. A healthcare particular person is required when designing within the healthcare area’
X6	Constructive	Don’t have a devoted accessibility engineer however included accessibility in any respect steps
X6	Constructive	In a11y first orgs: Accessibility is taken into account fairly early within the course of – embedded within the design section
X8	Destructive	‘But when we don’t have these sorts of wants, our person suggestions is just not asking for any of these options. We’d not do this.’
X5	Destructive	Regardless of the consumer being into healthcare, no person labored on the accessibility facet
X3, X7	Constructive	‘I believe accessibility is just not one thing that you may incorporate in direction of the top. It’s one thing you begin working with from the very starting.’
X9	Destructive	‘It’s not that they’re not doing it as a result of they don’t like disabled folks, proper? It’s that they simply didn’t give it some thought.’
A1	Constructive	Contemplating a number of disabilities and having various controls
A1	Constructive	If a studio has a devoted accessibility crew/ persons are passionate => good accessibility options
A9	Constructive	Accessibility pointers are extra about participant expertise and their consolation and value
A6	Destructive	‘Lots of the time one thing’s accessible however nonetheless won’t be usable’
A1	Constructive	Different concerns embody environmental components like motion of textual content, acceleration of objects/surroundings
A2	Constructive	The strategy was extra ‘how will we do that’ than ‘we don’t wish to do that’
A1	Constructive	‘I believe there’s a false impression on the market that VR simply is totally unusable for those who can’t see, and it’s not essentially the case.’
A4	Constructive	Data structure performed a significant position in revamping the web site’s design to make it extra accessible
A9	Constructive	‘If it’s not accessible, it’s a bug’
A4	Constructive	Focuses extra on shapes and symbols over colour to convey sure issues like avoiding purple for destructive and inexperienced for constructive

Challenges Confronted

Participant	Sentiment	Perception
X8	Destructive	Present prototyping instruments for XR lack customization wrt accessibility
X1	Destructive	Technical difficulties like file measurement for audio assist
X7	Constructive	Accessibility points generally get addressed unknowingly
X4	Impartial	Contemplate UX however don’t contemplate accessibility explicitly
X1	Destructive	Much less curiosity from XR Dev groups labored with or a devoted crew
X4	Impartial	Haven’t had anybody within the org answerable for a11y – labored with purchasers and their necessities
X4, X5	Impartial	Made a couple of options/adjustments to make the expertise accessible unintentionally
X1	Destructive	Lack of understanding/knowledge about customers – tough to give attention to any incapacity
X8	Impartial	Conflicting pointers like Meta and Apple may be tough to resolve for cross-platform appropriate experiences
X6	Impartial	Including an accessibility function in a extra user-intuitive approach
X7	Constructive	Necessary to know the way to have conversations about accessibility options and necessities
X1, X3	Destructive	Tough to pitch accessibility options/adjustments in business purposes
A9	Destructive	There are some present options that aren’t essentially the definitive options
A2	Impartial	‘The roles and obligations usually are not clarified relating to accessibilities between, like, all of the completely different roles’
A8	Destructive	Lots of conversations and backwards and forwards with design and dev groups to repair points primarily based on the testing carried out
A3	Destructive	Figuring out success standards for cognitive disabilities is difficult
A5	Destructive	‘I actually don’t know who to speak with on it (accessibility points)’
A4	Impartial	Tough to accommodate a lot of completely different stakeholders with completely different necessities
A8	Destructive	‘How the webpage goes to look for those who use enlarged texts – usually ignored’
A9	Destructive	Hand monitoring allows pure interplay with out having to carry a controller, however comes with necessities for e.g. gestures
A9	Constructive	Sport will ship someway – wish to get as a lot into it to let folks play as potential

Pointers and Requirements

Participant	Sentiment	Perception
X1	Impartial	Did have a couple of concerns whereas designing for sure disabilities – However not conscious of accessibility compliance and current pointers
X2	Impartial	Present requirements & pointers: Targeted on conventional interfaces and don’t actually apply to XR
X1, X3	Destructive	Didn’t use any particular pointers – Brainstormed potential points with the crew
X6	Impartial	Don’t have any particular inside pointers – making issues accessible and intuitive testing inside the crew
X6	Constructive	‘It’s normally a variety of inside and play testing that basically sort of form what that’s however a minimum of at the moment we don’t essentially have like a selected set of requirements for every thing we do’
X7	Impartial	Additionally used online game accessibility pointers – don’t really feel as official
X4	Destructive	Have referred to Oculus pointers – however after completion of the event
X9	Impartial	Didn’t actually confer with every other pointers and referred to the interior doc created because it felt enough
X7	Constructive	‘There must be testing. There’s no substitute.’
X8	Destructive	Have referred to Meta’s XR Design pointers in addition to Apple’s pointers
X9	Impartial	Used spreadsheets to doc points and prioritize into buckets
X9	Constructive	Personal set of pointers – XR interplay model information that features common greatest practices
X2	Constructive	Tried to reference WCAG to satisfy minimal font sizing necessities
X7	Constructive	Have tried skimming by way of different pointers like WCAG however they appear extra web-oriented and don’t at all times apply to XR
X6	Constructive	Discuss with WCAG when in search of extra “fleshed out” pointers
A1	Constructive	A number of codecs of reporting together with full reviews, slide decks or conversational walkthrough
A2, A8	Constructive	Use venture administration device to log accessibility points
A5	Constructive	Doc suggestions within the type of notes/observations
A2, A5, A7	Constructive	Have inside set of pointers
A1, A3	Constructive	Additionally use consumer inside pointers if any for evaluating accessibility
A9	Constructive	Have inside information documented utilizing a number of sources like GAG, W3C, APX, and so forth
A1	Impartial	‘No quantity of analysis will ever substitute testing with gamers with disabilities’
A1	Constructive	Have inside pointers/ design patterns referred to as APX – work along side pointers
A6	Constructive	Inside ranking system (Google Accessibility Ranking)
A9	Constructive	Use imaginative and prescient simulation instruments and in addition take a look at for spoken audio and auditory processing points
A1, A9	Constructive	Issues fall below a number of pointers and design patterns usually overlap
A3	Destructive	Referring to WCAG or different pointers may very well be tough for novices/layman to know
A9	Constructive	‘I like the thought of WCAG pointers classes over GAG’
A9	Impartial	Not a variety of requirements about VR-specific accessibility proper now
A7	Destructive	WCAG may be very complicated
A8	Destructive	Generally it’s obscure the WCAG success criterion and tough to satisfy it due to person system settings that may result in the web site or app failing WCAG compliance
A5	Constructive	Have seen a high-level similarity between pointers for internet/cell and XR interfaces

Perceived Want for XR-specific Accessibility Pointers

Participant	Sentiment	Perception
X3	Impartial	Toolkit – one thing like a plugin that may assist implement/maintain a11y
X3	Constructive	A properly documented useful resource on non-2D platform – An interactive VR primarily based strategy to know and take a look at the rules
X7	Constructive	Want for actual pointers that will be easy to interpret and use
X1	Constructive	Can be useful but additionally might change with context
X3	Impartial	Design system – Choose property on the go, catering to the XR a11y
X8	Constructive	Customizable XR interplay toolkit
X2	Constructive	Useful to have standardized instruments/packages in line with pointers
X2	Constructive	Would like to have a11y plugins
X2	Constructive	Simpler to make the code extra accessible utilizing AI instruments
X2	Constructive	Examples of a11y points in code for XR experiences and the way to repair – like WCAG
X6	Constructive	Focus extra on platform stage or native accessibility that purposes might extra depend on
X9	Constructive	Accessibility needs to be constructed into the toolkit/infrastructure
X2	Destructive	Customization results in ambiguity by way of placing every thing in the identical basket
A9	Constructive	Hitting the minimal stage of necessities/standardization/measurements could be helpful
A3	Constructive	‘I undoubtedly assume it will be simpler, you already know, if there was simply sort of one common set of standards that everybody was in settlement on’
A7	Constructive	Use personal code examples in inside pointers for higher understanding of pointers
A1	Impartial	‘Unreal and Unity have accessibility pointers and templates and so forth and so forth that you may sort of learn by way of, however nothing that pulls every thing collectively’
A1	Impartial	Having a holistic set of pointers might assist understanding the issue
A9	Constructive	Having a cheat sheet / extra approachable could be useful
A3	Destructive	Having good examples in documentation is admittedly essential
A9	Constructive	‘There needs to be a TLDR’
A5	Constructive	Interactive tutorials/information together with a11y options for customers to know and adapt
A4	Constructive	‘Having a extra standardized approach of labeling issues for non builders could be actually useful’
A4	Constructive	Useful to incorporate an alt textual content within the metadata of photographs and movies – will make it simpler for builders and designers