13:57:03 RRSAgent has joined #svg-a11y 13:57:03 logging to http://www.w3.org/2015/09/04-svg-a11y-irc 13:57:05 RRSAgent, make logs public 13:57:05 Zakim has joined #svg-a11y 13:57:07 Zakim, this will be WAI_PF 13:57:07 I do not see a conference matching that name scheduled within the next hour, trackbot 13:57:07 chair: Fred 13:57:08 Meeting: Protocols and Formats Working Group Teleconference 13:57:08 Date: 04 September 2015 13:57:13 RRSAgent, make log public 13:57:23 Meeting: SVG Accessibility Task Force 13:59:02 fesch has joined #svg-a11y 14:01:08 present+ fesch 14:01:48 present+ Amelia 14:03:17 scribe: AmeliaBR 14:03:54 TOPIC: Roles & Properties Taxonomy (Amelia's Proposal) 14:04:13 Fred: I think there have been some changes, do you want to describe them? 14:05:30 abr: main differences from earlier (week and half ago) is attributes, roles haven't changed much, will try and post an updated summary before next weeks call 14:05:58 abr: differences from how Fred has marked up, focus on making it machine readable. 14:06:22 abr: one conflict was different use of valuemin and valuemax 14:06:58 abr: some of the structural guides, Fred had distinct roles for guides 14:07:46 Fred: Jason sent a note to the list, suggesting we focus on what can a sighted person perceive from a chart. 14:08:30 Jason: My point was that the AT user should be able to access a similar level of information and precision as a sighted viewer would get. 14:08:52 Fred: Did you think my reply was reasonable? 14:10:33 Jason: I think it will depend a lot on the graphic and how much information the author has included. Sometimes the data is unreasonable to include, but the sighted user would still get overall, imprecise sense of the data. 14:11:07 ... values and ranges and other things you would want to know about, that can be approximated by visual inspection, even if exact data isn't included. 14:11:25 Fred: That sounds more like observations that statistical min/max/mean etc. 14:11:29 q+ 14:11:35 q? 14:11:53 Jason: Observations, yes, but we need to think of how to provide that in a systematic way. 14:12:20 abr: good point, approach I have done so far has been annotating charts with raw data 14:13:54 abr: one thing someone brought up last week, was a certain value was encoded on the chart - like x,y position 14:15:28 abr: - not my ideal, but reverse engineering data may be a possible approach, to avoid doubling the size 14:16:07 fe: becomes problematic when you have non linear scales, and polar transformations... 14:16:54 abr: something to think about... I prefer to keep data and representation separately 14:17:58 Jason: I think that's reasonable, but I also think that it's important in those data-heavy cases for authors to include summary data 14:18:45 Fred: That's one reason I was using the ARIA min and max properties all over the place. But that wouldn't do other statistics like medians or trends. 14:19:32 Jason: Yes, there must be reasonable limits. But we also need to be sure that if the full data isn't included in accessible format, then appropriate summary is. 14:19:57 ... For example, I brought up sonification, and you really need to know the data to know what frequencies should be used. 14:22:05 Fred: The other question I had was for when data is represented by aesthetics, such as color or size. Could you have multiple palettes, and just swap one in or the other. Maybe even audio palettes of tones. 14:22:18 Amelia: Author-supplied alternative palettes, or AT-generated? 14:22:40 Fred: Maybe author, but probably AT. 14:23:37 Amelia: That's pretty much what I'd suggested last week, but I'd suggested you'd need the raw data & then use it to create a new mapping. Are you suggesting an AT could map from one color palette to another without needing the data? 14:24:17 Fred: To a degree, although it would be difficult for continuous color. It would be easier with a discrete set of values. 14:24:38 ...Even just to provide pop-up labels or tooltips. 14:25:43 Fred: In RAID, we had a checkbox option to give labels as an enhancement to color. 14:26:17 s/RAID/RAVE? 14:26:58 Amelia: But that's slightly easier, because that's in the same charting software. It's more complicated when the AT doesn't have the raw data, only the file. 14:27:45 Jason: As a reminder, we do have WCAG rule that color should never be the only distinguishing factor. 14:28:02 https://lists.w3.org/Archives/Public/public-svg-a11y/2015Aug/0022.html 14:28:55 Fred: We want to get a clear list of roles in the module as soon as possible. 14:29:13 Amelia: The main change from that summary are that we agreed no special rules for special chart types. 14:30:40 abr: talked about doc role - letting AT know that you are getting into a area with semantic meaning 14:31:08 abr: figure is different 14:31:29 abr: figure role defines how it relates to the larger document 14:33:27 abr: graphics- doc would be the default element for SVG 14:34:26 q? 14:34:32 ack Amel 14:48:51 [long discussion on focus vs point of regard, figure vs graphics-doc: when would we use both, how would they be navigated.] 14:49:39 Fred: Did we, or should we, resolve on the graphics-doc role? 14:50:23 Jason: I'm not sure it's helpful to decide on roles one at a time. I think we need to assess a taxonomy as a whole. 14:57:20 abr: will try to see if graphics-doc children have different properties 15:07:49 [follow up of Fred's email re aria-owns, Amelia suggests maybe an aria-labelledby relationship would have been more appropriate] 15:10:02 trackbot, end telcon 15:10:02 Zakim, list attendees 15:10:02 As of this point the attendees have been fesch, Amelia 15:10:10 RRSAgent, please draft minutes 15:10:10 I have made the request to generate http://www.w3.org/2015/09/04-svg-a11y-minutes.html trackbot 15:10:11 RRSAgent, bye 15:10:11 I see no action items