14:57:49 RRSAgent has joined #html-a11y
14:57:49 logging to http://www.w3.org/2015/07/02-html-a11y-irc
14:57:51 RRSAgent, make logs world
14:57:51 Zakim has joined #html-a11y
14:57:53 Zakim, this will be 2119
14:57:53 I do not see a conference matching that name scheduled within the next hour, trackbot
14:57:54 Meeting: HTML Accessibility Task Force Teleconference
14:57:54 Date: 02 July 2015
14:58:01 present+ janina
14:58:08 richardschwerdtfeger has joined #html-a11y
15:00:48 paulc has joined #html-a11y
15:00:49 Present+ Rich
15:01:03 waves
15:01:12 JF has joined #html-a11y
15:01:13 s/waves//
15:01:14 LJWatson has joined #html-a11y
15:01:25 present+ LJWatson
15:01:31 scribe: janina
15:01:47 present+ JF
15:02:01 chair: Chaals
15:02:02 agenda+ any other items for the agenda?
15:02:02 agenda+ transcript: CfC resolution
15:02:02 agenda+ are we on track for canvas
15:02:03 agenda+ Web Components
15:02:03 agenda+ Action item review: https://www.w3.org/WAI/PF/HTML/track/actions/open
15:02:38 present+ Liam_Quin
15:02:53 agenda+ face to face meeting
15:03:56 present+ paulc
15:04:05 present+ Joanie
15:04:21 zakim, drop agendum 1
15:04:21 agendum 1, any other items for the agenda?, dropped
15:05:31 zakim, next item
15:05:31 agendum 2. "transcript: CfC resolution "
15:05:35 ... taken up [from chaals]
15:06:07 cn: We are taking up the doc -- Result of our CfC
15:06:28 cn: We'll set up on W3C github
15:06:44 cn: However, prefer to use W3C Issue Tracker
15:07:06 +1 to W3C Tracker
15:07:31 cn: Any objection to the above?
15:07:34 [crickets]
15:07:42 +1
15:08:08 +1 to the working proposal
15:08:18 cn: Next issue -- How to move forward
15:08:27 IanPouncey has joined #html-a11y
15:09:00 cn: Concerns include properly encapsulated ... building on Joanie's Longdesc
15:09:22 cn: We have 5 alternatives on linking right now in order to see available options
15:09:30 cn: We're not takingall to rec, of course
15:09:35 cn: Somehow, we get to 1
15:10:04 cn: We propose to published an FPWD with all 5, but clearly document that at least 4 are expected to go away by rec time
15:10:24 cn: One reason for early FPWD is to start the RAND exclusion clock
15:10:42 s/RAND/patent/
15:10:57 Q+
15:11:03 cn: Also, a formal draft -- the FPWD -- arguably gets better review
15:11:05 ack jf
15:11:20 jf: How weill we narrow 5 down to 1?
15:11:30 sivoais has joined #html-a11y
15:11:41 cn: We'll look for agreement to implement
15:11:53 cn: That will influence what stays, clearly
15:12:07 cn: Next we would look at objections and their rationales
15:12:31 cn: Then we ask the HTML WG (or perhaps by then Web Apps) what draws least objections
15:12:45 cn: If nothing implemented, then we can't go further, of course
15:13:06 cn: Perhaps code in content, or perhaps in browser ...
15:13:36 cn: If we have multiple options implemented, we ask preference
15:13:51 q+
15:13:56 ack pa
15:14:10 pc: How to you propose to ask implementers that question?
15:14:20 cn: Will propose to the HTML-WG directly
15:14:43 cn: We'll take it directly to the Media TF
15:15:09 cn: Key is sufficient feedback from enough implementors
15:15:17 Q+
15:15:42 ack jf
15:16:13 jf: It was my impression that Media TF F2F in April gave us a general direction consensus
15:16:45 jf: There was fine tuning to do, but the basics were agreed, I believe
15:17:05 cn: Yes, a consensus on a particular direction, but it had two posibilities still
15:17:11 cn: Both are in this doc
15:17:46 cn: For completeness, per advice of the Media TF Chair, we've also looked at other suggestions previously made and added those as well
15:18:22 cn: I expect people will gravitate to one of the two discussed in TF F2F
15:18:56 cn: Difference today is we have a doc that shows what the spec looks like laid out in candidate form
15:19:19 cn: I expect this cycle just once--but that depends on getting implementations
15:19:58 q+
15:20:02 cn: Is there objection here toward going to FPWD with multiple approaches listed?
15:20:15 jf: Feels a bit wierd process
15:20:20 ack pa
15:20:28 pc: Agreed
15:20:33 q+
15:20:43 pc: Can't recall this approach previously
15:20:56 q+
15:20:57 pc: I'm trying to think if anything wrong with this approach
15:21:24 q+ to explain who would be upset and how…
15:21:26 pc: Can't think of an example of this approach previously, but seems possibly the best plan -- just unusual
15:21:27 ack ja
15:21:44 JS: only other way I see to go is have 5 alternative documents which seems excessive.
15:21:53 ack me
15:21:53 chaals, you wanted to explain who would be upset and how…
15:21:56 Q+
15:22:20 cn: Not sure about precedent -- Certainly docs have changed as work continues
15:22:32 cn: Patent search folks would be most annoyed, probably
15:23:22 cn: Perhaps we get that kind of objection -- then we're figuring out what to do with the objection
15:24:17 cn: It's possible we publish, then near end of patent disclosure period we get exclusions, and we're looking at how to proceed
15:24:22 cn: Believe that's low probability
15:25:17 q+
15:25:23 ack jf
15:25:31 cn: It would be far less efficient to start on one option, get someway down the road, then have pushback that sends us to another option ...
15:26:04 jf: Think this doc is a combo of three separate approaches in wiki
15:26:54 cn: One clear way we have progress is that some ideas suggested in the F2F are now demonstrably problematic, because we have this spec
15:27:03 cn: That's valuable
15:27:32 cn: Out of F2F src and track seemed equal, but no longer
15:27:35 I suggest we explicitly ask the W3C team if publishing a FPWD with multiple choices of approaches is appropriate. I would rather "ask for permission" than "ask for forgiveness".
15:27:42 ack pau
15:28:00 ack li
15:28:00 pc: I suspect we should ask permission rather than chance forgivness on this approach. I expect we'd get permission, but should ask
15:28:03 q+
15:28:26 lq: Reason for WD is we haven't decided on a final approach
15:28:27 q+ to say "yes we will (have to" get permission
15:28:38 ack me
15:28:38 chaals, you wanted to say "yes we will (have to" get permission
15:28:43 lq: Almost any WD that's short of LC has issues
15:29:05 cn: We have to get permission to go FPWD. So, we will explicitly ask
15:29:17 zakim, close this item
15:29:17 agendum 2 closed
15:29:18 I see 4 items remaining on the agenda; the next one is
15:29:18 3. are we on track for canvas [from chaals]
15:29:41 rs: Mark not here, nor on line at the moment
15:29:46 rs: We don't know any progress
15:30:24 zakim, close this item
15:30:24 I do not know what agendum had been taken up, chaals
15:30:29 zakim, close item 4
15:30:29 agendum 4, Web Components, closed
15:30:30 I see 3 items remaining on the agenda; the next one is
15:30:30 3. are we on track for canvas [from chaals]
15:30:39 zakim, close item 3
15:30:39 agendum 3, are we on track for canvas, closed
15:30:40 I see 2 items remaining on the agenda; the next one is
15:30:40 5. Action item review: https://www.w3.org/WAI/PF/HTML/track/actions/open [from chaals]
15:30:51 Topic: Web Components
15:31:08 cn: Please see email on list about this
15:32:16 http://lists.w3.org/Archives/Public/public-html-a11y/2015Jul/0000.html
15:32:49 cn: Some of what we want to do, e.g. date picker, is unclear whether this approach suffices
15:33:03 cn: So we need use cases and more info -- examples
15:33:18 cn: This also applies to tab panels
15:33:34 cn: We need better coverage of the kinds of things we might extend
15:33:45 Panel prototypes using Web Components: http://bkardell.github.io/common-panel/prototype/panelset-element.html
15:34:18 zakim, close this item
15:34:18 I do not know what agendum had been taken up, chaals
15:34:45 cn: Seems will be quite small
15:34:46 i/rs: Mark not here, nor on line at the moment/Topic: Canvas - are we there yet/
15:35:02 cn: Register immediately, please!
15:35:24 cn: Accomodations need -- talk to me by Friday AM
15:35:55 cn: Expect to do a deal of work on the above
15:36:11 cn: If dialin, please advise
15:36:15 janina: Yes, please
15:36:33 i/cn: Seems will/Topic: face to face/
15:36:38 zakim, agenda?
15:36:38 I see 2 items remaining on the agenda:
15:36:39 5. Action item review: https://www.w3.org/WAI/PF/HTML/track/actions/open [from chaals]
15:36:39 6. face to face meeting [from chaals]
15:36:45 zakim, next item
15:36:45 agendum 5. "Action item review: https://www.w3.org/WAI/PF/HTML/track/actions/open" taken up [from chaals]
15:37:15 action-317?
15:37:15 action-317 -- Charles McCathie Nevile to Look at the mse and spliced advertising cases in particular 05/01/2015 -- due 2015-07-02 -- OPEN
15:37:15 http://www.w3.org/WAI/PF/HTML/track/actions/317
15:37:36 cn: Expect to do this during the F2F
15:37:54 action-317 due in 8 days
15:37:54 Set action-317 Look at the mse and spliced advertising cases in particular 05/01/2015 due date to 2015-07-10.
15:39:52 q?
15:39:52 cn: Other items?
15:40:04 Adjournment
15:40:08 zakim, bye
15:40:08 Zakim has left #html-a11y
15:40:13 rrsagent, make minutes
15:40:13 I have made the request to generate http://www.w3.org/2015/07/02-html-a11y-minutes.html janina
15:46:24 chaals, still there? do you need a webex teleconference for the f2f? or are you going to use your "Personal Room"?
15:48:50 i can set one up right now if you have 5 minutes (I think)
15:49:16 or, if you still have webex open, you should be able to do it I think
15:49:35 (which is better because only the person who sets up a call can make changes to it)