W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > May 2021

Re: Review of XR Accessibility User Requirements COGA

From: Lisa Seeman <lisa1seeman@gmail.com>
Date: Thu, 27 May 2021 17:11:40 +0300
Message-ID: <CAKExBMK4tDtG653YXuL6MdR2OVGQ3tb79GJ7mRO2Z_qoKf7K9w@mail.gmail.com>
To: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
Cc: John Kirkwood <kirkwood@citymouse.com>, David Fazio <dfazio@helixopp.com>
On Wed, May 12, 2021 at 6:13 PM Joshue O'Connor <joconnor@w3.org> wrote:

> Hi John, Lisa and David,
>
> We reviewed these suggested user needs and requirements in the research
> questions meeting today (minutes here
> https://www.w3.org/2021/05/12-rqtf-minutes.html).
>
> Can you please give us some more info on the following?
>
> [New User Need] 4.20 Wayfinding - Review of XR Accessibility User
> Requirements COGA [1]
>
> Q: RQTF would like some more information on the user case for mono, and we
> are not clear why this is especially a use case for low vision? Can you
> please clarify?
>
> Also regarding: [New User Need] 4.21 Understanding Actionable Targets -
> Review of XR Accessibility User Requirements COGA #181 [2]
>
> While there was some agreement that this is an interesting request in
> terms of how interaction affordances can be translated across modalities
> (and that this is important) - the group thought while the user need is
> clear we need more detail around suggested requirements/implementation. For
> example, the XAUR already states the need for personalization support for
> people with cognitive disabilites (as a user need with a related
> requirement):
>
> User Need 3: Users with cognitive and learning disabilities may need to
> personalise the immersive experience in various ways.
> REQ 3a: Support Symbol sets so they can be used to communicate and layered
> over objects and items to convey affordances or other needed information in
> way that can be understood according to user preference.
>
>
> https://raw.githack.com/w3c/apa/6d5bf713d9d7c65ecda104c213ad47b0e98cfbe1/xaur/index.html#immersive-personalisation
>
> This would seem to already cover the actionable target use case that you
> suggest. Any extra details on your thinking and a response to the
> suggestion that the actionable targets case  may be covered, would be
> great. I've also added these questions to Github so please feel free to
> reply there (whatever works).
>
> Thanks in advance
>
> Josh
>
> [1] https://github.com/w3c/apa/issues/180
> [2] https://github.com/w3c/apa/issues/181
>
> John Kirkwood <kirkwood@citymouse.com>
> Saturday 1 May 2021 03:11
> Upon review of draft XR Accessibility User Requirements
> <https://raw.githack.com/w3c/apa/6d5bf713d9d7c65ecda104c213ad47b0e98cfbe1/xaur/index.html> we
> propose the addition of the following paragraphs:
>
>
>
>
> 4.20 Wayfinding
>
>    -
>
>    User Need 20: Users with limited vision and spatial orientation
>    impairments may have issues orienting and navigating.
>
>
>    -
>
>    REQ 20: Provide clear landmarks.clear landmarks either visual or audio
>    landmarks to follow or to enable return to paths. Provide visual land
>    marks.  Mono audio sound to be sent to both headphones so that the user can
>    perceive and navigate and remember the landscape and enable return paths.
>
> 4.21 Understanding Actionable Targets
>
>    -
>
>    User Need 21: Users with cognitive impairments need to understand what
>    items in a visual display are actionable targets, and how to interact with
>    them.
>    - REQ 21a: Targets that are actionable should be clearly  indicated
>    -
>
>    REQ 21b: Users need to be provided a clear understanding of how to
>    interact with actionable targets. For example, a slider, where the user
>    needs to click and drag.
>
>
>
>
> _________________________________________________________
>
>   John Kirkwood
>   President / CEO
>   CityMouse, Inc.
>   DisabilityIN®  DOBE®
>   www.citymouse.com
>  kirkwood@citymouse.com
> _________________________________________________________
> Please consider the  environment before printing this email. The
> information found
> in this message may be privileged and confidential and protected from
> disclosure. If you
> are not original intended recipient you are hereby notified that any
> review, dissemination
> retransmission, or other use of, or taking of any action in reliance upon,
> this information
> is prohibited. If you have received this communication in error, please
> notify the sender
> immediately by replying to this message and deleting it from your
> computer.  Thank you.
>
>
>
> --
> Emerging Web Technology Specialist/Accessibility (WAI/W3C)
>
Received on Thursday, 27 May 2021 14:12:35 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:12 UTC