W3C

COGA

04 Jan 2018

Attendees

Present
Regrets
Chair
Lisa
Scribe
alastairc

Contents


<scribe> scribe:alastairc

<LisaSeemanKestenbaum> zakim take up item 6

any updates

Lisa: Any interesting updates?

Update WCAG 2.1

Lisa: WCAG 2.1 situation update -

<LisaSeemanKestenbaum> https://www.w3.org/TR/WCAG21/

Lisa: we are at a stable last review of the working draft, so the intent is not to chance any SCs from this point.
... in a month or 2 we're aiming for CR, so takes strong objections for changes.

https://w3c.github.io/wcag21/guidelines/

<LisaSeemanKestenbaum> https://w3c.github.io/wcag21/guidelines/

Lisa: We have in the most cutting edge things, purpose of controls, identify pupose. Accessible Auth went to AAA, but didn't get in.
... tried to do time-outs at triple-A, but didn't see that go in. Interuptions, don't think that got in either.
... The more advanced ones are more compatible with how WCAG works, but others are less reliant on technology didn't make it.
... biggest task is making sure there is enough support implementation, and doing techniques & understanding.

<kirkwood> As per Alastair that was my understanding to.

<LisaSeemanKestenbaum> zakim take up item 7

<kirkwood> agree with Alistair about bridging towards Silver in order to provide proper guidance. Hoping that will be into Silver as well

<LisaSeemanKestenbaum> silver

Lisa: One of the streams of work this year is to compile the work done that hasn't gotten into WCAG.

<neilmilliken> +1 to bridging towards silver

Lisa: Not sure we are represented in the Silver stream of work?

<LisaSeemanKestenbaum> -WCAG support, including support for implementations and understanding documents

<LisaSeemanKestenbaum> -building techniques for WCAG

<LisaSeemanKestenbaum> -guidance for making coga friendly content and application

<LisaSeemanKestenbaum> -issue papers on navigation,

<LisaSeemanKestenbaum> -more user research modules including emotional disabilities

<LisaSeemanKestenbaum> -support for APA

<LisaSeemanKestenbaum> -silver

<LisaSeemanKestenbaum> +1

Neil: With Silver, entirely agree, should look towards that. Like the BBC guidelines, they are more COGA friendly! How do we influence Silver?

<kirkwood> I could help with connectivity to Siler

Lisa: If we get the spec out, and people use it, blog about it etc. Then silver will need to use it.

<kirkwood> Siler/Silver

Lisa: Need to keep an eye on Silver, do we know anyone involved from a COGA point of view.

John: Been in touch with Sean and Jeanne when doing Silver presentations, I can connect more to them if that is useful.

Lisa: Let's just check in with them, perhaps John, Alastair?
... if they build up a stakeholders base, let's make sure that we know what's going on.
... I tried, found their stakeholder questionnaire very long and confusing.
... we should check in on who the stakeholders are, users of the guidelines? Not sure at the moment, if it is everyone, that might not be working yet.

<kirkwood> https://www.w3.org/WAI/GL/wiki/Process_of_Designing_Silver

Lisa: John, could you check that COGA is being including in the process, and the stakeholders?

<LisaSeemanKestenbaum> ACTION: kirkwood to check with silver that coga experts are being included in 1. process and 2. stakeholders [recorded in http://www.w3.org/2018/01/04-coga-minutes#action01]

<trackbot> Created ACTION-251 - Check with silver that coga experts are being included in 1. process and 2. stakeholders [on John Kirkwood - due 2018-01-11].

<LisaSeemanKestenbaum> -WCAG support, including support for implementations and understanding documents -building techniques for WCAG -guidance for making coga friendly content and application -issue papers on navigation, -more user research modules including emotional disabilities -support for APA -silver

Lisa: For WCAG 2.1, need to support those, get the support for implementations. Understanding documents are in progress, and the techniques. Have the WCAG deadlines for that.
... Another topic is support for APA, they review various standards. Would like to be more closely involved in that, e.g. for knowing more about WebAuth.
... 3rd: Doc putting together COGA friendly additions.
... missing the gap-analysis, getting through the process and updating it more often.
... also have pending the additional issue papers, and the user-research module.
... that's quite a lot for this year! Is that what the group wants to be doing?

Neil: Seems like a lot to do. Need the time to dedicate to it. I'm cautious about it, need to focus strategically.

<LisaSeemanKestenbaum> do we need to reurte?

John: I agree with Neil, and maybe we should address that, try and get more people into the task force? Silver also have the issue, big ball to roll up hill, so the more people the better. Let's bring in more stakeholders.

Lisa: I agree we should recruit. It isn't a question of needin less stuff, it is what we can realistically do.
... issue papers a bit lower priority, need to gather up what we have already, make it more findable, digestable. We need to finish that off.

<LisaSeemanKestenbaum> WCAG support, including support for implementations and understanding documents

<LisaSeemanKestenbaum> -building techniques for WCAG

<LisaSeemanKestenbaum> -guidance for making coga friendly content and application

<LisaSeemanKestenbaum> p1

<LisaSeemanKestenbaum> gap anais published with all we have.

<LisaSeemanKestenbaum> -support for APA

Lisa: hearing that support for APA is P1, is that right?

Neil: Issue we have, whilst APA is important, is creating workable techniques. We might struggle with that. Need help with that...

Lisa: APA is something a bit different, they are a parent group, reviewing other people's specs.
... Yanina will tell us if there are things to review.

<LisaSeemanKestenbaum> -WCAG support, including support for implementations and understanding documents

<LisaSeemanKestenbaum> -building techniques for WCAG

<LisaSeemanKestenbaum> -guidance for making coga friendly content and application

<LisaSeemanKestenbaum> -gap analisiss

<LisaSeemanKestenbaum> -curent support for APA

<LisaSeemanKestenbaum> -recute

Lisa: I'll change priorities, so current support for APA is adhoc, we help when asked.
... we can also put in techniques for other SCs that might help.

<LisaSeemanKestenbaum> p1

Lisa: do those priorities make sense, is there anything to put at P2?

<Mark_Wilcock> Agree with those prioritise

<LisaSeemanKestenbaum> -addtion support for APA

<LisaSeemanKestenbaum> -issue papers on navigation,

<LisaSeemanKestenbaum> -more user research modules including emotional disabilities

<LisaSeemanKestenbaum> -silver

<LisaSeemanKestenbaum> p2

<LisaSeemanKestenbaum> ACTION: neil, kirkwood and all to try with recuting [recorded in http://www.w3.org/2018/01/04-coga-minutes#action02]

<trackbot> Error finding 'neil,'. You can review and register nicknames at <http://www.w3.org/WAI/PF/cognitive-a11y-tf/track/users>.

<LisaSeemanKestenbaum> ACTION: neilmillikem, kirkwood and all to try with recuting [recorded in http://www.w3.org/2018/01/04-coga-minutes#action03]

<trackbot> Error finding 'neilmillikem,'. You can review and register nicknames at <http://www.w3.org/WAI/PF/cognitive-a11y-tf/track/users>.

<LisaSeemanKestenbaum> ACTION: neil millikem, kirkwood and all to try with recuting [recorded in http://www.w3.org/2018/01/04-coga-minutes#action04]

<neilmilliken> We need a basic person spec

<neilmilliken> or specs

Lisa: Would it be better to meet every other week?

John: I'd rather not at this point, seems too soon.

Alastair: I think a weekly short meeting is best for now.

<LisaSeemanKestenbaum> (see https://docs.google.com/document/d/1WcfVALVq8PS9CLXUuAfV9Op0wXvI2yJYedj5jO23GTk/edit#heading=h.rgqn5t5157lo)

Lisa: Moving onto the content for making things accessible for COGA people.
... I'll put the tooling question to next week, painful issues around github.
... this week let's close off the recruiting issue.
... I see a few options:

<LisaSeemanKestenbaum> more expetease in the challanges use technolgy faced by people coga

<Mark_Wilcock> +1

<kirkwood> +1

Lisa: 1 is more expertise on the challenges faced by COGA people. Not even limited to the web, given IOT and navigation. Having more people who are eager, and understand.
... 2 is people who can read & write specs, speak to the technical community about integrating the needs of COGA into the technologies.

<LisaSeemanKestenbaum> who can read specification, write technical advice speek to the technical comunity about intergrating the needs of coga intotechnolgy support

<kirkwood> +1

<Mark_Wilcock> +1

+1, I'd be happy to write something to encourage participantion from the second group.

<neilmilliken> +1

<Mark_Wilcock> Cannot get Mic to work with WebEx

Lisa: We've all had issues with WebEx, let us know if we can help.
... Google docs issue, we've been working on pulling the various checkpoints togehter. Much of it is in github already, which I can copy in, it will become long and huge. Is there any way we can use github with a wysywig?

trackbot, end meeting

<Mark_Wilcock> Thank you Lisa

<LisaSeemanKestenbaum> thank u!

Summary of Action Items

[NEW] ACTION: kirkwood to check with silver that coga experts are being included in 1. process and 2. stakeholders [recorded in http://www.w3.org/2018/01/04-coga-minutes#action01]
[NEW] ACTION: neil millikem, kirkwood and all to try with recuting [recorded in http://www.w3.org/2018/01/04-coga-minutes#action04]
[NEW] ACTION: neil, kirkwood and all to try with recuting [recorded in http://www.w3.org/2018/01/04-coga-minutes#action02]
[NEW] ACTION: neilmillikem, kirkwood and all to try with recuting [recorded in http://www.w3.org/2018/01/04-coga-minutes#action03]
 

Summary of Resolutions

    [End of minutes]

    Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
    $Date: 2017/02/06 11:04:15 $