See also: IRC log
<trackbot> Date: 24 September 2014
<janina> agenda: this
<scribe> scribe: JF
RESOLUTION: publish minutes from last weeks meeting as submitted
JS: hotel is almost fully booked, start to look for altenative lodging
skeleton page for agenda is now up
MC: Action 1503
leave open
Actions on Janina and Cyns to investigate moz/ie implementation of CSS device adaptations
Action 1428 - no progress
<trackbot> Error finding '1428'. You can review and register nicknames at <https://www.w3.org/WAI/PF/Group/track/users>.
MC X-query and X-path
<MichaelC> XQuery and XPath Full Text 3.0
JS: seems we can let this one go
[agreement]
MC: pretty sure we noted geometry
interfaces
... Clipboard API advanced - might want to watch this, based on
IndieUI work
... seem to recall this is related to ARIA drag-and-drop
JS: how far is this from last call?
MC: need to check - hard to
tell
... no projected time-frame listed
notes testing status is 85% complete
JS: suggest we bring this to the
IndieUI group
... CSS Flexbox on its way to second last call
Rich has noted that this needs more review
JS: we should likely not do anything formal at this time, but need to keep an eye on it
MC: could go up tomorrow or next Tuesday
JS: Rich and Cyns will want to review
JS: Rich is not here. Not much to report
slow progress on Work Statement with digital publishing group
draft exists but needs more work
soon come
JS: have made some edits to the SVG WG
need to identify and appoint a facilitator - a joint effort
after that, do a formal review of work statements
JS to post draft statement
<MichaelC> [DRAFT] SVG Accessibility Task Force (SVG A11Y TF) Work Statement
<MichaelC> ACTION: cynthia to review Sept 2014 version of CSS Flexbox http://www.w3.org/TR/css3-flexbox/ - due 2 weeks [recorded in http://www.w3.org/2014/09/24-pf-minutes.html#action01]
<trackbot> Created ACTION-1510 - Review sept 2014 version of css flexbox http://www.w3.org/tr/css3-flexbox/ [on Cynthia Shelly - due 2014-10-08].
<MichaelC> ACTION: rich to review Sept 2014 version of CSS Flexbox http://www.w3.org/TR/css3-flexbox/ - due 2 weeks [recorded in http://www.w3.org/2014/09/24-pf-minutes.html#action02]
<trackbot> Created ACTION-1511 - Review sept 2014 version of css flexbox http://www.w3.org/tr/css3-flexbox/ [on Richard Schwerdtfeger - due 2014-10-08].
JS: nothing much to report
expecting HTML WG to start reviewing "HTML.next" additions, etc. Prioritize and assign
COGA is moving slowing
JS: we've talked about this before
quesstion is: what do we want to do about this?
suspect that at least we express our concerns
JF: if already implemented, it will be an uphill battle
JS: don't think there are any implementations
JN: the meta-tag solutions is implemented across many UAs
MC: not sure if the CSS is
implemented, but both CSS and metatag are in spec
... the CSS allows to restrict zoom
CS: could ask for browsers to ignore zeros
looking at WCAG
doesn't actually require zooming - could be text scaling
does this prevent text scalling as well?
setting font settings on mobile is complicated
MC: may have to write failure techniques for WCAG
JN: only fail in WCAG is allow to enlarge text to 200%
Fred: seen lots of products that depend on zoom
CS: WCAG is not very strong on zoom, likely not strong enough in 2015
MC: we could seek to not have it published in the spec, but browsers can continue to implement (may invoke WHAT WG version instead)
JN: perhaps we can ensure that in
the spec, if it limits zoom that authors need to use other
means to ensure compliance to WCAG 200%-text enlarge
... believes that WCAG doesn't have a problem here; zoom is but
one of the tools available to meet the standard
CS: UX may surpass WCAG
MC: sounds like this is an issue for the WCAG WG
likley will result in a *lot* of discussion
JS: so we don't think in terms of
failure techiniques
... perhaps we should have WCAG WG look and agree
JN: could craft a success/failure technique
CS: good for author
education
... it would be good to have something in WCAG about this
MC: believe we need to discuss
this, but it will likely be a year or more from now
... we should be asking for text in the CSS spec that warns
about this issue
JS: and that should point to the failure
JN: onced we have one
... perhaps the mobile TF could look at that?
CS: sounds like a good idea
JS: looking for volunteers to draft something (advisory)
ACTION Janina to work on a draft for next wednesday
<trackbot> Created ACTION-1512 - Work on a draft for next wednesday [on Janina Sajka - due 2014-10-01].
JS: any progress?
Fred: huge amount of stuff that appears to be ongoing
not really sure of the scope of what is being undertaken
JS: want to spot individual issues, but also an overall sense of the "big picture"
Fred: that, plus there is no single spec - new stuff just gets added
CS: yes, the big question is "what is CSS"
There is also SASS
Fred: there are also issues around color and transparency
issue around transparency
CS: the only way to test in the rendered source is using the eyedropper method
Fred: now that there is transparency, will get-computed-style now "work"
JN: you can never determine via CSS alone
[discussion on programmatically checking color contrast]
Fred: concern is when transparency is in CSS
CS: could ask for a feature to get this from the CSS rendering engine
JN: agree this is complex, but not sure if CSS is going to give us this.
CS: it is an interesting feature to look into
JN: likely will be shot down - huge security implications
JS: we need to continue this discussion, but we are out of time this week
CS: suggests that Fred file an issue here
JS; until next week