Re: XAUR - User requirements for augmentd and virtual reality - general comments

Hi Jason,

Excellent feedback, some comments inline. There are some substantive 
items below that we can discuss on Weds call and beyond. I've noted them 
inline and I will send some agenda+ items to the list for our call on Weds.

On 26/08/2019 15:50, White, Jason J wrote:
> Here are general (first impression-based) comments on the draft at
> https://www.w3.org/WAI/APA/wiki/Xaur_draft<https://www.w3.org/WAI/APA/wiki/Xaur_drafts>
> offered by way of preparation for the meeting. Thanks are owed to Josh for working on this draft.
>
> There is interesting and informative material in this draft. For purposes of a subsequent draft, I think it could be better organized. [...]
> 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.

I like this approach. It is helpful for the reader to parse both what 
the user requirement is and what they technically need to do with their 
technology x, to meet that requirement. We will need to discuss in more 
detail who is the primary audience for this doc, it could be those 
working in standards for example - so we need to work out if we should 
be focusing on having technical requirements (Describe purpose of input 
x) vs user requirement (a blind user needs to know that x exists and 
what x is so they can do y). Some combination will also be possible.  [1]

There is also a broader question of the nexus with the FAST and we need 
to work out how our XAUR relates to that, as well what may come from 
Silver and the XR space. So we have a lot to discuss and work out, some 
of which we can do leading up to and during TPAC.

I do like the approach of functional performance statements a la EN 301 
549, as they nicely outline what the user's accessibility 
needs/requirements are when trying to perform some task etc and this 
could be very useful in XR. [1]


> ([...]I would suggest placing emphasis on those aspects of XR that make it distinct from typical Web-based user interfaces, including tracking, and the combinations of input and output mechanisms employed.

I like this idea - as this approach may help to dynamically build on 
existing accessibility knowledge that people have, so they can leverage 
that in application to the XR space.


> An actual numbered list of user requirements would be very helpful (R1, R2, …), so that a reader of the document knows what the requirements are. At the moment, they have to be inferred from examples and explanations.

+1


> What I find missing in the current draft is a clear conception and explanation of what features “universally designed” (broadly accessible) XR-based systems should have, and how these relate to user needs.

Right - I'm still working that out *grin.


> There are examples provided, but they don’t yet constitute a unified description of what has to be done if one wants to apply principles of accessible design in creating an XR technology, or developing a new XR-based application.

Yes, we have work to do.


> I would also suggest expanding the “inputs” section to include gesture recognition (using computer vision, not controllers).

+1


> We can probably improve the examples further, but, for the moment, my interest lies in the over-all focus, content and organization of the document.

Great input Jason.

Thanks

Josh

[1] http://mandate376.standards.eu/standard/functional-statements

[2] https://w3c.github.io/apa/fast/


> There are editorial issues that can safely be addressed later.
>
> I hope these comments prove useful, and I look forward to a discussion on Wednesday of different perspectives regarding the draft.
>
>
> ________________________________
>
> 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.
>
> ________________________________

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

Received on Tuesday, 27 August 2019 11:02:34 UTC