RE: Understanding the RAUR/XAUR relationship

To Jason

I had a read through and can’t think of anything else in either document that’s not covered by one or the other, but do think it’d be helpful to have a reference to XAUR in RAUR that specifically mentions that if remote meetings are to be held in the XR space, the accessibility aspects highlighted int the XAUR are likely to be relevant and should be considered. I don’t think there’d be a need to cross-reference the other way as XAUR deals with more specific XR elements.

Scott.


[Scott Hollier logo]Dr Scott Hollier
Digital Access Specialist
Mobile: +61 (0)430 351 909
Web: www.hollier.info<http://www.hollier.info/>

Technology for everyone

Keep up with digital access news by following @scotthollier on Twitter<https://twitter.com/scotthollier> and subscribing to Scott’s newsletter<mailto:newsletter@hollier.info?subject=subscribe>.

From: White, Jason J <jjwhite@ets.org>
Sent: Tuesday, 21 July 2020 4:23 AM
To: public-rqtf@w3.org
Subject: Understanding the RAUR/XAUR relationship

The 2020 XR Access Symposium, in which I am participating, has raised anew the prospect of real-time communication and collaboration being implemented as augmented reality applications.

This is a possibility that we have discussed at RQTF meetings in the past. However, if we think that some, at least, real-time communication tools (used for remote meetings and other collaborative activities) are likely to be XR applications, then there is a question of whether there are any issues at the intersection of RTC and XR which haven’t been captured by our documents, but which should be included.

If developers of platforms or applications supporting collaborative XR environments take into account the needs identified in XAUR and in RAUR, is this sufficient? Does anything fall through the cracks?

My purpose here is only to raise the question as a check on our proposed requirements. The answer may well be in the negative (i.e., that we’ve covered the important issues between the two documents). It may also be worth explicitly cross-referencing one document from the other and acknowledging that some real-time communication tools are (perhaps increasingly will be) XR in nature.


________________________________

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.

________________________________