18:01:41 RRSAgent has joined #svg-a11y 18:01:41 logging to http://www.w3.org/2016/08/02-svg-a11y-irc 18:02:22 rrsagent, set logs world-visible 18:02:43 chair: Fred 18:02:53 present+ Fred 18:02:57 present+ LJWatson 18:04:00 present+ Shepazu 18:04:08 rrsagent, make minutes 18:04:08 I have made the request to generate http://www.w3.org/2016/08/02-svg-a11y-minutes.html LJWatson 18:04:17 TOPIC: SVG 2.0 18:04:29 DS: I'm prepping SVG 2.0 for CR. 18:04:53 FE: Has the shadow tree/shadow DOM terminology issue been resolved? 18:05:02 DS: Don't know. 18:09:59 https://www.w3.org/TR/shadow-dom/#events 18:12:55 https://www.w3.org/TR/SVG2/interact.html#PointerEvents 18:16:35 https://www.w3.org/TR/SVG2/struct.html#UseElement 18:20:53 DS: Noting that we don't have quorum. 18:21:39 ... So suggest we raise an issue about whether to include references to Shadow DOM - given that it is still a WD. 18:25:40 https://github.com/w3c/svgwg/issues/99 18:27:14 This 201 on Shadow DOM and styling is worth reading http://www.html5rocks.com/en/tutorials/webcomponents/shadowdom-201/ 18:27:20 TOPIC: TF recruitment 18:27:37 FE: Have been trying to encourage people working on maps to join the TF. 18:27:58 DS: Suggest that until the TF is seen to be working on maps, there is little of interest to maps people here. 18:28:25 FE: If we can bring them to the table we'll be able to identify the problems they have. 18:29:06 LW: Can we ask the maps people for a problem statement, we could start looking at it as a technical problem. 18:29:20 ... Then we would have something the maps people could review, and that might encourage them to join. 18:30:03 FE: But what is a problem statement for something like slippy maps? 18:30:20 LW: No idea. But that's what the maps people will be able to tell us about. 18:30:33 ... We need to identify problems before we go looking for solutions. 18:30:42 FE: Do you use maps Léonie? 18:30:49 LW: No, not really. 18:31:26 FE: There is an app that gives directions. 18:32:29 LW: Lots of apps that do that, but they're directions based rather maps based. 18:32:57 FE: Should there be a11y requirements for slippy maps? Those are things that let you pan etc. like a Google map. 18:33:06 ... Might have points of interest on it. 18:34:36 LW: Probably for exploring a map for a maps sake. 18:34:44 ... Like discovering where a country is in the world. 18:34:53 FE: Or discovering a map of the Grand Canyon. 18:35:00 LW: Yes. 18:35:30 FE: so can we start looking at these things? 18:35:50 LW: I don't think that's a clear enough problem statement. We need to talk to lots more people to find out what people typically want to do with maps first. 18:36:09 DS: Also what the map itself is trying to accomplish. 18:36:49 FE: How would someone claim accessibilitFE: It's hard to make an interactive decision tree accessible for ATs. 18:37:36 s/FE: How would someone claim accessibilitFE: It's hard to make an interactive decision tree accessible for ATs./FE: It's hard to make an interactive decision tree accessible for ATs./ 18:37:52 DS: Think this is too speculative at the moment. 18:38:05 ... Suggest we focus on things like graphs first. 18:38:12 LW: +1 18:38:20 rrsagent, make minutes 18:38:20 I have made the request to generate http://www.w3.org/2016/08/02-svg-a11y-minutes.html LJWatson 18:39:08 FE: Meeting adjourned for lack of quorum 18:39:13 scribenick: LJWatson 18:39:57 rrsagent, make minutes 18:39:57 I have made the request to generate http://www.w3.org/2016/08/02-svg-a11y-minutes.html LJWatson 18:40:04 fesch has left #svg-a11y 18:40:21 Meeting: SVG A11y TF meeting 18:40:26 rrsagent, make minutes 18:40:26 I have made the request to generate http://www.w3.org/2016/08/02-svg-a11y-minutes.html LJWatson 18:41:36 LJWatson has left #svg-a11y 20:04:26 chaals has joined #svg-a11y