W3C

- DRAFT -

SV_MEETING_TITLE

20 Jul 2016

See also: IRC log

Attendees

Present
Tzviya, MichaelC, Janina, shadi, Joshue108, Brent, Katie_Haritos-Shea, Judy, Lisa_Seeman, Liam, Kathy
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Joshue

Contents


<Joshue108> Scribe: Joshue

RQTF: Good to see RQTF/CAPTCHA announcement on WAI IG; ways to promote input into that thread?

<Joshue108> JB: Its good to see this announcement on WAIIG.

<Joshue108> JB: We have Jason to thank for that, along with Katie.

<Joshue108> JB: Can we talk about how to big up the CAPTCHA question on WAIIG?

<Joshue108> JB: I think if people see the announcement and coversation that would be good.

<Joshue108> JB: May get more traction etc.

<Joshue108> JB: We want to draw others in for a started TF at TPAC.

<Joshue108> JB: Any ideas?

<Ryladog> Suggest asking individual questions

<Ryladog> to memebers

<Joshue108> JB: Can you give examples Katie?

<Ryladog> What particular issues you may have had?

<Ryladog> What have you seenis a very good experine?

<Joshue108> JB: That would be of interest - esp in China.

<Joshue108> JB: Thats good.

<Ryladog> What modalities are we missing?

<Ryladog> yes

<Joshue108> JB: Those are good suggestions Katie, would you be happy to pose those?

<Joshue108> JB: Ty

<Joshue108> TZ: This would be of interest to lots.

<Ryladog> What alternatives to CAPTCHA can you suggest?

<Joshue108> TZ: Also to hear about any positives?

<Joshue108> JB: Janina, Michael could you get Jason into these discussion?

<Joshue108> TZ: There are breakout session etc, that would be successful.

<Ryladog> We could put up aposter andask people to just write a note - that we could discuss in the group

<Joshue108> TZ: For solutions, its depends who is there but internationa aspect is good.

<Joshue108> MC: Put a proposal in the wiki, there is one there, and one on the way - but we need help.

<Joshue108> MC: I support adding it however.

<Joshue108> JB: Tziya would you support if from the dPub angle?

<Ryladog> In a public area, may be in the lunch room, we could put up a poster, with pens attached - to get feedback from all attendees at TPAC

<Joshue108> TZ: A little of topic.

<Joshue108> TZ: But of interest.

<Joshue108> LS: From COGA angle, there are also problems.

<Joshue108> LS: Logging in and identification for example.

<Joshue108> LS: There is a teachable moment here.

<Joshue108> LS: Passwords aer problematic for example..

<Joshue108> LS: Can we broaden the scope?

<Joshue108> LS: There is a huge market here. Over 60s have memory issues for example.

<Joshue108> LS: There is a wider market angle.

<Judy> +1 to Lisa's concept of a teachable moment on cognitive accessibility

<Joshue108> LS: If people think about it.

<Joshue108> JB: The reaserach questions tf could look at this, in terms of problem,solution and wraparound package.

<Ryladog> +1 to Lisa's comment

<Joshue108> LS: COGA has a long issue paper on this.

<Joshue108> LS: There are @alts such as biometrics etc.

<Joshue108> LS: I also have an abstract on technology agnostic architecture.

<Joshue108> JS: For some context..

<Joshue108> JS: We started out with CAPTCHA problem, then that leads into improved authetication.

<Joshue108> JS: There is recognition that we do want a better approach.

<Joshue108> JS: We have discussed this in APA.

<Joshue108> JS: There is a broader issue around security, we need their engagment to develop inclusive platforms.

<Joshue108> JS: We are working in tandem with COGA.

<Joshue108> JS: The immediate problem is the deliverable in APA charter.. PF did publish a note on these issues but it needs updating.

<Joshue108> JS: We should start from that point.

<Joshue108> JS: Dual factor authentication is also a factor.

<Joshue108> JB:Reads Katies comment.

<Joshue108> JS: Katie did you want to say anything more?

<Ryladog> No thanks

<Judy> Katie: We could put up a poster and ask people to just write a note - that we could discuss in the group

<Ryladog> In a public area, may be in the lunch room, we could put up a poster, with pens attached - to get feedback from all attendees at TPAC

<Zakim> Ryladog, you wanted to seemy notes above about putting up a poster to ask people to write in their experiences and ideas

Mobile accessibility progress request relative to EC work

<Joshue108> JB: Shadi?

<Ryladog> Yeah!

<Joshue108> SAZ: In Europe we have the Web A11y directive approved by parliment :-)

<Ryladog> For gov sites right?

<Joshue108> SAZ: It didn't originally cover mobile, but does now.

<Joshue108> SAZ: They have been looking at our work on mobile however.

<Joshue108> SAZ: There is a revision of the EU procurement standard also.

<Joshue108> SAZ: This will start in autumn.

<Joshue108> SAZ: We need to align the timelines, from Mobile TF to other core work.

<Joshue108> SAZ: This is important for uniform adoption.

<Joshue108> SAZ: I'm getting more info at the mo to share with the chairs etc.

<Joshue108> JB: This is mentioned in regard to the upcoming announcement from the WCAG group.

<Joshue108> SAZ: Yes, this is important.

<Joshue108> SAZ: We should mention some specifics in the upcoming work with an emphasis on mobile etc.

<Joshue108> SAZ: There is an optics issue here.

<Joshue108> MC: <speaks delicately> Yes, there is work on a draft annoucement, some requests to modify the core announcement, would have reservations unless the additions are minor.

<Joshue108> JB: Could be useful to break up that message per audience.

<Joshue108> JB: Good to co-ordinate with Katie also.

<Zakim> MichaelC, you wanted to say separate announcement if it´s proposing a big change

<Joshue108> SAZ: To add to that, Michael does have a point. We shoud take a step back, reassess etc.

<Joshue108> SAZ: Good to hear what Kathy thinks...

<Joshue108> SAZ: So we are on message.

<Joshue108> JB: We have some pending offers to do articles/blog on the mobile area.

<kathy> I am good

REVIEWS: Pending inter-group review requests

<Joshue108> JB: when the message goes out Michael, Katie, Kathy etc will co-ordinate etc.

<Joshue108> JB: There should be timely links to things on public facing things.

<Joshue108> SAZ: The Mobile A11y page can be updated.

<Joshue108> JB: Good idea.

<Joshue108> JB: Do we need reminders on any that are out for review?

<Joshue108> JB: Michael, anything about ARIA?

<Joshue108> MC: ARIA 1.1 LC working draft (pseudo) is going out tomorrow.

<Joshue108> MC: Maybe issues with the new pub sys.

<Joshue108> JB: The WAIIG, is that the ARIA authoring practices replaces older resources etc.

<Judy> https://lists.w3.org/Archives/Public/w3c-wai-ig/2016JulSep/0053.html

<scribe> scribenick: tzviya

<Ryladog> There is none at this time

TS: George Kerscher sent email about EPUB A11y documentation

<Ryladog> I thinkthey do need context

<Ryladog> That would be good

JB: I received many emails, but people may need context

TS: I will respond to george's email to WAI IG and give some context and ask some targeted questions to the group

<AWK> +AWK

PUBS: Upcoming publications, announcements, discussion threads to promote?

MC: WCAG Understanding and Notes published yeterday, COGA FPWD coming soon
... I am drafting announcements
... Should pub announcements go through Katie as well?

JB: Will clarify later, have to look at notes, don't believe it was for formal review but may be helpful to know that it's coming up

LS: We started designing semantics to support reminders, so that they can be turned off/on (based on machine and user input)
... and a log - similar to a breadcumb of events

JB: Is this a Task Force FYI?

LS: Working on in COGA

TPAC: registration reminders and pre-coord on joint meetings

<Lisa_Seeman> we are looking at syntax for reminders and for log information

<Lisa_Seeman> and what infromtion needs be captured for that

JB: Weekly reminders about TPAC in active meetings

AWK: Lisa and I need to talk about COGA meeting and whether that is with/apart from WCAG

JB: TAG/ARIA discussions moving smoothly
... There is a second a11y issue on TAG list regarding access key

JS: I don't think there has been activity on that issue recently. I would rely on Leonie if there was any discussion

JB: It would be good to close out the HTML A11y TF if it's not active

<Zakim> MichaelC, you wanted to speak when I don´t have to try to get a word in edgewise

MC: I subscribed to the GitHub issue after Judy mentioned it. It's not clear if it's on TAG agenda for next week yet

HTML 5.1 diff reviews nearly set?

<Judy> [JB notes that people are welcome to queue at any time]

JB: This seems to be largely completed

JS: We are done with that

Liaisons: needs in Community Groups, new WGs, Workshops?

JS: We are overdue to review CGs
... The agenda is a little lighter now, so we should be able to get to this soon.

<Ryladog> Virtual?

JB: We spoke about recruiting in WAI IG for VR Workshop. Has that happened?

<Ryladog> I havent yet, buut it is a good idea

<AWK> Do we have a link to the workshop?

<Ryladog> I willdo that

<Ryladog> no

<Ryladog> link

<Ryladog> or Ill look for it

<AWK> This one: https://www.w3.org/2016/06/vr-workshop/

<Ryladog> Perfect thanks Andrew

TPAC: registration reminders and pre-coord on joint meetings

TFs: any TF updates

Next meeting: date, and requested topics

<Ryladog> Aug 3rd?

<Judy> Any regrets for Aug 3rd?

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/07/20 19:29:38 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/haev/have/
Succeeded: s/aposter andask/a poster and ask/
Succeeded: s/at notes/at notes, don't believe it was for formal review but may be helpful to know that it's coming up/
Succeeded: s/access-key/access key/
Found Scribe: Joshue
Found ScribeNick: tzviya
Present: Tzviya MichaelC Janina shadi Joshue108 Brent Katie_Haritos-Shea Judy Lisa_Seeman Liam Kathy

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


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

Got date from IRC log name: 20 Jul 2016
Guessing minutes URL: http://www.w3.org/2016/07/20-waicc-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]