+AWK

<alastairc> +alastairc

AC: how is progress, I hear that it is still challenging to get people involved

<kim> https://docs.google.com/spreadsheets/d/1wRAViPfAJ4Ytqc71tGZp6gU07HNd2QQaNgtJsog-D90/edit#gid=0

Kim: We have a spreadsheet of older discussions so we have everything in one place
... in the proposals link there is what is needed and why, and proposal text
... some things are clashes with other user needs.
... seems like this is a good time to talk about these and try to resolve, whether destined for 2.2 or Silver
... some problems may not be solvable
... other tabs are self-explanatory - other conversations and info to avoid going around and round

AC: Can see some overlaps, but don't see many clashes
... more common issues

KIm: Agreed, but there are some
... that we should look at
... not many people have commented, so we do need to get more people involved
... Last time we had issues that got handed to one TF and then the other TF didn't worry about it - we should be more coordinated.

JA: Agreed.

AC: How about LVTF?

<AllanJ> http://w3c.github.io/low-vision-a11y-tf/user-needs-coverage.html

JA: our document
... trying to decide if something is author/user agent/other issue

AC: Wonder about a joint LVTF/MATF session to discuss these

MATF meets on Thursdays at 11am ET, LV does too

Kim: You seem more organized.

JA: ha ha ha

Talking about joint TF meeting next week - kim thinks might be early, or would need another meeting later

Kim: Perhaps Jan 10?

JA: Can do that

Kim will confirm with Kathy

AC: mentions the goal of having lists of items that might be in a future update - in January.
... How about Silver Jeanne?

JS: Working on conformance model
... it is hard - details

hard with TF participants not wanting to write stuff

scribe: love to talk, less love to write things
... we are going to do a sketchier conformance prototype than we would ideally want
... it will likely get more criticism but we aren't getting all of the expert support we need
... we can add editor's notes to help indicate what sections need more or less work
... conformance model is in good share at high level but runs into problems at the detail level
... we are also updating the IA prototype
... got good feedback on that one and some feedback on the plain language prototype but less
... than the info arch one
... LVTF was very helpful - really worked through the whole process
... didn't get tests from other TFs
... Particularly need COGA

Kim: Can you share what LVTF did - we can model off that

AC: CC Steve Lee and me for COGA

<alastairc> https://webaim.org/discussion/mail_thread?thread=9054

Kim: Do we have a good mechanism to gather examples?
... instead of submitting a technique, which is hard
... do we have a way to allow people to submit good and bad examples, and use cases?
... "here's my issue that you should know about"

<AllanJ> https://web-a11y.herokuapp.com/

AC: open to suggestions for what we could do

TF updates to WG

JA: Will do Dec 11

Kim: will do the 18th, maybe, will check with Kathy

COGA the week after christmas?

trackbot, end meeting

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/LVTF/LVTF?/
Default Present: Alastair, Andrew, Jeanne, Jim, Michael, Kim

WARNING: Replacing previous Present list. (Old list: Alastair, Andrew, Jeanne, Jim, Kathy, Mary, Jo, Michael, Shawn, Kim, AWK, alastairc)
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ Alastair, Andrew, Jeanne, Jim, Michael, Kim

Present: Alastair Andrew Jeanne Jim Michael Kim
No ScribeNick specified.  Guessing ScribeNick: AWK
Inferring Scribes: AWK

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 05 Dec 2018
People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)