14:36:11 RRSAgent has joined #coga 14:36:11 logging to http://www.w3.org/2015/10/19-coga-irc 14:36:54 agenda: this 14:36:56 agenda+ review actions, and timelines reminder about next weeks call 14:36:57 agenda+ Proposal for aria, importance or occurrence? and lisa's new thread 14:36:59 agenda+ Proposal for wcag 14:37:00 agenda+ Issue papers - GA 14:37:02 agenda+ Techniques - GA 14:37:03 agenda+ Next ftf ideas (TPAC and Katie suggestion) 14:37:05 agenda+ Other issue papers such as mobile 14:37:06 agenda+ be done 14:38:02 regrets: John Rochford 14:59:28 janina has joined #coga 15:51:45 Chaohai_Ding has joined #coga 15:58:43 ayelet_seeman has joined #coga 16:00:31 Mike_Pluke has joined #coga 16:05:35 scribe: ayelet_seeman 16:06:19 Present+ Mike Pluke, Lisa Seeman, Ayelet Seeman, Chaohai Ding 16:06:39 nexyt item 16:06:42 next item 16:07:35 https://rawgit.com/w3c/coga/master/issue-papers/links-buttons.html 16:09:36 LS: We won't have a call next week, as I (Lisa) will be traveling and we will have a joint call the next morning 16:10:45 present+ Janina 16:13:06 https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2015Oct/0047.html 16:13:12 Tony has joined #coga 16:13:52 q? 16:15:07 LS: what we actually want aria-importance 16:15:18 q+ 16:15:56 MP: doesn't like calling it personalisation, but rather a simplification for the average user 16:16:46 LS: It is a personalisation because you enable people to control how many features they want 16:17:29 MP: yes, the personalisation is built on top of the simplifacation 16:18:29 aria-importance= "critical" this content is essential for the key function of the page (Example: The send button for an email draft) OR if it is sometimes critical to a user being able to use the site, such as "save my work" or "emergency instructions" OR if it is used by over 90% of users most times they use the content, If you were making an interface as simple as posible, this is what you... 16:18:31 ...would keep 16:18:32 LS: should we keep it as personalisation, and change the description to "the simplest possible interface"? 16:21:26 AS: what with aria-simplification? 16:21:55 MP: best 16:23:41 AS: how would we name the different levels? 16:23:43 Q+ 16:24:00 LS: Simplest, high, med, low 16:24:11 ? 16:24:16 q? 16:26:50 TD: talked to a web developers about this, and there was a discussion over advertisements, as well as the revenue generators versus the highest traffic 16:27:42 LS: that's why frequency has to be included. If they are conforming to the spec, it will be the traffic 16:28:11 ... Suggests adding this as an open issue 16:29:03 Present+ Tony Doran 16:30:04 LS: we could change it to 90% of this user group 16:31:14 q? 16:31:21 ack t 16:31:44 LS: would you like me to write up something adding context? 16:31:59 https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2015Oct/0045.html 16:33:40
16:33:41
16:36:07 LS: this is the replacement for the easylang tag 16:36:07
16:36:09 In studies it was found that only 30% of users prefer long convoluted text with obtuse words and lots of numbers, with 56% claiming there preferred the simplified text , with the remainder unsure or stated it depends on the context
16:37:37 the problem is that we had a long list of different tags for different users. 16:37:45 Q? 16:37:57 Simple is good :)( 16:41:24 LS: it sounds like we don't know what we want, whicjh is a problem as we'll be eaten alive in the call in a week 16:43:37 LS: from the developers point of view the second option is simpler 16:49:50 TD: what we do is say we need to provide alternative text so that everyone could understand it. but the content providers see it as that the content needs to be understandable by everyone 16:50:11 LS: some people like the full information 16:50:46 ... or content with numbers, non literal, etc. 16:51:32 (in answer to why would someone want the non simplified version) 16:52:07 MP: the issue is that there need to be different alternatives 16:54:00 LS: back to the question, which way of doing it is bette, do we want to make the developers insert a span in to the div, or do we prefer to enable them to provide only one alternative 16:56:13 TD: the content provider should see if the numbers are needed and if they are include 16:56:21 slim has joined #coga 16:56:40 LS: do we want to enable both? 16:59:44 TD: It enables an easy way of doing it, and lets people who know what they're doing do it in a better more robust way 17:00:21 17:00:29 or 17:00:30 17:00:36 or (option 4 - can be with option 1,2 and 3) 17:00:38 17:00:44 URI 2 may read: 17:00:45 17:00:47 17:01:42 I need to drop off - sorry 17:04:01 whjat is neater? 17:04:15 chaals are you there? 17:04:58 LS: we could put them both in the proposal, and let them decide 17:05:23 ayelet? 17:05:39 rrsagent, make logs public 17:07:13 rrsagent, create minutes 17:07:13 I have made the request to generate http://www.w3.org/2015/10/19-coga-minutes.html Lisa_Seeman 17:07:36 zakim, please part 17:07:36 leaving. As of this point the attendees have been Rich_Schwerdtfeger, Mike, Pluke, Lisa, Seeman, Ayelet, Chaohai, Ding, Janina, Tony, Doran 17:07:36 Zakim has left #coga 17:07:46 rrsagent, please part 17:07:46 I see no action items