14:53:12 RRSAgent has joined #wai-wcag 14:53:12 logging to http://www.w3.org/2014/10/14-wai-wcag-irc 14:53:14 RRSAgent, make logs public 14:53:14 Zakim has joined #wai-wcag 14:53:16 Zakim, this will be WAI_WCAG 14:53:16 trackbot, WAI_WCAG()11:00AM is already associated with an irc channel; use 'move WAI_WCAG to here' if you mean to reassociate the channel 14:53:17 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 14:53:17 Date: 14 October 2014 14:53:29 Chair: Joshue 14:53:33 Zakim, Agenda? 14:53:33 I see nothing on the agenda 14:53:49 regrets+ Kathy 14:54:22 regrets+ James 14:54:26 agenda+ Finish survey from last week [from take up from 'Mobile TF proposed changes to G78' via Joshue] 14:54:36 agenda+ Eric Eggert will join the call for a brief discussion on WCAG feedback on the WAI-DEV tutorials. 14:54:46 agenda+ Technique needed for CSS and alt text for generated content: https://www.w3.org/WAI/PF/Group/track/issues/542 14:54:55 agenda+ Discuss Action 274 and Mobile TF feedback 14:55:03 agenda+ Follow up on Aside technique 14:55:13 agenda+ TPAC Planning: Current TPAC structure and other ideas. 14:55:25 regrets: Jon Avila 14:56:06 regrets: Mike E, Jon A, James N, Kathy W 14:57:09 zakim, who is on the phone? 14:57:09 sorry, AWK, I don't know what conference this is 14:57:11 On IRC I see RRSAgent, AWK, bbailey, jamesn, Joshue, MichaelC, yatil, Kenny, trackbot 14:57:49 https://www.w3.org/2002/09/wbs/35422/14thOct2014/ 14:58:39 meeting: WCAG Working Group Teleconference 14:58:52 zakim, [IPcaller] is Joshue 14:58:52 sorry, Joshue, I do not recognize a party named '[IPcaller]' 14:59:26 Zakim, move WAI_WCAG to here 14:59:27 ok, AWK; that matches WAI_WCAG()11:00AM 14:59:31 zakim, who is on the phone? 14:59:32 On the phone I see +1.617.766.aaaa, [IPcaller] 14:59:37 zakim, aaaa is AWK 14:59:37 +AWK; got it 14:59:53 zakim, agenda? 14:59:53 I see 6 items remaining on the agenda: 14:59:54 1. Finish survey from last week [from from take up from 'Mobile TF proposed changes to G78' via Joshue via Joshue] 14:59:54 2. Eric Eggert will join the call for a brief discussion on WCAG feedback on the WAI-DEV tutorials. [from Joshue] 14:59:54 3. Technique needed for CSS and alt text for generated content: https://www.w3.org/WAI/PF/Group/track/issues/542 [from Joshue] 14:59:55 4. Discuss Action 274 and Mobile TF feedback [from Joshue] 14:59:57 5. Follow up on Aside technique [from Joshue] 14:59:57 6. TPAC Planning: Current TPAC structure and other ideas. [from Joshue] 15:00:10 https://www.w3.org/2002/09/wbs/35422/14thOct2014/ 15:00:15 David has joined #wai-wcag 15:00:33 +??P31 15:00:37 +Bruce_Bailey 15:00:39 zakim, call EricE-Skype 15:00:39 ok, yatil; the call is being made 15:00:40 +EricE 15:00:53 zakim, i am bruce_bailey 15:00:53 ok, bbailey, I now associate you with Bruce_Bailey 15:00:57 zakim, nick yatil is EricE 15:00:57 ok, yatil, I now associate you with EricE 15:00:58 agenda+ https://www.w3.org/2002/09/wbs/35422/14thOct2014/ 15:01:00 +David_MacDonald 15:01:02 zakim, mute me 15:01:03 EricE should now be muted 15:01:19 agenda? 15:01:55 agenda order 1,7,2 15:01:58 agenda: http://lists.w3.org/Archives/Public/w3c-wai-gl/2014OctDec/0050.html 15:02:52 +Katie_Haritos-Shea 15:03:15 marcjohlic has joined #wai-wcag 15:03:27 zakim, call kenny-mobile 15:03:28 ok, Kenny; the call is being made 15:03:29 +Kenny 15:03:31 zakim, who is on the phone? 15:03:31 On the phone I see AWK, [IPcaller], Michael_Cooper, Bruce_Bailey, EricE (muted), David_MacDonald, Katie_Haritos-Shea, Kenny (muted) 15:03:50 zakim, [IPcaller] is Joshue 15:03:50 +Joshue; got it 15:03:51 +Marc_Johlic 15:04:06 zakim, who is on the phone? 15:04:06 On the phone I see AWK, Joshue, Michael_Cooper, Bruce_Bailey, EricE (muted), David_MacDonald, Katie_Haritos-Shea, Kenny, Marc_Johlic 15:04:06 zakim,mute me 15:04:09 Kenny should now be muted 15:04:56 scribe Bruce_ 15:05:09 scribe: Bruce 15:05:17 Loretta has joined #WAI-WCAG 15:05:23 scribeNick: bbailey 15:05:32 zakim, take up item 1 15:05:32 agendum 1. "Finish survey from last week" taken up [from from take up from 'Mobile TF proposed changes to G78' via Joshue via Joshue] 15:05:36 s/scribe Bruce_// 15:05:45 +[IPcaller] 15:05:59 zakim, IPCaller is orretta 15:05:59 +orretta; got it 15:06:07 zakim orretta is Loretta 15:06:21 Couple things from last week before next survey 15:06:23 Mobile TF proposed changes to G78 15:06:25 ZAkim, take up item 1 15:06:25 agendum 1. "Finish survey from last week" taken up [from from take up from 'Mobile TF proposed changes to G78' via Joshue via Joshue] 15:06:26 zakim, orretta is Loretta 15:06:27 +Loretta; got it 15:06:28 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/G78 15:06:36 s/zakim orretta is Loretta// 15:06:36 https://www.w3.org/2002/09/wbs/35422/20141007Misc/results#xg202edit 15:07:03 Discussed last week, did not close 15:07:07 TOPIC: G78 15:07:31 6. Mobile TF proposed changes to G202 15:07:42 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/G202 15:07:50 See new text step in wiki 15:08:07 thanks to jon availl 15:08:19 Ryladog has joined #wai-wcag 15:08:50 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/G78 15:09:46 q+ 15:09:50 Earlier text script was a little wordy 15:09:50 q- 15:10:17 Jon made pithy and added example 15:11:32 KHR asks question about players that don't look like player, but response resolves this 15:12:22 RESOLUTION: Accept G78 as ammended 15:13:08 s/ammended/amended 15:13:08 AWK / MC : wiki may be having problems 15:14:03 Bruce sharded problem with WBS home page 15:14:30 MC reports problems only sporatic, 15:14:35 we continue 15:14:44 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/G202 15:14:50 Mobile TF proposed changes to G202 15:14:53 TOPIC: G202 15:15:49 https://www.w3.org/2002/09/wbs/35422/20141007Misc/results#xg202edit 15:16:16 Reviewing survey responses 15:16:42 Discuss that some tone in proposed response may be harsh 15:17:11 MC has proposed change to remove combative phrase 15:17:47 AWK suggest linking to defintion of keyboard interface 15:18:10 s/defintion/definition/ 15:18:46 q+ 15:18:54 RESOLUTION: Accept G202 as amended 15:19:53 Wiki login issues continues, so Micheal Cooper having to do the labor... 15:20:18 ack d 15:21:20 Discussion of keyboard functionality versus keyboard control 15:23:10 Discussion if test script as written is explicit enough wrt keyboard 15:24:29 MC concerned that example is too leading for test proceedure 15:25:25 There are many examples for keyboard interface, not specific to mobile, so no compelling reason to scope to mobile 15:26:14 Emphasizing one example in test procedure may give it too much emphasis 15:26:49 Discuss removing example from test procedure, information is in body of technique 15:27:14 Reviewing text and MC suggested edit 15:28:16 Accept edit to test procedure, removing example 15:28:25 Return to discussion of Note 15:28:44 q? 15:29:33 q+ 15:29:35 q+ 15:29:36 David concerned with “does not necessarily mean that each of the individual controls can be used from the keyboard” 15:30:02 ack lor 15:30:14 Note is already in place, was not suggested for change 15:30:46 Loretta recalls that keyboard shortcut might be available for control that is not directly keyboard operable 15:31:10 Requirement is for keyboard functionality, not that each control be keyboard accessible per se 15:31:45 ack awk 15:31:50 Example of keyboard shortcut for bold, rather than tabbing to a bold button 15:32:38 AWK gives example of mouse-only click for video play, but may be other keyboard means for triggering video 15:33:00 q- 15:33:12 David concurs that being able to do functionality from keyboard is different than each control from keyboard. 15:33:36 David volunteers to bring this back for more discussion, add clarity 15:35:04 ACTION: David to file issue on G202 regarding language distinguishing functionality from control and clarify necessity of keyboard accessibilty 15:35:04 Created ACTION-284 - File issue on g202 regarding language distinguishing functionality from control and clarify necessity of keyboard accessibilty [on David MacDonald - due 2014-10-21]. 15:35:46 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/G9 15:36:01 TOPIC: G9 15:36:28 Joshue: recaps from last week, don't want to work this too much this week 15:36:44 ack me 15:37:12 KHS speaks to keeping phrasing 15:37:55 Discussion is around Exampl 2 15:38:07 Proposed is: Example 2: A user watches an online seminar on their mobile device, including captioning provided through the use of Communication Access Real-time Translation (CART). The captions provided also benefit in-person participants who need captioning and can view the information on their own device. 15:38:25 ack me 15:38:27 Example 2: A user watches an online seminar on their mobile device, including captioning provided through the use of Communication Access Real-time Translation (CART). The captions provided also benefit in-person participants who need captioning and can view the information on their own device. 15:39:48 RESOLUTION: Accept Example 2 on G9 15:40:50 zakim, agenda? 15:40:50 I see 7 items remaining on the agenda: 15:40:52 1. Finish survey from last week [from from take up from 'Mobile TF proposed changes to G78' via Joshue via Joshue] 15:40:52 7. https://www.w3.org/2002/09/wbs/35422/14thOct2014/ [from Joshue] 15:40:52 2. Eric Eggert will join the call for a brief discussion on WCAG feedback on the WAI-DEV tutorials. [from Joshue] 15:40:52 3. Technique needed for CSS and alt text for generated content: https://www.w3.org/WAI/PF/Group/track/issues/542 [from Joshue] 15:40:56 4. Discuss Action 274 and Mobile TF feedback [from Joshue] 15:40:56 5. Follow up on Aside technique [from Joshue] 15:40:56 6. TPAC Planning: Current TPAC structure and other ideas. [from Joshue] 15:41:08 ack me 15:41:28 zakim, take up item 2 15:41:28 agendum 2. "Eric Eggert will join the call for a brief discussion on WCAG feedback on the WAI-DEV tutorials." taken up [from Joshue] 15:41:56 Eric talks about WAI-ACT tutorials 15:41:58 zakim, mute me 15:41:58 Joshue should now be muted 15:42:24 Eric has lead for editorial work, really appreciates the feedback so far 15:42:35 https://github.com/w3c/wai-tutorials/labels/%E2%9C%97 15:42:36 Two open issues, pretty quick 15:42:47 https://github.com/w3c/wai-tutorials/issues/124 15:43:40 Topic is Change color contrast for placeholders? 15:43:58 ack me 15:44:01 Is this a browser or should we address in tutoirals? 15:44:21 s/tutoirals/tutorials 15:44:42 Contrast: https://github.com/w3c/wai-tutorials/pull/145/files?diff=split 15:45:03 Other issue (carousel) is probably more straightforward 15:45:17 Particular line: https://github.com/w3c/wai-tutorials/pull/145/files?diff=split#diff-c9c21451eb33fff0fb847235af4bebe8L228 15:45:51 KHR: definitely an issue 15:46:11 q+ 15:46:19 Joshue: Placeholder text came up on calls before 15:46:21 ack davi 15:46:38 We don't have current technique specific to placeholder 15:47:05 David thinks instructions below form are pretty well addressed 15:47:24 ARIA-described-by provides sufficient pointer 15:47:38 Issue is more with prompts like mm/dd/yyyy 15:47:45 https://github.com/w3c/wai-tutorials/issues/124 15:47:52 http://w3c.github.io/wai-tutorials/forms/instructions/#placeholder-text 15:48:04 Daivd points out problem is more like prompts like mm/dd/yyyy 15:48:28 s/Daivd/David 15:49:17 Joshue asks if Eric might take lead with tutorials 15:49:52 Eric points out that browsers do not honor contrast setting for place holder text 15:50:02 Can or should we make this a browser issue? 15:50:20 https://www.w3.org/WAI/GL/wiki/Using_@placeholder_on_input 15:50:46 One approach is for page authors to specify foreground and background color on placeholder text 15:51:25 q? 15:51:42 q+ 15:51:44 Joshue points out that more attention seems to be given from authors on placeholder attributes 15:52:01 AKW comments that he likes proposed text 15:52:41 Example we provide should have good contrast, so do we provide CSS code that does this? 15:52:57 Or do we say this is UA / browser issue? 15:53:18 Joshue thinks we have a fine line to walk on this. 15:53:58 q+ 15:54:01 AWK reminds that recent response was that it would be nice if browsers handled this, but for now author has to supply as matter of practice 15:54:14 ack r 15:55:01 KHR likes that we provide example, link back to related techniques 15:55:39 Authors are having difficulty with the issue, and end-user with low vision having problems reading placeholder text 15:56:14 Katie thinks this is an important issue, we want browsers to change, but have to provide work-around in meantime 15:56:15 ack dav 15:56:19 ack d 15:56:31 Would be a mistake to pass on the opportunity. 15:57:08 David gives hypothetical example that this might already come down to accessibility supported 15:57:54 If one browser provide sufficient contrast, but that's not the end-users preferred browser, is this still a wcag contrast requirement or not? 15:58:02 q+ 15:58:23 Joshue also thinks this ties back to UAAG 15:58:35 ack awk 15:58:43 When using a UAAG conforming browser, issue may be addressed. 15:59:23 AWK points out that accessibility support is theoretical future problem as all browsers do poorly with placeholder text 15:59:47 zakim, agenda? 15:59:47 I see 7 items remaining on the agenda: 15:59:48 1. Finish survey from last week [from from take up from 'Mobile TF proposed changes to G78' via Joshue via Joshue] 15:59:48 7. https://www.w3.org/2002/09/wbs/35422/14thOct2014/ [from Joshue] 15:59:48 2. Eric Eggert will join the call for a brief discussion on WCAG feedback on the WAI-DEV tutorials. [from Joshue] 15:59:48 3. Technique needed for CSS and alt text for generated content: https://www.w3.org/WAI/PF/Group/track/issues/542 [from Joshue] 15:59:51 4. Discuss Action 274 and Mobile TF feedback [from Joshue] 15:59:51 5. Follow up on Aside technique [from Joshue] 15:59:51 6. TPAC Planning: Current TPAC structure and other ideas. [from Joshue] 15:59:53 q 15:59:56 + 16:00:04 Response for now has to be providing examples of good contrast for place holder text 16:00:14 q+ 16:00:17 AWK points out for tutorial we should be providing 16:00:42 ack ryla 16:00:57 UAAG #4 Optional Settings: Throughout UAAG 2.0, all required behaviors may be provided as optional preference settings unless a success criterion explicitly says otherwise. For example, if a success criterion requires high contrast between foreground text and its background, the user agent may also provide choices with low contrast. While it is preferred to have a required behavior as a... 16:00:59 KHR need good user agent notes 16:00:59 ...default option, it does not need to be, unless the success criterion explicitly says otherwise. 16:02:02 Joshue thanks Eric for flagging, need to address in techniques. Katie volunteer to help or review 16:02:07 ee@w3.org 16:03:06 https://github.com/w3c/wai-tutorials/issues/163 16:03:09 https://github.com/w3c/wai-tutorials/issues/163 16:03:27 ACTION: yatil to work with Katie on providing example with CSS providing sufficient contrast for placeholder text 16:03:27 Error finding 'yatil'. You can review and register nicknames at . 16:03:56 ACTION: Ryladog to work with Eric on providing example with CSS providing sufficient contrast for placeholder text 16:03:57 Error finding 'Ryladog'. You can review and register nicknames at . 16:04:11 ACTION: Katieto work with Eric on providing example with CSS providing sufficient contrast for placeholder text 16:04:11 Error finding 'Katieto'. You can review and register nicknames at . 16:04:26 ACTION: Katie to work with Eric on providing example with CSS providing sufficient contrast for placeholder text 16:04:26 Created ACTION-285 - Work with eric on providing example with css providing sufficient contrast for placeholder text [on Katie Haritos-Shea - due 2014-10-21]. 16:05:13 TOPIC: Carousel interaction #163 16:05:49 Eric describes problem with using ARIA live regions 16:06:40 Eric asks if technique is okay as is, or do we need to expect additional work-around? 16:07:39 David discusses that behavior is not too unusual for experienced screen reader user, but instruction or prompt really is needed before encountering. 16:08:03 s/ee@w3.org// 16:08:27 Joshue points out that any way to escape, get around, or ignore carousel for keyboard users should be okay. 16:09:02 Joshue asks if anyone has issue with what Eric has so far. 16:09:24 No objections. David suggest providing some addition links,. 16:09:54 Joshue points out that screen reader behavior can vary quite a lot from platform to platform 16:10:57 David comments that we don't want to imply that way we address carousel makes them a solved problem 16:11:19 Will need to emphasize that this is one solution, not only solution 16:11:23 q? 16:11:37 All thank Eric 16:11:43 zakim, mute me 16:11:43 EricE should now be muted 16:11:43 zakim, agenda? 16:11:44 I see 7 items remaining on the agenda: 16:11:44 1. Finish survey from last week [from from take up from 'Mobile TF proposed changes to G78' via Joshue via Joshue] 16:11:44 7. https://www.w3.org/2002/09/wbs/35422/14thOct2014/ [from Joshue] 16:11:44 2. Eric Eggert will join the call for a brief discussion on WCAG feedback on the WAI-DEV tutorials. [from Joshue] 16:11:45 3. Technique needed for CSS and alt text for generated content: https://www.w3.org/WAI/PF/Group/track/issues/542 [from Joshue] 16:11:45 4. Discuss Action 274 and Mobile TF feedback [from Joshue] 16:11:45 5. Follow up on Aside technique [from Joshue] 16:11:45 6. TPAC Planning: Current TPAC structure and other ideas. [from Joshue] 16:12:01 zakim, next item 16:12:01 agendum 1. "Finish survey from last week" taken up [from from take up from 'Mobile TF proposed changes to G78' via Joshue] 16:12:09 zakim, take up item 3 16:12:09 agendum 3. "Technique needed for CSS and alt text for generated content: https://www.w3.org/WAI/PF/Group/track/issues/542" taken up [from Joshue] 16:13:02 https://www.w3.org/WAI/PF/Group/track/issues/542 16:13:16 Joshue and AKW note that we are not resolving this now 16:13:23 e.g.
Foo
16:13:54 ACTION: David to work on technique for issue 542 16:13:54 Created ACTION-286 - Work on technique for issue 542 [on David MacDonald - due 2014-10-21]. 16:13:55 ISSUE-542: David Mac D to work on it 16:13:55 Notes added to ISSUE-542 . 16:14:23 q? 16:14:31 zakim, agenda? 16:14:31 I see 6 items remaining on the agenda: 16:14:33 1. Finish survey from last week [from from take up from 'Mobile TF proposed changes to G78' via Joshue via Joshue] 16:14:33 7. https://www.w3.org/2002/09/wbs/35422/14thOct2014/ [from Joshue] 16:14:33 3. Technique needed for CSS and alt text for generated content: https://www.w3.org/WAI/PF/Group/track/issues/542 [from Joshue] 16:14:33 4. Discuss Action 274 and Mobile TF feedback [from Joshue] 16:14:34 5. Follow up on Aside technique [from Joshue] 16:14:36 6. TPAC Planning: Current TPAC structure and other ideas. [from Joshue] 16:15:02 ACTION-274 16:15:02 ACTION-274 -- Katie Haritos-Shea to Review description for g4 to ensure that keyboard interface support is included. -- due 2014-09-30 -- PENDINGREVIEW 16:15:02 http://www.w3.org/WAI/GL/track/actions/274 16:15:14 zakim, take up item 4 16:15:14 agendum 4. "Discuss Action 274 and Mobile TF feedback" taken up [from Joshue] 16:16:28 zakim, take up item 5 16:16:28 agendum 5. "Follow up on Aside technique" taken up [from Joshue] 16:16:31 https://www.w3.org/WAI/GL/wiki/Using_the_aside_element_to_indicate_tangentially_related_content 16:17:03 Recall status? 16:17:05 A 16:17:26 AWK recalls that David and Jon Avilla working on 16:17:52 Technique was post-pone from recent pub 16:20:02 ACTION: David to follow-up on aside technique 16:20:02 Created ACTION-287 - Follow-up on aside technique [on David MacDonald - due 2014-10-21]. 16:20:18 ACTION-287: David MacD to review https://www.w3.org/WAI/GL/wiki/Using_the_aside_element_to_indicate_tangentially_related_content 16:20:18 Notes added to ACTION-287 Follow-up on aside technique. 16:20:40 TOPIC: Action 274 16:20:40 ACTION-274 16:20:40 ACTION-274 -- Katie Haritos-Shea to Review description for g4 to ensure that keyboard interface support is included. -- due 2014-09-30 -- PENDINGREVIEW 16:20:40 http://www.w3.org/WAI/GL/track/actions/274 16:21:00 "We also discussed the proposed changes to G4. The taskforce feels that no change is required and doing so would “muddy the waters”. If the WCAG working group feels that the change is necessary, we would like this revisited to align with the keyboard language coming from the taskforce so that we have consistency and keep the techniques in synch." 16:21:30 http://www.w3.org/WAI/GL/track/actions/274 16:21:45 AWK review changes 16:22:05 http://www.w3.org/TR/WCAG20-TECHS/G4.html 16:22:18 Review description for g4 to ensure that keyboard interface support is included. 16:23:00 https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/G4 16:23:15 We asked mobile task force for feed back 16:23:19 q? 16:23:32 -Kenny 16:24:19 KHR reported that she discussed with Kathy, ties back to earlier issue discussed on this call with regard to keyboard support 16:24:53 Mobile group pushed back from what KHR and Kathy though was okay. 16:25:22 AWK summaries status, we need to decide if we are changing G4 16:25:31 Do we like having additional text? 16:26:19 It is good to remind people that keyboard access is required -- but keyboard access is not specifically a related technique for G4 16:26:46 AKW summarize issue is balance of being verbose versus being complete 16:27:30 AKW points out that other SC are also required even when not specially mentioned 16:27:52 Another option: reduce description to "The objective of this technique is to provide a way to pause movement or scrolling of content. If the user needs to pause the movement, to reduce distraction or to have time to read it, they can do so, and then restart it as needed." 16:28:34 Loretta points out that the issue of keyboard access come up a lot, but this technique is not especially particular to the issue 16:29:23 q+ 16:29:25 If each technique linked to everything, the techniques would get lost 16:29:29 ack awk 16:29:44 +1 to Loretta also 16:29:54 Lots and lots of techniques could related to keyboard accessible 16:30:49 AWK observes that loading up each technique with valuable accurate and helpful information makes them hard to read 16:31:22 Might want to focus on main topic, rely on examples that include keyboard access 16:31:49 q= 16:31:55 q+ 16:32:18 Joshue concise techniques more valuable than muddying them up with related issues 16:32:46 Discussion seems to be that shorter is better 16:33:16 ack ryl 16:33:31 David opens discussion for how to link to other things to look out for 16:34:17 AWK to offer possible changes to G4 per discussion on ACTION-274 16:34:23 If a person comes to a particular technique, how do they get back to big picture that includes keyboard accessilbity? 16:34:41 ACTION-274: AWK to offer possible changes to G4 per discussion 16:34:41 Notes added to ACTION-274 Review description for g4 to ensure that keyboard interface support is included.. 16:35:03 ACTION-274: on AWK 16:35:03 Notes added to ACTION-274 Review description for g4 to ensure that keyboard interface support is included.. 16:35:39 zaki, agenda? 16:35:42 zakim, agenda? 16:35:42 I see 6 items remaining on the agenda: 16:35:43 1. Finish survey from last week [from from take up from 'Mobile TF proposed changes to G78' via Joshue via Joshue] 16:35:43 7. https://www.w3.org/2002/09/wbs/35422/14thOct2014/ [from Joshue] 16:35:43 3. Technique needed for CSS and alt text for generated content: https://www.w3.org/WAI/PF/Group/track/issues/542 [from Joshue] 16:35:43 4. Discuss Action 274 and Mobile TF feedback [from Joshue] 16:35:44 5. Follow up on Aside technique [from Joshue] 16:35:47 6. TPAC Planning: Current TPAC structure and other ideas. [from Joshue] 16:35:59 zakim, take up item 6 16:35:59 agendum 6. "TPAC Planning: Current TPAC structure and other ideas." taken up [from Joshue] 16:36:02 https://www.w3.org/2002/09/wbs/35422/14thOct2014/ 16:38:42 -Joshue 16:39:03 trackbot, end meeting 16:39:03 Zakim, list attendees 16:39:03 As of this point the attendees have been +1.617.766.aaaa, AWK, Michael_Cooper, Bruce_Bailey, EricE, David_MacDonald, Katie_Haritos-Shea, Kenny, Joshue, Marc_Johlic, Loretta 16:39:11 RRSAgent, please draft minutes 16:39:11 I have made the request to generate http://www.w3.org/2014/10/14-wai-wcag-minutes.html trackbot 16:39:12 RRSAgent, bye 16:39:12 I see 7 open action items saved in http://www.w3.org/2014/10/14-wai-wcag-actions.rdf : 16:39:12 ACTION: David to file issue on G202 regarding language distinguishing functionality from control and clarify necessity of keyboard accessibilty [1] 16:39:12 recorded in http://www.w3.org/2014/10/14-wai-wcag-irc#T15-35-04 16:39:12 ACTION: yatil to work with Katie on providing example with CSS providing sufficient contrast for placeholder text [2] 16:39:12 recorded in http://www.w3.org/2014/10/14-wai-wcag-irc#T16-03-27 16:39:12 ACTION: Ryladog to work with Eric on providing example with CSS providing sufficient contrast for placeholder text [3] 16:39:12 recorded in http://www.w3.org/2014/10/14-wai-wcag-irc#T16-03-56 16:39:12 ACTION: Katieto work with Eric on providing example with CSS providing sufficient contrast for placeholder text [4] 16:39:12 recorded in http://www.w3.org/2014/10/14-wai-wcag-irc#T16-04-11 16:39:12 ACTION: Katie to work with Eric on providing example with CSS providing sufficient contrast for placeholder text [5] 16:39:12 recorded in http://www.w3.org/2014/10/14-wai-wcag-irc#T16-04-26 16:39:12 ACTION: David to work on technique for issue 542 [6] 16:39:12 recorded in http://www.w3.org/2014/10/14-wai-wcag-irc#T16-13-54 16:39:12 ACTION: David to follow-up on aside technique [7] 16:39:12 recorded in http://www.w3.org/2014/10/14-wai-wcag-irc#T16-20-02 16:39:32 -EricE