23:00:46 RRSAgent has joined #html-a11y
23:00:46 logging to http://www.w3.org/2014/01/13-html-a11y-irc
23:00:48 RRSAgent, make logs world
23:00:48 Zakim has joined #html-a11y
23:00:50 Zakim, this will be 2119
23:00:50 JatinderMann has joined #html-a11y
23:00:50 ok, trackbot; I see WAI_HTML AT()6:00PM scheduled to start now
23:00:51 Meeting: HTML Accessibility Task Force Teleconference
23:00:51 Date: 13 January 2014
23:00:51 agenda?
23:00:54 agenda+ Review Action items taken up at last meeting
23:00:54 agenda+ Revisit Bug 23980 RE: Naming of focusRing methods http://j.mp/L3I6tf
23:00:54 agenda+ Continue Bug Walkthrough (next up: 23984-23987)
23:00:54 agenda+ Publication path/timeline for Canvas (from PaulC) http://j.mp/KfCUkH
23:00:55 agenda+ Next Meeting
23:01:03 zakim, who is on the phone
23:01:03 I don't understand 'who is on the phone', MarkS
23:01:08 zakim, who is on the phone?
23:01:08 WAI_HTML AT()6:00PM has not yet started, MarkS
23:01:09 On IRC I see JatinderMann, Zakim, RRSAgent, richardschwerdtfeger, IanPouncey, davidb, MarkS, janina, cabanier_, hober, trackbot
23:01:51 zakim, this is WAI_HTML
23:01:51 ok, MarkS; that matches WAI_HTML AT()6:00PM
23:01:59 zakim, who is on the phone?
23:01:59 On the phone I see Rich_Schwerdtfeger, marks, [Microsoft]
23:02:10 zakim, [Microsoft] is Jatinder
23:02:10 +Jatinder; got it
23:02:17 scribe: MarkS
23:03:08 zakim, agenda?
23:03:08 I see 5 items remaining on the agenda:
23:03:09 1. Review Action items taken up at last meeting [from MarkS]
23:03:09 2. Revisit Bug 23980 RE: Naming of focusRing methods http://j.mp/L3I6tf [from MarkS]
23:03:09 3. Continue Bug Walkthrough (next up: 23984-23987) [from MarkS]
23:03:09 4. Publication path/timeline for Canvas (from PaulC) http://j.mp/KfCUkH [from MarkS]
23:03:10 5. Next Meeting [from MarkS]
23:03:37 http://www.w3.org/WAI/PF/HTML/wiki/Summary_of_focusRing_method_naming#Summary
23:04:06 +cabanier
23:04:09 plh has joined #html-a11y
23:04:25 +Plh
23:04:56 zakim, take up item 1
23:04:56 agendum 1. "Review Action items taken up at last meeting" taken up [from MarkS]
23:06:01 +[Microsoft]
23:06:24 zakim, who is making noise?
23:06:35 MarkS, listening for 10 seconds I heard sound from the following: Rich_Schwerdtfeger (25%), marks (5%), Jatinder (14%), cabanier (20%), [Microsoft] (49%)
23:06:36 zakim, [Microsoft] is PaulC
23:06:38 +PaulC; got it
23:06:51 paulc has joined #html-a11y
23:07:36 MS: I will follow up with Jay Munro regarding the two action items on him for last week.
23:07:41 zakim, next item
23:07:41 agendum 2. "Revisit Bug 23980 RE: Naming of focusRing methods http://j.mp/L3I6tf" taken up [from MarkS]
23:07:52 -> http://www.w3.org/WAI/PF/HTML/wiki/Summary_of_focusRing_method_naming#Summary Summary
23:08:21 MS: drawFocusIfNeeded seems to be a favorite at this point.
23:08:41 JM: I am OK with that
23:08:53 RS: : I am OK with that
23:09:08 s/JM/JMann
23:09:24 JMann: drawFocusIfNeeded seems to solve all the issues I originally raised.
23:09:56 ...talked about splitting the methods?
23:10:13 RS: Ian originally wanted to have both together to make it easier on developers. I still think that is a good idea.
23:10:36 RC: If we change the name and clarify purpose in spec, there should be no reason to split them up
23:11:14 JMann: seems like if you are using the 2D context, this is the way to do it. Spoke with Graphic designers that understand this concept
23:11:31 RESOLUTION to change drawSystemFocusRing to drawFocusIfNeeded
23:12:04 zakim, next item
23:12:04 agendum 3. "Continue Bug Walkthrough (next up: 23984-23987)" taken up [from MarkS]
23:12:07 https://www.w3.org/Bugs/Public/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=CR%20HTML%20Canvas%202D%20Context&list_id=30985&order=Importance&product=HTML%20WG&query_format=advanced
23:12:25 -> https://www.w3.org/Bugs/Public/show_bug.cgi?id=23984 23984 Is it possible to implement drawCustomFocusRing? (JM. Moved to Level 2)
23:12:25 -> https://www.w3.org/Bugs/Public/show_bug.cgi?id=23985 23985 drawCustomFocusRing and color scheme (JM. Moved to Level 2)
23:12:25 -> https://www.w3.org/Bugs/Public/show_bug.cgi?id=23986 23986 Current default path
23:12:25 -> https://www.w3.org/Bugs/Public/show_bug.cgi?id=23987 23987 Empty path and drawSystemFocusRing
23:12:53 PLH: some of these are still assigned to CR component
23:13:34 RS: 23984 should not be in the list because it is being moved to L2
23:14:01 ... 23985 same thing
23:14:24 JMann: 23986, which path actually gets drawn?
23:14:38 PLH: I think you are talking about 23987
23:15:06 JMann: if you call it immediately, what happens?
23:15:08 RC: depends on what you have done previously
23:15:15 PLH: Assuming you have not done anything
23:15:41 RC: whatever path is in the canvas at that point, will be the focus area
23:15:53 PLH: The spec states that there is always a current default path, what is it?
23:16:18 http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas_CR/#current-default-path
23:17:02 JMann: scenario 1, just created canvas, call drawFocusIfNeeded, what happens, and just drew a path and called drawFocusIfNeeded what happens
23:17:27 PLH: I will amend the bug
23:17:47 JMann: what do we think should happen?
23:18:04 PLH: I don't think anything should happen, there is no default path when the canvas element has been created
23:18:29 JMann: if you call drawFocusIfNeeded before than you have a region associated with that path
23:18:41 RS: can always have the path be outside the canvas area, nothing gets drawn
23:19:04 ...it should have a default path of some sort
23:19:23 RC: by default a fallback element has not region associated with it.
23:19:52 JMann: I think it should get the bounds of the entire canvas element
23:19:56 RS: Makes sense
23:20:04 RC: that is not in the spec right now right?
23:20:12 RS: no, should be
23:20:37 RC: should that be in the HTML spec? That is where we talk about fallback content
23:21:25 RS: What does context.fill do ?
23:21:31 nothing
23:22:22 RC: if you bring focus to fallback content, but the associated path has not even been drawn, nothing should happen
23:22:26 JMann: agree
23:23:02 JMann: so if I do the beginPath forces UA to cache the last path always.
23:23:03 For CanvasRenderingContext2D objects, the points and lines added to current default path by these methods must be transformed according to the current transformation matrix before they are added to the path.
23:24:04 zakim, who is on the phone?
23:24:04 On the phone I see Rich_Schwerdtfeger, marks, Jatinder, cabanier, Plh, PaulC
23:24:27 RS: 0,0 is path, doesn't go anywhere?
23:24:44 JMann: i think we should just change algorithm to abort
23:24:59 RC: you need to update the region
23:25:13 RS: If you are adding to the path, then yes
23:25:36 RC: updated a11y api with the bounding box of the element
23:25:55 RS: we could put a note that says to make sure that you have created a path
23:26:03 RC: there is always a path
23:26:29 The beginPath() method must empty the list of subpaths in the context's current path so that the it once again has zero subpaths.
23:26:50 JMann: the moment you call beginPath, you have no path until you build on that path . it's empty
23:27:33 ... so we draw the bounding of the canvas, or draw the last path, or we draw 0,0 or we ??
23:28:34 RC: If the current default path is empty, then don't draw anything but set the accessible region back to the original value
23:28:45 JMann: do we all agree that it is an error case?
23:28:52 RC: I think it something an author might do
23:29:05 ...a way to remove the association with the fallback content
23:29:24 JMann: ah to reset a11y dom
23:29:31 ...that is a use case
23:29:38 ...means we shouldn't do nothing
23:30:04 ...so 0,0 or the entire canvas. I like entire canvas, which is still true, but it may not be a real reset.
23:30:13 RC: can we say initial value?
23:30:49 RS: if its the entire canvas the magnifier focuses on entire canvas
23:31:16 JMann: is there a default location?
23:31:24 RS: not that I am aware of
23:31:28 RC: can you make it invisible?
23:31:37 RS: yes
23:32:11 JMann: If we can tie it to the initial value (invisible) then that should cover the use case.
23:33:08 RESOLUTION that initial value should be invisible if author would like to disassociate fallback content with path
23:33:42 s/invisible/invisible in aapi
23:34:23 JMann: does this feel buggy or will developers get this concept
23:35:16 JMann: this should also resolve 23987
23:35:26 https://developer.mozilla.org/en-US/docs/Web/Accessibility/AT-APIs/MSAA/States
23:35:42 RS: states are different on each platform. MSAA has the concept of unavailable
23:35:56 STATE_SYSTEM_INVISIBLE
23:36:29 ...offscreen means not visible, but not necessarily gone.
23:36:46 ...that means disabled, so that wouldn't work
23:37:11 ...if the author really wants to remove it from the AT they should just remove it from the AAPI
23:37:56 JMann: are we expected developers to delete the element and add it back later on?
23:41:40 JMann: the recommend approach for removing your controls would be to change the ARIA state or delete the node. Maybe we should just a no op if the path is empty
23:41:48 RS: so do nothing?
23:41:51 yes
23:42:12 JMann: should be as easy as updating the processing model
23:43:09 RESOLUTION: Update the process to include "if there are zero sub paths in the current path, abort these steps"
23:43:39 RS: we can close 23986 and 23987 when this is done.
23:44:00 https://www.w3.org/Bugs/Public/show_bug.cgi?id=23982
23:44:20 PLH: 23982 focus ring out of canvas is that one closed?
23:45:16 JMann: I don't think the bug reflects that, but we need to get the spec updated and then update the bug
23:46:15 It was agreed that the focus ring would be clipped to the bounds of the canvas area but that the location of the corresponding fallback element would not be clipped and would match the current default path passed.
23:46:31 zakim, agenda?
23:46:31 I see 3 items remaining on the agenda:
23:46:32 3. Continue Bug Walkthrough (next up: 23984-23987) [from MarkS]
23:46:32 4. Publication path/timeline for Canvas (from PaulC) http://j.mp/KfCUkH [from MarkS]
23:46:32 5. Next Meeting [from MarkS]
23:46:42 zakim, take up next item
23:46:42 agendum 4. "Publication path/timeline for Canvas (from PaulC) http://j.mp/KfCUkH" taken up [from MarkS]
23:47:28 https://www.w3.org/Bugs/Public/show_bug.cgi?id=23981
23:48:22 Canvas CR bugs: http://tinyurl.com/kxmqysj
23:49:37 JMann: I'll have Jay close the bugs as soon as the spec is updated
23:50:03 "Informs the user of the canvas location for the fallback element, based on the current path. If the given element has focus, draws a focus ring around the current path following the platform or user agent conventions for focus rings as defined by the user agent."
23:50:30 PC: When will all the changes to the spec be made, and when will the bugs will be closed.
23:50:47 ...next week we should have an agenda item to confirm these bugs are closed
23:51:21 RS: I can confirm that 23978 has been completed
23:51:53 JMann: scrollPathIntoView has been moved to L2 because it requires Path
23:52:35 plh3 has joined #html-a11y
23:53:13 q+ to ask about a potential new issue
23:54:37 " the bounding box of the area to which the user agent is scrolling as the bounding box of the current selection."
23:54:46 https://www.w3.org/Bugs/Public/show_bug.cgi?id=23983
23:55:05 ack plh
23:55:05 plh, you wanted to ask about a potential new issue
23:55:54 http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas_CR/#dom-context-2d-drawsystemfocusring
23:56:17 http://www.w3.org/html/wg/drafts/2dcontext/html5_canvas_CR/#dom-context-2d-drawsystemfocusring
23:58:14 PLH: If i have two checkbox in my canvas and two canvas elements to match, and I call drawFocusIfNeeded. Now, I move focus to the second element, second checkbox and I all drawFocusIfNeeded. I am assuming it does not remove the focus once focus is removed it is up to the author to remove the focus ring
23:58:22 yes
23:58:46 RS: also when author calls .focus
23:59:44 JMann: is dominic in agreement with all of our changes?
23:59:55 RS: I think we should send him an updated draft
00:00:13 JMann: I will follow up with Jay to get all changes implemented so we have a new draft.
00:01:35 PC: I talked to W3C Team and as long as we are removing material to canvas and not adding substantive new material, we can waive the disclosure period, so that is no longer a factor.
00:02:35 PLH: we have two problems. We have added some text to this spec. Also, with changing the name of the method...
00:03:09 PC: PLH can you add this to the discussion with Ian Jacobs?
00:03:11 PLH: OK
00:03:55 PC: doesn't look like we will have much of a delay going into LC. If we go back into CR what the min time will be. If another disclosure is required, the min length would match the 6 week period anyway, so we should be OK.
00:04:38 ...main thing is that we need to get this into LC ASAP
00:04:56 RS: when we get this draft, there is an apple guy that needs to look at it as well.
00:05:20 RC: I think we have addressed his concerns as well. He may need to be convinced.
00:05:32 JMann: will be worth it to share our changes and reasoning with him.
00:05:37 RC: I'll email him.
00:05:48 JMann: how long to get changes in?
00:06:07 RC: Should be a small patch, the AAPI stuff might take a few weeks.
00:06:39 PLH: Need dominic to update implementation in Blink
00:06:46 JMann: we also need test suites as well
00:07:02 PLH: I have some tests, but nothing that looks at the AAPI
00:07:27 https://github.com/w3c/web-platform-tests/pull/457
00:09:25 PC: During this week, if the canvas editors are closing out bugs, they should be prepping LC document as well
00:09:25 ACTION: plh to update his tests in https://github.com/w3c/web-platform-tests/pull/457
00:09:25 Created ACTION-225 - Update his tests in https://github.com/w3c/web-platform-tests/pull/457 [on Philippe Le Hégaret - due 2014-01-21].
00:09:41 ...we have to do a CfC, earlier the better
00:09:55 ...probably what we would do is have a heartbeat for L2 as well
00:10:21 ...we will be doing heartbeats in early Feb
00:10:47 zakim, next item
00:10:47 agendum 5. "Next Meeting" taken up [from MarkS]
00:10:55 -cabanier
00:10:56 -Jatinder
00:10:56 MS: same time, same place next week
00:10:56 -Rich_Schwerdtfeger
00:10:58 -Plh
00:10:58 -PaulC
00:11:02 -marks
00:11:03 WAI_HTML AT()6:00PM has ended
00:11:03 Attendees were Rich_Schwerdtfeger, marks, Jatinder, cabanier, Plh, PaulC
00:11:16 rrsagent, make minutes
00:11:16 I have made the request to generate http://www.w3.org/2014/01/13-html-a11y-minutes.html MarkS
00:12:12 zakim, bye
00:12:12 Zakim has left #html-a11y
01:47:55 richardschwerdtfeger has joined #html-a11y
03:06:12 richardschwerdtfeger has joined #html-a11y