See also: IRC log
<scribe> Scribe: Katie Haritos-Shea
<scribe> ScribeNick: Ryladog
JB: Doing an intro in a minutes, any agenda additions
JB: Intorduce At&t Lead Ralph Swick
RS: Watching from a far for a long time
... Been around as long as Judy, I look forward to learning more. We
will rely on Judy to lead the A11Y work. We want to better integrate
a11y work across all our W3C activities
<Ryladog_> Scribe: Katie Haritos-Shea
<Ryladog_> RS: Hopefully you have all read the Functional Reorg Doc, from about a month ago
<Ryladog_> RS: We created the TAG to support Tim in doing spec reviews that the Director is asked to do. Look at common web arch issues. TAG mission is still that, but have been driven by the needs of TAG
<Ryladog_> RS: We support the Director in all directorial roles, transitions, working with TAF on common arc cjallneges
<Ryladog_> RS: No less challenging than Phillip and Wendy have. We make suree that Horizontal Reviews get done, we dont do them
<Ryladog_> RS: Judy and I will be working closely together. Arch and Technology mandate cuts across all the work, including WAI work
<Ryladog_> JB: People introduce themselves...
<Ryladog_> JB: Most WG or Task Force leads attend this call
<Ryladog_> JS: Hi Ralph and congrats. APA is taksed with the a11y horizontal reviews
<Ryladog_> JA: I am co-facilitator of the Low Visions TF
<Ryladog_> RS: Thank you, will you be in Lisbon
<Ryladog_> JA: No
<Ryladog_> LQ: HTML Accessibility TF is inactive.
<Ryladog_> LS: I work for facilitator of the Cognitive TF in APA and WCAG
<Ryladog_> RS: H Ralph, I chair the ARIA WG, one of the editors for ??, and work for IBM, and Chairman of Knowbility
<Ryladog_> WF: Ho Ralph, co-facilitator of the Conformance Testing TF of WCAG WG
<Ryladog_> JB: I see Lisa in Q
<Ryladog_> T: I chair the D-Pub ARIA TF
<Ryladog_> LS: Is the structure of the Restructure was sent to all?
<Ryladog_> JB: We will put in the URL
<Ryladog_> co-facilitator of the Low Visions TF
<Ralph> W3C Internal Functional Reorganization announcement
<Ralph> 2016 W3C Internal Reorganization
<Ryladog_> JB: Recc track work will be less of a focus of this call, unless there is some major announcment
<Ryladog_> JB: Or cross review. The coordination isn the various areas especially how the architecture fits together, making sure we dont drop things
<Ryladog_> JB: Pockets of accessibility work not colliding, having these discussions. Ralph the idea is to be supporting his work and the strategy area. Ralph and I will be in ongoing discussions with endt S on that
<Ryladog_> JB: MC may also be chasing that work. Ralph, further comments?
<Ryladog_> RS: I will let you drive the conversation. Sometimes folks are surprsied to hear that TAG has taken up an a11y issue without directly contacting . Ralph will be letting the a11y folks who should come to discuss issues with the TAG
<Ryladog_> RS: The TAG hasnt had a formal reporting relationship through W3M other than Tim himself. So that will be interesting to see
<Ryladog_> Kim: We enable people using speach to use it in a better way. Co faciltator of the Mobile TF of WCAG
<AWK> +AWK
<AWK> All set for WCAG
<Ryladog_> JB: TPAC logistics, last minute check,Any issues for TPAC?
<Ryladog_> JB: (provide contact info)
<Ryladog_> JB: Last time there was a question about WAI staffing, accessibility staff will be integrated within the functional model, and I will be coordinating with them and other colleagues as needed
<Ryladog_> JB: Are there updates that will come out after TPAC?
<Ryladog_> LS: MC may be on mute
<Ryladog_> MC: WE have arranged alot of cross reviews, dne see a need at this time
<Ryladog_> LS: COGA revieew will be coming out after TPAC but anyone can look at the on GitHuB
<Ryladog_> KIm: I sent something this morning
<Ryladog_> LS: I see that you did
<Ryladog_> Kim: It has to do wth customization. We used the wiki page that was set up for it
<Ryladog_> LS: Thanks TF Exchnage
<Ryladog_> JB: I mentioned that when we want to keep people interested I will just use the pages of reference, sometimes it is up to date or out of date.
<Ryladog_> JB: It is important to please put in serach terms to see if you can find your group before TPAC to ensure that information is findable
<Ryladog_> LS: What is the main page we should be putting the search criteria into?
<scribe> ScribeNick: Ryladog
JB: You need to hae multiple ways to find your content. At some point we talked about having a page that identifies where all of our stuff is
T: Should we remove PF stuff
JB: This is th estuff that trips people up ,and makes people confused
JB: The workshop that I had been concerned
about in Virtual Reality. One person Charles LaPierre, has already
registered; anyone know of a second person as well??
... Janina or MIcheal do you have any needs for liaison in new CG that
have a need?
Janina, we continue to be overdue of our regular review of CG
JB: Before we talked about getting someone to volunteer
JS: We have domne that previouly successfully. WE have been wrapped up with publication review
JB: Is that something that Katie and WAI IG
somehow help on that?
... Can we croudsource CG review via WAI-IG?
... If you are looking for resources it mmight be a good idea
Janina: I need to think about whether that might be a good idea. Can we think about it?
MC: I think it would be best to cede it
JB: Lets discuss ceding it
JSL I agree with MC, we spent alot of time on it. We did not get much benefit out of it
JS: It got in the way of other things we need to do. There are many that go out, so we wated time that way. We are waiting until they have been around for 3 or 6 mnths
JB: Can I suggest that MC, KHS< and JS
talk about it at TPAC
... What if you do find a group that does need a liaison? We want to
have an a11y person that is in coordiation with the WAI
... Some previw of the work so that it is accessibility ready that might
effect wht kind of a message you would want to send to the Accessibility
IG
JS: I am certainly happy to have that converstaion. It is just that it is a time killer. Best if we do it less often
JB: OK , please figure something out
KHS: We will find a way to talk about that at TPAC
JB: Are there things going on that you think
you would like to share with the community?
... Things
<tzviya> https://www.w3.org/blog/2016/09/portable-web-publications-use-cases-and-requirements-fpwd/
T: D-PUB published the FPWD of Portable Web Publications Use Cases and Requirements
Sure
JB: C
KHS: EO asked us to ask WAI-IG folks to join them on Mondayy afternoon
JB: Where is the best place to put stuff for informal communications for TPAC?
RS: I am not aware of anything
... The most formal I can recall is the BOF proposals
<liam> +1 also called "unconference sessions"
JB: Do people have any BOF ideas?
<MichaelC> https://www.w3.org/wiki/TPAC2016/SessionIdeas
JB: Maybe something we could put in place notices to the TPAC attendees
RS: Yes there are TPAC hastags
SA: We contact WCAG WG Chairs in europe
there is actvieit EN 301549.
SA: It is intended to fix issues related to realtime-text and align with US Section 508, but also to improve coverage on mobile - it is important to ensure continued harmonization with WCAG 2.0/2.1 in this effort
JB: The next meeting would be the 28th
<janina> APA is taking the post TPAC week off. Probably regrets for me
<Judy> Regrets for 28th?
JB: If you have regrets for the 28th, please type that in. We may need a survey?
<AWK> 28th is ok, but I'll be late due to my recurring conflict
28 is OK for me
JB: We can move to a monthly meeting, but I
would like to keep it at every two weeks if we can
... The transition will take a little while and then see