15:58:09 RRSAgent has joined #html-a11y
15:58:09 logging to http://www.w3.org/2012/01/05-html-a11y-irc
15:58:11 RRSAgent, make logs world
15:58:11 Zakim has joined #html-a11y
15:58:13 Zakim, this will be 2119
15:58:13 ok, trackbot; I see WAI_PFWG(HTML TF)11:00AM scheduled to start in 2 minutes
15:58:14 Meeting: HTML Accessibility Task Force Teleconference
15:58:14 Date: 05 January 2012
15:59:27 WAI_PFWG(HTML TF)11:00AM has now started
15:59:34 +??P16
15:59:42 zakim, ??P16 is Janina_Sajka
15:59:42 +Janina_Sajka; got it
15:59:54 regrets: Laura_Carlson, Marco_Ranon
16:00:17 +??P20
16:00:23 zakim, ??P20 is Michael_Cooper
16:00:23 +Michael_Cooper; got it
16:00:25 Zakim, call Mike
16:00:25 ok, MikeSmith; the call is being made
16:00:27 +Mike
16:00:45 zakim, drop Mike
16:00:45 Mike is being disconnected
16:00:46 -Mike
16:01:04 hmm
16:01:06 agenda: http://lists.w3.org/Archives/Public/public-html-a11y/2012Jan/0012.html
16:01:44 richardschwerdtfe has joined #html-a11y
16:01:47 Zakim, call Mike-goog
16:01:56 ok, MikeSmith; the call is being made
16:01:58 +Mike
16:02:21 chair: Mike_Smith
16:02:50 +Rich
16:03:16 +John_Foliot
16:03:22 dboudreau has left #html-a11y
16:03:52 +[IPcaller]
16:04:16 zakim, IPcaller is Steve_Faulkner
16:04:16 +Steve_Faulkner; got it
16:04:50 +Cynthia_Shelly
16:06:42 scribe: janina
16:06:55 topic: status re deadlines
16:07:26 ms: Good starting point might be recap from Bug Triage
16:07:43 cs: Also have an agendum--Have sent in bug update
16:07:55 http://lists.w3.org/Archives/Public/public-html-a11y/2012Jan/0002.html
16:08:30 mc: Looked at needsinfo bugs, still need relevant info
16:09:17 mc: Categorized the won'tfix bugs (approx 80) into 12 categories
16:09:36 mc: Each category contains related bugs
16:09:50 -> http://lists.w3.org/Archives/Public/public-html-a11y/2011Dec/0316.html detailed bugs summary from Cynthia on Dec 23
16:09:52 RRSAgent, make minutes
16:09:52 I have made the request to generate http://www.w3.org/2012/01/05-html-a11y-minutes.html MikeSmith
16:10:01 mc: Some issues are closed, wondering whether to reopen? or create new issue?
16:10:41 mc: Currently believe there might be 8 to 10 issues to escalate
16:14:30 rs: Concern about how decisions reached can be vacated under WG process
16:14:45 js: Think it's worth discussing, but orthagonal to current discussion
16:15:25 ms: We were discussing existing, unescalated bugs, whether we need to escalate in order to make January 15 deadline
16:15:41 cs: Any we can review now?
16:15:44 mc: No.
16:16:51 js: Are we OK on work load?
16:17:00 mc: Yes on the won'tfix set that we categorized
16:17:09 mc: Unsure about the needsinfo
16:17:24 mc: Approx 30-40 needsinfo ones
16:17:57 mc: Also some marked fixed which we haven't verified, and may not be able to verify, or verify that we agree with the fix
16:18:47 -> http://www.w3.org/Bugs/Public/buglist.cgi?product=HTML+WG&keywords=a11ytf&bug_status=RESOLVED&resolution=NEEDSINFO Bugs as needsinfo
16:19:03 -> http://www.w3.org/Bugs/Public/buglist.cgi?product=HTML+WG&keywords=a11ytf&bug_status=RESOLVED&resolution=WONTFIX Bugs marked won't fix
16:19:21 ms: Was asking about the categorizations ...
16:19:30 -> http://www.w3.org/Bugs/Public/buglist.cgi?product=HTML+WG&keywords=a11ytf&bug_status=RESOLVED&resolution=FIXED Bugs marked as fixed
16:19:43 Potential issues to escalate:
16:19:45 Text alternatives
16:19:49 ARIA mapping
16:19:52 Canvas
16:19:56 Conformance
16:20:03 Media
16:20:05 Keyboard Access
16:20:11 Tooltip vs title
16:20:17 Contenteditable
16:20:20 Drag and Drop
16:20:31 ... and some misc ones that might be new issues
16:21:47 ms: I posted a comment re drag and drop, and want to note that I haven't seen any new info relating to keyboard issues on it.
16:21:57 ms: We went around on this a year ago
16:22:37 ms: Gez re-reviewed following the editor's changes approx November 2010, and found no remaining issues
16:22:52 ms: Looking through everything since, I see nothing new to identify problem
16:23:23 jf: I think Everett filed comments and bugs around this recently
16:23:50 mc: I think there were some drag and drop bugs we verified in December.
16:24:22 mc: We're triagging for a closer look
16:25:15 ms: Important to identify what specific issues are if we go forward with a new dnd bug
16:25:25 ms: Possible to get Gez on this briefly?
16:25:54 mc: Both Gez and Everett participate in Bug Triage, Everett more
16:27:55 q+
16:28:07 ms: Seems we're OK on bugs
16:28:16 rs: So, going back to the issue I've raised
16:28:45 rs: Concerned W3C doesn't have control of this spec, because lacking process
16:29:58 ack Stevef
16:30:37 sf: Some of the needsinfo have to do with adding role attrib
16:30:52 sf: Seems these should be a priority
16:31:28 mc: won'tfix we'll be covering on Tuesday, needsinfo we've assigned
16:31:51 https://www.w3.org/Bugs/Public/show_bug.cgi?id=11891
16:33:20 mc: Our expectation is to create tracker items for escalated issues, then associated parts of particular bugs to those
16:33:29 mc: So, the TF will be following the tracker issues
16:33:48 mc: So, for ARIA, perhaps something like "Make sure ARIA is completely mapped"
16:34:11 sf: Agree, but also have the concern that we follow process and not be at risk for changes that come out of the blue
16:34:31 rs: Because if our time and resolutions are at risk, we're wasting our time here
16:35:22 cs: Leonie sent me needsinfo, and I also looked at any I had previously touched
16:36:06 -> http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review Spec review wiki page
16:36:12 cyns has joined #html-a11y
16:36:15 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/All
16:36:53 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13512
16:36:57 cs: First one I thought needed discussion
16:38:05 mc: We triagged this as a feature request
16:38:33 cs: Pretty significant issue for web apps, don't see it as a feature request, think it's underspecified
16:38:39 cs: If moving to another spec, that's fine
16:38:59 cs: AT's have hacked around this, but a resolution would be better
16:40:41 mc: Maybe that we could agree this should be worked on in Web Apps
16:40:47 cs: Don't feel qualified to say that
16:41:00 ms: Willing to have an opinion, but don't know we have a consensus
16:41:09 cs: Who does Anna speak for on this?
16:41:10 -John_Foliot
16:41:20 ms: Nobody speaks for the wg in bugzilla
16:41:27 +John_Foliot
16:42:00 -Mike
16:42:01 ms: So, as an editorial assistant, he speaks on behalf of the editor on this
16:42:12 cs: Is there wg consensus on this?
16:42:13 Zakim, call Mike-goog
16:42:13 ok, MikeSmith; the call is being made
16:42:15 +Mike
16:42:18 js: Should we ask for wg consensus on this?
16:43:07 ms: As of now this is outside of html
16:44:04 mc: So our interest may be to insure there's a normative ref to DOM in the html specs
16:44:27 cs: OK. Will move bug to Web Apps
16:45:13 cs: OK, next ... 13659
16:45:30 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13659
16:45:50 cs: duplicate of 13599
16:46:00 cs: not really a11y, inclined to drop from our radar
16:46:44 cs: 13662
16:47:30 cs: I suggest we verify
16:47:35 [agreement]
16:47:46 cs: 13656
16:47:57 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13656
16:48:23 cs: Anyone have examples?
16:48:30 cs: Help appreciated on this
16:48:37 ms: Suggest an email on list for this one
16:48:51 mc: Also possibly John Gunderson
16:49:09 cs: 13528
16:49:17 cs: I verify
16:49:30 [agreement]
16:49:34 cs: 13531
16:49:58 https://www.w3.org/Bugs/Public/show_bug.cgi?id=13531
16:50:27 cs: there are examples in the spec that aren't best practice, though editor doesn't agree
16:50:58 cs: It's allowed, but not the best example
16:51:10 sf: Did a study of this recently, and there are issues
16:52:05 http://www.html5accessibility.com/tests/form-labels.html
16:52:40 ms: Meta question here is is this something to escalate to an issue?
16:53:03 ms: Perhaps to update the bug with comments
16:53:19 sf: Basically, this doesn't work with crome and safari
16:54:05 js: What about the invalids?
16:54:16 mc: I see about 15, and I'll make sure triage looks at them
16:54:56 ms: Suggest Triage should also look at Cynthia's remaining items, about 7 more bugs
16:56:06 ms: So let's talk about the issue Rich raised
16:56:23 ms: Agree with Janina that this isn't specifically a TF issue, but something that should be discussed in the WG
16:56:46 ms: My concern is whether the chairs even have control over the W3C spec
16:57:01 ms: Well, they do about the WG process
16:57:27 ms: Clearly, the HTML-WG is in many ways different from other W3C
16:57:46 ms: The chairs are making decisions, and have made a decision in this case
16:58:04 rs: Based on their assessment that browsers would not implement, but we're not in CR
16:58:33 rs: It's premature to use that as a yardstick
16:59:55 ms: PLH also involved in the discussion on this as was I
17:00:07 RS: I'm not wed to the API we created, ncesarrily
17:00:17 rs: people are using canvas to do text
17:00:58 rs: seems their decision is based on issues that have persisted, and we have no a11y support or the ability,
17:02:29 ms: reminds that our process is edit and then discuss
17:03:50 ms: pointing out the separate canvas spec
17:03:52 laura has joined #html-a11y
17:04:00 rs: but the changes are not tracking
17:10:40 -John_Foliot
17:36:11 HTML Canvas 2D Context Extensions
17:36:12 http://dev.w3.org/html5/canvas-extensions/Overview.html
17:44:03 -Steve_Faulkner
17:44:06 -Rich
17:44:52 -Michael_Cooper
17:44:57 -Mike
17:44:58 zakim, bye
17:44:58 Zakim has left #html-a11y
17:44:58 leaving. As of this point the attendees were Janina_Sajka, Michael_Cooper, Mike, Rich, John_Foliot, Steve_Faulkner, Cynthia_Shelly
17:45:05 rrsagent, make minutes
17:45:05 I have made the request to generate http://www.w3.org/2012/01/05-html-a11y-minutes.html janina
19:06:52 richardschwerdtfe has left #html-a11y
21:06:27 jongund has joined #html-a11y