<LisaSeemanKest> http://w3c.github.io/apa/fast/checklist
<LisaSeemanKest> ageda?
<scribe> scribe: Rachael
zakim takeup item 1
Lisa: WCAG 2.2 Update
Rachael: We went through the SC but didn't get to Undo errors. Most at risk is Most Important Things. Everything else had good feedback and moved forward.
Michael: In and out but what he heard sounded like it could lead to a successful path for SC
Rachael action to invite Steve and John Kirkwood to the WCAG meeting to discuss Undo Errors. Include relevant links
<JohnRochford> I was present for all COGA discussions during the AGWG meeting at TPAC.
Lisa: I asked more experts for input on mental health. We did get more input
<JohnRochford> I reviewed the text for Silver. I suggest it be copyedited before it is sent.
Rachael: Need any more comments on silver letter.
JohnRochford: did review.
Lisa: Update, In the APA group,
there is a checklist that Michael is working on so groups can
self evaluate whether they support full accessibility support.
Some of COGA needs are included but I think there are things in
our patterns and other documents that are not in the
list.
... If you can't support our patterns in these technologies,
then content creators can't support. Its important for platform
creators. Does anyone want to take a stab at reviewing it?
Comparing our patterns with our document?
<LisaSeemanKest> http://w3c.github.io/apa/fast/checklist
Michael: This checklist is aimed at technologies not authors. The patterns to content won't apply but the technology to facilitate the patterns apply.
Lisa: Make sure the support is
there. Can you use something that saves a password or use an
extension in this platform?
... how well is that reflected in the platform?
Michael: Let me offer a
translation. Instead of saying can you use a password, it would
say does it support authentication?
... extensions are user agent features. You might say
extensibility of the technology. Not all technology needs to be
extensible. What categories of technologies need to provide
extensibility. If extensibility features are provided, they
provide full support of accessibility features. Accessibility
features are avialable to increase accessibility.
... we need to be reasonable about what we are asking
technology.
Lisa: This is for groups creating
technology. Does anyone want to volunteer to take a look at
it?
... any other TPAC updates?
Lisa: We have user needs
everywhere. We want to make sure in all our documents, we have
all the user needs represented. That each user need has a
persona and a pattern.
... its part of the next version of content usable and the gap
analysis.
... we had user needs in two places in the gap analysis and
also in the design guide. Some matched up but not
consistently
... for each objective in the design guide, I pulled together
from user needs from all the places. I didn't add new ones but
made sure we had a single list.
<LisaSeemanKest> https://docs.google.com/spreadsheets/d/1Rt51xg57oZW56mfTw_t33T9zlPDOV7o4Za6veCCqDtI/edit#gid=2019648557
Lisa: The excel sheet above is
good for the editorial group but is difficult to manage so I
pulled it out into a separate document. Please take a look at
it.
... I think we need a user review of us as users/experts.
... have we got the user needs here? Are we missing any? And
the other is from an old action item to compare the user needs
to the other standards looking at this space.
<LisaSeemanKest> pending ABI - Review ETSI TR103 349 standard ETSI accessibility document move pending untill we organize our userneed
<LisaSeemanKest> https://docs.google.com/document/d/1xmmQkuZLEG014zDRVkgr3QLyINb7BNvWxqL7POn6Ei8/edit#
ABI: Is this for adding to the personas or separate?
Lisa: It is a prerequisite to the
persona work. Because we got out of synch in different places,
the work of linking the user needs to personas should likely
wait until we have a clean list.
... the order of work is (we think, please comment): 1. Create
a consolidted list of user needs. and then 2. Map the user
needs to the personas and patterns.
... this user need is met by this pattern. This user need is
described by this persona.
... Then 3. We can fill in the gaps.
... Abi, can I ask you to start on the action item of comparing
it to the ETSI standard and move that up?
<LisaSeemanKest> https://docs.google.com/document/d/1xmmQkuZLEG014zDRVkgr3QLyINb7BNvWxqL7POn6Ei8/edit#
Abi: Where it is saying things like "I know what is not a control" I would write it differently. How should they be written?
Lisa: We have a page that provides a pattern such as "I, as a ??? user, need ??? so that ???" That is another job. We need to find the template and then change these to meet the template.
Abi: You are referring to a template. Where is the template?
Lisa: On our Wiki. Need to
find.
... 3 things to do: 1. check the list by experts 2. Check
against standards 3. Get everything into template form
... Abi are you still OK with the ETSI pattern?
Abi: Yes
Lisa: John Rochford and JF, are
you willing to review this?
... John Rochford and John Kirkwood, can you read it over?
John Rochford: I do not feel comfortable doing this.
Lisa: Even if it is only some objectives?
John Rochford: I am focusing on accessible authentication.
<LisaSeemanKest> https://docs.google.com/document/d/1xmmQkuZLEG014zDRVkgr3QLyINb7BNvWxqL7POn6Ei8/edit#
John Kirkwood: I am comfortable with reviewing it again.
Lisa: Over the next week?
John Kirkwood: Yes
Lisa: I will also try to do so
but the more eyes the better.
... Then we can move forward with getting the mapping
complete
Lisa: Does anyone have questions
about the order of work?
... Question: Will people be at CSUN? Should we schedule a face
to face?
<JohnRochford> +1
+1
<JohnRochford> Yes, I will likely attend CSUN.
<abij> Not sure i can attend due to funding constraints
JF: AG typically meets Monday and Tuesday so if you want to do this, we should check with Andrew and Alastair and also get in early to make sure there is space.
Lisa: Maybe the weekend after?
Michael: That may be too many meetings the weekend after.
<JF> +1 to M. Cooper
Lisa: First we need to find out
is the group will be there. We dont' have enough people on the
call today to know.
... Next step is to ask people.
Lisa action to see if at least 5 people can go.
Rachael: Even if we don't have a full on meeting, there may be enough people there to get together in the evening.
Lisa: If we do have enough people, we get so much work done during a face to face it may be worth having one.
Lisa: Back to talking about the
FAST. Any questions?
... I have a question for Michael: What is the time scale for
this?When will it move forward? when will people start using
it?
Michael: I don't have a formal
schedule. It will be ever evolving but we are aiming for an
approved version over the next few months
... next couple months would be the best time for review.
JF: When you say reviewing, do you mean reviewing the document from the COGA point of view?
Michael: There are two documents. There is the full FAST framework. We are only looking at the checklist.
JF: I should have time to review.
Lisa: You can look at the pattern document and gap analysis.
the task is to look at the FAST checklist from a COGA perspective and compare it with the patterns to see what makes sense for the checklist ot support
<LisaSeemanKest> https://w3c.github.io/coga/content-usable/
Michael: It may be that technology doesn't support the entire pattern but that some aspect of the pattern requires technology support
<LisaSeemanKest> https://w3c.github.io/coga/content-usable/#appendix1
Lisa: There are many different groups. Example, voice xml would have to support objective 5 and 6.
JF: I am less familiar with this work here but I can do a review and go through making content usable and try to look at it through the FAST lense.
<JF> ACTION: JF to review https://w3c.github.io/coga/content-usable/ and FAST checklist
<trackbot> Created ACTION-316 - Review https://w3c.github.io/coga/content-usable/ and fast checklist [on John Foliot - due 2019-10-03].
<LisaSeemanKest> https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage#Priorities
Lisa: the last couple of minutes, we did a review of our priorities and put a summary of our reviews at the top of our actions.
<LisaSeemanKest> https://docs.google.com/spreadsheets/d/1YH4YETBmAdhfL9p8FK5ATUiXDGibeJh66psQCSUAvLQ/edit#gid=0
Lisa: it is easy to get brought
down by the fact that everything is important. We had to
prioritize our focus to remind ourselves what we are trying to
do. We also have a spreadsheet where we built a prioritization.
We wrote down everything we'd like to do.
... we had to push things down compared with priorities at the
top. Anything below a certain point we listed as wish list
items.
... we did note that everything is important. If someone gets
funding and can take it up, fantastic! This is about
facilitator and time prioritization.
... We discussed this at a prior meeting but we asked if anyone
had comments.
So this year we are focusing on the design document, WCAG 2.2 and personas. We wanted to get the gap analysis and glossary to wide review next year.
<JohnRochford> signing off now
scribe: by year 3, get the design
guide and gap analysis published. Then revisit research. That
is the order. More detail is in the spreadsheet. any
comments?
... do you all feel this is the right direction?
John Kirkwood: Yes
JF: It matches the larger pattern and vision, so yes
<abij> +1
Lisa: One thing you might take and run with if you are willing, is creating a testable statement for each pattern. Its important but only made the wishlist this year.
<johnkirkwood> bye all
bye
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/cooper// Succeeded: s/+1 to M. /+1 to M. Cooper/ Default Present: Fazio, stevelee_, Rachael, Jennie, stevelee, LisaSeemanKest, JF, JohnRochford, johnkirkwood Present: Fazio stevelee_ Rachael Jennie stevelee LisaSeemanKest JF JohnRochford johnkirkwood Regrets: EA_Draffan Jennie David Found Scribe: Rachael Inferring ScribeNick: Rachael WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 26 Sep 2019 People with action items: jf 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]