15:52:23 RRSAgent has joined #coga 15:52:23 logging to http://www.w3.org/2017/06/26-coga-irc 15:52:31 zakim, this will be WAI_CogTF 15:52:31 ok, lisa 15:52:45 regrets: Jan, ayelet 15:53:28 agenda: this 15:53:29 agenda+ proposed new wording 15:53:31 agenda+ review SC, and timelines show status table.sc status: https://rawgit.com/w3c/coga/master/extension/status.html, rewording https://rawgit.com/w3c/coga/master/extension/rewroded%20sc%203.html agenda+ review sc wording to get to pending agenda+ Tables https://rawgit.com/w3c/coga/master/gap-analysis/table.html 15:53:32 instuctions: https://www.w3.org/WAI/GL/wiki/SC_Managers_Phase1, 15:53:34 issues: https://github.com/w3c/wcag21/issues?q=is%3Aissue+is%3Aopen+label%3ACOGA 15:53:35 agenda+ the supplement, moving forward 15:53:37 agenda+ What have we missed for issues page 15:53:38 agenda+ be done 15:54:01 zakim, close item 4 15:54:01 agendum 4, personlization, closed 15:54:02 I see 9 items remaining on the agenda; the next one is 15:54:02 3. accessible authentication [from lisa] 15:54:11 zakim, close item 3 15:54:11 agendum 3, accessible authentication, closed 15:54:12 I see 8 items remaining on the agenda; the next one is 15:54:12 5. the supplement, moving forward [from lisa] 15:54:16 zakim, close item 5 15:54:16 agendum 5, the supplement, moving forward, closed 15:54:17 I see 7 items remaining on the agenda; the next one is 15:54:17 6. What have we missed for issues page [from lisa] 15:54:22 zakim, close item 6 15:54:22 agendum 6, What have we missed for issues page, closed 15:54:23 I see 6 items remaining on the agenda; the next one is 15:54:23 7. be done [from lisa] 15:54:27 zakim, close item 7 15:54:27 agendum 7, be done, closed 15:54:29 I see 5 items remaining on the agenda; the next one is 15:54:29 8. proposed new wording [from lisa] 15:54:51 zakim, item 8 15:54:51 I don't understand 'item 8', lisa 15:54:58 zakim, open item 8 15:54:58 agendum 8. "proposed new wording" taken up [from lisa] 15:55:43 proposed new wording for personlization. See https://github.com/w3c/wcag21/issues/6. (the wording is at https://rawgit.com/w3c/wcag21/support-personalization_ISSUE-6/guidelines/sc/21/support-personalization-minimum.html) 15:57:40 kirkwood has joined #coga 16:02:26 Mike_Pluke has joined #coga 16:02:59 proposed new wording for personlization. See https://github.com/w3c/wcag21/issues/6. (the wording is at https://rawgit.com/w3c/wcag21/support-personalization_ISSUE-6/guidelines/sc/21/support-personalization-minimum.html) 16:03:43 not quarum but worth ploding on 16:07:36 core: the mimimum functionality and content that is needed for users to identify the topic and fulfill the purpose of the content 16:07:38 For example, core content is generally identified by the page title. Core functionality is that which is needed to fulfill the purpose described by the page title. 16:11:22 Pietro has joined #coga 16:11:41 Present+ Pietro 16:12:12 http://www.bbc.com/ 16:19:06 john: top navigation is very important 16:19:52 we need to include top navigation 16:21:22 mike example: going on bookign.com, might just be intersted in checking iteninary, but if i came to book then that would be core 16:21:43 Lisa: I would say they are both core 16:22:07 has to have direct link to page titile 16:22:08 present+ 16:22:44 scribe: kirkwood 16:22:52 present+ Mike_Pluke 16:23:19 criss do you know how to add the audio? 16:23:20 discussing core content 16:24:00 Lisa: what is core content, lets start with BBC news as en example 16:24:21 Lisa: one issue we have to keep main navigation open consistent 16:25:14 MC: think those are sepaparate issues with core content. simply to be identified 16:25:35 MC: at user request rather than user preferences 16:25:58 MP; no body would want to lose top level navigation 16:26:21 MC: might prefer naviation to be rmoved if i can get it back 16:27:57 MC: larger screen and smaller screen. Doesn't like need to learn about how to use hamburger menu 16:28:58 MC: personlzation can in theory would play in context of another criteria to get to SC 16:29:33 MP: if start adding additional words would be an issue 16:30:18 LS: do we want to say remove some core content, we need a tight definition on non core functionlity 16:30:49 MC: don't think page title should be too baked into SC 16:31:22 MC: better to be as general as we can be 16:33:57 MC: meant to navigate headings and follow links. prefer to leave wiggle room and clarify understand and leave room to do in different ways 16:34:12 Lisa: issn't that a problem with testability? 16:35:13 MC: often different evaluators report different results. each have valid interpretation and one way testers and authors differentiate themselves 16:35:30 LS: but won't go through i think 16:35:59 MC: trying to go for generic success criteria. need to get it through 16:36:28 LS: my take is it will fail for that. maybe michael reply to Alastair and see if thats ok with him 16:37:06 LS: anything that people had gone to site to find it would be core 16:37:38 MC: arguably that is contextual. don't see how address that personalization requirment without living with some vagueness 16:38:04 MP: doubt he is the only one with question. trying to get it close is tricky 16:38:59 LS: if user is going to page to find content than it is core. unless we make it more vague like you can remove some content 16:39:18 LS: if don't relate to page title some content can be removed 16:40:33 LS: some lesser used or non core content can be removed 16:40:44 LS: that way they have ocnformed 16:41:24 LS: the first bullet point is the way we can get people into personlization without adding RDs or something else 16:41:55 MC: in general, a SC we don't go as far as we hoped is something we lived with in 2.1 16:42:24 LS: the first is way to get perosnlization in we'd prefer the second but realize it is an issue 16:42:56 LS: the BBC example to remove some core content as a good example 16:43:27 MC: if it will pass under that expection yes. we are mainly setting up future work but we are getting some stuff in 16:44:19 MC: via education material there is a site called the before after demo. here is what we mean by it even at mimimal compliance its a low bar. we're setting the floor not the ceiling 16:45:15 LS: fany other isssues with this support perosnliaztion SC 16:45:37 zakim, next item 16:45:37 agendum 9. "review SC, and timelines show status table.sc status: https://rawgit.com/w3c/coga/master/extension/status.html, rewording 16:45:39 ... https://rawgit.com/w3c/coga/master/extension/rewroded%20sc%203.html agenda+ review sc wording to get to pending agenda+ Tables 16:45:39 ... https://rawgit.com/w3c/coga/master/gap-analysis/table.html" taken up [from lisa] 16:45:50 LS: i can respond or Miichael can respond to Alistair 16:46:28 https://rawgit.com/w3c/coga/master/extension/status.html 16:47:08 LS: look at status link page. we've got groups that we thought most important. interrupiton, task completion didn't get through, mimize 3errors didn't get through, reminders, help 16:47:41 LS: we can try and push through high prioriy ones 16:48:17 LS; go through list of things [audio dropping out] 16:48:39 LS: the others are important, chunks, undo might be able to get in 16:48:48 LS: timed events didnt get through 16:49:11 LS: critical reature, erro prevention, change upon reequest that one maybe try and get through 16:49:32 LS: slightly lower retunr clear text voice 16:49:53 LS: not seeing things hit me as likely to get in 16:51:09 Ls: lets look sat issue 38 undo 16:51:27 LS: that one might get through 16:51:53 MC: that might be relatively straight forward and benefit various user groups 16:52:09 LS: another i thought was important was task completion 16:52:42 LS: a lot laike the authtication one just for any task acnc could include dialogues could borrow some wording and work on that 16:52:52 LS: do people think thats important? 16:53:35 LS: one important to me is the press 3, with issue of processing language you can't do both 16:53:53 MC: foreign language happens all the time 16:54:35 https://github.com/w3c/wcag21/issues/21 16:55:10 LS: issue 21 we are talking 16:55:48 MP: task completion imbedded in authitecation 16:56:20 MC: we have asked to submit duplications all the time we need to remind over an over 16:56:33 LS: what is more important task completion of undo? 16:56:48 MC: i feel undo is clearer and easier to get through id focus on thath 16:57:12 LS: i'll pull up undo 16:57:35 LS: doesn't have links on top of it 16:57:51 MC: i can add but have to remind me 16:58:19 LS: jake has some edits there we can put in on a short call, like clearly labeled actions 16:58:28 LS: i say the next one is undo 16:58:43 LS: maybe end now 16:59:12 LS: we got a lot done even though not a big call 16:59:40 rrsagent, make logs public 16:59:54 rrsagent, create minutes 16:59:54 I have made the request to generate http://www.w3.org/2017/06/26-coga-minutes.html lisa 17:00:05 zakim, please part 17:00:05 leaving. As of this point the attendees have been kirkwood, MichaelC, Pietro, janina, Mike_Pluke 17:00:05 Zakim has left #coga 17:00:37 rrsagent, please part 17:00:37 I see no action items