15:33:12 RRSAgent has joined #wai-wcag 15:33:12 logging to http://www.w3.org/2015/01/13-wai-wcag-irc 15:33:14 RRSAgent, make logs public 15:33:16 Zakim, this will be WAI_WCAG 15:33:16 ok, trackbot; I see WAI_WCAG()11:00AM scheduled to start in 27 minutes 15:33:17 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 15:33:17 Date: 13 January 2015 15:33:20 zakim, agenda? 15:33:20 I see 1 item remaining on the agenda: 15:33:21 5. Discussion on working group priorities [from Joshue108] 15:33:28 zakim, clear agenda 15:33:28 agenda cleared 15:33:34 Chair: AWK 15:34:51 agenda+ Final Tutorials Review/Publication approval. 15:35:00 15:35:11 agenda+ Tuts approval 15:35:24 Scrub of actions https://www.w3.org/WAI/GL/track/actions/open 15:35:43 agenda+ Scrub of actions https://www.w3.org/WAI/GL/track/actions/open 15:35:53 agenda+ Comments needing responses: https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses 15:56:44 AWK has joined #wai-wcag 15:56:45 WAI_WCAG()11:00AM has now started 15:56:52 +AWK 15:57:03 Zakim, who is on the phone? 15:57:03 On the phone I see AWK 15:57:08 ZAkim, agenda? 15:57:08 I see 4 items remaining on the agenda: 15:57:10 1. Final Tutorials Review/Publication approval. [from Joshue] 15:57:10 2. Tuts approval [from Joshue] 15:57:10 3. Scrub of actions https://www.w3.org/WAI/GL/track/actions/open [from Joshue] 15:57:10 4. Comments needing responses: https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses [from Joshue] 15:57:19 Chair: AWK 15:57:21 Mike_Elledge has joined #wai-wcag 15:57:57 +Mike_Elledge 16:01:46 marcjohlic has joined #wai-wcag 16:02:18 +Marc_Johlic 16:02:45 jon_avila has joined #wai-wcag 16:02:55 +??P34 16:03:20 zakim, call EricE-Skype 16:03:20 ok, yatil; the call is being made 16:03:22 +EricE 16:03:39 zakim, nick yatil is EricE 16:03:39 ok, yatil, I now associate you with EricE 16:03:42 Kathy has joined #wai-wcag 16:03:50 +Jon_avila 16:03:52 zakim, mute me 16:03:52 EricE should now be muted 16:04:15 +Kathy_Wahlbin 16:04:30 Zakim, who is on the phone? 16:04:30 On the phone I see AWK, Mike_Elledge, Marc_Johlic, Michael_Cooper, EricE (muted), Jon_avila, Kathy_Wahlbin 16:04:50 Regrets+ David, Kenny 16:06:46 +Katie_Haritos-Shea 16:06:49 Loretta has joined #wai-wcag 16:07:04 Ryladog_ has joined #wai-wcag 16:07:12 https://www.w3.org/WAI/GL/wiki/Scribe_List#2015_Scribe_History 16:08:13 +[IPcaller] 16:08:20 +[IPcaller.a] 16:08:25 scribe: jon_avila 16:08:34 zakim, IPcaller is Loretta 16:08:34 +Loretta; got it 16:08:55 Zakim, take up item 1 16:08:55 agendum 1. "Final Tutorials Review/Publication approval. " taken up [from Joshue] 16:09:06 awk: first item is forms tutorial 16:09:40 awk: thank you to those who provided comments. Looks like we have variety of comments. 16:09:42 Tutorial: http://www.w3.org/WAI/tutorials/forms/ 16:10:27 awk: bottom line is that we'd like to publish and we have 1 supporting, 4 suggest changes, 3 say only with changes address, and 1 that says don't support w/ comments. 16:10:45 q+ 16:10:53 Joshue_ has joined #wai-Wcag 16:11:30 awk: Ideal to get a vote on whether we say yes or no -- we want to make decision either contigent or say not yet. We want to get this published as these are great resources. 16:11:53 q? 16:12:34 marc: on fence as to say publish yet or not -- most of comments around getting ARIA examples and techniques. Could be swayed to move if there is more support to add in ARIA example after publishing. 16:13:35 awk: under form concepts - several comments about moving ARIA up in discussion. Made suggestion on different ways to structure language. 16:14:25 awk: understand we want to use native elements whenever possible. The way it is written makes it seems like ARIA is rare. There should be an easy fix. 16:14:30 ack me 16:14:50 ack marcjohlic 16:15:25 Eric: can quickly comment as we go through; EO had been cautious on certain techniques -- want to be more neutral on techniques -- we could add more weight to best practices. 16:15:44 Focus should *first* be on HTML semantics - then - on ARIA 16:15:51 eric: tutorials are not set in stone -- will change over time. Will try to add more ARIA example as quick as possible 16:16:01 q+ 16:16:26 q+ 16:16:44 JO: only have in IRC -- but wanted to say happy to go as they are -- don't want to delay -- Eric says we can update as needed -- ok to put these out for review. 16:17:06 ack ry 16:17:10 s/only have/only halve/ 16:17:19 marc: Think tutorials are great -- like to get ARIA in there so we could point people to them. 16:17:54 s/only halve/only half/ 16:18:05 ack mike 16:18:07 khs: HTML semantics should be front and center -- ARIA is fine after -- room to add more about ARIA -- but keep ARIA as later option -- not first option. 16:18:16 q? 16:18:54 zakim, who is speaking? 16:19:04 jon_avila, listening for 10 seconds I heard sound from the following: Mike_Elledge (10%) 16:19:38 ME: question on timing on when the updates will occurs. 16:20:19 Eric: Funding has run out on tutorials -- can find time here and there to update and make improvements in the near future 16:20:52 awk: Pull requests into github could be used to get updates in 16:21:16 Eric: we will just do updates -- but it will take some time from other projects that we have allocated. Hard decision to look at what we want to change. 16:21:55 JO: What Eric is saying is practical. Good to get these out and see where they go -- that would be prudent. 16:22:32 awk: key question to answer - does the info in their represent our view of what people should do for accessibliity to say WCAG really likes these -- it's a legitamite question. 16:22:53 awk: If these are in the current form for 3 or 6 moths -- is that we want to put out there? That's the question. 16:23:23 awk: tutorials don't need to represent every method of doing something. 16:23:51 JO: moving goal post of user agent support, etc. emphasis on various technologies, etc. 16:23:57 +1 to Josh 16:24:33 JO: We are playing catchup on many things -- so we need to look for clangers and address those -- but I didn't really see any. Is there anything you can't live with? 16:25:04 awk: move on to next seciton -- labeling controls. Charles had a few show stoppers. Not sure if any of them have been addressed. 16:25:54 awk: Charles says it's important to use the for attribute in the first example, awk not sure if it's a show stopper. Eric have you resolved any of these yet? 16:26:04 +1 to Charles comment 16:26:19 eric: Switching a few labels here and there are no big problem we can just make that change. 16:26:59 q+ 16:27:25 ack mi 16:27:40 awk: Section on hding labels - do we need to update to make it clear that labels are important to users other than screen readers. 16:27:56 ME: think it is clear that you can understand visually but a screen reader user may need additional information. Ok with it. 16:28:17 awk: We need to recognize a reality of what people do. 16:28:28 q+ 16:28:44 JO: Emphasis there are certain use cases where this is the case to show the real world examples. 16:29:46 kw: Wanted to make a note about bugs where labels are hidden but they are not announced by VoiceOver or in Firefox. Could lead people down path where it might not work with AT. 16:30:39 +James_Nurthen 16:30:53 awk: Eric posted note about hiding elements which talks about when labels are hidden with display none and visibility hidden. 16:30:58 q+ 16:31:00 jamesn has joined #wai-wcag 16:31:19 kw: Code here would be fine with CSS clip. 16:31:30 rrsagent, make minutes 16:31:30 I have made the request to generate http://www.w3.org/2015/01/13-wai-wcag-minutes.html jamesn 16:31:36 kw: it's the off-screen one that prevents it from being spoken in FF and VO. 16:31:51 q- 16:32:15 jo: Could catch from kathy - a note about anti-partern could be useful. 16:33:47 awk: Charlies search should always have search role -- that's a problem. 16:34:22 jo: disagrees that it isn't needed. 16:34:24 ee: We can add a link to this section of the Page Structure tutorial: http://w3c.github.io/wai-tutorials/page-structure/sections/#search-section 16:34:41 ack jon 16:35:20 q+ 16:35:44 marc: had commetns about adding in aria-labelledby 16:35:49 ack ma 16:35:59 marc: As for role = search, not show stopper, but perhaps a note that could be added to one of these. 16:36:25 JN: Are we talking role of search or type = search? 16:36:49 eric: we have another section in tutoral that talks about page structure. We have a dedicated example there. 16:37:48 awk: what are the benfits of search is it just ARIA landmarks? 16:38:01 JN: Seems like adding role of search might dupliate search text. 16:38:28 awk: People on call seem to agree that role of search is not a show stopper. 16:39:19 JN: Did we discuss table layout CSS and what was the conclusion? 16:39:31 awk: we'll come back to CSS Table layout 16:39:37 q? 16:40:50 awk: we are mentioning things that can allow you conform and we are applying an amount of preference through order but we are not explicitly saying recommended or not recommended. Everything in the tutorial is recommended but some things might be more strongly recommended. Any othter thoughts on that? 16:41:41 q+ 16:41:46 marc: Order may need to be tweaked -- e.g. explicit labels might come before implicit labels. 16:41:50 awk: Eric said he would re-order that for id one to be first. Any one else? 16:41:55 ack mi 16:42:42 ME: somewhere we should say that we put them in priority or preference order. Could put at top so we are not repetitious 16:42:50 awk: What pages do we do that? 16:43:03 awk: Any suggestions on best way to handle that? 16:43:32 ME: put at beginning of each section, at beginning at tutorial and then each section such as form concepts. Hard call because people may come directly to specific pages. 16:43:56 awk: Same conversations on resources that have thick boiler plate text at the top of all techniques. 16:44:03 q+ 16:44:28 awk: having it be implicit is better than saying it's preferrable and cloud message 16:44:49 awk: prefer to have people see more useful examples and let people decide. 16:45:23 ack jon 16:47:07 JO: agree with Andrew and Jon implicit structure without explicitly saying preferrable but might be useful to say that these are designed to support legacy situations. 16:47:33 awk: Does anyone feel like we should delay publication over this issue? 16:47:54 awk: Hearig no one -- we will keep it queue for later. 16:48:10 https://bugzilla.mozilla.org/show_bug.cgi?id=1007975 16:48:24 http://w3c.github.io/wai-tutorials/forms/labels/#associating-labels-explicitly -> CSS table example 16:48:28 JN: problem with Firefox bug where content will be exposed table semantics 16:49:35 eric: CSS in this example doesn't add too much to the example. Would still work if we could rid of the CSS display: none. We wanted to show that they are not in one element so you can't use the implicit label. 16:50:46 awk: should still be clear since each part of the form is in a separate element. Will drop CSS display: table bit 16:51:26 awk: Question about content that would valid if copied out into a single document. 16:51:54 -1 to that 16:52:27 ME: Not a big thing but something to point out. e.g. some controls re-use ids in pages so examples are not unqie for the page. 16:52:59 JN: if you modify all ids in the doc to be unique then it will make it more difficult to read. 16:53:08 jo: Clearer code is better for this purpose. 16:53:26 ME: Can live with this -- James makes good point. 16:54:19 marc: Question about using ARIA at bottom was confusion, example talks about aria-label but didn't use aria-label. Perhaps the code sample needs to be updated. 16:54:54 JN: get rid bit about using aria-label attribute -- it's already been covered. 16:58:25 q+ to say scope and richness of examples 16:59:13 -[IPcaller.a] 17:00:25 ack e 17:00:25 EricE, you wanted to say scope and richness of examples 17:00:26 q+ 17:01:55 ack m 17:02:12 Joshue has joined #wai-wcag 17:02:34 jon_avila has joined #wai-wcag 17:02:39 +[IPcaller] 17:02:40 zakim, [IPcaller] is Joshue 17:02:40 +Joshue; got it 17:02:45 zakim, mute me 17:02:45 Joshue should now be muted 17:02:58 q? 17:03:04 My suggested view is HTML (including 5) and then ARIA 17:03:05 marc: Nice to have some things that are new -- but oh by the way it may not work in certain AT and browswer combinations. 17:03:26 q+ 17:03:45 example 2 from aria-9 17:03:52 marc: We do have some examples such as pulling labels from multiple sources. 17:03:53 q- 17:04:01 q+ 17:04:01 +1 marc on labels form multiple sources. 17:04:21 ack me 17:04:22 marc: example such as phone numbers of dates -- would be good to have in tutorial 17:04:29 +1 to multiple label examples also 17:04:35 ARIA provides a way to explicitly associate text on a web page with a form control, using the aria-labelledby attribute to reference the id of an element containing text that can serve as a label for the control. Like other uses of ARIA, support for the use of the aria-labelledby attribute is still developing. 17:04:46 awk: how would people feel about adding to end of explicit label section. See not in IRC 17:05:04 +1 17:05:15 +1 17:05:20 q+ 17:05:22 +1 17:05:23 awk: This wouldn't be an example, but we would acknowledge aria-labelledby by and reference ARIA techniqueds 17:05:24 +1 17:05:34 +1 So long as you point to an example or further explanatino 17:05:36 ack me 17:05:39 ack jos 17:05:58 ARIA provides a way to explicitly associate text on a web page with a form control, using the aria-labelledby attribute to reference the id of an element. This can contain text that serves as a label for the control. 17:06:10 jo: things that is fine -- first sentence is long. Put change in IRC 17:06:13 or "ARIA provides a way to explicitly associate text on a web page with a form control, using the aria-labelledby attribute. This attribute references the id of an element containing text that can serve as a label for the control. Like other uses of ARIA, support for the use of the aria-labelledby attribute is still developing." 17:07:08 awk: Eric, are you agreeable to adding wording and techniques to techniques list? 17:07:11 eric: yes 17:07:40 awk: Rather remove things like g162 which we don't want people to do and add ARIA techniques. Not suggesting we get rid of G162. 17:08:19 awk: is optgroup support and useful to justify highlighting it in here? 17:08:37 q+ 17:08:54 JN: Is ti AT supported? Is there any other way to do what it is mean to do? 17:09:05 ack me 17:09:08 awk: abseent knowing more let's leave it. 17:09:19 To my knowledge it isn't well supported. 17:09:28 jo: there is some support but I can't remember. 17:10:15 q? 17:11:44 Really nice, especially labels. 17:11:44 An ARIA alternative to
: Many developers do not use the form element or fieldset element anymore, but grouping is important. What WAI-ARIA structure should we use to group for a collection of controls that make up virtual field set. We can use the landmark, form, for the entire collection. Do we just use a "region" role instead of a
. 17:11:44 I think we should make suggestions, because the programming trend of abandoning the HTML form is widespread. 17:11:53 jn: Wanye says allow aria grouping mechanisms 17:12:59 awk: ARIA grouping roles -- used once in images tutorial. Need to compare two situations -- using it for form controls is probably more important concept to have. 17:13:19 awk: people want to use aria grouping because of the issues around styling fieldset and legend. 17:14:22 s/Really nice,/Wayne’s comment: Really nice, 17:14:32 awk: worreid that this will take more time. One of us could take an action to do a pull request to add a note that this is availalbe via ARIA. What do people think? 17:14:33 s/An ARIA alternative/… An ARIA alternative/ 17:15:01 s/I think we should/… I think we should/ 17:15:51 eric: it's not such a complicated example that we could add it with limited work. I will do it myself unless someone else wants to. 17:16:03 awk: sounds like we agree that it's a good thing to have. 17:16:12 ack me 17:16:57 zakim, mute me 17:16:57 Joshue should now be muted 17:17:13 mc: Tutorial should go into why and when to use fieldset because I think there is confusion about it. Radio buttons are only the beginning. 17:17:15 ack me 17:17:23 mc: would not block publication. 17:17:29 q+ 17:17:34 ack me 17:17:49 ISSUE: We need someone to think about how to beef up the fieldset section of grouping section in the forms tutorial. "Should fieldset be used around controls other than checkbox and radio button groups? Why or why not? How is the user experience different from when a fieldset is not used?" 17:17:50 Created ISSUE-44 - We need someone to think about how to beef up the fieldset section of grouping section in the forms tutorial. "should fieldset be used around controls other than checkbox and radio button groups? why or why not? how is the user experience different from when a fieldset is not used?". Please complete additional details at . 17:18:09 .... that sounds like an AT bug if that happens 17:18:11 zakim, mute me 17:18:11 Joshue should now be muted 17:20:26 yes 17:20:28 ack me 17:22:20 zakim, mute me 17:22:20 Joshue should now be muted 17:24:56 +(describedby for me) 17:26:07 Its an option 17:26:10 ack me 17:27:15 jon_avila has joined #wai-wcag 17:27:35 awk: we need to have it read expirary date and date format. 17:27:46 sorry my IRC keeps kicking me out 17:27:51 eric: sounds good to me. 17:28:08 awk: add ARIA 9 to techniques because we are using that. 17:28:30 awk: we are not going to make it through whole one. Other two tutorials were easier to review compared to this one. 17:29:13 -James_Nurthen 17:29:16 awk: Are there any things in the remaining comments, seciotn 6, 7,8,9, 10, and 11 in the tutorial. Are there any real show stopper. 17:29:26 awk: Leon was only one who said don't publish it. 17:29:40 s/Leon/Léonie/ 17:30:11 s/seciotn/section/ 17:30:13 awk: correciton: Leonie 17:31:12 I am concerned that we are providing techniques and examples - not in this document as much - but rather in the WCAG documents - that are designed to address gaps in AT implementations, and this bothers me. We are having to re-do new techniques based on lesson learned out in the wild - which means we are not doing enough research/testing ourselves. I see it as a staffing/volunteer breadth issue. Putting out and then pulling back techniques is hurting u[CUT] 17:31:16 jo: should we say that this may not be best practice but it's what we recommend -- what is our position on this. The term best practice is taken the wrong way. There is a disconnect. 17:31:33 jo: Leonie says that some things are mis-explained or inappropriate. 17:31:47 jo: not sure if this will get out of the gate as quick as we think. 17:32:44 awk: perhaps we need to ask people to review existing comments and see what needs to be done. I feel we are quite close taking into account some things we agreed to today . 17:33:00 awk: certainly talking about these being published in short number of weeks not months 17:33:22 eric: plan to bring it to EO this week including the comments -- will get more complete picture 17:33:32 awk: Leonie is on EO 17:33:52 awk: will need people to review survey response sections 6 through 11. 17:34:00 s/be best practice but /be strictly best practice but works in terms of WCAG compliance and best current accessibility support 17:34:02 awk: need aria grouping example. 17:34:06 awk: that's it, thank you. 17:34:08 -Kathy_Wahlbin 17:34:08 ack me 17:34:10 Thx! Bye! 17:34:10 zakim, list attendees 17:34:10 As of this point the attendees have been AWK, Mike_Elledge, Marc_Johlic, Michael_Cooper, EricE, Jon_avila, Kathy_Wahlbin, Katie_Haritos-Shea, Loretta, James_Nurthen, Joshue 17:34:13 -Katie_Haritos-Shea 17:34:14 -Joshue 17:34:15 -Mike_Elledge 17:34:17 -Marc_Johlic 17:34:17 Trackbot, end meeting 17:34:17 Zakim, list attendees 17:34:17 As of this point the attendees have been AWK, Mike_Elledge, Marc_Johlic, Michael_Cooper, EricE, Jon_avila, Kathy_Wahlbin, Katie_Haritos-Shea, Loretta, James_Nurthen, Joshue 17:34:21 -Loretta 17:34:23 -Michael_Cooper 17:34:24 zakim, drop me 17:34:25 EricE is being disconnected 17:34:25 -EricE 17:34:25 RRSAgent, please draft minutes 17:34:25 I have made the request to generate http://www.w3.org/2015/01/13-wai-wcag-minutes.html trackbot 17:34:26 RRSAgent, bye 17:34:26 I see no action items 17:34:29 -AWK