See also: IRC log
<trackbot> Date: 06 August 2014
<janina> Meeting: PFWG telecon
<janina> agenda: this
<janina> http://www.w3.org/WAI/PF/HTML/wiki/GitHub
<scribe> scribe: JF
RESOLUTION: Publish
meeting minutes of 7/16 as submitted
... Publish meeting minutes of 7/23 as submitted
CYNS: last week MS had a
hackathon / product fair. Many hacks were related to a11y -
huge positive momentum
... Can share a few public things, most still internal, but
huge positive buzz
JS: just in case some are unaware, Apple has signalled intent to file FO on @longdesc
<MichaelC> TPAC meeting page
MC: not yet formally announced,
but have set up a meeting page for PF for this year's
TPAC
... only 4 people have registered so far
... rate goes up 8 Oct, and deadline is 18 Oct
JS: we are the Thursday / Friday
JF: asking about working with CSS WG
MC: confirming that CSS WG are meeting Mon / Tues
JS: we need to work out an agenda
and approach them ASAP
... Lots of up-in-the-air items - we need to start coordinating
this quickly
JF: suggest that we send out an email and start blocking this out in the next week or two
JS: hope to have this nailed down by Labor Day (Sept 1)
JS, CYNS: both been very busy last few days
<MichaelC> action-1479 due 13 August
<trackbot> Set action-1479 Review content security policy level 2 http://www.w3.org/tr/2014/wd-csp2-20140703/ due date to 2014-08-13.
MC: deadline for comments to Jame's review of Security Policy is next week
<MichaelC> action-1480 due 13 August
<trackbot> Set action-1480 Review content security policy level 2 http://www.w3.org/tr/2014/wd-csp2-20140703/ due date to 2014-08-13.
JS: top priority for next wednesday's call
<MichaelC> close action-1483
<trackbot> Closed action-1483.
CYNS: getting caught up on outstanding items this week
<MichaelC> Developers' Guide to Features of Web Accessibility Evaluation Tools
MC: very little due to last
week's publishing moratorium
... Shadi and Co. have a new work, from evaluation
methodology
JS: good to see, likely will be a good resource
MC: already quite rich
JS: still open and outstanding -
need response from Judy
... believe we are ready from content perspective, but Judy
needs to clear some details
JS: just want to be sure everyone is aware of Michael
's summary
JS: there is a spec in CSS that includes a provision that effectively prevents some devices fromzooming
been around for several years, but has been in working draft status
yet we are now hearing that it is being implemented
that's an issue we need to investigate, but the larger issue is the impact of early publications that move slowing at W3C, but quickly at implementors level
likely no resolution today, but we need to discuss this at length
returning to the specific spec, what are we to do now?
CYNS: with the new CR combined process, this is ging to be the new normal, right?
MC: not sure if the process directly influences this, but yes, there seems that this will be the tendancy
CYNS: point is, by the time something reaches LC, it is likely already in a working, mainstream browser
MC: correct, but this 1st PWD already had implementations on the ground
CYNS: perhaps we need a protocol between staff contacts to keep information flowing
JS: this is supposed to be happening at the Mgmt level and charters
MC: there is a bit of a catch
there as well - some groups seem to manage to add new
deliverables without rechartering
... the issue here was that the idea gained some significant
momentum before it even reached W3C
... this is about Zoom: for example if you set zoom-minimum and
zoom-maximum both to =1, then it effectively halts zooming
CYNS: perhaps we need to work
with our contacts at the various browser vendors to ensure that
these things can get caught at that level too
... noting similar larg-org communication issues exist
everywhere
JS: we need to flag our concern
about this early and flag our concerns
... hope to put up some draft language on next weeks call
CYNS: and ask for the use-cases
[meta discussion on technology versus awareness of a11y]
<jcraig> If there is any time, can you review a few pending actions?
<jcraig> action-931?
<trackbot> action-931 -- James Craig to Drive working with CSS on how various mouse cursor options should be chosen -- due 2012-01-30 -- PENDINGREVIEW
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/931
<jcraig> action-932?
<trackbot> action-932 -- James Craig to Explore CSS generated content more -- due 2012-01-30 -- PENDINGREVIEW
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/932
<jcraig> no worries if you're out of time
james, can you jnoin the call?
92473#
JS: noting that there is a lot of action around CSS these days
JC: think these items should be closed, have been getting feedback from CSS WG
JS: think that the group should
review these, as we are looking at a larger CSS approach - will
add these to next weeks agenda
... thanks
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/WQG/WG/ Succeeded: s/beleive/believe/ Succeeded: s/halst/halts/ Found Scribe: JF Inferring ScribeNick: JF Default Present: janina, Michael_Cooper, Lisa_Seeman, Cynthia_Shelly, John_Foliot, James_Craig Present: janina Michael_Cooper Lisa_Seeman Cynthia_Shelly John_Foliot James_Craig Agenda: http://lists.w3.org/Archives/Public/public-pfwg/2014Aug/0008.html Found Date: 06 Aug 2014 Guessing minutes URL: http://www.w3.org/2014/08/06-pf-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]