17:59:45 RRSAgent has joined #aria-apg 17:59:45 logging to http://www.w3.org/2017/02/06-aria-apg-irc 17:59:56 agenda? 18:00:03 zakim, clear agenda 18:00:03 agenda cleared 18:00:22 Agenda+ Around the table - quick updates on current milestone work: 18:00:23 annabbott has joined #aria-apg 18:00:32 Agenda+ Issue 248: Template pages use a div where they should use `pre` https://github.com/w3c/aria-practices/issues/248 18:00:42 Agenda+ Issue 268: Editorial consistency question: 18:00:48 Agenda+ Final review of issue 144: Review editor menubar example (menubar-2.html) 18:00:54 Agenda+ Issue 210: Review accordion example https://github.com/w3c/aria-practices/issues/210 18:00:59 Agenda+ Issue 264: Review long description disclosure example 18:01:07 Agenda+ Issue 265: Review FAQ disclosure example 18:03:35 present+ AnnAbbott 18:03:54 present+ JamesNurthen 18:03:59 agenda? 18:04:04 Meeting: ARIA APG TF 18:04:18 present+ MattKing 18:04:26 present+ Shirisha Balusani 18:04:45 jemma has joined #aria-apg 18:05:08 rrsagent, make log world 18:05:35 present+ JaeunJemmaKu 18:05:49 scribe:JaEunJemmaKu 18:06:09 agenda? 18:06:52 present+ Bryan Garaventa 18:07:19 next item 18:07:38 present+ 18:08:10 https://github.com/w3c/aria-practices/issues/228 18:08:48 jon worked on this. 18:09:15 mck: one comment about context menu 18:10:11 mck: I would like to solicite context menu from the group 18:11:19 mb: I think context menu only works on ff 18:12:06 s/context menu/ context menu feedback 18:12:44 Ann: we need to make that, context menu, optional. 18:13:43 brian: context menu through javascript window? 18:14:16 mck: we may want to open a separate issue for this. 18:14:44 mck: I will take care of this after the meeting. 18:16:57 mck: issue 183 is done? 18:17:07 jongund has joined #aria-apg 18:17:23 mb: I am done 18:18:02 ann: can we assign the reviewer? 18:18:09 mck: I will do that after the meeting 18:19:21 https://github.com/w3c/aria-practices/issues/187 18:19:28 https://github.com/w3c/aria-practices/pull/266 18:19:51 present+ jongund 18:20:52 I have updated issue 187 to have a checkbox for the separators. 18:21:32 mck: do we need further discussion on content info? 18:21:38 https://github.com/w3c/aria-practices/issues/249 18:22:05 mck: anything decorative should be silent 18:22:56 jongund: developers may not think about aria property like we do. 18:24:18 brian: developers use bg image or css content but it is not a deal breaker. 18:25:30 jongund: I would like to suggest that we may want to add info for these different techniques to show different states. 18:26:14 jongund: there is separate issue for bg image - color contrast issue. 18:27:24 does this work - https://www.w3.org/TR/css-content-3/#alt 18:27:31 mck: the best practices are 1) content css property and 2) inline style image 18:28:01 james: text alternative for content image is working? 18:28:18 michiel: it is not implemented any where yet 18:29:29 brian: one way it can be done is using span tag with aria- hidden true and add css style 18:29:37 mck: we dont 18:29:50 https://rawgit.com/MichielBijl/font-awesome/master/tests/index.html 18:30:07 mck: we don't know yet about that technique. 18:30:20 jongund: then what should be done to finish the example? 18:31:38 bijl: here is aria-hidden example with font awesome 18:32:18 https://rawgit.com/MichielBijl/font-awesome/master/tests/index.html 18:33:02 mck: our discussion regarding this landed on 1) content css property 2) aria -hidden 18:36:52 mck: I will create the issue for this. 18:37:40 https://github.com/w3c/aria-practices/issues/274 18:39:08 jongundL it seems all the example with bg image to indicate state should be changed with css content property 18:39:15 james: yes 18:39:21 mck: yes 18:43:34 jongund: I would like to put all different techniques into a table with advantage vs disadvantages 18:44:07 +1 for Jon's suggestion 18:45:27 brian: there is another technique using pseudo Classes to update states. 18:45:50 next item 18:47:17 mck: michiel suggested use

 in html source code for APG example page
18:47:51  michiel: browser issues
18:48:22  mck: can you fix example.js, Michiel?
18:48:28  mb: yes
18:49:06  next item
18:50:16  mck: in the menu pattern, see the potential confusion  'pop up' vs 'submenu'
18:50:49  JG: I think we should be consistent
18:51:02  brian: we should use the word 'submenu' if it is used for menu
18:51:33  mck: good point, brian - I did not think about pop up widget.
18:51:57  mck: so I will make it consistent to use "submenu"
18:51:59  next item
18:52:21  http://w3c.github.io/aria-practices/examples/menubar/menubar-2/menubar-2.html
18:54:03  https://github.com/w3c/aria-practices/issues/144
18:54:23  agenda 4
18:54:25  https://github.com/w3c/aria-practices/issues/144
18:54:47  zakim, take up agenda 4
18:54:47  agendum 4. "Final review of issue 144: Review editor menubar example (menubar-2.html)" taken up [from jamesn]
18:54:56  https://github.com/w3c/aria-practices/issues/144
19:00:34  http://w3c.github.io/aria-practices/#menu
19:01:15  next item
19:02:13  rrsagent, make minutes
19:02:13  I have made the request to generate http://www.w3.org/2017/02/06-aria-apg-minutes.html jemma
19:02:32  make log public
19:02:41  https://github.com/orgs/w3c/teams/aria-contributors
19:20:32  Ann, webex cutt me off
19:20:39  me too
19:21:12  I didn't have much else to say - just wanted to share that with you...