SV_MEETING_TITLE -- 05 Jul 2017

<Judy> scribe: George

<scribe> scribe: George

Confirm scribe, agenda, next meeting date Milestones,

<Judy> NEXT MEETING DATE IS JULY 21

<Judy> NEXT MEETING DATE IS JULY 19

JB: next meeting July 19

publications, announcements check Any updates on cross-group doc

JB: publications announcements?

MC: Two published last week, but not nnounced. WCAG 3.1 and ARIA authoring practices

JB: Sean intended to help, MC: her publications announcements would be brief and just let people know it is out.
... JB will take an action to contact Shawn on the messaging.

MC: would want to set up his own messaging, but does not have clearance.

JB: MC can you give us a draft of something to propose. Not clear on where to do this in Shawn's place.
... Getting something started would be a beefit.
... is there something on messaging on ARIA publishing practices.
... MC, please check with ARIA TF facilitators for a short summary.

GK Nothing published from PWG

JB: Any announcements that need to be tracked? None mentioned.

Any updates on cross-group doc agenda+ reviews? (personalization, etc)

JB: Cross reviews.
... Which groups plan to review the personilization?

TS: Publishing will take a look at it, but not a complete review.

MC: in ARIA they are planning to create a task force and perhaps publishing would be better to join and provide feedback there.

<Judy> agenda item 4 = Update on WCAG 2.1 messaging, including myths debunking?

TS: It seems narrow

<Judy> agendum 4 = Update on WCAG 2.1 messaging, including myths debunking?

JB: anybody else waiting for reviews.

JS: APA would be interested in planning out a comprehensive review.

JB: Can we fit some discussion in? Yes.

Update on WCAG 2.1 messaging, including myths debunking?

JB: f Update on WCAG 2.1 messaging.

JB Shawn has not had a chance to do that yet, but JB would like to capture themes.

JB: Some people think WCAG 2.1 is done, but it is not.
... key reminders continues to be in process. A draft every month? What else is not understood?

<Judy> [JB: Some people think that AGWG not taking up anything from some TFs.]

<Judy> scribe: Judy

GK: It isn't clear what additional things can be brought forward.
... For instance, we would like to bring forward some things from publishing.
... We don't know how much we can integrate further into WCAG 2.1
... Or whether we should plan to move those into Silver.
... in EPUB 3.1 we have accessibility conformance @@ specification including @@ and Techniques, and we refer to WCAG 2.0, but eventually these things need to get integrated into accessibility guidelines/

<scribe> scribe: George

MC: tzviya sent a message a week agou with the same question. Chairs have not reacted and MC has put it on his todo list to work on this.GK: unclear

MC We are Because these requests have not come through a TF it has sliped through.

MC: David McDonald did the original SC write up. We can get together with the chairs.

TS: MC covered what she would say. If we need to create a task force, but perhaps it is just needs t be

MC: Missing the internal discussions of what is happending in the TF.
... We could invite you to the meetings, but need to check with the chairs. TS ping was good.

<Judy> [JB: Back & forth btw George, Tzviya, Michael about how to close the loop on getting this SC written up. MC helpful to have the ping on this.]

JB: Is the ball in MC's court?

MC: MC will remind the chairs on what they want to do next. We might pass the invite on to Matt Garrish.
... We do need to figure. out our process in that forum.
... MC has a chat with chairs tomorrow, so might have something after that.

<tzviya> scribenick: Tzviya

Note updated WCAG 2.0 Policy References, with invitation for

JB: WCAG 2.0 policy references have been updated

<Judy> https://lists.w3.org/Archives/Public/w3c-wai-ig/2017AprJun/0195.html -- with invitation to update further

JB: If you have been tracking legal updates, please make sure that this information is circulated

input RQTF Update on RQTF Captcha inputs, and upcoming accessible VR discussion

JB: The point is to share this information with your groups and TFs. There are more than 40 gathered VR accessibility articles

JS: We are looking to update APA's note on Captcha. RQTF has helped us by looking at the literature. We will request comments
... In the case of VR, we've asked RQTF to look over articles about VR Accessibility. They've gathered more than 40 articles. The goal is to assess how to make VR accessible.
... We had a special call about VR with the VR WG. They want to make their specs accessible. We need to follow up with them.

JB: Are there any related discussions from other groups?

JS: We promised the VR people some sort of response about what we think needs to happen. We will give RQTF more time to assess before we meet again.

Progress on coordinating accessible authentication discussions?

JB: Follow up from last meeting, concerns that authentication discussions going in multiple directions

JS: I'm feeling on top of things again

Publishing meeting at TPAC

GK: On 9-10 Nov, there will be a Publishing Summit concurrent with TPAC (1.5 days)
... I'll register for TPAC on M-W, Summit on Th-F

https://www.w3.org/publishing/events/summit2017

JS: Do you need a different badge? Register separately?

GK: Separate registration

All: Discussion about the nature of Publishing Summit

<Judy> [JB: will check on a question about registrations]

GK: The publishing WG has been chartered

https://www.w3.org/publishing/groups/publ-wg/

<Zakim> janina, you wanted to ask whether a different pass is required?

Publishing WG Charter, & coordination with WAI

GK: We had a WG/IG/BG Face to Face meeting on June 22 and 23

JB: When will you publish first documents?

GK: FPWD of Web Publications before TPAC

https://www.w3.org/publishing/groups/publ-wg/PublStatus

JB: What coordination do you most want with WAI?

<George> TS: We are inherting a lot from IDPF. We want to make sure that whatever the PWG does is accessible.

<lisa> can i have the webex password

<George> TS: It would be a good idea to have a formal task force or whatever is appropriate to make sure that.

<George> TS: We have a large group of accessibility folks in PWG and it would be good to capatolize on that work.

<George> TS: we wrote the succ criterias for publishing.

<George> JB: MC do you want to comment?

<George> JB: either want to give an example.

<George> TS: A navigation document is a recommendation in EPUB and there has been a long discussion about the use of this type of document.

<George> TS: There would possible be a benefit to have WAI experts chime in.

<George> MC: This may be an APA issue, because you are crossing boundries.

<George> MC: Some of these may apply to WCAG guidelines. APA might have a better idea on the overall trends that you want to plub into.

<George> MC: Guidelines cannot recommend on technologies not implemented.

<George> MC: It would tak time to evolve.

<George> GK: Perhaps bring this to the PWG and coordinate with the multiple working groups involved.

<George> TS: George and TS bring this back to our TF and start to put a list of issues. Avneesh will be the one to lead this.

<Judy> [JB: Encourages you to send issues to WAI CC not just Judy or Michael, to get more perspectives]

<Judy> agenda order is 10, 14, 11, 13

Publishing WG is doing with ISO and the EPUB specs.

<George> TS: If JB is aware of the ISO coordination , then perhaps we are good.

<Judy> [JB thinks that Bill was going to raise this, or has already, with liaisons group]

<George> JB: I thought this was going to be addressed by the liaison's group?

Things potentially missing from current plan for achieving accessibility personalization

<George> JB: JB will follow up with Bill on this issue.

<George> GK: scribing

<George> MC: The personilization spec is limited in scope so that WCAG could reference it.

<Judy> scribe: George

MC: It could be expanded in a future version. Personalozation is important in many areas.
... The personalization TF in ARIA would be the home for this.

JS: Do we want the media quiries there too?

MC We need an overall coordination mechanism.

JB: What is the next steps?

MC: We are in process of forming the TF and it has not been formed. A work statement would need to be created. It is in process, but going slow.
... We are not expecting too many from ARIA to be active.

LS: Few points. We have reached out to low vision and there is common ground.
... We need to move that forward.
... There is clear overlap with publishing.

GK: I just lost my phone, becaus of weather.

<Judy> scribe: Judy

<George> GK: can somebody else take over on scribing?

LS: Needs to tie in with the work of IMS wrt accessibility metadata
... there is this other piece of user settings
... needs some kind of mapping

- DRAFT -

SV_MEETING_TITLE

05 Jul 2017

Attendees

Contents