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 JS: Greg should file his comments, Simons comments are picked up in his bug. 16:34:18 JF: Gregory Rosmaita was doing work on AccessKey etc, 16:34:28 JF: I have a lot to do and don't want to take too much on, 16:34:55 JF: AccessKey should be revisited, Gregory did a lot of work 16:35:06 JS: More on Simons comments? 16:35:12 JF: A typo etc 16:35:21 JS: File a bug anyone? 16:36:12 Greg: Is that relating to contenteditable? 16:36:28 CS: A WAI issue, not a HTML bug 16:37:05 Greg: It seems reasonable to me (Simons suggestion) 16:37:13 CS: We need to talk about that. 16:37:27 JF: I second Gregs idea 16:38:07 JS: We'll leave it as discuss, put it on the PF agenda 16:39:07 JF: To continue, Simon notes Global att hidden - it should be up to AT. Should it be rendered if in the DOM? 16:39:11 CS: Don't agree 16:39:32 JS: Is this a UAAG discuss? 16:39:36 JF: Yeah 16:39:55 JS: Lets point it to UAAG 16:40:31 JF: Any comments on the rest of Simons issues? 16:40:39 Group: Seems right. 16:40:55 Re:Tabindex 16:41:44 the title att is a UAAG issue 16:42:03 zakim, who is making noise? 16:42:03 JAllan has joined #html-a11y 16:42:13 Joshue, listening for 10 seconds I heard sound from the following: Janina (15%), Rich_Schwerdtfeger (80%) 16:43:30 CS: Deadline next Weds, midnight Boston. 16:43:50 16:43:55 JS: Moving on 16:44:20 Simon notes 'Content Models' looks fine 16:44:24 zakim, unmute me 16:44:24 Joshue should no longer be muted 16:44:25 scribe: JF 16:44:32 Josh: 16:44:57 1 think that is a missed opportunity to reinforce semantics for assistive technology 16:45:10 proposed some sample spec text to address thta 16:45:46 seems to be a recurring theme in the spec - that it often misses the opportunity to highlight the benefits of semantics to users of AT 16:46:11 CS: agree that is a good idea - if done carefully it would likely be embraced 16:48:21 [Josh reading out his proposed text found in the wiki] 16:48:27 GL: 2 thoughts 16:48:48 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/Globals#3.2_Elements_.5B1.5D 16:49:20 there are times when being conforming is less important than ensuring accessibility - for example if an author uses a non-conforming code (eg. @longdesc) how terrible is it? 16:50:04 perhaps setting a flag that notes that a series of changes conformant content that will emerge at the end of interaction conformant, but may fall "out of conformance" during the process 16:50:54 JS: do we want what is suggested here filed at this time 16:50:58 or discuss further 16:51:13 GL: since it is non-normative, i don't see an issue with filing that 16:51:23 Josh: will file this as a bug then 16:52:13 GL: should we discuss the idea of a flag for batch actions that move from conformant to non-conformant to conformant again? 16:52:36 CS: file the bug, but be prepared for a lengthy discussion on that idea 16:52:55 JO: happy to file this as a bug, as-is and then go from there 16:53:19 Next looked at content models 16:53:36 LJW has joined #html-a11y 16:53:43 mostly good, however there was some issues around SVG and a11y 16:54:27 the SVG example(s0 in the spec should be fully accessible 16:54:42 Josh thinking of pinging Doug or Chaals about this 16:54:56 Josh will file another bug here 16:55:31 JO: issue with metadata being "out of band" - confused, what does this mean? 16:55:58 +??P3 16:56:20 Does this relate to @summary? 16:56:35 zakim, ??P3 is Leonie 16:56:35 +Leonie; got it 16:57:16 JO: the definition of what Fallback content is needs to be made clear - this is a recurring "discussion" that has surfaced often 16:57:22 http://www.w3.org/Bugs/Public/show_bug.cgi?id=8885 16:57:40 this resolves to an existing bug (just referenced by Josh) 16:58:01 +1 16:58:09 +q 16:58:31 JS: doesnt sound like there is a bug her to file - is there an action we need to take? 16:59:06 gotta run 16:59:14 JO: suggest that we might need to resurrect bug 8885 at this time 16:59:22 richardschwerdtfe has left #html-a11y 16:59:37 zakim, mute me 16:59:37 Joshue should now be muted 16:59:42 JS: sounds like we're covered 16:59:45 zakim, unmute me 16:59:45 Joshue should no longer be muted 17:00:13 zakim, mute me 17:00:13 Joshue should now be muted 17:00:15 -Rich_Schwerdtfeger 17:00:17 SCRIBE: Marco_Ranon 17:00:19 thanks Marco 17:01:06 +Jim_Allan 17:01:19 rrsagent, make minutes 17:01:19 I have made the request to generate http://www.w3.org/2011/07/28-html-a11y-minutes.html kford 17:01:26 I'm going to step off for a bit, can someone please ping me on IRC when table is coming up? 17:01:33 JF: want to flag that metadata needs to be discussed further 17:02:06 rrsagent, set logs public 17:03:48 thanks JF 17:04:07 [discussion about editing wiki] 17:04:58 Laura has joined #html-a11y 17:06:15 +Laura_Carlson 17:06:42 MC: Josh to file bug re 3.2 Elements, followed by further discussion 17:07:07 JS: JOC to file bug on SVG example 17:07:29 JS no action on device independent events 17:08:04 Metadata Content/ Other notes: further discussion 17:08:23 Linked to bug 8885 17:09:17 s/Metadata Content/ Other notes/Fallback content 17:09:54 Metadata Content: further discussion 17:10:32 MC: Gregs reccommendations 17:11:33 GL: those are use cases for an author element 17:12:03 GL: there is a lack of ways to identify an author 17:13:19 + +1.617.325.aacc 17:13:29 JF: probably the group will say that maybe this could be done with microdata/microformats 17:13:37 JS: to be discussed 17:13:52 KimPatch has joined #html-a11y 17:14:03 -Leonie 17:14:24 zakim, aacc is really KimPatch 17:14:24 +KimPatch; got it 17:15:12 GL: what is the decision on the two decisions: using keywords or author? 17:15:57 GL: i don't thing microdata/microformats would address the issue 17:16:06 +??P3 17:16:45 JF: probably keyboard is a good reccommendation, but author is microformats 17:17:37 JF: we can discuss this and file a bug if we think it necessary 17:17:45 -??P3 17:18:13 MC: add 'for discussion' to the wiki 17:18:28 MC: JF to follow up on both 17:19:12 MC: Next is ARIA 17:19:17 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/ARIA 17:19:41 MC: Joseph Scheuhammer's comments 17:20:15 MC: general comment, to be discussed 17:21:12 MC: First table: 1. menu: Why isn't the implicit ARIA role "menu"? 17:21:24 JS: ARIA call should discuss this 17:22:08 MC: ARIA call on Monday, then report to the team 17:22:26 CS: Joseph and Steve Faulkner on vacation 17:22:28 +??P3 17:22:50 CS: we can try to answer now 17:23:07 -??P3 17:24:04 MC: aria role search - applies to a section, not the element 17:25:05 action: Rich to write whitepaper on ARIA features that seem similar to HTML features but aren't 17:25:05 Created ACTION-131 - Write whitepaper on ARIA features that seem similar to HTML features but aren't [on Richard Schwerdtfeger - due 2011-08-04]. 17:25:17 action-131: we might assign this to someone else, just putting in the tracker for now 17:25:17 ACTION-131 Write whitepaper on ARIA features that seem similar to HTML features but aren't notes added 17:25:59 MC: input type time ect, Why isn't their implicit role "textbox"? 17:26:38 CS: there is no appropriate ARIA role for that 17:29:08 action-131: questions raised in Joseph's review for LC are the sort of things it would be good to explain http://www.w3.org/WAI/PF/HTML/wiki/index.php?title=Spec_Review/ARIA 17:29:08 ACTION-131 Write whitepaper on ARIA features that seem similar to HTML features but aren't notes added 17:29:33 rrsagent, make minutes 17:29:33 I have made the request to generate http://www.w3.org/2011/07/28-html-a11y-minutes.html JAllan 17:30:21 +Q 17:31:02 Second table: CS answering to all questions, all answers will be in the wiki and will be addressed in the new action 131 17:31:56 ack JF 17:32:06 JF: i'm working on a note about aria describedby 17:32:17 CS: will it go in this section? 17:32:44 JF: it impacts a lot of things 17:32:59 Next: Insert 17:33:04 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/Insert 17:33:23 CS: something might be actionable 17:34:06 CS: 3.5.1 log a bug against the mapping document 17:34:36 CS: 3.5.3 same as above 17:39:30 CS: not sure that's true, who should we ask to? 17:39:34 LJW_ has joined #html-a11y 17:39:48 JS: maybe RS or SF? 17:40:42 CS: look for someone to confirm before we file a bug, and see if iot should be addressed as part of WCAG2 techniques 17:41:26 CS: 3.5.5 and 3.5.6: are those really problems? 17:41:57 JS: ask David Bolter 17:42:42 CS: mutation events, it would be good to ask AT vendors about this 17:43:21 CS: too weak to opena bug 17:43:44 CS: open a bug anyway and look for more information 17:44:20 CS: HTML 5 WCAG 2.0 techniques, it would be good to have some 17:45:32 MC: there is something in the techniques wiki, but we raise an agenda item to discuss this further in wcag WG 17:46:03 JS: short break - 5 minutes 17:46:25 -Laura_Carlson 17:47:35 Have to go now. Bye. 17:52:24 Scribe: KFord 17:52:38 rrsagent, make minutes 17:52:38 I have made the request to generate http://www.w3.org/2011/07/28-html-a11y-minutes.html kford 17:53:00 zakim, who's here? 17:53:00 On the phone I see Janina, JF, Marco_Ranon (muted), Kelly_Ford, Michael_Cooper, [Microsoft], Joshue (muted), Greg, Jim_Allan, KimPatch 17:53:02 [Microsoft] has cyns 17:53:03 On IRC I see KimPatch, JAllan, Greg, Joshue, JF, Marco_Ranon, kford, Zakim, RRSAgent, MichaelC, davidb, janina, trackbot, [tm] 17:53:38 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/Block 17:53:39 4.5.3. The pre element 17:53:49 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/Block 17:53:57 Group starting with comments on pre element. 17:54:14 MC reading comments from Wiki. 17:54:25 JF: A bug has already been filed. 17:54:52 Task force agrees with bug. 17:55:19 Second comment was around div. 17:55:30 No objections to this being a TF comment. 17:55:37 No comments on inline. 17:56:38 Embeds, canvas and media have no comments that made it to the wiki. 17:56:48 JF will be filing media bugs later today. 17:58:47 LJW has joined #html-a11y 17:58:49 Media minutes at http://lists.w3.org/Archives/Public/public-html-a11y/2011Jul/0136.html 17:59:23 Imagemaps are next. MC did a review. 17:59:32 +??P5 17:59:38 MC: I had no accessibility issues on the map element 18:00:14 MC going over comments on area. 18:00:55 CS: Area doesn't sound right at all. Each area needs alt. 18:01:30 MC: It explains later that user agents should sort out duplication. 18:01:54 Group doesn't think this is right and that UA shouldn't have to sort this out. MC filing bugs. 18:02:04 Now on image map. 18:04:15 Group talking about relative sizing of images and such as outlined in MC comments. 18:04:25 MC asks about what happens with browser zoom. 18:04:37 MC: It does seem like some clarification is needed. 18:04:49 CS: Also a line on what happens with browser zoom. 18:05:08 MC filing bugs. See wiki comments. 18:05:24 Now moving to section on math. 18:05:42 -??P5 18:05:54 John Gardener did a areview. 18:06:15 CS: I had people from MS look at this and we think the issues are implementation not in the spec. 18:06:43 Group now sorting out if math element has correct mappings in other specs. 18:07:49 CS thinks a bug might have been filed already or that this was discussed. 18:08:14 MC: SteveF filed 10438 which was resolved as won't fix. 18:08:44 JS: I think we need a bug. 18:09:03 JS will ask John to file bug so this comes as public feedback. 18:10:11 Group now talking about alt text on the math element. 18:11:32 MC: Spec says the details of how mathml are defined in the appropriate specs. 18:11:43 Now looking at SVG. 18:11:51 Comments again from John Gardener. 18:12:26 JS will ask John to file bug on his comment about talking about image role. 18:13:13 Now talking about alt text and title. 18:13:54 Janina will need to follow up with John to get issues filed and determine if these go to SVG or HTML5. 18:14:49 See MC wiki comments for full details. 18:15:04 Now moving to tables. 18:15:15 zakim, unmute me 18:15:15 Joshue should no longer be muted 18:15:26 http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/Tables 18:16:10 rrsagent, make minutes 18:16:10 I have made the request to generate http://www.w3.org/2011/07/28-html-a11y-minutes.html JAllan 18:17:07 Group sorting out whether to talk about JO comments on summary. 18:17:40 JO: The examples are not overly accessible, in particular the way they work with screen readers. 18:17:59 JO: The examples don't work well today. 18:18:40 JO: I used these experiences as as the foundation for my change proposal. 18:19:20 JF: There was a question between the author spec and the full spec about the attributes scope could take. 18:19:41 @scope bug filed here: http://www.w3.org/Bugs/Public/show_bug.cgi?id=13331 18:20:38 JS: Thanks to JO for getting a great talbe change proposal together. 18:20:53 JO: I'd like to talk about the change proposal if we could. 18:21:09 Judy has joined #html-a11y 18:21:32 JO: I'm trying to give this loads of energy but am quite happen to open source this to my friends and colleagues. 18:21:42 CP http://www.w3.org/WAI/PF/HTML/wiki/Category:Table_Summary#Extending_.40summary.3F 18:22:12 zakim, mute me 18:22:12 Joshue should now be muted 18:22:32 MC: Three other people submitted comments so we should look. 18:23:32 Beleive issue of tables being created without caption caught up in change proposal. 18:23:35 +Judy 18:24:46 MC entering bug details for one of the examples. See wiki. 18:26:49 Group now looking at SH comments. 18:28:28 Relative to layout tables, TF feels they have achieved the balance needed with role=presentation and still allowing good compat story. 18:28:39 My comment "Reading and navigation order" discusses tables. 25.1.2.4 Reading and navigation order - http://www.w3.org/WAI/PF/HTML/wiki/Spec_Review/All#Reading_and_navigation_order 18:29:14 Joshue has left #html-a11y 18:29:22 -Joshue 18:29:57 Authors should be able to specify preferred direction and/or order for sequential navigation, even among things such as tables that would not normally have a tab order. 18:29:59 * Use case: Masahiko is reading a web page, and uses browser commands to move the text cursor to the next and previous paragraphs. In most cases this works fine because the suggested reading order is that in which elements occur in the HTML. However, when Masahiko encounters a table that is designed to be read down the columns rather than across the rows, this simplistic navigation is... 18:30:00 ...entirely inappropriate. A similar problem occurs when CSS is used to rearrange blocks of text on the screen. 18:30:02 * Recommendation: Allow marking up a table to indicate whether the preferred reading order is by columns, by rows, both, or neither. This could be done with a new attribute, such as orientation="columns". 18:32:01 Group indicating GL idea sounding like new feature. Suspect it is too late for feature in HTML 5 but still want to file as a bug. 18:32:35 Expect it will get moved to the next version of HTML. 18:35:40 q+ 18:36:27 ack j 18:36:44 Group now talking about opportunities to get issues raised and when. 18:37:16 MC: Anyone can file an individual bug. Just don't put a11ytf on those bugs because a11ytf indicates task force approval. 18:38:26 CS: We should be careful about asking for new features without having compelling evidence. 18:39:08 JB: There is not 100% agreement on the fact that the HTML 5 spec is feature complete. 18:39:40 CS: I'm just saying that if we know something is going to controversial we should have a better case. 18:40:10 Group again revisists concept that anyone can file a bug. 18:40:38 s/not 100% agreement on the fact/not agreement on whether/ 18:40:45 s/revisists/revisits 18:41:13 Group now working on schedule because task won't be finished today. 18:42:57 Group sorting out scheduling times. 18:43:08 MC likes 7A eastern. 18:43:24 Group laughs. 18:46:43 Group settling on 8A Pacific as a starting time on 8/1. Same time as today's meeting. 18:48:03 MC: If you file a bug, please update wiki on the line where you are listed to file a bug. 18:48:54 JB: I was looking at a lot of bugs coming to the list and see a lot of good bugs. I appreciate the work. 18:50:35 zakim, who's here? 18:50:35 On the phone I see Janina, JF, Marco_Ranon (muted), Kelly_Ford, Michael_Cooper, [Microsoft], Greg, Jim_Allan, KimPatch, Judy 18:50:37 [Microsoft] has cyns 18:50:38 On IRC I see Judy, KimPatch, JAllan, Greg, JF, Marco_Ranon, kford, Zakim, RRSAgent, MichaelC, davidb, janina, trackbot, [tm] 18:50:53 http://www.w3.org/WAI/PF/HTML/wiki/Process_to_submit_HTML_spec_comments 18:51:41 http://www.w3.org/WAI/PF/HTML/wiki/Bugs 18:52:06 Group going over bug filing and resources. 18:53:04 rrsagent, make minutes 18:53:04 I have made the request to generate http://www.w3.org/2011/07/28-html-a11y-minutes.html kford 18:53:16 Group jumping to the details element. 18:53:25 MC: I looked at this. 18:53:54 MC goes over his wiki comments. 18:54:40 JS: There was a time we thought details should be expanded to include the longdesc case. 18:55:15 MC: We can think of use cases that this element can meet. Do we want to pursue this path or others. 18:55:27 CS: I like the details element. 18:55:52 CS: We often use more info on our pages and this is tough. I think details would be helpful in this case. 18:56:38 CS: If this was done well, supported keyboard access and such I think this would be good. 18:56:58 GL: I don't want to overload this. 18:57:04 q+ 18:57:47 q- 18:58:14 JS: The question is now do we think this is clear enough. 18:58:40 MC: I will file a bug suggest examples that demonstrate use cases on details. 18:58:54 rrsagent, make minutes 18:58:54 I have made the request to generate http://www.w3.org/2011/07/28-html-a11y-minutes.html kford 18:58:57 Joshue has joined #html-a11y 18:59:59 -Jim_Allan 19:00:09 -JF 19:00:18 Joshue has left #html-a11y 19:00:46 zakim, list attendees 19:00:46 As of this point the attendees have been Janina, +1.650.468.aaaa, Marco_Ranon, JF, Michael_Cooper, Kelly_Ford, Cooper, cyns, Joshue, +1.425.895.aabb, Greg, Léonie_Watson, 19:00:49 ... Rich_Schwerdtfeger, Leonie, Jim_Allan, Laura_Carlson, +1.617.325.aacc, KimPatch, Judy 19:01:03 -KimPatch 19:01:07 -Marco_Ranon 19:01:25 -Judy 19:01:26 -Michael_Cooper 19:01:27 -Janina 19:01:29 -[Microsoft] 19:01:32 -Greg 19:04:35 janina has left #html-a11y 19:06:02 zakim, please part 19:06:02 leaving. As of this point the attendees were Janina, +1.650.468.aaaa, Marco_Ranon, JF, Michael_Cooper, Kelly_Ford, Cooper, cyns, Joshue, +1.425.895.aabb, Greg, Léonie_Watson, 19:06:02 Zakim has left #html-a11y 19:06:05 ... Rich_Schwerdtfeger, Leonie, Jim_Allan, Laura_Carlson, +1.617.325.aacc, KimPatch, Judy 19:06:22 rrsagent, make minutes 19:06:22 I have made the request to generate http://www.w3.org/2011/07/28-html-a11y-minutes.html kford 19:08:51 rrsagent, please part 19:08:51 I see 1 open action item saved in http://www.w3.org/2011/07/28-html-a11y-actions.rdf : 19:08:51 ACTION: Rich to write whitepaper on ARIA features that seem similar to HTML features but aren't [1] 19:08:51 recorded in http://www.w3.org/2011/07/28-html-a11y-irc#T17-25-05