See also: IRC log
<shawn> [13:30] * Judy go!waicc!
<scribe> scribe: janina
jb: Next meeting on the 21st. Any expected unavailability?
<AWK> +AWK
janina: COGA/ARIA Personalization FPWD published.
awk: Working draft for WCAG 2.1 expected later in June.
<shawn> https://www.w3.org/WAI/EO/wiki/EOWG_Current_Projects
<shawn> first draft redesigned home page: <https://visa.invisionapp.com/share/YPAVCUZA9#/screens/234693428_Home_Page>
jb: EO Charter is being updated in coming months.
<shawn> Draft charter: <https://www.w3.org/WAI/EO/charter2017>
<shawn> Member e-mail: <https://lists.w3.org/Archives/Member/chairs/2017AprJun/0094.html>
<shawn> Includes: "We welcome your general expressions of interest and support on
<shawn> <w3c-ac-forum@w3.org>."
jb: An advance notice of work has
gone to the AC
... It's important to get feedback from all WAI groups on
this
sh: We've finished all but one
milestone
... Moving slowly, but moving on the redesign
... Main focus in new recharter is to update all
resources
... e.g. more skimmable, fresh perspectives, etc
jb: Requests from public to update?
sh: Yes
... We're responding to member and public requests
gk: We're getting requests for
chartered work for cut and paste examples of correct coding for
various elements
... Anything like that exist?
khs: There are techniques, we could do this there
sh: Also have tutorials that
address some things
... The one deliverable we've not finished is a list of
accessible components, e.g. accessible date picker
ts: Not sure we can succeed at
best practices on this, partly because we'd never finish, and
because publishers can be reluctant on their solutions
... Could do examples
... Images can be a problem, if you describe the image too
well, it can give away the answer
gk: Seems like fundamental techniques should get you a good way to the good solution
jb: Noting that assessment
examples may be different from other publishing use cases
... EO is similar to APA in that it provides service to other
W3C groups
sh: Noting that expressed support is welcome on the AC list.
<Zakim> shawn, you wanted to ask AC rep to speak up (esp AC list with +1s) and comments welcome
jb: Also concerns, of course, so we can cover all that's needed
jb: Primarily on the agenda today to because of the mention of ISO coordination (I realized that wasn't aware of all of your relevant epub accessibility documents)
<shawn> EOWG charter comments encourged this week so we can get them addressed
gk: Wanting to take epub standard
to ISO
... E.U. is in need of a standard for digital publishing, but
this spec is not a W3C recommendation
... Getting ISO could help prevent forking, etc
<tzviya> https://www.idpf.org/epub/a11y/accessibility.html
<George> http://www.idpf.org/epub/a11y/accessibility.html
jb: Because not a formal W3C, probably not a candidate for the defined ISO/W3C process
gk: Noting that this is already an ISO Technical Specification -- as opposed to an ISO Standard
jb: Suggesting we put expected W3C specs that may be candidates for ISO in the months and years ahead
ts: Need in Korea for ISO standardization, and expecting this will be discussed
gk: In the future, of course, the chartered work of the D-Pub WG
jb: So Bill McCoy needs to be plugged in on this
jb: Expect TPAC schedule should be out today
awk: Not yet, but Susan expecting it soon
jb: Reminding groups to ask now
about any desired joint meetings
... WCAG?
awk: Hopefully, none! We should be heads down
<George> W3C Publishing Summit: How Web technologies are shaping publishing today, tomorrow, and
<George> Thursday November 9 and half day 10.beyond"
jb: As previously discussed,
still looking for feedback on what's missing, or what may be
able to be better stated
... Please review from our various subject area foci
... Anyone able to look at since our last call?
[crickets]
jb: Upcoming next week in
DC
... Monday-Wednesday -- usually good networking
... AWK will be talking WCAG 2.1
... I'll be discussing update of WCAG generally
... Any networking requests -- people I should look for to
recruit?
ts: Area we need in D-Pub is hard
core sciences accessibility.
... Problem is that everything is captured in images, and we
need a serious subject matter expert to correctly alt tag the
images
jb: Maybe another approach
jb: Link in item 11
<Joshue108> https://rawgit.com/w3c/wcag21/single-key-shortcuts_ISSUE-69/guidelines/#character-key-shortcuts
josh: A request for coord with
APA re SC criteria
... Need a bypass for single key shortcuts
... Competes with other AT
... Jason White has requested review and potential request for
APA review, or ARIA review
<Joshue108> https://www.w3.org/2002/09/wbs/35422/character-key-issue69/results
khs: Discovered this myself using
speech reco when logging in
... Didn't work in password entry
<Zakim> Joshue, you wanted to say that we wish to do due diligence
<AWK> Regrets for June 21
<tzviya> Regrets for June 21
Regrets from GK and KHS for the 21st
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 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/requests/requests for chartered work/ Succeeded: s/discuss ISO coordination/because of the mention of ISO coordination (I realized that wasn't aware of all of your relevant epub accessibility documents)/ Succeeded: s/crickers/crickets/ Default Present: janina, Shawn, Judy, Joanmarie_Diggs, Shadi, tzviya, George, Katie, Michael, Josh, AWK Present: George Joanmarie_Diggs Josh Judy Katie Shadi Shawn janina tzviya Found Scribe: janina Inferring ScribeNick: janina 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: 07 Jun 2017 Guessing minutes URL: http://www.w3.org/2017/06/07-waicc-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]