W3C

- DRAFT -

Accessible Platform Architectures Working Group Teleconference

31 Jan 2018

Attendees

Present
janina
Regrets
Chair
jasonjgw
Scribe
janina

Contents


<scribe> scribe: janina

jgw: Somewhat informal, but intent to discuss ...
... Navigation, VR/AR, then planning work going forward

<scott_h> apologies everyone - WebEx seems to have something against me today and keeps disconnecting

<scott_h> Will try dialing in through Skype direclty rather than through app

jgw: SH has provided goo references for vr/ar
... Noting scanning approachjgw: Personally uncertain how generalizable this is
... Explanation does note bio evolution parallels--searching for food

<jasonjgw> Janina notes that where there is a large number of UI controls, information seeking may be a good analysis of the task of finding the correct control for a given purpose.

<jasonjgw> Janina notes that we need an iterative process of finding a useful approach.

jgw: Believe task analysis is needed
... Suggest listing various scenarios where nav is relevant
... So we can defined reqs and possible nav approaches

<jasonjgw> Janina supports the notion of categorizing and identifying scenarios. Where we can't easily classify, we will have identified the need for novel appraoches/solutions.

sh: Believe the papers will give us many useful scenarios

jgw: Agrees
... Recalling svg discussion about nav reqs of graphical material inluding data visualization
... Semantic vs spatial
... Was never a priority conversation in the svg a11y, though

<scott_h> dropped out again, I'm guessing there's osme sort of network issue

<jasonjgw> ACTION: jasonjgw to establish a wiki page for collecting navigational use cases (applications, graphics, VR/AR).

<trackbot> Error finding 'jasonjgw'. You can review and register nicknames at <http://www.w3.org/WAI/APA/track/users>.

jgw: Would like to go back to noting SH's references provided

sh: Just spent time digging and listing--haven't yet read them
... Regretably current process doesn't provide the very helpful abstracts
... Noted that much of the research was weighted toward cognitive
... Can continue, and do some reading this coming week
... Are we wanting only xr (vr/ar) for now? Or wider?

jgw: We have overlapping topics
... We have web apps, graphics, and also vr/ar
... Also to simply gather reqs for vr/ar
... But the nav piece is broader

<jasonjgw> Janina notes that we want a good general understanding of where spatial or semantic navigation are more useful. This applies to VR/AR as well. It's a very broad topic that we need to approach from several different directions.

sh: Noting there's really not a lot of research, so we aren't going to be overwhelmed

jgw: Noted that IBM's research was aimed at satisfying internal development needs
... IBM did consider where spatial is more relevant

Summary of Action Items

[NEW] ACTION: jasonjgw to establish a wiki page for collecting navigational use cases (applications, graphics, VR/AR).
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/01/31 14:41:51 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: janina
Present: janina

WARNING: Fewer than 3 people found for Present list!

Found Scribe: janina
Inferring ScribeNick: janina

WARNING: No "Topic:" lines found.

Found Date: 31 Jan 2018
People with action items: jasonjgw

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


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]