12:01:27 RRSAgent has joined #apa 12:01:27 logging to https://www.w3.org/2021/07/22-apa-irc 12:01:29 RRSAgent, make logs public 12:01:29 Zakim has joined #apa 12:01:31 Meeting: Accessible Platform Architectures Working Group Teleconference 12:01:31 Date: 22 July 2021 12:01:39 Judy has joined #apa 12:02:31 Leticia has joined #apa 12:02:39 present+ 12:03:01 present+ 12:03:12 present+ 12:03:19 present+ 12:03:22 scribe: Joshue108 12:03:25 present+ 12:03:32 regrets+ Becky, Scott 12:03:58 agenda? 12:04:18 SAZ: Thanks e'one, we had intro meeting two weeks ago 12:04:35 Looking at research and organising symposia etc 12:04:45 CarlosD has joined #apa 12:04:46 Looking at more indepth analysis 12:04:52 Interest was strong. 12:04:55 present+ 12:05:12 To make use of interest and expertise 12:05:42 The question is how to use the opportunities of the symposia, round table discussions etc 12:06:12 This is my understanding - the question of if we use this for specific topics, or do it more broadly 12:06:22 to frame questions or look at bigger gaps etc 12:06:38 Sorta meta research, or looking into what is needed 12:06:50 To allow for follow on work and contribs 12:07:02 We can also do a combination of that 12:07:16 First two could be broad, and then more specific 12:07:28 or create an exemplar 12:07:39 SAZ: I'd like to get a sense today of what we should do 12:07:56 And what the first symposium should be 12:08:33 There has also been work done on keywords in conference proceeding etc 12:09:03 SAZ: We can also look at what was not looked at 12:09:48 https://drive.google.com/drive/folders/1uLkgAvLGFr3UApAaOtrG4guPZRo64JqK 12:10:11 Carlos and Leticia from FCID 12:10:42 JS: Should we start with something specific and end up with more meta topics? 12:10:45 SAZ: We could 12:10:57 CD: We could combine them - do them other way around 12:11:10 Could be done at the same time. 12:11:18 We have possibilities 12:11:36 JS: I have a suggestion.. 12:11:48 We could frame this both ways... 12:12:03 The most immediate issue in APA, is from Google and Vispero 12:12:34 Both stating a problem.. relating to pronunciation 12:13:07 How do we design this in a way that works via an AAM or something else into UI A11y or iAccessible2, various APIs 12:13:16 The spec will fail if we can't solve this 12:13:57 s/AAM/AMM 12:14:17 JS: There are also XR meetings relating to AOM, that we've been invited to. 12:14:38 People are talking about APIs, their limitations, what do they need to do etc? 12:14:49 Could be framed as a research question. 12:15:04 JW: Jason and Josh 12:15:32 JW: System level interfaces is a good topic 12:15:33 q+ 12:15:56 JW: Based on recent comments in APA work, this could be turning into a more urgent issue 12:16:14 JS: It is for pronunciation - but it is in general an emergent issue 12:16:33 ack josh 12:16:42 Joshue108: Agrees on framing 12:16:57 JoC: short-term need may be driver to look into this issue 12:17:07 Joshue108: Suggests the short term need provides a way to possibly structure a broader conversation around these issues 12:17:26 Joshue108: we do have a broader sense that aapi issues are arising 12:17:57 Joshue108: also notes that groups outside W3C are also looking at this 12:18:21 JB: This direction is good 12:18:34 SAZ: Other reactions? 12:18:54 JW: If you want a topic then this is a candidate/ 12:19:20 CD: My reaction is that this fits quite well, in terms of stuff in our keyword search 12:19:44 If the research community is not aware of this, then we can do that. 12:20:06 CD: I do have some project concerns, deep analysis may be hard if there are no publications 12:20:37 JB: We ran into issues in the past with lighter weight approaches? 12:20:55 SAZ: We have no required format - can be as we want. 12:21:19 There is the issue that with the less publications there are, it can be tricky 12:21:51 CD: There are enough people here to come up with good ideas 12:22:11 We would need to connect this with what the community is doing. 12:22:13 q+ 12:22:45 CD: I wonder if the first symposium should be helping to build bridges 12:22:47 ack me 12:23:23 Joshue108: Should look for greater coop between W3C and other communities; this is an opportunity for that 12:24:13 Joshue108: Especially when they propose tech solutions in areas we care about, such as XR, WoT, etc; where it's hard to find a locus of control 12:24:49 Joshue108: Not sure we should go all the way into an area where there's no research--but maybe we do? 12:25:01 SAZ: I'd like to switch a little.. 12:25:17 Can we derive some criteria for topic selection? 12:25:22 q+ 12:25:34 There may be urgent topics, that can help an existing issue 12:25:46 another angle is impact in accessibility 12:26:07 q- 12:26:10 There could be criteria so we say - as Jason indicated there could be other topics 12:26:25 q+ 12:26:27 We dont need to set those now, but we can have candidates. 12:26:35 Across certain criteria 12:26:45 This gives a paper trail etc 12:27:24 ack jas 12:27:45 q+ 12:27:49 JW: Seems that topics that affect multiple aspects of a11y would be useful 12:28:22 There are both sides about prior publications, or could mean if there are few, then the reserach community is not looking at an area. 12:28:43 I don't think just having recent publications should be a deciding factor 12:28:51 We can discuss short and long term 12:28:57 We should have envisioned outcomes also 12:29:22 What is the benefit of looking at x or y? 12:30:06 SAZ: Thats helpful 12:30:37 I agree but are recent publications a sign of something? 12:30:46 Could show gaps etc 12:31:03 We should be thinking about this either way w other criteria 12:31:45 JW: It connects with my larger concern around architecural issues around how a11y is implemented and in general dont attract the research community in a substantial way 12:31:55 Focus on empirical HCI stuff 12:32:13 If we could stimulate the architectural discussions that would be good. 12:32:14 q+ 12:32:20 ack jan 12:32:45 JS: I'd like to see TTS engines work in a multi-lingual manner 12:32:58 There is no consistency today, across browsers etc 12:33:15 q+ 12:33:43 12:34:27 JS: The push for the standard is coming out of necessity - people are not looking at the standards for pronunciation and they fail 12:34:36 We can do better - no one is going there. 12:34:45 may not be traditional a11y research 12:35:29 ack me 12:36:01 SAZ: My question.. Is it more impactful for a11y, to look at this problem, the lack of support etc.. 12:36:06 q+ to make a case for a higher-level approach 12:36:29 Or is it better to shed light in the research community and the fact they are not looking at it. 12:37:03 We do need to look at the reviewers and what they want etc 12:37:12 We will need to justify it 12:37:46 I'm just questioning - its interesting to hear the research community is not looking at this. 12:38:01 JS: Google may not be doing this as they want market share etc 12:38:37 This may not be via co-operation, and the development of standards 12:38:55 But we can point to easy things that will help for the general population etc 12:39:16 I'm hoping the EU may care more - with language diversity 12:39:21 ack jud 12:39:21 Judy, you wanted to make a case for a higher-level approach 12:39:40 JB: Reflects on the first conversation/meeting... 12:40:43 We can have framing conversations to raise visibility 12:41:16 What about doing a workshop on a topic that frames a space? 12:41:32 Like AI etc and how we could plug that into testing and remediation? 12:41:56 To try to structure the space, so we could work on these 12:42:01 q+ 12:42:10 q+ 12:42:25 ack jas 12:42:50 JW: Seems some topic that would engage the architectural issues of a11y, and intergration with APIs etc 12:43:05 That would satisfy the criteria of earlier suggestions 12:43:16 Seems like a candidate 12:43:45 Regarding machine learning etc on the web.. we can see that on the authoring and testing side, also meets that criteria 12:43:51 Agree we have two good candidates 12:44:09 Promising on initial analysis 12:44:33 Framing it on a more generic level could be appropriate 12:44:40 Important hard problems 12:44:45 ack me 12:45:02 q+ 12:45:47 Joshue108: agree with jason; have preference for arch at the moment; like the notion of doing the hard work identifying gaps in but also pulling players together who can meet the needs 12:46:28 Joshue108: Suggest we need to lead in this space 12:46:42 Joshue108: AI/ML is less of a preference; but do think these are related 12:46:59 Joshue108: believe pronunciation is a massive issue 12:47:20 josh add xr and we have yet more 12:47:29 SAZ: +1 to Josh, we have more and more pieces 12:47:41 CD: Just want to echo that this is an interesting conversation.. 12:48:06 Most research in a11y is done by HCI related groups 12:48:19 This is an opportunity also to bring other groups in.. 12:48:36 Solve the hard problems that we should be working on. 12:49:04 CD: Could pronunction be framed in the language domain? 12:49:11 And Natural Language Processing? 12:49:34 This is a good topic to justify to the commission, many EU languages 12:49:35 +1 to broadening the framing of the pronunciation to a broader language issue 12:49:42 SAZ: Yes, there are interesting intersections 12:50:03 I'd like us to have some tangible outcomes. 12:50:23 SAZ: Would like to hear from Michael also. 12:50:48 SAZ: Here is a concrete idea, Jason referred to criteria but we need to agree and document those. 12:50:57 Various topics etc, all important. 12:51:14 Its important to see that there are gaps in various communities etc 12:51:46 So i propose for our first topic, we ask what are the gaps, topics that the W3C feel are urgent? 12:51:59 Can they described in a set of criteria that we agree on? 12:52:26 Our first symposium could be around good practices in a11y research, and what the community needs? 12:52:37 Could set out our stall in broader circles. 12:53:10 Set parameters in the field, foundation and we can pick specific things 12:53:22 AI I still imagine as a vertical 12:53:37 Could be a model that others can follow. 12:53:47 How does this sound? 12:54:13 q+ 12:54:25 ack carlos 12:54:30 ack jan 12:54:54 JS: What comes to mind, while it has value, who would come to that kind of symposium? 12:55:02 It would be hard to get industry. 12:55:18 We've never gotten AT vendors to participate at W3C. 12:55:56 SAZ: Good point but devils advocate, wouldn't it be great to address them, we could build a network. 12:56:27 JW: There could be value in a wider discussion - in what are the hard problems. 12:56:36 q+ 12:57:19 JW: Could be good - when thinking of hard issues that need to solved. Would need to be clear. 12:57:38 We'd need strong underlying criteria 12:57:41 ack me 12:58:25 Joshue108: not thrilled about too general a framing 12:58:55 Joshue108: having spent last two years on emerging tech am concerned that we know a lot of what needs focus that isn't being covered 12:59:14 Joshue108: concerned to resource more known issues 12:59:30 CD: I would need to think about this more. 13:00:01 I would be concerned that we just have three. There is a value bringing these challenges to the research community 13:00:35 I see a place where various stakeholders could present their issues and challenges to the research community 13:00:45 So think we already have good topics. 13:01:12 But there could be value in the more general approach but could we achieve more value going direct to the topics that we floated. 13:01:23 SAZ: My worry is that we jump into firefighting. 13:01:42 Josh is saying we know what some of the issues are but I don't think we have fully formulated this 13:01:55 Could be really good for the community based on data 13:02:14 SAZ: Am thinking about road mapping. 13:02:32 rrsagent, draft minutes 13:02:32 I have made the request to generate https://www.w3.org/2021/07/22-apa-minutes.html Joshue108 14:10:24 stevelee has joined #apa 14:18:43 janina has changed the topic to: APA Teleconference; Wednesday 28 July at 1600Z 14:59:38 Zakim has left #apa