See also: IRC log
<scribe> scribe:JaEunJemmaKu
next item
<mck> https://github.com/w3c/aria-practices/issues/228
jon worked on this.
mck: one comment about context
menu
... I would like to solicite context menu from the group
mb: I think context menu feedback only works on ff
Ann: we need to make that, context menu, optional.
brian: context menu through javascript window?
mck: we may want to open a
separate issue for this.
... I will take care of this after the meeting.
... issue 183 is done?
mb: I am done
ann: can we assign the reviewer?
mck: I will do that after the meeting
<MichielBijl> https://github.com/w3c/aria-practices/issues/187
<MichielBijl> https://github.com/w3c/aria-practices/pull/266
<MichielBijl> I have updated issue 187 to have a checkbox for the separators.
mck: do we need further discussion on content info?
<annabbott> https://github.com/w3c/aria-practices/issues/249
mck: anything decorative should be silent
jongund: developers may not think about aria property like we do.
brian: developers use bg image or css content but it is not a deal breaker.
jongund: I would like to suggest
that we may want to add info for these different techniques to
show different states.
... there is separate issue for bg image - color contrast
issue.
<jamesn> does this work - https://www.w3.org/TR/css-content-3/#alt
mck: the best practices are 1) content css property and 2) inline style image
james: text alternative for content image is working?
michiel: it is not implemented any where yet
brian: one way it can be done is using span tag with aria- hidden true and add css style
mck: we dont
<MichielBijl> https://rawgit.com/MichielBijl/font-awesome/master/tests/index.html
mck: we don't know yet about that technique.
jongund: then what should be done to finish the example?
bijl: here is aria-hidden example with font awesome
https://rawgit.com/MichielBijl/font-awesome/master/tests/index.html
mck: our discussion regarding
this landed on 1) content css property 2) aria -hidden
... I will create the issue for this.
<mck> https://github.com/w3c/aria-practices/issues/274
jongundL it seems all the example with bg image to indicate state should be changed with css content property
james: yes
mck: yes
jongund: I would like to put all different techniques into a table with advantage vs disadvantages
+1 for Jon's suggestion
brian: there is another technique using pseudo Classes to update states.
next item
mck: michiel suggested use <pre> in html source code for APG example page
michiel: browser issues
mck: can you fix example.js, Michiel?
mb: yes
next item
mck: in the menu pattern, see the potential confusion 'pop up' vs 'submenu'
<jongund> JG: I think we should be consistent
brian: we should use the word 'submenu' if it is used for menu
mck: good point, brian - I did
not think about pop up widget.
... so I will make it consistent to use "submenu"
next item
<mck> http://w3c.github.io/aria-practices/examples/menubar/menubar-2/menubar-2.html
<jongund> https://github.com/w3c/aria-practices/issues/144
agenda 4
<mck> https://github.com/w3c/aria-practices/issues/144
<mck> https://github.com/w3c/aria-practices/issues/144
<sirib> http://w3c.github.io/aria-practices/#menu
next item
This is scribe.perl Revision: 1.148 of Date: 2016/10/11 12:55:14 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/context menu/ context menu feedback/ No ScribeNick specified. Guessing ScribeNick: jemma Found Scribe: JaEunJemmaKu Present: AnnAbbott JamesNurthen MattKing Shirisha Balusani JaeunJemmaKu Bryan Garaventa MichielBijl jongund WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 06 Feb 2017 Guessing minutes URL: http://www.w3.org/2017/02/06-aria-apg-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]