12:51:57 RRSAgent has joined #dpub-aria 12:51:57 logging to http://www.w3.org/2016/08/04-dpub-aria-irc 12:52:09 trackbot has joined #dpub-aria 12:52:16 Zakim has joined #dpub-aria 12:53:08 Meeting: DPUB-ARIA Weekly Meeting 12:53:11 chair: Tzviya 12:53:15 present+ 12:53:43 agenda: https://lists.w3.org/Archives/Public/public-dpub-aria/2016Aug/0000.html 12:57:15 present+ George_Kerscher 13:00:06 present+ Janina 13:00:09 present+ Rich 13:03:13 present+ MichaelC 13:03:18 present+ Ivan 13:04:53 Tzviya: George raised concerns about how aria-details will be used in real world 13:05:06 ...I logged issue with APG 13:05:28 Rich: ARIA cannot dictate browser implementation 13:06:01 ...AT will find it as long as it's in mappings 13:07:07 George: View of id-ref may disrupt reading from publisher perspective, so we would like guidance for implementation best practices 13:08:25 janina: We have made a commitment to make extended descriptions discoverable in APA 13:08:46 ...We would like to explore this with Web Platforms (with Leonie) 13:09:03 ...It will be intersting to hear how UAs will react to this 13:10:21 Rich: This could be a solution for reading systems, not browsers 13:11:01 ...We had this discussion with the TAG already, and it lasted for years 13:11:41 George: If we implement this in RS, we have ARIA details, pointing to ID of details element, what do we do about hiding
? 13:14:50 Rich: Put something in the CSS that triggers on the attr selector, and display the summary only when user requests it 13:15:10 Ivan: In a sense, want to turn the aria reference into a link 13:15:19 textarea:focus { 13:15:19 background: pink; 13:15:20 } 13:16:07 Ivan: I think this can be accomplished only with javascript 13:16:35 Rich: This can be done by Reading Systems 13:17:55 Ivan: This goes against what we've been saying about not needing specialized reading systems and shifting to standard UAs 13:18:43 Janina: APA will take up work with Web Platforms defining mechanism in HTML 5.x for recognizing extended description 13:19:26 Ivan: It might be helpful to broaden definition, not exclusively tie it to details 13:19:45 ...The question is whether this is HTML feature or CSS feature 13:20:16 Janina: The identification is either HTML or CSS, the rendering is HTML 13:20:46 Ivan: if we have a selector that can express the bridge, that can be done without the core browser involvement 13:21:31 Janina: Goal is for native support in browsers. 13:21:54 ...We need to support discovery and rendering 13:23:39 Tzviya: There is a long-term solution, but what am I supposed to do today? 13:23:59 ... What am i supposed to do for extended description today? 13:24:22 Rich: Add Javascript to book or reading system 13:24:46 Tzviya: Not necessarily possible, which means that there is no solution for extended solution today 13:25:00 s/extended solution/extended description 13:27:46 Janina: We need to make the case that users of reading system require this functionality 13:28:03 Rich: Start with Readium. See if they can implement this. 13:28:54 George: In ARIA 1.1, it says "MUST not hide", please change to "SHOULD not hide" 13:29:48 ...if the publisher wants to allow the AT to trigger the presentation, what is the best mechanism for author to indicate this? 13:30:20 Janina: Author should not be involved. It should be accomplished by AT 13:30:59 George: Configuration of RS tells you whether the extended desc is exposed automatically 13:32:38 Janina: I will provide the implementaion report regarding aria-details 13:33:52 George: Is the toggle mechanism only on details? 13:34:12 Rich: you can always use describedby, which will stringify 13:35:13 Longdesc Implementation Report is at: 13:35:14 http://w3c.github.io/test-results/html-longdesc/cr-report.html 13:39:02 Rich: What do you want to tell authors to do? 13:39:23 Tzviya: Ideally, authors should not touch anything 13:39:49 George: there is also the use case of defaulting to displaying all extended description 13:40:02 Tzviya: I will add that to the APG issue https://github.com/w3c/aria-practices/issues/70 13:40:23 http://rawgit.com/w3c/aria/master/aria/aria.html#aria-details 13:43:07 Rich: will change "MAY" to "SHOULD" 13:43:17 ...will put out a CfC 13:44:40 Janina: If we are going to try get browser support, we need to explain the need for not-sighted readers to access this 13:46:23 Topic: Update about TAG meeting 13:46:43 Rich: Meeting was more about updates 13:46:58 ...I don't think there will be an issue going forward 13:47:25 ...It was more about education. We will meet again at TPAC. 13:49:08 Tzviya: We had talked about going to CR for DPUB-ARIA until we had a sense of extensibility. Thoughts? 13:56:16 Rich: discussion of Apple mappings and whether Safari accesses the DOM 13:59:07 Ivan: If the whole extensibility conversation falls over, then we will run into problems 13:59:23 Rich: I don't think we will have problems with extensibility 14:00:12 ...and we don't want to have to be so concerened with mappings 14:02:42 rrsagent, make logs public 14:02:54 rrsagent, make minutes 14:02:54 I have made the request to generate http://www.w3.org/2016/08/04-dpub-aria-minutes.html tzviya 15:29:11 Zakim has left #dpub-aria 15:56:52 rrsagent, bye 15:56:52 I see no action items