W3C

- DRAFT -

Accessible Platform Architectures Working Group Teleconference

04 Sep 2019

Attendees

Present
jasonjgw, MichaelC, SteveNoble, janina, Joshue108_, Judy
Regrets
Chair
jasonjgw
Scribe
SteveNoble

Contents


XAUR Draft: review, and interrelations among documents.

<Joshue108_> https://www.w3.org/WAI/APA/wiki/Xaur_draft#XR_Checkpoints_DRAFT

Jason: good discussions lately on email - checklist draft has been distributed via email previously

Scott: did a quick readthrough of the checklist and thought it was well done - complements the other work done

Jason: did a brief review of the chacklist - seems to be going in the right direction
... we should look at the relationship between these points and the examples and use cases and other WCAG requirements
... would be appropriate to highlight this as non-normative

<Zakim> janina, you wanted to discuss wcag reference advisability

Janina: wondering if it would it be helpful at this stage to cross-reference to other guidance documents
... Silver TF is explicitaley looking at XR
... there may be different ways to test for various criteria like alt text, and knowing how usable such things are will not be easy

<Joshue108_> +1 to Janina

Jason: There will be some areas in XR where there are no easy direct crossreferences to existing standards

Janina: Example of how captions might be done in XR due to positioning in a sonic landscape - not clear how that will be done

<Joshue108_> I think we just minted a new checkpoint Janina!

<Zakim> Joshue108_, you wanted to give some overview of thinking

<Joshue108_> http://gameaccessibilityguidelines.com

Josh: Context for checkpoints - these are big things that need to be done to make XR more accessible - some conncetions to gaming accessibility guidelines

Scott: agreed - the gaming guidlines are a good starting place

Josh: what I would hope to do is to use a modular approach, since some XR environments will have some modules but not others

Janina: have been expecting that gaming would be the leading edge for XR work

Josh: agreed - the gaming industry is very big and lots of money involved

Scott: will send along the paper he wrote on gaming

Judy: people from Able Gamers have been well involved and we hope that they will continue to contribute to this effort, and their guidelines approach is considered (much) more usable for that field

Jason: using things like 3D audio and haptic technology that we don'ty commonly used in desktop environments - these could be used to benefit accessibility - valuable to address in some way

Josh: some of the current haptic technology may be edge cases

Jason: the group should continue to review the checklist document and bring comments to next meeting
... will put this on the head of the next meeting agenda

Janina: more discussion will be going on at TPAC

<janina> APA agenda at TPAC is here:

<janina> https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2019

XR Accessibility and the FAST

Josh: how does the XR work relate to other groups like Silver TF, etc.?

<Joshue108_> https://w3c.github.io/apa/fast/

<janina> Some useful FAST links are:

<janina> Introductory: https://www.w3.org/2019/Talks/0516_FAST_MC/ Checklist: http://w3c.github.io/pfwg/wtag/checklist.html

<janina> Framework: http://w3c.github.io/apa/fast/

<janina> Checklist: http://w3c.github.io/apa/fast/checklist

Josh: the FAST is a useful "uberarchitecture" understanding and our XR spec goes below that as a child

<Joshue108_> User needs framework, then UAAG, ATAG etc as children.

Michael: that is a possible understanding...the user need framework in FAST is a good structure, where all the guidleines come down as a result

Jason: seems as the current process is starting at the user end and then deriving what the application needs to support
... we should also seek to identify matters that are not yet fully addressed by WCAG 2 guidelines

<Zakim> Joshue108_, you wanted to say we need guidance that is clearer about what need is being met.

<Judy> [JB: rejoins from another meeting]

Real-time communication accessibility: review and discussion.

<Joshue108_> https://www.w3.org/WAI/APA/wiki/Accessible_RTC_Use_Cases

Jason: Josh has developed a draft that takes into account several stages of review and comments
... are there comments or significant issues to raise on continuing developemnte of this draft?

Janina: our next step is working with the Web RTC/RTT group

Judy: Hopes to have conversation ahead of TPAC with regards to some current implementations

<Zakim> Joshue108_, you wanted to mention RTC use cases that relate to other groups and how to address that at TPAC

Josh: still working on Jason's comments
... Is trying to identify other groups like second screen and audio/media groups - no formal involvement yet

Janina: agrees those groups are helpful and we have had useful contacts in the past, but many of the contact people have changed - let's find out and re-engage

Josh: asks Janina to consider some of those cross-group interactions

Judy: APA contact - assumption that Janina is the default contact to reach out to other organizations, and others should coordinate with Janina

<Joshue108_> +1 to Judy

Janina: agreed that messaging should originate with her, but she needs our help to coordinate specific information that we want to communicate
... TPAC meeting coming up, but timing of meetings may be hard for some to participate remotely - we are all welcome to participate
... be aware that when the meeting is with another group, then the WebEX and IRC information will refelcet where that meeting is taking place

Jason: we may simply not have the regular call that week
... next week we will continue working on the RTC and the XR items
... we can do a TPAC retrospective for the week after TPAC - others agree

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/09/04 14:06:15 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/to this effort/to this effort, and their guidelines approach is considered (much) more usable for that field/
Succeeded: s/invironments/environments/
Default Present: jasonjgw, MichaelC, SteveNoble, janina, Joshue108_, Judy
Present: jasonjgw MichaelC SteveNoble janina Joshue108_ Judy
No ScribeNick specified.  Guessing ScribeNick: SteveNoble
Inferring Scribes: SteveNoble
Found Date: 04 Sep 2019
People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]