20:57:26 RRSAgent has joined #svg 20:57:26 logging to http://www.w3.org/2012/08/23-svg-irc 20:57:28 RRSAgent, make logs public 20:57:28 Zakim has joined #svg 20:57:30 Zakim, this will be GA_SVGWG 20:57:30 ok, trackbot; I see GA_SVGWG(SVG1)5:00PM scheduled to start in 3 minutes 20:57:31 Meeting: SVG Working Group Teleconference 20:57:31 Date: 23 August 2012 20:57:38 Agenda: http://lists.w3.org/Archives/Public/public-svg-wg/2012JulSep/0167.html 20:58:20 GA_SVGWG(SVG1)5:00PM has now started 20:58:27 +Doug_Schepers 20:58:32 Kelvin has joined #svg 21:00:09 +??P1 21:00:11 Zakim, ??P1 is me 21:00:11 +heycam; got it 21:00:39 +Kelvin 21:01:05 +Rich 21:01:20 richardschwerdtfe has joined #svg 21:01:49 +??P8 21:01:57 +??P7 21:02:09 zakim, ??P8 is me 21:02:09 +cabanier; got it 21:02:37 nikos has joined #svg 21:02:45 -??P7 21:03:28 agenda? 21:04:24 richardschwerdtfe has left #svg 21:04:34 richardschwerdtfe has joined #svg 21:05:03 Zakim, who is on the call? 21:05:03 On the phone I see Doug_Schepers, heycam, Kelvin, Rich, cabanier 21:05:39 +Tav 21:06:36 +??P5 21:06:45 Zakim, ??P5 is me 21:06:45 +ed; got it 21:06:57 Agenda: http://lists.w3.org/Archives/Public/public-svg-wg/2012JulSep/0167.html 21:08:40 scribenick: cabanier 21:08:55 topic: SVG2 status 21:09:27 heycam: we were planning on publishing last tuesday but there were some issue 21:10:08 heycam: we tried again on thursday but we had some issues with Chris' color changes. I waiting to hear back from him and we'll probably publish on tuesday 21:10:25 heycam: because we have inline svg and we have mathml 21:10:46 heycam: we needed to change the format of the doc to HTML5 which took a bit of time 21:10:59 cabanier: so we're using mathml? 21:11:24 heycam: I converted a couple of formulas of the painting formulas and some of of the path stuff 21:11:34 +??P6 21:11:35 heycam: I'm using mathjax 21:11:41 Zakim, P6 is me 21:11:41 sorry, nikos, I do not recognize a party named 'P6' 21:11:47 Zakim, ??P6 is me 21:11:47 +nikos; got it 21:11:52 +??P7 21:12:02 heycam: to provide fallback. 21:12:22 Zakim, ??P7 is me 21:12:22 +birtles; got it 21:12:33 heycam: and around 6 months ago it was decided that mathml was OK 21:13:23 heycam: are you having trouble? 21:13:34 tav: I tried it today and it took me around 20 min 21:13:51 heycam: let me know if you have issues and I'll help you 21:14:08 topic: Lucerne F2F reminder 21:14:16 http://www.w3.org/Graphics/SVG/WG/wiki/F2F/Switzerland_2012 21:14:34 http://www.w3.org/Graphics/SVG/WG/wiki/F2F/Switzerland_2012/Agenda_proposals 21:14:45 ed: there's a page for attending and for proposals 21:14:57 heycam: I think only cyril hasn't replied 21:15:26 topic: SVG Accessibility Gap Analysis 21:15:28 http://www.w3.org/mid/OF38278C69.E13ACB0C-ON86257A5E.006A2B07-86257A5E.006B7B8B@us.ibm.com 21:16:01 Rich 21:17:11 heycam: can I reformat it as text and send it to the list 21:17:15 rich: sure 21:17:28 doug: that will make it easier to search the archives 21:17:55 http://lists.w3.org/Archives/Public/www-svg/2012Aug/0105.html 21:18:16 rich: the first part is just about the technology of what happens in the browser 21:18:31 rich: looking at SVG, we have the gap analysis 21:19:23 (it might be useful to also look at this http://www.w3.org/TR/2011/WD-html-aapi-20110414/ ) 21:19:34 rich: the reason for the rule attribute is to give the system information 21:19:48 s/rule/role/ 21:20:20 (rich: going over the reason we need accessibility in SVG) 21:20:31 rich: we have no keyboard navigation 21:20:51 rich: the structure of SVG doesn't map to platform accessibility 21:21:07 rich: the grouping element can be repurposed for that reason 21:21:25 rich: you can assign semantics to it 21:21:48 rich: the first svg document alludes that we can do this with the element 21:22:37 rich: svg rendering don't follow system settings such as high contrast 21:23:05 rich: does high contrast tie in with the developers? 21:23:18 I wonder whether the CSS system colour keywords in conjunction with default colours is sufficient for high constrast support. 21:23:21 rich: panning and zooming inside of a SVG rendering is important too 21:23:31 rich: do we do something with animations 21:23:42 rich: we heard that they are being removed? 21:23:55 heycam: no. Brian is working on something new 21:24:18 rich: we want to look into how to make these accessibility 21:24:36 rich: we should introduce 'role' on elements 21:25:24 rich: the role attribute on safari and webkit on svg is mapped to the accessibility API 21:25:44 rich: we could develop more states to ARIA and apply them to SVG 21:26:05 rich: MS and ??? would like tabindex applied to SVG so you can have keyboard navigation 21:26:42 rich: do we want to provide the ability to zoom into content that is not visible 21:27:04 doug: what is the behavior of fragment id with zooming and panning? 21:27:30 doug: the user might not want to zoom in on the bounding box. 21:28:11 doug: we've talked about the idea of adding tab index to SVG but SVG already has one that is better 21:28:13 an example of tabbing between nodes in an svg, with panning: http://dev.w3.org/SVG/profiles/1.2T/test/svg/interact-focus-203-t.svg 21:28:16 works in opera 21:28:18 rich: so you want both models? 21:28:23 doug: yeah 21:28:33 (testcase is from the SVG 1.2T testsuite) 21:28:38 rich: that sounds fine. I have to look into again 21:28:54 rich: but there doesn't seem opposition to adding tab index 21:29:23 heycam: yes, we should have keyboard navigation. Even outside the accessibility use case 21:31:20 ed: do we just want tab behavior or 4/8 way navigation too? 21:31:35 ed: I'd prefer that whatever we had in tiny keeps working 21:31:45 heycam: we should look into the model 21:32:09 ed: yes, it should be possible to make it work. It makes sense to have it in SVG if it works in HTML 21:32:24 heycam: weren't they going to be added to CSS? 21:32:53 doug: tantek decided not to add the navigation keyword to CSS UI 3 but I don't know why 21:33:26 doug: tab index is not sufficient for a lot of scenarios. We would have to define how those work together 21:33:52 doug: for arrow key navigation, the keyword are: up/right/etc 21:34:09 doug: those are directional navigation elements 21:34:19 http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Commitments -- see items 97, 98, 99 -- that covers the navigation properties and HTML's tabindex 21:35:09 doug: you need an algorihtmic way to find out what 'up' means 21:35:39 heycam: item 99 is similar to tabindex, 97 covers nav 21:35:50 rich: so it's resolved to do this feature? 21:35:54 heycam: yes 21:36:03 rich: who is going to do the spec work? 21:36:20 heycam: nobody has signed up for it 21:36:36 http://www.w3.org/TR/SVGTiny12/interact.html#specifyingnavigation 21:36:52 doug: here's what we have so far 21:37:19 doug: the only conflict is nav-next and nav-prev 21:37:46 doug: I will take a look if there's a conflict with tab index. It's an interest of mine 21:38:18 action: shepazu is going to look into conflicts between the model of tab index and navigation 21:38:18 Created ACTION-3341 - Is going to look into conflicts between the model of tab index and navigation [on Doug Schepers - due 2012-08-30]. 21:39:01 doug: I see they're attributes but not properties. We need to talk to the CSS people about that 21:39:28 rich: I''m willing to take an action for the aria and the role attribute 21:39:37 q+ to discuss system colors 21:39:41 heycam: we already have role in tiny 21:39:44 http://www.w3.org/TR/SVGTiny12/struct.html#RoleAttribute 21:40:48 tav: please provide examples because I tried to do it in the past and there's no documentation out there 21:40:53 doug: I have some! 21:41:00 tav: those are the only ones... 21:42:39 doug: I dropped in a document. This contains a table that has all the ally api's 21:42:52 doug: I found it really useful 21:43:13 rich: yes, everyone needs to understand what we're doing 21:43:13 q? 21:44:06 resolution: define Role and ARIA states and property attributes in SVG 21:44:26 doug: we want to do the same as HTML did it 21:46:41 rich: we feel that the industry hasn't done enough for accessibility 21:46:56 rich: with flash going away, we want to look into SVG 21:47:13 heycam: what did flash do? 21:47:44 rich: it doesn't deal with table structure. You can have a group or a panel. The evens are hardcoded to the windows platform 21:47:50 example of SVG table with ARIA http://schepers.cc/svg/accessibility/table.svg 21:48:00 rich: it has no knowledge about rich text. 21:48:13 rich: they don't have structure content 21:48:46 rich: it was not that great and Adobe is not investigating it any more 21:49:32 rich: limited windows support. They wanted to add richer accessibility support but it's not happening 21:50:32 ack shepazu 21:50:32 shepazu, you wanted to discuss system colors 21:50:49 doug: what did you mean with system colors? 21:51:06 rich: desktop applications can respond to going to high contrast mode 21:51:13 CSS 3 system colors deprecated http://www.w3.org/TR/css3-color/#css-system 21:51:41 rich: we could add an API for that so the application is notified 21:52:04 doug: I think there's an opportunity for doing this in CSS 21:52:14 doug: like with a media query 21:52:38 doug: not just for ally, but various lighting conditions 21:53:19 doug: or for people that are color blind 21:53:38 doug: using media queries we can have the document be styled differently 21:54:39 CSS luminance media queries http://fremycompany.com/BG/2012/Ambient-light-sensors-and-CSS-Media-Queries-971/ (doesn't support the red-green red-blue thing though) 21:54:41 doug: then designers can provide an alternate representation 21:54:52 tav: do you think designers will do this? 21:55:13 doug: I think there will be aftermarket people will do this redesigns 21:55:40 doug: designers don't want to do the high contrast page because it doesn't look good 21:56:11 ed: I like Brian's doc 21:56:24 rich: we should go to the CSS WG for the media queries? 21:56:28 all: yes 21:58:13 action: richardschwerdtfe to write up a proposal for role and aria states and properties integration 21:58:14 Created ACTION-3342 - Write up a proposal for role and aria states and properties integration [on Richard Schwerdtfeger - due 2012-08-30]. 21:58:42 rich: panning and zooming is something that Kelvin wants 21:58:53 rich: it would be nice to pan and zoom portions 21:59:02 rich: of an SVG document 21:59:24 kelvin: you could describe a rectangle to do pan and zoom 22:00:06 kelvin: it's not an SVG thing. I'm not sure how the WG can influence this. The Adobe viewer had 22:00:31 ed: it's supported in some other viewers. Not sure if it's well documented 22:00:41 rich: can we put this in the spec? 22:01:03 heycam: it's still in the spec but it hasn't gotten widespread implementation 22:01:12 s/ well documented/ well documented in the respective UA's docs how it works/ 22:02:08 doug: in the past people wanted to limit the scope that we can influence the UI 22:02:12 s/it's supported in some other viewers/ctrl+dragging inside an svg for panning, alt+click / shift+alt+click for zooming in and out is supported in some other viewers/ 22:02:14 -birtles 22:02:34 doug: Opera has the zoom slider 22:02:52 thorton has joined #svg 22:02:58 doug: we can try to say that they need to implement some sort of zoom and pan 22:03:12 thorton has joined #svg 22:04:06 kelvin: with accessibility we can say that we need it which might force them to add it 22:04:21 rich: should we strengthen the language? 22:05:14 doug: Kelvin, would you want to write up what we need from pan and zoom? so we can feedback from browser vendors 22:05:29 kelvin: yes, I will reread the spec and write something up 22:05:55 action: kelvin to write requirement for zoom and pan for accessibility 22:05:55 Created ACTION-3343 - Write requirement for zoom and pan for accessibility [on Kelvin Lawrence - due 2012-08-30]. 22:06:16 topic: CSS4 as value for 22:06:23 http://www.w3.org/mid/FBBDBDBC-F3CD-404E-AFC1-0369A75DAA89@adobe.com 22:06:57 -Doug_Schepers 22:07:09 ed: why was this for css4 images and not 3? 22:07:30 cabanier: isn't 3 already in LC? Tab is working on version 4 22:07:55 heycam: so, the element() is in CSS4 22:08:10 cabanier: maybe put it on the agenda again next week 22:08:25 ed: css3-images is in CR 22:08:44 cabanier: wasn't there also a decision to push off element() 22:09:11 cabanier: maybe it was the one that referred to other html chunk 22:09:26 ed: we 22:09:38 ed: we'll put it on the topic next week 22:09:51 topic: element 22:09:57 ed: chris isn't here 22:10:18 s/the topic next/the agenda for next/ 22:10:35 heycam: we already decided to remove the font element 22:11:04 heycam: there is no advantage to be able to specify as an element as well as a CSS @ rule 22:11:12 cabanier: that sounds reasonable 22:11:20 heycam: and it wasn't widely implemented 22:11:37 ed: is this tagging the image with a profile? 22:11:41 https://svgwg.org/svg2-draft/color.html#ColorProfileElement 22:12:18 cabanier: it's there so you can give it a link to an ICC profile and give it a name 22:14:00 heycam: and then you can reference the name of the color profile in the paint 22:14:34 heycam: it makes sense just to have the @ rule 22:15:14 ed: I can't think of a reason to have it 22:16:36 heycam: it's just as easy to get to an @ rule through the DOM 22:17:00 resolution: remove the element from the spec 22:18:01 action: heycam to remove element from the spec 22:18:02 Created ACTION-3344 - Remove element from the spec [on Cameron McCormack - due 2012-08-30]. 22:18:23 ed: any other topics? 22:18:47 heycam: there are some things on the mailing list but we can do that later 22:18:58 glenn has joined #svg 22:19:04 nikos: weren't there things that we want Erik's input on? 22:20:05 heycam: one of the items was clipping on filters: before/after/both 22:20:11 nikos: we didn't decide 22:20:55 ed: we discussed it a lot. the current version of the spec picks one of the ways and we discussed doing auto for drop shadows etc 22:21:30 heycam: we have margins too. 22:21:46 ed: we took them out but re-added them for shaders 22:21:55 ed: I have to look into it again 22:22:15 heycam: dirk should be here to drive the discussion 22:22:24 http://www.w3.org/2012/08/09-svg-minutes.html#item07 22:22:38 heycam: this is the discussion 22:22:52 ACTION: ed to respond to the filter issues raised in http://www.w3.org/2012/08/09-svg-minutes.html#item07 22:22:52 Created ACTION-3345 - Respond to the filter issues raised in http://www.w3.org/2012/08/09-svg-minutes.html#item07 [on Erik Dahlström - due 2012-08-30]. 22:22:54 http://www.w3.org/2012/08/16-svg-minutes.html#item04 22:23:43 ed: I will respond to both offline 22:25:18 s/I will respond to both offline/I will read these offline and respond/ 22:26:24 -Kelvin 22:26:25 -cabanier 22:26:26 -heycam 22:26:27 -Rich 22:26:27 -Tav 22:26:28 -ed 22:26:28 -nikos 22:26:28 GA_SVGWG(SVG1)5:00PM has ended 22:26:30 Attendees were Doug_Schepers, heycam, Kelvin, Rich, cabanier, Tav, ed, nikos, birtles 22:26:57 trackbot, end telcon 22:26:57 Zakim, list attendees 22:26:57 sorry, trackbot, I don't know what conference this is 22:27:05 RRSAgent, please draft minutes 22:27:05 I have made the request to generate http://www.w3.org/2012/08/23-svg-minutes.html trackbot 22:27:06 RRSAgent, bye 22:27:06 I see 5 open action items saved in http://www.w3.org/2012/08/23-svg-actions.rdf : 22:27:06 ACTION: shepazu is going to look into conflicts between the model of tab index and navigation [1] 22:27:06 recorded in http://www.w3.org/2012/08/23-svg-irc#T21-38-18 22:27:06 ACTION: richardschwerdtfe to write up a proposal for role and aria states and properties integration [2] 22:27:06 recorded in http://www.w3.org/2012/08/23-svg-irc#T21-58-13 22:27:06 ACTION: kelvin to write requirement for zoom and pan for accessibility [3] 22:27:06 recorded in http://www.w3.org/2012/08/23-svg-irc#T22-05-55 22:27:06 ACTION: heycam to remove element from the spec [4] 22:27:06 recorded in http://www.w3.org/2012/08/23-svg-irc#T22-18-01 22:27:06 ACTION: ed to respond to the filter issues raised in http://www.w3.org/2012/08/09-svg-minutes.html#item07 [5] 22:27:06 recorded in http://www.w3.org/2012/08/23-svg-irc#T22-22-52 22:27:31 richardschwerdtfe has left #svg