14:58:06 RRSAgent has joined #html-a11y
14:58:06 logging to http://www.w3.org/2011/07/28-html-a11y-irc
14:58:08 RRSAgent, make logs world
14:58:08 Zakim has joined #html-a11y
14:58:10 Zakim, this will be 2119
14:58:10 ok, trackbot; I see WAI_PFWG(HTML TF)11:00AM scheduled to start in 2 minutes
14:58:11 Meeting: HTML Accessibility Task Force Teleconference
14:58:11 Date: 28 July 2011
14:58:12 Hi Janina
14:58:19 WAI_PFWG(HTML TF)11:00AM has now started
14:58:24 kford has joined #html-a11y
14:58:25 +??P42
14:59:02 zakim, ??P42 is Janina
14:59:02 +Janina; got it
14:59:26 Marco_Ranon has joined #html-a11y
15:00:13 + +1.650.468.aaaa
15:00:17 +??P56
15:00:22 zakim, code?
15:00:22 the conference code is 2119 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), kford
15:00:46 zakim, ??P56 is me
15:00:46 +Marco_Ranon; got it
15:00:49 JF has joined #html-a11y
15:00:58 zakim, who's here?
15:00:58 On the phone I see Janina, +1.650.468.aaaa, Marco_Ranon
15:01:00 On IRC I see JF, Marco_Ranon, kford, Zakim, RRSAgent, richardschwerdtfe, Joshue, MichaelC, davidb, janina, trackbot, [tm]
15:01:12 zakim, aaaa is JF
15:01:12 +JF; got it
15:01:19 zakim, mute me
15:01:19 Marco_Ranon should now be muted
15:01:41 zakim, this will be 2119
15:01:45 ok, janina; I see WAI_PFWG(HTML TF)11:00AM scheduled to start now
15:01:55 zakim, this is 2119
15:01:58 ok, MichaelC; that matches WAI_PFWG(HTML TF)11:00AM
15:02:00 zakim, who's on the phone?
15:02:06 On the phone I see Janina, JF, Marco_Ranon (muted), [Microsoft], Michael_Cooper
15:02:22 zakim, Microsoft is Kelly_Ford
15:02:26 +Kelly_Ford; got it
15:03:44 Meeting: HTML-A11Y telecon
15:03:44 Chair: Janina_Sajka
15:03:44 Scribe: Marco_Ranon
15:03:44 Scribe: John_Foliot
15:03:44 Scribe: Cynthia Shelly
15:03:45 Scribe: Michael_Cooper
15:03:47 agenda: this
15:03:49 agenda+ Last Call Bug Review http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review
15:03:51 agenda+ Other Business
15:03:53 agenda+ Actions Review http://www.w3.org/WAI/PF/HTML/track/actions/open
15:03:55 agenda+ Identify Scribe for 4 August http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Scribe_List
15:03:57 agenda+ be done
15:04:02 LJW has joined #html-a11y
15:05:00 -Michael_Cooper
15:05:06 +Michael_Cooper
15:06:28 Greg has joined #html-a11y
15:06:55 zakim, take up item 1
15:07:10 agendum 1. "Last Call Bug Review http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review" taken up [from janina]
15:07:45 scribe: JF
15:08:26 -Michael_Cooper
15:08:30 OK
15:09:12 JS: we should start by going through the wiki issue by issue
15:09:21 +Cooper
15:10:15 +Michael_Cooper
15:11:27 Greg, We're about to figure out how to proceed. Certain people have particular knowledge/concerns.
15:11:42 JS: we have a lot to go through
15:12:02 -Cooper
15:12:08 how to proceed through the reviews in house to date - we have a fair bit of content already
15:12:24 we also have people who will be coming and going on this call
15:13:13 cyns has joined #html-a11y
15:13:20 JS: given this, not sure how to proceed due to people coming and going - suggest we just go through sequentially from top to bottom
15:13:29 +??P21
15:13:34 Joshue has joined #html-a11y
15:13:38 JS: Greg has submitted a lot of content - "camera ready" bugs
15:13:57 Greg is on the IRC, wonders if there are any other comments that were not included in the wiki
15:14:15 KF: If Greg is on the phone please speak up
15:14:33 some of the content might not have made it to the wiki - it only went to the UAAG list and janina
15:14:38 +[Microsoft]
15:14:50 MC: if it was only added to UAAG wqiki yesterday it may not have been noted
15:14:53 -??P21
15:15:04 zakim, microsoft has me
15:15:04 +cyns; got it
15:15:53 MC: as a note, at the top of the wiki there is a full page review of the wiki content available at: http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/All
15:15:59 same content as in the wiki
15:16:47 [working on having Greg's submissions sent to the TF mailing list
15:17:54 +??P1
15:17:59 zakim, ??P1 is Joshue
15:17:59 +Joshue; got it
15:18:45 zakim, mute me
15:18:45 Joshue should now be muted
15:19:15 + +1.425.895.aabb
15:19:22 zakim, aabb is me
15:19:22 +Greg; got it
15:19:36 zakim, who's here?
15:19:36 On the phone I see Janina, JF, Marco_Ranon (muted), Kelly_Ford, Michael_Cooper, [Microsoft], Joshue (muted), Greg
15:19:38 [Microsoft] has cyns
15:19:39 On IRC I see Joshue, cyns, Greg, LJW, JF, Marco_Ranon, kford, Zakim, RRSAgent, richardschwerdtfe, MichaelC, davidb, janina, trackbot, [tm]
15:20:46 +??P21
15:21:50 zakim, ??P21 is Léonie_Watson
15:21:50 +Léonie_Watson; got it
15:23:43 Go Léonie :-)
15:23:45 JS: for the record, Leonie has agreed to chair the bug triage sub-team, which will have a fair bit of work after today's call
15:23:54 shepharding these bugs through the process
15:24:33 JS: doesn't mean she will be doing all the work, but rather will direct to others with specific expertese
15:25:05 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review
15:25:49 JS: Looking at the wiki, it is our intent to work through this wiki today, to decide what we need/want to escalate to the bugzilla
15:26:24 suggest that unless we have a particular reason to skip around, perhaps we should start at the top
15:26:45 however if the UAAG folk (who have joined us today) need to leave early, we could also start with their submissions first
15:27:54 as we go through this, and assign bugs-to-be-filed to various individuals, they should file the bug and then add the URI of that bug into the wiki'
15:28:28 KF: does the wiki also contain all the links of other issues of concern?
15:28:45 is this the definitive source of issues of concern?
15:29:28 JS: the only reason to be hesitant is that the wiki might not have a complete listing of issues we have already raised (i.e. @longdesc)
15:29:30 JS says wiki pretty solid excluding issues where reconsideration may be needed.
15:30:00 this is a good representation of the issues we have been working on, but some details may not be fully captured
15:30:30 Alls aid however, this is probably the best resource - how complete however is unknown
15:31:10 Michael Cooper (for example) has copied over all of the UAAG wiki comments to this wiki as well
15:33:38 http://www.w3.org/TR/2011/WD-html5-20110525/scripting-1.html#scripting-1
15:34:16 Janina, I just put the link to the scripting part of the spec in IRC
15:34:38 Cyns, good feedback on Forms btw
15:35:47 JS: Can we ask someone to review the comments we have on Structure - provide a summary from the wiki page
15:35:52 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/All#Structure
15:35:56 No bugs on structure?
15:36:35 MC: Simon notes that it looks fine, made some comments about accessibility semantics
15:36:51 -Léonie_Watson
15:37:12 MCL James Craig asked about print-formatted file issues
15:37:30 +??P21
15:37:41 JS: Seems that these are not really items we can file as bugs - we should monitor them but not much more we can do at this time
15:39:33 MS: asks Greg to summarize his comments
15:40:20 [Greg has supplied a couple of use-cases and proposed replacement language]
15:40:55 will paste into irc now
15:41:00 Here's email I sent:
15:41:02 Hi! The following has been added to the wiki at http://www.w3.org/WAI/UA/work/wiki/HTML5_review_by_UAWG_notes#Non-Interactive_User_Agents:
15:41:04 Non-Interactive User Agents
15:41:05 The current draft HTML5 spec says:
15:41:07
15:41:09 Non-interactive presentation user agents
15:41:10 User agents that process HTML and XHTML documents purely to render non-interactive versions of them must comply to the same conformance criteria as Web browsers, except that they are exempt from requirements regarding user interaction.
15:41:12 Typical examples of non-interactive presentation user agents are printers (static UAs) and overhead displays (dynamic UAs). It is expected that most static non-interactive presentation user agents will also opt to lack scripting support.
15:41:13 A non-interactive but dynamic presentation UA would still execute scripts, allowing forms to be dynamically submitted, and so forth. However, since the concept of "focus" is irrelevant when the user cannot interact with the document, the UA would not need to support any of the focus-related DOM APIs.
15:41:16
15:41:18 It is very important that developers should not relegate user agents to the "non-interactive" category if there is benefit to the user in being able to interact with them.
15:41:21 Use case: Imelda uses a screen enlarger. She runs an application that displays a static, web-based slide detailing today's weather forecast. Imelda uses a screen enlarger, and normally reads blocks of text by having the magnifier track the text caret as she moves it through the content. However, as the developers considered theirs a non-interactive user agent, they left out the ability to do...
15:41:26 ...caret browsing. With luck, the screen enlarger will be able to access the application's DOM and determine the screen coordinates of each word, but it would certainly be easier if the application supported caret browsing.
15:41:29 Use case: The weather application that Imelda is running allows the user to select text with the mouse and automatically copies that text to the clipboard. However, the developers did not consider this "focus" or "activation", or even "selection" because the selection does not persist and the user can't perform their choice of actions on it. However, by this decision they are making...
15:41:34 ...functionality available to only one input modality, and users who rely on other modalities such as keyboard or speech recognition are denied full access. In this case, the developers should not have considered their application non-interactive, and instead implemented full focus and selection functionality.
15:41:38 Recommendation: The HTML5 spec should include wording that clarifies that user agents should not consider themselves non-interactive if they render content to the user on any system that can take input, and more specifically should not omit support for focus-related DOM APIs just because they do not expect to be taking input. Ideally it would include use cases similar to the above in order...
15:41:43 ...to help readers understand the issue.
15:42:38 nope
15:42:52 that is, I don't disagree
15:43:01 JS: Looks like this could be filed as-is
15:43:23 http://www.w3.org/Bugs/Public/
15:43:36 HTH
15:44:09 http://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG&component=HTML5%20spec%20%28editor:%20Ian%20Hickson%29&priority=P3
15:45:21 +Rich_Schwerdtfeger
15:45:22 [setting up Greg to file his bugs directly to bugzilla]
15:46:26 [Michael cooper updating wiki to reflect fact that Greg will file his own bugs]
15:47:03 KF" James Craig points out a few things
15:47:33 some are not really actionable, while others (such as awkward wording) could be actionable
15:48:01 Greg: James first point overlaps with one of the comments i submitted
15:48:32 cyns has joined #html-a11y
15:48:33 MC: as we review this, some items are actionable and smoe are not
15:49:02 -??P21
15:49:06 will add a note to the bottom that Greg Lowney is filing a bug that encompasses James' first point
15:49:22 JS: can someone else take on the task of filing the other bugs?
15:49:52 KF: can take the others
15:50:38 KF: will file bugs - even the low priority ones as once in the system...
15:52:06 JF: Embed is legacy and object is more recent.
15:52:37 JF: I'll take it
15:53:02 JF will file a bug on Jame's comment re: 2.2.3. Extensibility and embed vs. object
15:54:36 JF: Seems we should push back on CSS Wg
15:55:18 MC: wonders if we should be pushing back on the Systems Colors issue at the HTML WG since CSS WG have not responded
15:55:35 JS: seems that we should file a bug on this
15:56:42 JF: Thats an easy bug, I'll take it
15:58:15 JS: Notes that Rich is now n the call, and mindful that he cannot be here for the whole call suggest we move to the sections that Rich looked at
15:58:21 +1
15:58:35 http://www.w3.org/TR/2011/WD-html5-20110525/editing.html#contenteditable
15:58:56 Rich has 9 bugs
15:59:22 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/Editing
15:59:27 http://www.w3.org/TR/2011/WD-html5-20110525/editing.html#contenteditable
15:59:50 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/All#Editing
16:01:03 7.5
16:01:07 RS: the general problem is that the editing section is called the contenteditable section
16:01:26 when you go into that section you start talking about contenteditable and then it jumps to design mode
16:02:09 what is not clear is the support between design mode and keyboard editable
16:02:30 design mode makes the whole section editable, while contenteditable is by section
16:02:44 it is mostly editorial
16:03:19 one of the other issues is that different browsers have different keyboard navigation
16:03:41 CS: The WG has pushed back fairly hard on specifying uA behaviors
16:04:02 wonders if a comment that notes "follow platform conventions" would be sufficient
16:04:08 JS: sounds like a clear bug
16:04:34 RS: that sounds fine to me. for example, the Mac does not have an insert key, but on the same platform it should be consistent
16:04:56 GL: notes that regardless of what happens in HTML5 that this should be addressed in the UAAG stack as well
16:05:52 JS: I think this distills down to being consistent at a platform level
16:06:06 sounds good
16:06:16 [all agree this should be a bug]
16:06:35 RS: agrees to file this as a bug
16:06:59 (and previous item as well "Title for Section")
16:07:27 RS: the problem appears that design mode looks like it was added after the fact
16:08:03 so these issues all seem to be based on that editorial change, however Rich will file 3 bugs based on this
16:08:57 JF, I'll scribe for a bit
16:09:12 Scribe, Joshue
16:09:19 Scribe: Joshue
16:09:42 MC: The wiki page for edits is above
16:10:04 MC: I can make edits now..
16:10:23 MC: We are filing a bug for each of his headings
16:10:38 JS: Please add the keywords a11ytf
16:10:45 RS: Ok
16:11:03 MC: We have other comments from Greg that I included.
16:11:47 Greg: Meaning rather than presentation is important to screen readers etc
16:12:09 Greg: I have some example solutions, do people agree?
16:12:13 JS: Comments?
16:12:20 CS: Sounds like a big bug
16:12:26 CS: Are we asking them to add elements?
16:12:41 Greg: I proposed atts to the mark element.
16:12:47 CS: Maybe less of a fight.
16:12:57 Greg: Should something else be used?
16:13:12 CS: Should we create a bug, but not have a specific edit?
16:13:20 JS: That would be acceptable.
16:13:35 JS: If we see an issue, file the bug - even if solution is not in hand.
16:13:42 JS: It keeps it on the table.
16:13:55 JS: Any objections?
16:14:02 JS: Yes Greg, please do
16:14:16 JS: We are noting it in wiki
16:16:07 Greg: Anyone who can give advice on this, new att to be used in this context please let me know.
16:16:20 Greg: Eg the meaning and flag att
16:16:25 Greg: Not sure yet
16:16:58 E.g. where I suggested a new "meaning" attribute, should we reuse the "title" attribute?
16:17:11 JS: Contenteditable is updated in the wiki, going back to the sequence.
16:17:25 Greg: Is that it from Rich?
16:17:37 RS: Not from me
16:17:45 RS: I am really busy with canvas.
16:17:54 JS: Going back to Globals.
16:17:55 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/All#Globals
16:18:22 JS: Break?
16:18:56 Scribe is on standby
16:19:10 zakim, mute me
16:19:10 Joshue was already muted, Joshue
16:25:42 SUBJECT: Globals
16:25:56 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/Globals
16:26:59 Comments etc above
16:27:02 Elements http://www.w3.org/TR/2011/WD-html5-20110525/elements.html#elements
16:27:18 Content Models http://www.w3.org/TR/2011/WD-html5-20110525/content-models.html#content-models
16:29:02
16:29:30 zakim, unmute me
16:29:30 Joshue should no longer be muted
16:30:13 The doc that we file bugs against is the HTML Spec (Editor:Ian Hickson)
16:30:21 zakim, mute me
16:30:21 Joshue should now be muted
16:30:56 P3 (as a level of urgency will suffice)
16:31:00 JS: Yes
16:31:16 s/P3/JF:P3
16:31:40 JF: The important thing is to capture the bug numbers etc so we can see them thru.
16:32:08 JS: We have noted who has taken the bugs on, if everyone can annotate them with the URI that would be great
16:32:21 JS: Looking at Globals
16:32:27 JS: Summary from anyone.
16:32:35 zakim, unmute me
16:32:36 Joshue should no longer be muted
16:32:57 JF: Simon noted these are UAAG issues etc,
16:33:02 Greg has joined #html-a11y
16:33:10 zakim, mute me
16:33:10 Joshue should now be muted
16:33:55