RE: RAUR and XAUR relationship: New note or user need and requirements?

It seems to me that noting the relationship should be sufficient for the moment. However, it would be valuable to consider whether there are user needs related to real-time communication applications that only apply in XR contexts.

One characterization of the relationship would be to note that if the RTC application is also an XR application, then relevant XAUR requirements should be addressed as well. This, for instance, would accommodate immersive caption requirements - assuming that these are ultimately covered by XAUR; and similarly for other XR-specific accessibility issues.

-----Original Message-----
From: Joshue O Connor <joconnor@w3.org>
Sent: Thursday, October 8, 2020 8:30 AM
To: RQTF <public-rqtf@w3.org>
Subject: RAUR and XAUR relationship: New note or user need and requirements?

Hi all,

I'm working on updating the RAUR and a question comes to mind about how to present the nexus between XAUR/RAUR. I've a sense this needs some further discussion/thought.

There are a couple of options from:

1) Add a note about XAUR to the 'Quality of Service' section - there are references there to audio quality etc and I could add something brief about RTC type applications and remote meeting in XR.
2) Create a new user need - XR and RTC - I'm happy to draft one along the lines of.

'DRAFT User Need: A user with disability x needs to attend remote meetings in XR' but then there is a potential for a range of new requirements etc.  So just I'm not sure how far to go with this if we take this option.

Is the first option around just adding a note, with a paragraph sufficient here do we think? I'm inclined to think so for now but would like input. Or do we want to discuss the new user need option?

Thoughts welcome!

Josh
--
Emerging Web Technology Specialist/Accessibility (WAI/W3C)


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________

Received on Thursday, 8 October 2020 12:57:06 UTC