<Judy> agenda order is 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
<shawn> Shawn: W3C Team Contact for WAI EOWG and Low Vision TF
<scribe> scribe: joanie
jb: We have a few new people on the call
Brent: I am with Pearson and my role is co-chair of Educational Outreach WG.
Jeanne: The Paciello Group. Silver task force.
Jemma: UIUC. Co-facilitator and Editor of ARIA Authoring Practices Guide.
Joanie: Co-chair of ARIA and editor of multiple ARIA specs.
Michael: ARIA+APA Team Contact.
Steve: W3C WAI staff, working with Coga task force
Tzviya: Wiley. Chair Publishing Working Group. Also on Advisory Board.
JB: Next meeting date would be
two weeks out.
... The purpose of this group is to coordinate amongst the
various WAI groups.
... We hope that there can be at least one chair from each
group present, and also one team contact from each group.
Kim: Redstart Systems. Patch on
Tech.
... Mobile task force
JB: People affiliated with some groups might not be aware of all the task forces affiliated with a given group.
<shawn> maybe not updated :/ https://www.w3.org/WAI/about/groups/taskforces/
JB: There should be a link which lists this information.
Shawn: W3C Team Contact for WAI EOWG and Low Vision TF
<Jemma> https://www.w3.org/WAI/ARIA/task-forces/practices/
<stevelee> looks like personalization is missing?
Charles: Personalization Task Force. Affiliated with Benetech and Diagram Center. I work with Digital Publishing Working Group and APA for the Personalization Task Force.
Brent: Is Personalization different from Pronunciation?
Charles: Yes, there are two different task forces.
Michael: And the similiarity in names can lead to confusion.
JB: Irfan is the one most closely working on Pronunciation?
Michael: Yes, at the moment Irfan is the only designated coordinator.
JB: Any other clarifications needed?
Zakim: take up item 1
JB: Is there by any chance a bunch of regrets for the 19th?
Joanie: Yes. Regrets
Brent: Sharon and I are trying to ensure one of us is at each meeting.
<Judy> NEXT MEETING IS DECEMBER 19
JB: Are there any publications that any of the groups are expecting before the end of the year?
Joanie: Does AccName going to Rec count?
Michael: AccName is going to
Rec.
... We're also publishing updates of ARIA, Core-AAM, and APG
1.2
... Also an update of Coga
JB: It sounds like there are probably a few announcements which will need to be made.
Michael: I drafted the AccName announcement a couple of months ago.
<stevelee> Coga content usable - https://w3c.github.io/coga/content-usable/
JB: Please bounce that back to
Shawn and me.
... Give me a heads-up before sending me a flurry of things to
look at.
... Digital Publishing or EO?
Brent: We just did the normal
announcement. Business case for Accessibility and Developing an
Accessibility Statement.
... We'll be doing additional outreach.
Tzviya: There is going to be a document about audio books coming out. This will be an explainer.
JB: Brent or Shawn, the Digital business case document is important. I'm curious if the group is familiar with what it is.
<Brent> Business Case for Digital Accessibility: https://www.w3.org/WAI/business-case/
Brent: I put the link in (above). It's sits in our Teach and Advocate section. It's a good educational read for excutives and others interested in why digital accessibility should be implemented.
<shawn> announcements (with tweet you can share) https://lists.w3.org/Archives/Public/public-wai-announce/2018OctDec/0001.html
Brent: There are four key areas that we touch on. And we go through those four key areas and how they are done.
<shawn> accessibility statements: https://lists.w3.org/Archives/Public/public-wai-announce/2018OctDec/0002.html
Brent: We also have case studies
and direct quotes from companies with experience in these
areas.
... We have gotten a lot of great feedback on this.
JB: You might have a need within
your organization to justify the need for accessibility.
... There are a lot of different ways to use this document.
<Zakim> shawn, you wanted to say new WAI annnounce list https://lists.w3.org/Archives/Public/public-wai-announce/2018OctDec/0000.html
Shawn: This list is high signal, low noise, and announcements mostly.
JB: Anything else on this topic?
<Judy> https://www.w3.org/2003/08/Workshops/
<Judy> https://github.com/w3c/strategy/projects/2
JB: The above link is for the
public W3C workshop page.
... There are two upcoming workshops, one next week in Redmond
on Strong Authentication and Identity.
... I'm going to check back on one or two things with that.
Tzviya: I don't know whose
attending, but I've been working with Verifiable Claims WG.
That topic is a large part of this workshop.
... It sounds like additional accessibility expertise/input
might be beneficial.
JB: The next workshop is in
Berlin. The call for participation is open.
... This workshop is on Web Standardization for Graph
Data.
... I'm curious if people have thoughts of who might be good to
attend this workshop.
... The deadline for participation is January 11th.
<crickets>
JB: Michael, I think you've been tracking SVG Accessibility Stuff. I could also ask Chris directly. I think it would be good to find someone in this area to attend if possible.
Charles: There might be some folks.... We're having an Accessible Data Visualization TF meeting in two weeks.
JB: When is the meeting?
Charles: We haven't set the final date yet as I'm waiting on some people. But probably the second week of December.
JB: Will you take an action item
to try to find someone interested and able to attend the Graph
Data workshop?
... I think it's important to have some representation
there.
... We could also say something on the WAI interest list.
Charles: I will do that.
JB: Looking a the second link.
It's to the strategy funnel.
... What we do here is track a lot of topics where people on
the team or working group or Adivsory Committee have identified
an area which needs exploration.
https://github.com/w3c/strategy/projects/2
JB: You can see that there are
some tags on the funnel page for workshops.
... For instance, there's one on archival, one on privacy,
permissions and user consent, etc.
... Some of these are fairly outdated; some are more
recent.
... Strong authentication and identity.
<Jemma> https://github.com/w3c/strategy/projects/2?card_filter_query=workshop
JB: I'm concerned that I'm
hearing more about workshops than are on this page. So I want
to talk to Wendy and make sure everything is tagged
correctly.
... I realize everyone's plate is full to begin with. But when
workshops come up where accessibility needs to be addressed, we
want to see if we can have someone participate.
JB: Tzviya, thank you for organizing a meeting. Could you update us?
Tzviya: There are several people
around the world working on ISO standards, including sending
various pieces of epub to ISO.
... David Singer asked me about this because there was a
statement suggesting that W3C wouldn't be working on epub
accessibility.
... It turns out it's too late in the ISO process to change the
existing language.
... But those of us voting are accepting it, but clearly
indicating we want this language updated.
... It appears the problem was translation from Japanese.
... Legislation in some cases points to ISO, so there's concern
that the ISO documents are complete and done.
... There are plans to coordinate better. And when the W3C
takes over EPUB this should be less of an issue.
JB: Was there also a clarifying statement indicating W3C's interest in further work on accessibility of digital publishing in the future?
Tzviya: George and I sent messages to the head of ISO. For some reason they cannot change the language.
JB: I understand. But is there some way to communicate that W3C intends to be working on this.
George: I submitted my vote
recommending approval of this work, with comments.
... My comment included what you just stated.
... We also included a statement about accessibility.
... But these comments only go out to ISO; not the rest of the
world.
Judy: Are you aware of some way to clarify this matter to other (outside of ISO) organizations?
George: No.
JB: I have some other questions
which I'll raise later.
... With regard to WCAG, we had heard from many countries that
we could only include an ISO version. Which is why we went
through the whole PAS process.
... This is not merely a rubber stamp and requires a lot of
work.
... We found that it was worth it, but many orgs were able to
accept the W3C version in the end.
George: That's changed. We're concerned about Europe because they don't recognize IDPF but do W3C.
JB: In our last call there had been a question from Jim Allen about relevance of personalization to users with low vision.
<Jemma> IDPF is international digital publishing forum. http://idpf.org/
JB: My recollection is that we concluded the low vision content would be a specific section and that we needed contributors. Did we get them?
Jim: Janina, Shawn, and I had a
call and chatted for about an hour.
... Janina explained some things about vocabulary which I
hadn't considered.
... But we still need to get more people involved, which I'm
working on.
... Janina also sent a bunch of reading material, which I'm
still reviewing.
CharlesL: Janina brought this to
our task force. We're updating our wiki page with all current
tokens and personalization elements into one page so that
they're not spread across three modules.
... Then Jim could look over that and look for holes.
... Adding a fourth module might be a possibility; another
might be to include it in existing modules. We still need to
determine that, along with how to implement it. Right now we
mainly need more input.
Jim: We will be in touch.
<Judy> present?
CharlesL: In the Diagram Center, we're thinking about creating a textbook that has all of the DPUB-ARIA roles embedded in it as a proof. We hope it will help ATs and reading tools to better expose this information.
JB: Jim, going back to your
comment about people being worn out trying to get WCAG
finished: Do you want to write up something with Katie directed
to the WAI interest group? A few sentences or paragraph calling
for participation.
... There are a couple of ways you could do this. Again, we now
have an Announce list.
... My guess is that we have people in the field who would like
to hear of your new work, and possibly contribute to it.
Jim: Will coordinate with Shawn.
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/[introductions]/Shawn: W3C Team Contact for WAI EOWG and Low Vision TF/ Succeeded: s/AB/Advisory Board/ Succeeded: s/APG/Authoring Practices Guide/ Succeeded: s/Digital Publishing/Digital/ Succeeded: s/???/Was there also a clarifying statement indicating W3C's interest in further work on accessibility of digital publishing in the future?/ Succeeded: s/sending various peoples/sending various pieces/ Succeeded: s/Pass/PAS/ Succeeded: s/IDRF/IDPF/ Succeeded: s/???/Europe/ Succeeded: s/Janina and I and maybe Shawn/Janina, Shawn, and I/ Present: tzviya Judy Joanmarie_Diggs Jemma W3C shawn Charles_Lapierre jeanne Brent CharlesL Katie_Haritos-Shea stevelee jamesn kim Jim_Allan Regrets: Janina Jason Found Scribe: joanie Inferring ScribeNick: joanie Found Date: 05 Dec 2018 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. 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]