See also: IRC log
<lisa> password please?
<lisa> i think i found it
<lisa> I'm in, thanks
<allanj> scribe: allanj
<Judy> scribe: Jim
<allanj> scribe: allanj
jb: reviews agenda
... no additions
... next meeting 2 Aug
jb: no publishing for a bit
(november) for Publishing
... ARIA TPAC deadline PR or done
<AWK> +AWK
gk: think its PR
awk: another working draft for WCAG21 by end of July
jb: WCAG21 draft in July will be last draft before CR
awk: DPUB is reviewing, as is
ARIA and PF
... wd end of july, and august (no more new items), then draft
in sept and nov. CR in Dec
janina: review before final. sometime in september (stable draft)
awk: before TPAC is ideal
<AWK> how long is the charter duration?
jb: reviews status. new charter
proposed for nearly 3 years
... charter review closes 10 Aug
<janina> https://www.w3.org/WAI/ARIA/task-forces/personalization/work-statement
janina: Charles Lapierre to be
co-facilitator
... CFC for work statement going out soon
... TF spawned from ARIA WG
... will liaze with CSS
... post draft to WAICC
jb: Charles can join WAICC calls, perhaps rotate with Lisa. will add Charles to WAICC meeting notifiactions
ls: want personalization to be
compatible with gpii
... not an implementation
janina: to be a spec in W3C need 2 implementations
<Judy> scribe: Judy
<lisa> we have it
JS: We're looking at one
implementation so far... we want a second one
... from somewhere in publishing, ideally
LS: We have a second one, actually, User First, from Israel
JS: What stack do they build user agents on?
LS: They do accessibility support
through personalization, and it works on all different
environments
... and he has also offered to make part of it open source
JS: Sounds like a longer conversation... let's not try to figure that all out here.
LS: He made a demo, and sent it
to the WCAG list, implementing it on a Spanish site, and making
an additional implementation there.
... so it is a server-side implementation, ready to go.
<tzviya> scribenick: Tzviya
TS: To clarify about reading systems as UAs for implemention, many are based on the same kernals as browsers. For example, if something is not implemented in WebKit, many Reading systems will say that they can't demonstrate functionality yet.
<janina> scribe: janina
mc: ARIA likely to move to a CFC on this after Thursday 27 July
<Zakim> tzviya, you wanted to clarify role of publishing implementations
<tzviya> https://lists.w3.org/Archives/Public/public-wai-cc/2017Jul/0007.html
jb: EME has been of concern off
and on ...
... Our testing has confirmed that accessibility information
(captions, transcripts, audio description) are available
regardless of EME implementation
... Assertions from outside have been made that EME is blocking
accessibility, but we have not found that to be so; also that
w3c has not addressed accessibility through w3c process, though
we have
... May be more updates to the doc that explains all this
... Still open for feedback
... The erroneous assertions included flash mitigation--can be
done, through browser driver post-processing
awk: Saw the discussion on AC list
ts: Seen what's been said via the blogs
jb: There is general distate in some quarters against any kind of DRM, but DRM as a11y barrier hasn't proven out
<tzviya> https://github.com/WICG/aom
<Judy> tzviya: Is there continuing work on that?
<Judy> michael: seemed inactive?
<Judy> tzviya: no, seems active within the last month
ts Recalling a TPAC presentation of ts: Notes issue tracker has had activity in the past month
<Judy> michael: seems to keep moving repos
mc: ARIA is confused--we'll look
at this again
... We've tried to track, but has seemed inactive
<Judy> s/EME has been a concern/EME and accessibility has been a report item/
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/good for 3/proposed for nearly 3/ Succeeded: s/announcement/draft/ Succeeded: s/co-chair/co-facilitator/ Succeeded: s|q-|https://lists.w3.org/Archives/Public/public-wai-cc/2017Jul/0007.html| FAILED: s/EME has been a concern/EME and accessibility has been a report item/ Succeeded: s/Our concern has been to confirm that alternative formats/Our testing has confirmed that accessibility information (captions, transcripts, audio description)/ Succeeded: s/that to be so/that to be so; also that w3c has not addressed accessibility through w3c process, though we have/ Succeeded: s/can be done/can be done, through browser driver post-processing/ Present: janina Judy tzviya lisa allanj George MichaelC Found Scribe: allanj Found Scribe: Jim Found Scribe: allanj Inferring ScribeNick: allanj Found Scribe: Judy Inferring ScribeNick: Judy Found ScribeNick: Tzviya Found Scribe: janina Inferring ScribeNick: janina Scribes: allanj, Jim, Judy, janina ScribeNicks: Tzviya, allanj, Judy, 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: 19 Jul 2017 Guessing minutes URL: http://www.w3.org/2017/07/19-waicc-minutes.html People with action items:[End of scribe.perl diagnostic output]