16:57:22 RRSAgent has joined #DPUB 16:57:22 logging to http://www.w3.org/2015/10/09-DPUB-irc 16:57:34 rrsagent, make logs public 16:57:54 present Charles LaPierre 16:59:22 Meeting: Weekly DPUB A11Y TF Meeting 17:00:42 dkaplan3 has joined #dpub 17:02:17 rego has joined #dpub 17:02:44 Topic: feedback about the extended description for PF 17:02:59 dauwhe has joined #dpub 17:03:03 present+ deborah_kaplan 17:03:24 charles, read the document in Dropbox and my question is what about "Custom Elements" 17:04:46 Deborah, we haven't added anything just filled in what PF gave us. 17:05:50 Charles, I think its important to include this but we may not have to fill it all out we could get Mark to help since he is trying to push this new tech forward as a viable option to extended long desc and alternative representation of image content. 17:06:29 mia, we need to get this by next Friday 17:08:33 mia, can you ask Mark to get us this for us 17:09:13 charles, sure I will reach out to Mark to get this info and give him all the row headers and he can get us the info. 17:10:31 deborah, do you all agree on the writeup on discoverable, skippable etc… 17:10:46 mia, yeah I think this all make sense. 17:11:06 deborah, I can do a 2nd pass then give it to Tzviya to send out to the larger group. 17:11:20 rego has joined #dpub 17:11:44 …, I am not sure about SVG, and imageMap when did this become a player?? 17:12:13 …, also not sure about webAnnotations. 17:12:34 charles, I think webAnnotations could be a viable solution once its all fleshed out. 17:12:55 deborah, but we only have the public working draft to go on. 17:13:48 mia, present technology should be one column and there may be future work which could be a * next to work that is not in reality right now 17:14:42 mia, we need to be clear on is this based on "Current" technology not "Pending / Working Drafts" etc… 17:15:36 we are on a webinar want to join us? 17:19:45 present+ doug Sheppards 17:21:18 s/Sheppards/schepers 17:21:52 Not restricted to images 17:21:52 Note from Dpub: For clarity, we suggest rephrasing to "Works for non-image content" 17:23:01 doug, yes for Annotations and SVG 17:24:01 …, SVG has always had text as text, it does not have structured text as data , but with ARIA we could make SVG more like HTML 17:24:38 …, SVG is not only about graphics, text is been a part since begining, and also has metadata 17:24:56 …, structured documents from SVG but may not be best use of it 17:25:01 rego has joined #dpub 17:25:26 …, SVG should not be used for rich document structures, but you could if you wanted. 17:25:40 mia, just because you can doesn't mean you should. 17:26:11 doug, the question is can any AT interact with the structured content so that it is meaningful for the user 17:26:46 …, yes in SVG but for highly structured content it may not be best sutied 17:27:22 …, SVG has links, text, nesting. you just can't say this is a paragraph, list or block quote… it depends on how much richness 17:27:50 …, really depends on what you need. 17:28:12 …, uses ARIA roles exclusively 17:28:38 Can hold rich content 17:29:06 doug, yes for both 17:29:07 Same technique for different objects 17:30:04 doug, if you are trying to say this is a replacement for describedAt… 17:30:21 deborah, yes but this is for any object not just for images. 17:30:32 doug, I am not sure. 17:30:38 Reusable in multiple content Note from Dpub: "contexts"? 17:31:08 deborah, use case: 15 text books use the same description external 17:31:16 …, update it once 17:31:37 doug, SVG is not suitable , Web Annotations yes. 17:31:40 Description clearly associated with object 17:31:59 Clear which associated object is the description 17:32:22 doug, Web Annotations yes: SVG no 17:32:32 Not bloat primary content page 17:33:00 doug, Web Annotations Yes not bloat, SVG no 17:33:06 Exposed meaningfully to the accessibility APIs and UA 17:33:28 doug, yes but AT would have to support webAnnotations 17:34:04 …, N/A for SVG 17:34:18 Able to pass structured content to an additional specialized user agent 17:35:42 deborah, here is a map and here is a 3d image of it… or charml 17:36:15 doug, depends on modality.. if your looking for footnote etc… you wouldn't use SVG and would use web Annotations 17:36:58 deborah, this requirement was pushed by George… 17:39:24 doug, SVG satisfy this. I would want there to be a link in there for a 3D image file. describedAt couldn't but could bring you to a page with multiple formats. 17:40:03 rego has joined #dpub 17:40:04 dauwhe has joined #dpub 17:40:43 …, so I am not sure this requirement make sense if describedAt can't handle this it may not make sense to force this requirement on other potential options. 17:41:45 Discoverable meaningfully by any current AT. 17:42:17 doug, webAnnotations No. SVG yes 17:42:25 …, depending on AT 17:42:42 deborah, but SVG doesn't offer outside of ARIA? 17:42:58 doug, title element, and description element 17:43:42 …, not sure if at supports this, would have to test 17:45:51 …, descriptions is hidden by default 17:45:52 Skippable meaningfully by any current AT 17:46:43 doug, svg wrapping bitmat "clown technique" not sure what is the thought behind this…. 17:47:16 deborah, must test. the skippable 17:47:35 Able to be accessed without using a screen reader in any current UA 17:47:40 deborah, will test 17:47:46 Hideable from the visual meaningfully by any current AT 17:47:55 deborah, will test 17:48:19 doug, if webAnnotations takes off this will be a HUGE boom for Accessibility! 17:49:40 …, one of the first things they are spec'ing out is find text "fuzzy matching" etc… 17:51:51 deborah, I will put this in our GitHub repo. and will incorporate these changes and do it right now. 17:52:34 s/clown/clown car 17:53:09 present+ Mia Lipner 17:53:45 scribe: clapierre 17:54:26 deborah, I really wanted to know if SVG should be used for all of this or not… 17:54:47 mia, sounded like it "could technically" be done but probably not the best use for SVG 17:56:10 SVG is a different technique, not a replacement for describedBy/At 17:56:27 s/boom/boon 17:57:48 if you presuppose the solution is describedBy/At, then you're not considering equally (or more) accessible possibilities done via SVG 17:59:38 agreed, shepazu, which is really the point of this document. DPub accessibility wanted to pull back from saying "could we have this feature" and reframe it as "we have this set of requirements we need met." So this matrix we are creating is to compare all of the proposed solutions with the requirements we have. 18:00:16 rego has joined #dpub 18:08:11 clapierre has left #dpub 18:09:26 clapierre has joined #DPUB 18:09:43 rrsagent, draft minutes 18:09:43 I have made the request to generate http://www.w3.org/2015/10/09-DPUB-minutes.html clapierre 18:19:15 rego has joined #dpub 18:30:15 rego has joined #dpub 18:51:16 rego has joined #dpub 18:52:09 dauwhe has joined #dpub 19:02:25 rego has joined #dpub 19:17:25 rego has joined #dpub 19:41:22 rego has joined #dpub 19:50:22 rego has joined #dpub 20:19:12 Karen has joined #dpub 20:27:22 rego has joined #dpub 20:42:31 rego has joined #dpub 20:51:33 rego has joined #dpub 21:02:41 rego has joined #dpub 21:11:41 rego has joined #dpub 21:20:41 rego has joined #dpub 21:31:40 rego has joined #dpub 21:42:42 rego has joined #dpub 21:53:42 rego has joined #dpub 22:02:41 rego has joined #dpub 22:13:41 rego has joined #dpub 22:23:18 clapierre has joined #DPUB 22:25:05 rego has joined #dpub 22:34:05 rego has joined #dpub 22:36:50 clapierre has left #dpub 22:53:12 rego has joined #dpub 23:02:13 rego has joined #dpub 23:15:13 rego has joined #dpub