W3C home > Mailing lists > Public > public-apa@w3.org > August 2020

Re: Comments on XAUR Specification

From: Thomas Logan <thomas@equalentry.com>
Date: Sun, 16 Aug 2020 17:26:48 +0900
Message-ID: <CAEqWofcC_mGtSojY8ALshdbQyDbfmWnN2_nz=i1d9ur-2rFjhA@mail.gmail.com>
To: Joshue O Connor <joconnor@w3.org>
Cc: public-apa@w3.org
Hi Josh,

Thank you for the feedback.  I've putt additional comments inline:

On Thu, Aug 13, 2020 at 9:50 PM Joshue O Connor <joconnor@w3.org> wrote:

> Hi Thomas,
>
> A couple of points of clarification here please (your comments are
> really helpful)
> >> *Over emphasis on motion controls*.
> >> I think it is worth mentioning and defining 3DOF and 6DOF because
> >> they will
> >> have their own specific mobility issues.
>
> Can you mention here in your experience what they are for people with
> disabilities?
>

6DOF will have implications for people who are quadripalegic and for people
that use a wheelchair / mobility aid for navigation. In this case we are
concerned about moving directionally in physical space and I think has a
higher emphasis on the lower extremity for movement.

3DOF will have implications for people who have motor impairments that
affect the use of one or both arms.


> >>
> >> *VR Headsets need the user to be a physical position to play*.
> >> Maybe illustrate even more clearly such as requiring someone to be
> >> standing
> >> versus seated
>
> Done.
>
> >>
> >> *Captions are missing*
> >> Currently platforms don't have base level support for captioning of
> >> multimedia content. Seems like this should be touched on in section
>
> I'm missing what section you are referring to, can you let me know?
>

I meant section 4. XR User Needs and Requirements. I see you have 4.19
about Subtitling Customization but I don't see a previous Requirement about
having Captions as a starting point.


[image: image.png]



>
> >> *Vestibular Disorders*
> >> Motion sickness is common issue raised by people trying out VR.
> >> Teleportation / other movement issues should be called out as core
> >> challenge.
>
> Done.
>
> >> 4.2 Immersive semantics and customization
> >> [image: image.png]
> >> Recommend navigate and identify locations be a separate item of
> >> interest.
>
> I'm not sure about that at this point - we may call out into different
> sections in a later draft.
>
>
Makes sense to me.  I think there is additional work to build a navigation
UI that is separate from having an annotation UI for objects. I'll try to
share some real world examples from VR experiences soon.


> Thanks!
>
> Josh
>
> >>
> >> Maybe
> >> User Need 1: A user of assistive technology wants to identify objects
> >> and
> >> interact within an immersive environment.
> >>
> >> User Need 2: A user of assistive technology wants to identify
> >> locations and
> >> navigate to them successfully in an immersive environement.
> >>
> >>
>
>
> --
> Emerging Web Technology Specialist/Accessibility (WAI/W3C)
>


-- 
*Thomas Logan*, Owner
*Equal Entry* “Contributing to a more accessible world”
206.801.0083 (o) | www.equalentry.com
Blog <http://equalentry.com/blog> | Facebook
<https://www.facebook.com/equalentryaccessibility/> | YouTube
<https://www.youtube.com/equalentryaccessibility> | Newsletter
<http://eepurl.com/dxd5Ln>

image.png
(image/png attachment: image.png)

Received on Sunday, 16 August 2020 08:27:39 UTC

This archive was generated by hypermail 2.4.0 : Sunday, 16 August 2020 08:27:40 UTC