<LisaSeemanKest> scribe: stevelee_
Lisa: added priorities to the planning page
steve: will update personas tomorrow
Lisa: will add action for Lisa /
Rachael to work on Web Design Guide
... WCAG 2.2 going well
... TPAC will see heavy reviewing so would be good to get the
SCs ready for that
David: good discussion and some
debate about overlap with others items
... eg failure techniques are educational purposes not just for
law. But no blockers
Rachael: feels is raady for TPAC,
David agrees
... will send email explaining what we need to be ready for
TPAC
https://www.w3.org/WAI/GL/task-forces/coga/wiki/WCAG_2.2_Success_Criteria_Groups
Rachael: will clarify what action on Steve creating feedback tab is.
<LisaSeemanKest> https://docs.google.com/spreadsheets/d/1Rt51xg57oZW56mfTw_t33T9zlPDOV7o4Za6veCCqDtI/edit#gid=2019648557
<LisaSeemanKest> ach je
Lisa: we are working on Content Usable mapping - including needs across all docs
Jennie: notes this is in table
and where cells are blank Assistive Tech may be confused
... suggest adding some text in empty cell to aid orientation /
understabding
Lisa: pleased jennie raised as highlights a spreadsheet is not a good base format
<Jennie> https://docs.google.com/spreadsheets/d/1lWTTYjzoCDx6goBCMH7pI72nsuIGu35JDu1hYGlyCwY/edit#gid=0
rachael: Need tab in spreadsheet to tack changes and feedback
Jennie: link is to new glossary
suggestions spread sheet - see above
... request for confirmation that is what we want for the
glossary
Lisa: is great to have the exaple
to see if this is a good format
... is clear that needs a picture to make it clear to people
external to the TF
... maybe a short definition for our use and longer general
one?
steve: possibly add new column for link to our personas
Jennie: need to consider focus so add Persona link to wards end of rows.
Steve: do we need long definition as could just have enough for our documents
Lisa: people might need need more detailed explanation
Jennie: popups and full non technical definition might work
Jannie: are the a resonable number of characters available in tools?
<Jennie> +1, as long as we have an idea of character numbers if we are going to have a way to use it
Lisa: should we add a short lang
version
... can add them later
<LisaSeemanKest> https://docs.google.com/spreadsheets/d/1YH4YETBmAdhfL9p8FK5ATUiXDGibeJh66psQCSUAvLQ/edit#gid=0
lisa: did this to help coordinate
co-chair work, then decided to share as is useful
... all are important and will not reject work but will not
gove it time every week unless high priority
<Jennie> Thank you for helping us track the action items, Lisa!
Lisa: please take a week to think about the priorities and let us know if anything is important
<Jennie> * Have to drop off for another meeting. Talk to you next week.
<Rachael> Suggest: Change column B label to Priorities
EA: seems a lot of priorities!
Lisa: up to row 12 is year 1 and
rest is later
... add a breaking row to make it clearer.
david: Utah Tredavis (ORCAD) has done a lot of AI work which may be worth exploring
EA: amazing work but not sure how it links to our work
david: we could contact them
<LisaSeemanKest> https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2019Sep/0007.html
<Fazio> Its OCADU
<Rachael> 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/jeniie/jennie/ Default Present: Fazio, stevelee_, Rachael Present: Fazio stevelee_ Rachael Regrets: John R. Abi Found Scribe: stevelee_ Inferring ScribeNick: stevelee_ WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 05 Sep 2019 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.)[End of scribe.perl diagnostic output]