22:54:10 RRSAgent has joined #html-a11y 22:54:10 logging to http://www.w3.org/2014/03/03-html-a11y-irc 22:54:12 RRSAgent, make logs world 22:54:13 Meeting: Canvas Accessibility Sub-Group Teleconference 22:54:14 Zakim, this will be 2119 22:54:14 ok, trackbot; I see WAI_HTML AT()6:00PM scheduled to start in 6 minutes 22:54:15 Meeting: HTML Accessibility Task Force Teleconference 22:54:15 Date: 03 March 2014 22:54:20 scribe: MarkS 23:00:44 richardschwerdtfeger has joined #html-a11y 23:01:13 JatinderMann has joined #html-a11y 23:01:40 zakim, who is on the phone 23:01:40 I don't understand 'who is on the phone', MarkS 23:01:45 zakim, who is on the phone? 23:01:45 apparently WAI_PFWG(HTML TF)10:00AM has ended, MarkS 23:01:46 On IRC I see JatinderMann, richardschwerdtfeger, RRSAgent, jaymunro, trackbot, MarkS, janina, Zakim, hober, cabanier 23:01:54 zakim, this is WAI_PFWG 23:01:55 sorry, MarkS, I do not see a conference named 'WAI_PFWG' in progress or scheduled at this time 23:02:26 present+ JatinderMann 23:02:27 zakim, this is 2119 23:02:27 ok, MarkS; that matches WAI_HTML AT()6:00PM 23:02:36 zakim, who is on the phone 23:02:36 I don't understand 'who is on the phone', MarkS 23:02:37 zakim, who is on the phone? 23:02:37 On the phone I see MarkS, Rich_Schwerdtfeger, [Microsoft], [Microsoft.a] 23:02:41 +cabanier 23:02:57 zakim, [Microsoft] is Jatiner_Mann 23:02:57 +Jatiner_Mann; got it 23:03:09 zakim, microsoft.a has me 23:03:09 +jaymunro; got it 23:03:10 zakim, [Microsoft.a] is Jay Munro 23:03:11 I don't understand '[Microsoft.a] is Jay Munro', MarkS 23:03:26 zakim, take up first item 23:03:26 I don't understand 'take up first item', MarkS 23:03:33 zakim, agenda? 23:03:33 I see 3 items remaining on the agenda: 23:03:34 1. Walk through Hit Regions spec to discuss priority for implementation [from MarkS] 23:03:34 2. Possible Testing and/or Coordination meeting at [from http://www.w3.org/wiki/HTML/wg/2014-04-Agenda HTML WG F2F April 7-9 via MarkS] 23:03:34 3. Next Meeting [from MarkS] 23:03:38 zakim, take up next item 23:03:38 agendum 1. "Walk through Hit Regions spec to discuss priority for implementation" taken up [from MarkS] 23:04:55 http://lists.w3.org/Archives/Public/public-canvas-api/2014JanMar/0159.html 23:05:35 Do we plan on supporting nested regions with hierarchical/ancestor relationships in L1? 23:05:46 RC: I had not implemented that yet. No parent ID 23:07:02 ...this is about how multiple regions on the page behave. 23:07:17 RS: Is this like a Z-order? 23:07:48 RC: This is a parent ID. Inherit z-order and other 23:08:17 RC: This is a pseudo DOM 23:09:34 ...the hierarchy is ignored in the fallback content, the relationship would be established using this parent ID 23:09:56 ...where it bubbles, it follows the DOM order. 23:10:13 RS: mouse event will bubble up the parent tree, like anything else in the DOM. 23:10:58 ...with Hit Testing, it would be nice if you have a parent region and a child, you would think that the child would get first chance to record the hit, otherwise bubble up to the parent. 23:11:04 http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#the-canvas-element 23:12:04 A hit region A is an ancestor region of a hit region B if B has a parent and its parent is either A or another hit region for which A is an ancestor region. 23:14:34 RS: lets say I had a container div in the fallback content, and then I had a B inside of it, I might have multiple children, each of those would have a hit region. The parent would contain all of those items. You would have to go through... 23:14:41 RC: First you set up the bigger region, then the smaller one. 23:14:47 RS: so its up to the author 23:15:02 RC: the fallback content does not need to match. 23:15:18 s/fallback/fallback nesting 23:16:53 ...subtract the children's pixels from the parent. 23:18:13 RS: If its a list, the children have to be higher in the list than their parent in order to get a hit. 23:18:23 RC: the algorithm takes care of that. 23:18:32 ...is the parent ID necessary for L1 23:19:42 RS: Do we have anything on here that says, when something is drawn it goes to the top of the region list? 23:20:25 19 Clear regions that cover the pixels in region's set of pixels on this scratch bitmap. 23:21:07 +??P5 23:21:44 zakim, who's on the phone? 23:21:44 On the phone I see MarkS, Rich_Schwerdtfeger, Jatiner_Mann, [Microsoft.a], cabanier, ??P5 23:21:46 [Microsoft.a] has jaymunro 23:21:55 zakim, ??P5 is me 23:21:55 +janina; got it 23:22:25 RC: I think this is for the AAPI to understand the relationship between regions. 23:23:32 RS: You have a new hit region, bind it to the element. Your fallback content will have the structural hierarchy that will be used in the AAPI. Since the options are in the listbox, there is an implied relationship there. 23:24:21 RS: The roles are not enough for the AAPI. 23:25:02 ...if you create a region that has a checkbox role, how do you specify its state? 23:26:12 ...what happens with an accessibility checker. i can't walk the structure. its sitting inside a virtual dom in the canvas 23:26:27 RC: it would expose the hit regions DOM 23:27:04 RS: not sure why they are doing this. 23:28:49 ...there are a number of issues with this that are problematic. You can't convey state with this. 23:29:43 ...they are trying to restrict fallback content to only HTML controls. 23:30:12 ...I wouldn't include any of this as it stands. 23:30:25 ...the browser would have to create new api's to expose this dom 23:30:54 RC: The WHAT WG spec has been updated to be less restrictive regarding elements that can be used for fallback content 23:31:51 The arguments object's control member is not one of the following: 23:31:51 null 23:31:51 an a element that represents a hyperlink 23:31:51 a button element 23:31:51 an input element whose type attribute is in one of the Checkbox or Radio Button states 23:31:51 an input element that is a button 23:31:51 a select element with a multiple attribute or a display size greater than 1 23:31:51 an option element that is in a list of options of a select element with a multiple attribute or a display size greater than 1 23:31:52 a sorting interface th element 23:31:52 an element that would not be interactive content except for having the tabindex attribute specified 23:31:52 a non-interactive table, caption, thead, tbody, tfoot, tr, td, or th element 23:34:10 RS: What if when your fallback content is a grid or a list box. all behavior is managed in a container in fallback. it will bubble up to the parent. 23:34:26 ...why would it be limited to elements with tabindex 23:35:12