21:59:49 <RRSAgent> RRSAgent has joined #html-a11y
21:59:49 <RRSAgent> logging to http://www.w3.org/2014/09/08-html-a11y-irc
21:59:51 <trackbot> RRSAgent, make logs world
21:59:51 <Zakim> Zakim has joined #html-a11y
21:59:53 <trackbot> Zakim, this will be 2119
21:59:53 <Zakim> ok, trackbot; I see WAI_HTML AT()6:00PM scheduled to start in 1 minute
21:59:54 <trackbot> Meeting: HTML Accessibility Task Force Teleconference
21:59:54 <trackbot> Date: 08 September 2014
22:02:05 <MarkS> zakim, who is on the phone?
22:02:05 <Zakim> WAI_HTML AT()6:00PM has not yet started, MarkS
22:02:07 <Zakim> On IRC I see RRSAgent, jaymunro, rubys, halindrome, richardschwerdtfeger, newtron, janina, IanPouncey, MarkS, joanie, cabanier, hober, sivoais, liam, trackbot
22:02:23 <MarkS> zakim, this is 2119
22:02:23 <Zakim> ok, MarkS; that matches WAI_HTML AT()6:00PM
22:02:30 <MarkS> zakim, who is on the phone?
22:02:30 <Zakim> On the phone I see Rich_Schwerdtfeger, Sam, MarkS, cabanier, [Microsoft]
22:02:33 <jaymunro> zakim, microsoft has me
22:02:33 <Zakim> +jaymunro; got it
22:02:58 <MarkS> zakim, who is making noise?
22:03:18 <Zakim> MarkS, listening for 12 seconds I heard sound from the following: Rich_Schwerdtfeger (80%), cabanier (24%)
22:03:41 <rubys> Meeting: Canvas Task Force
22:03:41 <rubys> Chair: Sam Ruby
22:03:41 <rubys> agenda+ Testing Status
22:03:41 <rubys> agenda+ Implementations Update
22:03:41 <rubys> agenda+ Level 1 CR
22:03:41 <rubys> agenda+ Heartbeat Level 2
22:03:41 <rubys> agenda+ Next Meeting
22:04:06 <MarkS> scribe: MarkS
22:04:25 <MarkS> zakim, take up next item
22:04:25 <Zakim> agendum 1. "Testing Status" taken up [from rubys]
22:04:29 <rubys> http://lists.w3.org/Archives/Public/public-canvas-api/2014JulSep/0027.html
22:05:23 <MarkS> JM: assembled these items from recent emails
22:05:33 <MarkS> ...have drawFocus tests.  Some may need to be updated.
22:05:42 <MarkS> ...don't know if there are any tests for Hit Regions
22:06:03 <MarkS> ...Rich gave a great list of methods for testing.
22:06:13 <MarkS> RS: mark, how many tests do we have
22:06:35 <MarkS> MS: no tests since the new features were added
22:06:49 <MarkS> RS: what do we have?
22:11:01 <jaymunro> http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas_CR/#dom-context-2d-drawfocusifneeded
22:11:50 <MarkS> From PLH:
22:11:52 <MarkS> From what I understand hit regions to be about, those are adding
22:11:52 <MarkS> information on mouse events (region) and can make routings events to DOM
22:11:52 <MarkS> elements automatic. Since we don't retarget, the target of a click event
22:11:52 <MarkS> in within a hit region in a canvas is still the canvas element. No where
22:11:53 <MarkS> in those steps do we talk about informing the user by the way.
22:11:58 <MarkS> Btw, regarding step 4 of drawFocusIfNeeded, it currently says:
22:11:58 <MarkS> [[
22:11:58 <MarkS> 4. Inform the user of the location given by the path. The full location
22:11:59 <MarkS> of the corresponding fallback element is passed to the accessibility
22:12:01 <MarkS> API, if supported. User agents may wait until the next time the event
22:12:05 <MarkS> loop reaches its "update the rendering" step to inform the user.
22:12:07 <MarkS> Note: "Inform the user", as used in this section, could mean calling a
22:12:09 <MarkS> system accessibility API, which would notify assistive technologies such
22:12:11 <MarkS> as magnification tools. To properly drive magnification based on a focus
22:12:13 <MarkS> change, a system accessibility API driving a screen magnifier needs the
22:12:15 <MarkS> bounds for the newly focused object. The methods above are intended to
22:12:21 <MarkS> enable this by allowing the user agent to report the bounding box of the
22:12:23 <MarkS> path used to render the focus outline as the bounds of the element
22:12:25 <MarkS> element passed as an argument, if that element is focused, and the
22:12:27 <MarkS> bounding box of the area to which the user agent is scrolling as the
22:12:29 <MarkS> bounding box of the current selection.
22:12:31 <MarkS> ]]
22:12:35 <MarkS> Should the step 4 read instead, since you want to given the location the
22:12:37 <MarkS> current path used for the focus ring, and NOT the location of the
22:12:39 <MarkS> fallback element:
22:12:41 <MarkS> [[
22:12:43 <MarkS> 4. Inform the user of the location given by the current path. The full
22:12:45 <MarkS> location of the corresponding current path is passed to the
22:12:51 <MarkS> accessibility API, if supported. User agents may wait until the next
22:12:53 <MarkS> time the event loop reaches its "update the rendering" step to inform
22:12:55 <MarkS> the user.
22:15:27 <MarkS> RS: When you do the association of the path with the fallback element, that gives the fallback element a new location
22:15:38 <MarkS> RC: yes
22:15:41 <MarkS> MS: That makes sense
22:17:01 <MarkS> RC: If this is not working correctly in FF, file a bug, send me a file and I'll take a look
22:17:23 <MarkS> RS: The issue is that the location was being reported for the fallback element, not the path
22:18:07 <MarkS> ACTION: for MarkS to create a test file and send to Rik for debugging
22:18:07 <trackbot> Error finding 'for'. You can review and register nicknames at <http://www.w3.org/WAI/PF/HTML/track/users>.
22:18:15 <MarkS> ACTION: MarkS to create a test file and send to Rik for debugging
22:18:15 <trackbot> Created ACTION-283 - Create a test file and send to rik for debugging [on Mark Sadecki - due 2014-09-15].
22:18:28 <MarkS> RC: create a bugzilla bug, is better
22:20:10 <MarkS> RS: Mark in your test file you have two hit regions.  We need to test that multiple hit regions are supported.  Can use the same test file for multiple tests.  We need to test a div with aria markup.
22:20:39 <MarkS> ...need to make sure those location values can be overridden
22:20:57 <MarkS> ...I can run tests here
22:22:09 <MarkS> MS: I've had success creating demos, they just need to be converted into simple test cases
22:22:28 <MarkS> RS: How many test cases do we want?
22:22:54 <MarkS> ...need tests for scrolling and moving the window
22:24:35 <MarkS> MS: I would love to have a list of testable statements that need tests written
22:24:42 <MarkS> RS: I can get started on that
22:24:47 <MarkS> ...maybe post them on the wiki
22:25:52 <jaymunro> https://www.w3.org/wiki/HTML/Canvas_Task_Force/Work_Statement   (one area)
22:26:50 <jaymunro> https://www.w3.org/wiki/HTML/Canvas_Task_Force/  (root)
22:26:57 <MarkS> "The methods above are intended to enable this by allowing the user agent to report the bounding box of the path used to render the focus outline as the bounds of the element element passed as an argument, if that element is focused, and the bounding box of the area to which the user agent is scrolling as the bounding box of the current selection."
22:27:15 <MarkS> "If the focus area is not on the screen, then scroll the focus outline into view by aligning it to the top when it receives focus.
22:28:27 <MarkS> RS: Firefox doesn't currently scroll to the top of the page
22:28:51 <MarkS> ...will need a test file with a lot of space before the canvas to test this
22:32:30 <richardschwerdtfeger> https://www.w3.org/wiki/HTML/Canvas_Task_Force/CR-Test
22:33:29 <MarkS> SR: Do we have any dates for getting this work done?
22:35:00 <MarkS> RS: lets aim to get this done by the end of the month
22:35:14 <MarkS> SR: All tests will be written and run by the end of the month
22:36:08 <MarkS> RS: We can record results there as well
22:36:25 <MarkS> zakim, take up next item
22:36:25 <Zakim> agendum 2. "Implementations Update" taken up [from rubys]
22:37:09 <MarkS> MS: I've had success with these features in Firefox Nightly and Chrome Canary
22:37:59 <MarkS> ...based on preliminary testing, we have support in those two browsers
22:38:22 <MarkS> RC: Anyone test in Safari 8?
22:38:36 <MarkS> ...I recently added support for drawFocus
22:38:47 <MarkS> RS: do they have any issues with Hit Regions?
22:38:56 <MarkS> RC: no, it just hasn't been implemented yet
22:39:01 <MarkS> zakim, take up next item
22:39:01 <Zakim> agendum 3. "Level 1 CR" taken up [from rubys]
22:39:34 <MarkS> JM: I think the only thing that is holding up progress is testing
22:39:43 <MarkS> SR: That is also my understanding
22:39:49 <MarkS> zakim, take up next item
22:39:49 <Zakim> agendum 3 was just opened, MarkS
22:39:54 <MarkS> zakim, close item 3
22:39:54 <Zakim> agendum 3, Level 1 CR, closed
22:39:55 <Zakim> I see 2 items remaining on the agenda; the next one is
22:39:55 <Zakim> 4. Heartbeat Level 2 [from rubys]
22:39:56 <MarkS> zakim, take up next item
22:39:56 <Zakim> agendum 4. "Heartbeat Level 2" taken up [from rubys]
22:40:27 <MarkS> SR: I think the plan is to switch to ReSpec?
22:40:28 <MarkS> JM: I haven't heard that, but its possible
22:40:53 <MarkS> RC: I think that is true for HTML (moving to respec) but I don't know about canvas
22:41:16 <MarkS> JM: since canvas is part of that same document, then perhaps canvas will go the same route
22:41:24 <chaals> chaals has joined #html-a11y
22:41:28 <MarkS> SR: no need for a heartbeat then
22:41:33 <MarkS> zakim, take up next item
22:41:33 <Zakim> agendum 5. "Next Meeting" taken up [from rubys]
22:41:50 <MarkS> SR: we should at least change the IRC channel
22:41:59 <MarkS> ...also would appreciate a different time slot
22:42:13 <MarkS> RC: two hours earlier?
22:42:26 <MarkS> MS: WFM
22:42:26 <MarkS> RS: i can only do an hour earlier
22:42:47 <MarkS> JM: I can also do 1 hour earlier or 90 minutes earlier
22:43:04 <MarkS> JM: should we consider a different day?
22:43:12 <MarkS> ...tuesday and friday work well for me
22:44:09 <newtron> newtron has joined #html-a11y
22:44:39 <MarkS> RS: I can do Friday afternoon 2Central
22:44:54 <MarkS> MS: WFM
22:44:58 <MarkS> JM: same
22:45:14 <MarkS> SR: 9/26 for next meeting?
22:45:40 <MarkS> ...bi-weekly
22:46:07 <MarkS> MS: #canvas-api for channel name?
22:46:11 <MarkS> [agreement]
22:46:27 <MarkS> Next meeting will be 9/26 in #canvas-api
22:46:39 <Zakim> -cabanier
22:46:40 <Zakim> -Rich_Schwerdtfeger
22:46:40 <Zakim> -Sam
22:46:44 <Zakim> -[Microsoft]
22:46:45 <Zakim> -MarkS
22:46:45 <Zakim> WAI_HTML AT()6:00PM has ended
22:46:46 <Zakim> Attendees were Rich_Schwerdtfeger, Sam, MarkS, cabanier, jaymunro
22:46:50 <MarkS> rrsagent, make minutes
22:46:50 <RRSAgent> I have made the request to generate http://www.w3.org/2014/09/08-html-a11y-minutes.html MarkS
22:46:56 <MarkS> yes, I can do that
22:47:42 <newtron_> newtron_ has joined #html-a11y
23:07:35 <newtron> newtron has joined #html-a11y
23:09:12 <newtron> newtron has joined #html-a11y