<JaEunJemmaKu> +present JemmaJaEunKu
<JaEunJemmaKu> https://github.com/w3c/aria/pulls
<JaEunJemmaKu> https://github.com/a11ydoer/practices/blob/master/examples/link/link.html
<JaEunJemmaKu> https://github.com/a11ydoer/practices/commit/bc68c3f6324fd91031fee59482544e5f334ee8c9
<scribe> scribe: matt_king
Changing agenda to look at John's example templates first.
<JaEunJemmaKu> https://rawgit.com/a11ydoer/practices/master/examples/link/link.html
<JaEunJemmaKu> https://rawgit.com/a11ydoer/practices/master/examples/button/button.html
JG: made adjustments to overall structure
... 4 sections, each w/l2 heading
... sections: example, kb support, roles/states/props, source code
mk: the example section has a table with different forms of the example
... for composite widgets, we probably can't do that in a single table
... we should probably have multiple sub h3 sections for multiple composite examples
discussion of format of source section
<JaEunJemmaKu> https://rawgit.com/a11ydoer/practices/master/examples/button/button.html
discussion of use of bg images in techniques and compatibility with high contrast mode.
jg: is using bg images on spans an authoring error
mk: not an error, but a limitation in ability to support hc mode
... apg examples shoyuld support hc mode
<JaEunJemmaKu> it use this, <script> sourceCode.add('sc1', 'example') sourceCode.make() </script>
<JaEunJemmaKu> to generate the code
mk: how is the source section generated?
jg: a js utility is generating it
... it is in the root jsdir for all examples
... where common js shared by all examples sit
... will work on creating 3 separate source regions in the source section, one for each link example