mck: meter pattern, colindextext, rowindextext should have something to review next week

TPAC review, including long term strategy and priorities

mck: one part of TPAC agenda to review
... long-term goals related to APG
... first goal has always been to get full coverage of aria spec so that folks can get guidance

<Jemma_> 1. Full coverage of ARIA spec

<Jemma_> 2. Integration of assistive technology support tables

<Jemma_> 3. Code quality and readability

<Jemma_> 4. APG Usability

<Jemma_> 5. Integration with other W3C accessibility educational resources

mck: add info about which examples can be used "right now"
... on track to deliver AT support tables next year
... quality of code, i.e. contrast issues, etc
... goal that by the end of next year that we have done an end to end audit
... longer term: usability of the apg itself, convert APG from a monolithic note into a web site.
... like WAI-ARIA Tutorials
... every time we publish, new versions of examples are created, old ones live forever
... need more educational/explanatory resources, all under one umbrella
... would need support from other groups, might need joint task force to make it happen

jon: what happened with combo box?

mck: microsoft isn't willing to go along with proposal, so more discussion is necessary
... nvda made fixes to support 1.1 model, so if we can get 1.1 pattern to work in AT, may be better not to introduce another new pattern

evan: I can do a PR for modernizing using build

sarah: I can help with build processes so that we can use more ES6 code, etc, and update examples

mck: how would this look for users?

zoe: we would still link to our js files to show the javascript

evan: can separate the type of code we require authors to write from the deployed code

james: debugging through code would not look the same as source code

sarah: can use source maps

jon: need to be careful that the code that you are seeing is not the code because is executing in the browser

mck: how much longer will we care about IE11
... people might still be required to produce stuff that works in IE11, and possibly not our job to show them how to support it

zoe: that boils down to "how many people use AT that only supports IE11"

mck: I am not aware of any AT that only supports IE11

<Jemma_> "This widget may have support gaps that can only be filled by the development of new technologies. Authors should fully test this widget before using it for a production ready project. Likewise, it may be poorly supported by certain browsers or assistive technologies."

<Jemma_> +1 for Matt's comments on the first sentence

mck: maybe first sentence and last sentence are redundant?

<Jemma_> other than that, this looks great, Mark

mck: which examples need this, other than slider?
... add it to slider first, then duplicate as needed

<MarkMccarthy> Thanks Jemma

mck: new technologies like AOM

jemma: "new technologies" sounds vague - maybe we need to specifically include AOM?

mck: don't want a dependency on AOM in wording