- From: White, Jason J <jjwhite@ets.org>
- Date: Thu, 29 Aug 2019 14:15:25 +0000
- To: Joshue O Connor <joconnor@w3.org>, RQTF <public-rqtf@w3.org>
- CC: "group-apa-chairs@w3.org" <group-apa-chairs@w3.org>
Another drafting possibility: we could express the major points as questions for developers to consider in creating their new XR technologies/libraries/frameworks/XR applications. -----Original Message----- From: Joshue O Connor <joconnor@w3.org> Sent: Thursday, August 29, 2019 9:48 AM To: White, Jason J <jjwhite@ets.org>; RQTF <public-rqtf@w3.org> Cc: group-apa-chairs@w3.org Subject: Re: Checklist proposal for XAUR document Ok, great, if I hear some more +1's I'll start drafting them for further discussion. Thanks (as always) Jason, for responsive feedback. Josh On 29/08/2019 14:29, White, Jason J wrote: > I think a “checklist approach” has the potential to be very useful. You could even label the items “starting points for designing accessible XR applications”, for example, to make it clear that they are suggestions based on currently available knowledge and thinking on the subject, not yet firm guidance. > > Then, we could clearly cover all of the dimensions of relevant human variability (hearing, vision, movement, speech, cognition, etc.), as I suggested in my earlier comments with reference to functional performance statements. > > From: Joshue O Connor <joconnor@w3.org> > Sent: Thursday, August 29, 2019 5:58 AM > To: RQTF <public-rqtf@w3.org> > Cc: group-apa-chairs@w3.org > Subject: Checklist proposal for XAUR document > > > Hi all, > > We had a very productive call yesterday in RQTF on what should be contained in the XAUR document. Concerns were raised that we are not trying to create any kind of normative standard, and we will continue the discussion around how XAUR relates to FAST, WCAG 2.x and work in Silver. > > Jason, expressed the concern that right now, authors and devs really have no-where to go to get any substantive advise on with what user needs in XR may be or how to need them. > > So I've a suggestion to float to the group. We currently have a useful > section that outlines some of the user needs in XR, in a rather clear > way - grouped under headings like education, gaming, health etc. [1] > > My vision for the following section was where there would be modules relating to XR Semantics (where objects role,state, properties etc are described), Navigation, Interaction etc. > > This would be a good place for generic advise on how to approach making these areas accessible and addressing some of the user needs that are outlined in the first part of the doc. They could be written as informative checklist/ indicators that could help the reader get to grips with what is needed, but doesn't have to be exhaustive or definitive. > > For example, there are some items I've started to draft for media in XR, a few months ago - and I used the MAUR as a template - here are some examples for accessible Media in XR that I've drafted. > > Navigating ancillary content > · [CN-XR-1] Provide a means to structure media resources so that users can navigate them by semantic content structure. Support keeping all media alternatives synchronized when users navigate. > Described Video in XR > > · [DV-XR-1] Provide an indication that descriptions for video are available, and details on their status (active/non-active). > · [DV-XR-2] Render descriptions in a time-synchronized manner, using the primary media resource as the timebase master, ensure tracking between descriptions is maintained. > · [DV-XR-3] Support multiple description tracks (e.g., discrete tracks containing different levels of detail). > · [DV-XR-4] Support recordings of high quality speech, or video audio, as a track of the media resource, or as an external file. > · [DV-XR-5] Allow the author to independently adjust the volumes and panning of the audio description and original soundtracks where these are available as separate audio channel resources. > > The full current draft can be found here. [2] > > For the XAUR I've removing some of the informative paragraphs just to make this more readable. > > So if we take that approach with say the XR Navigation, some of the initial checkpoints could be: > > XR Navigation > > Movement Model > > [MV-XR-1] Provide a means to map all functionality to a users preferred settings. > > [MV-XR-2] Ensure the user can make a move or action without having to > physically emulate that movement or action. Each movement and action > should have an alternative, or an alternative mapping to a control > > etc > > Use of sounds > > [MV-XR-3] Provide a means that audio describes sounds within a game. > > [MV-XR-4] Ensure the user understand any speech or dialogue within a game, by modifying background music or game dynamics to their preference. > > etc > > Haptics > > [MV-XR-5] Ensure haptics reflect correct game feedback and are synchronised with audio game dynamics. > etc > > Location > > [MV-XR-6] Ensure the user can find their location within a game or other immersive environment easily. > etc > Orientation > > [MV-XR-7] Ensure the user can find their location of other players, targets etc within a game - without compromising game dynamics easily. > > etc > > Ok, so that's an initial stab at it and to indicate an option - and I look forward to feedback on this idea. How to you feel about this suggested checklist approach? > > I do hear the need for something that authors and devs can actually refer to. > > Thanks > > Josh > > [1] > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > w3.org%2FWAI%2FAPA%2Fwiki%2FXaur_draft%23XR_User_Needs&data=02%7C0 > 1%7Cjjwhite%40ets.org%7C5e462b968d5244f04ed208d72c87788e%7C0ba6e9b760b > 34fae92f37e6ddd9e9b65%7C0%7C0%7C637026832678478577&sdata=LtQD4lD8r > xpVRUzItVsNPFdql2p%2BWNTLvmvvF7KIUec%3D&reserved=0<https://nam01.s > afelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2F > APA%2Fwiki%2FXaur_draft%23XR_User_Needs&data=02%7C01%7Cjjwhite%40e > ts.org%7C5e462b968d5244f04ed208d72c87788e%7C0ba6e9b760b34fae92f37e6ddd > 9e9b65%7C0%7C0%7C637026832678478577&sdata=LtQD4lD8rxpVRUzItVsNPFdq > l2p%2BWNTLvmvvF7KIUec%3D&reserved=0> > > [2] > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > w3.org%2FWAI%2FAPA%2Fwiki%2FMedia_in_XR&data=02%7C01%7Cjjwhite%40e > ts.org%7C5e462b968d5244f04ed208d72c87788e%7C0ba6e9b760b34fae92f37e6ddd > 9e9b65%7C0%7C0%7C637026832678478577&sdata=HIWkrnd5DfFBaM8l08E3Y7Nb > PoQujF5hmyCInFKXGM4%3D&reserved=0<https://nam01.safelinks.protecti > on.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Fwiki%2FMedi > a_in_XR&data=02%7C01%7Cjjwhite%40ets.org%7C5e462b968d5244f04ed208d > 72c87788e%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637026832678478 > 577&sdata=HIWkrnd5DfFBaM8l08E3Y7NbPoQujF5hmyCInFKXGM4%3D&reser > ved=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. > > ________________________________ -- 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 Thursday, 29 August 2019 14:15:55 UTC