Re: XAUR and COGA input branch for review

Good point Jason - how about:

"User Need 13: A screen magnification user or user with a cognitive and 
learning disability or spatial orientation impairment needs to maintain 
focus and understand where they are in immersive environments."

Is that a better statement of need?

Thanks

Josh

> White, Jason J <mailto:jjwhite@ets.org>
> Tuesday 29 June 2021 16:32
>
> Thank you, Josh, for working on this branch. It’s a substantial move 
> in the directions discussed at recent Task Force meetings.
>
> My main suggestion would be to consider the text of the proposed user 
> needs (e.g., User Need 13), which in some cases are more of a problem 
> statement describing what users can have difficulties with, rather 
> than a statement of what their needs are. I think a slight rewording 
> would help to clarify the needs more effectively
>
> For example, in User Need 13,. The actual need is for support in the 
> user interface to enable users to avoid losing focus or becoming 
> disoriented. The need is for something in the application to avoid or 
> prevent the disorientation/loss of focus, which can then be satisfied 
> by implementing one or more of the requirements listed under User Need 13.
>
> Regards,
>
> Jason.
>
> *From: *Joshue O'Connor <joconnor@w3.org>
> *Date: *Tuesday, June 29, 2021 at 10:52
> *To: *RQTF <public-rqtf@w3.org>
> *Cc: *White, Jason J <jjwhite@ets.org>, Scott Hollier <scott@hollier.info>
> *Subject: *XAUR and COGA input branch for review
>
> Hi all,
>
> Just a heads up that I have minted a new branch for us to review 
> tomorrow on our call.
>
> Please have a look beforehand if possible. The main parts to note are:
>
> Relating to #180 - Wayfinding
>
> I've changed the name of two categories to 'Orientation and 
> navigation' as well as 'Spatial orientation: Mono audio option' - and 
> edited User Need 13 to include people with spatial orientation 
> impairments. I like this as it broadens the net for the basic user 
> need. Most of the wording for the user need is from David Fazio, as he 
> clearly articulates it.
>
> https://raw.githack.com/w3c/apa/COGA-XR-input/xaur/index.html#orientation-and-navigation 
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fraw.githack.com%2Fw3c%2Fapa%2FCOGA-XR-input%2Fxaur%2Findex.html%23orientation-and-navigation&data=04%7C01%7Cjjwhite%40ets.org%7Ce7eeffb7f3bc42c3e5fd08d93b0d9430%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637605751779845437%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jLVskZ0CmtibN8gbW6is%2BYUz3sqbZsSHs2FRo9VGB8g%3D&reserved=0>
>
> https://raw.githack.com/w3c/apa/COGA-XR-input/xaur/index.html#spatial-orientation-mono-audio-option 
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fraw.githack.com%2Fw3c%2Fapa%2FCOGA-XR-input%2Fxaur%2Findex.html%23spatial-orientation-mono-audio-option&data=04%7C01%7Cjjwhite%40ets.org%7Ce7eeffb7f3bc42c3e5fd08d93b0d9430%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637605751779855437%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Wshyb0VTaEvlyJtOOzle16bIq7q8oknm3FWRVl7%2FD88%3D&reserved=0>
>
> Relating to #181 and #184 - Actionable Targets.
>
> I've taken the suggested new user needs/requirements and now refer to 
> them in a note, and then riff on the need for accessibility APIs to 
> map custom user interface actions to control types as suggested last 
> week. I've also referenced in the note the content usable doc to 
> provide useful patterns for the reader.
>
> https://raw.githack.com/w3c/apa/COGA-XR-input/xaur/index.html#interaction-and-target-customization 
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fraw.githack.com%2Fw3c%2Fapa%2FCOGA-XR-input%2Fxaur%2Findex.html%23interaction-and-target-customization&data=04%7C01%7Cjjwhite%40ets.org%7Ce7eeffb7f3bc42c3e5fd08d93b0d9430%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637605751779855437%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=BQy8ViSkK95ASUAHAjuum%2FB%2FCpiBjnr0zHuT7ZhovIY%3D&reserved=0> 
>
>
> Then we have issues 176 and 183 to also discuss tomorrow.
>
> Thanks
>
> 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.
>
> ------------------------------------------------------------------------
> Joshue O'Connor <mailto:joconnor@w3.org>
> Tuesday 29 June 2021 15:52
> Hi all,
>
> Just a heads up that I have minted a new branch for us to review 
> tomorrow on our call.
> Please have a look beforehand if possible. The main parts to note are:
>
> Relating to #180 - Wayfinding
>
> I've changed the name of two categories to 'Orientation and 
> navigation' as well as 'Spatial orientation: Mono audio option' - and 
> edited User Need 13 to include people with spatial orientation 
> impairments. I like this as it broadens the net for the basic user 
> need. Most of the wording for the user need is from David Fazio, as he 
> clearly articulates it.
>
> https://raw.githack.com/w3c/apa/COGA-XR-input/xaur/index.html#orientation-and-navigation
> https://raw.githack.com/w3c/apa/COGA-XR-input/xaur/index.html#spatial-orientation-mono-audio-option
>
> Relating to #181 and #184 - Actionable Targets.
> I've taken the suggested new user needs/requirements and now refer to 
> them in a note, and then riff on the need for accessibility APIs to 
> map custom user interface actions to control types as suggested last 
> week.  I've also referenced in the note the content usable doc to 
> provide useful patterns for the reader.
>


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