RE: XAUR - User requirements for augmented and virtual reality - general comments

To the RQTF

I've finished having a read through of the XAUR draft and Jason's pretty much covered it. The only thing I'd look to add is to improve how the definitions are introduced. To me it is odd that given we're talking about mixed reality, but the document doesn’t define mixed reality until the third definition. 

In my opinion, I'd recommend having the Purpose of XR section first, and within this section mention that XR includes: VR, then provide the definition, and AR, then provide the definition. Most people I talk to that are involved in the VR and AR research space aren't familiar with XR as an acronym yet so if we're aiming to use XR in the naming of the document, which makes sense, it'd be good to kick off with that as the definition then pull in the VR and AR definitions. 

Otherwise all the feedback I've provided previously is in there so aside from Jason's' excellent comments all good from me - certainly in a good place to seek public comment. 

Scott. 




Dr Scott Hollier 
Digital Access Specialist 
Mobile: +61 (0)430 351 909
Web: www.hollier.info
 
Technology for everyone
 
Australian Access Awards 2019 Call For Nominations – celebrate best practice by nominating your favourite accessible Australian website or app. It’s free!  
 
Keep up with digital access news by following @scotthollier on Twitter and subscribing to Scott’s newsletter. 

-----Original Message-----
From: White, Jason J <jjwhite@ets.org> 
Sent: Wednesday, 28 August 2019 3:22 AM
To: Joshue O Connor <joconnor@w3.org>; public-rqtf@w3.org
Subject: RE: XAUR - User requirements for augmented and virtual reality - general comments

Those generic functional requirements refer to "closed functionality", which is defined here:
http://mandate376.standards.eu/standard/definitions-and-abbreviations

as meaning "functionality that is limited by characteristics that prevent a user from attaching, installing or using assistive technology".

In the absence of assistive technologies that can interoperate with XR-based interfaces, this may indeed be a category to which some XR applications currently belong.

Obviously, we'll need to consider how and to what extent to support "external" assistive technologies in making such XR applications accessible. My central point here is only that the purpose of these generic functional requirements in EN 301 549 appears to be to address cases of "closed functionality" as defined above.

-----Original Message-----
From: Joshue O Connor <joconnor@w3.org>
Sent: Tuesday, August 27, 2019 7:20 AM
To: White, Jason J <jjwhite@ets.org>; public-rqtf@w3.org
Subject: Re: XAUR - User requirements for augmented and virtual reality - general comments

On 26/08/2019 15:50, White, Jason J wrote:

> A possible approach to organization of at least the requirements aspect of the document would be to review the Functional Performance Statements in EN 301 549. (There are somewhat similar, parallel statements in the U.S. section 508/section 255 regulations).

One thing to add is that there are also generic functional accessibility requirements a la EN 301 549 that could be applicable for XR. [1]

So (as far as my understanding goes) functional and performance
(non-functional) requirements are differentiated by 'what needs to be done to make a system work for a user in situation x', vs 'how the system should behave in situation x'. We'll need to discuss these distinctions and see if mirroring this approach is beneficial.

HTH

Josh

[1]
https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmandate376.standards.eu%2Fstandard%2Ftechnical-requirements%3Ffunctional_statements%3D20%26functional_statements_submitted%3Dtrue&amp;data=02%7C01%7Cjjwhite%40ets.org%7C4fbc0cc9d84748ddb4aa08d72ae0885c%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637025016172429949&amp;sdata=QhGIGHXNQPehQYiNZc9UCeE52%2F5Wf70InZge931DGys%3D&amp;reserved=0


--
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 Wednesday, 28 August 2019 02:08:05 UTC