See also: IRC log
<trackbot> Date: 07 May 2014
<scribe> ScribeNick: ShaneM
<MichaelC> DOM Parsing and Serialization
Not a PF concern.
<MichaelC> CSS Custom Properties for Cascading Variables Module Level 1
Should review just to see if there is anything important for PF.
<MichaelC> ACTION: shane to review CSS Custom Properties for Cascading Variables Module Level 1 http://www.w3.org/TR/2014/WD-css-variables-1-20140506/ - due 21 May [recorded in http://www.w3.org/2014/05/07-pf-minutes.html#action01]
<trackbot> Created ACTION-1436 - Review css custom properties for cascading variables module level 1 http://www.w3.org/tr/2014/wd-css-variables-1-20140506/ [on Shane McCarron - due 2014-05-21].
<MichaelC> TTML Text and Image Profiles for Internet Media Subtitles and Captions 1.0
Discussion about captioning and whether graphical captions are useful.
Standardizing delivery of graphical captions is a good idea, but graphical captions themselves are problematic
JF: Maybe we should acknowledge the work but point out that it does not solve all of the problem.
<MichaelC> ACTION: foliot to discuss with Sean Hayes and David Singer potential a11y issues on TTML-IMSC1 http://www.w3.org/TR/ttml-imsc1/ [recorded in http://www.w3.org/2014/05/07-pf-minutes.html#action02]
<trackbot> Created ACTION-1437 - Discuss with sean hayes and david singer potential a11y issues on ttml-imsc1 http://www.w3.org/tr/ttml-imsc1/ [on John Foliot - due 2014-05-14].
take up item 6
<MichaelC> Web Payments Charter Development CG
<MichaelC> Voting system CG
take up item 4
<MichaelC> close action-1410
<trackbot> Closed action-1410.
take up item 9
Cynthia reviewed the spec. It is an improvement over CSS positioning. Things are closer together in the DOM.
scribe: there is a sentence about A11Y about screen reader order and meaningful order. Should bring it in line with WCAG.
It does not deal with taborder - some things can change the order of the document.
two possible corrections. Strengthen the language about order and taborder. And maybe add some WCAG techniques.
<jamesn> this one? http://www.w3.org/TR/WCAG20-TECHS/failures.html#F1
Maybe we can add something about flexbox to F1 or add another technique that has flexbox in the title?
Cyns: We should respond with a PF comment.
No objections.
Cyns: I would like to make an edit to the comments before Michael sends it to the group.
RESOLUTION: Forward the edited flexbox comments Cynthia wrote as PF comments on the specification.
take up item 2
RESOLUTION: Publish the 30 April minutes to the public mailing list.
take up item 7
Last week we discussed this. The CG supported our proposal. Janina wrote up the scheme and circulated it.
A note that if there are normative requirements in a document, then it should be a specification, not a guide.
<MaryJo> +1
<jamesn> +1
<JF> +1
Suggestion that we drop the word entirely (no "guide" nor "specification").
richardschwerdtfeger: it would be nice if the target stopped moving
We are not talking about changing the content - just the names
janina: we seem to have a problem explaining to people that core needs to be implemented in addition to the language specific requirements. Is there a way to incorporate this into the name?
richardschwerdtfeger: it will be in the spec and will be clear. It does not need to be in the title.
Cyns: We should take "ARIA" out of the name of Core
... it would be "Core Accessibility API Mappings"
... others would be "HTML Accessibility API Mappings" etc.