See also: IRC log
<trackbot> Date: 15 July 2015
<janina> agenda: this
<janina> chair: Janina
<scribe> Scribenick: ShaneM
ShaneM: Second Screen Working Group is reviewing their presentation API draft against the MAUR and will get back to the PFWG in Septemberl
<MichaelC> action-1631 due 1 week
<trackbot> Set action-1631 Review credential management level 1 http://www.w3.org/tr/credential-management-1/ due date to 2015-07-22.
<MichaelC> action-1631: Shane has comments from Manu Sporny to process
<trackbot> Notes added to action-1631 Review credential management level 1 http://www.w3.org/tr/credential-management-1/.
<MichaelC> action-1669?
<trackbot> action-1669 -- Katie Haritos-Shea to Look at data on the web best practices http://www.w3.org/tr/dwbp/ -- due 2015-07-08 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1669
<MichaelC> action-1669: https://lists.w3.org/Archives/Public/public-pfwg/2015Jul/0029.html
<trackbot> Notes added to action-1669 Look at data on the web best practices http://www.w3.org/tr/dwbp/.
<Ryladog> http://www.w3.org/TR/dwbp/
Ryladog: what I recommended is
that they add to the diagram about "data on the web
challenges"
... ACA requires some meaningful use rules about electronic
health records and A11Y
... suggested they add something about data formats to include
one WCAG 2 conforming data type
... or include the information elsewhere in the document
MichaelC: the question is what makes a data format conforming to WCAG 2?
<janina> OK to DOM4
cynthia: Concerned about proprietary
jamesn: How can a data format be accessible? Isn't it hidden?
MichaelC: WCAG cares about
whether the data can be presented to the user
... if we tell them this they are going to ask what to do. What
do we tell them?
Ryladog: that's why I mentioned plain text or CSV
MichaelC: That's fine - just don't mention WCAG then.
cyns: Plain formats do assist the
user agent in helping information be exposed.
... you might want to look at the WCAG accessibility supported
stuff
janina: you might want to refer to these minutes so it is clear that we discussed it when you talk to them
MichaelC: Note that this is NOT a last call.
<MichaelC> CSS Basic User Interface Module Level 3 (CSS3 UI)
MichaelC: I think that we want to review this
janina: what is the timeframe and who will look at it
MichaelC: this came up when talking about grid style sheets. We were worried about DOM and navigation order
JanesM: There is a whole much of stuff in here that is of interest. Text overflow...
MichaelC: "overflow ellipsis" which actually sounds interesting
<MichaelC> ACTION: cooper to review CSS Basic User Interface Module Level 3 (CSS3 UI) http://www.w3.org/TR/2015/CR-css-ui-3-20150707/ [recorded in http://www.w3.org/2015/07/15-pf-minutes.html#action01]
<trackbot> Created ACTION-1682 - Review css basic user interface module level 3 (css3 ui) http://www.w3.org/tr/2015/cr-css-ui-3-20150707/ [on Michael Cooper - due 2015-07-22].
MichaelC: I am interested in reviewing this but dont want to be the only reviewer
<MichaelC> ACTION: nurthen to review CSS Basic User Interface Module Level 3 (CSS3 UI) http://www.w3.org/TR/2015/CR-css-ui-3-20150707/ [recorded in http://www.w3.org/2015/07/15-pf-minutes.html#action02]
<trackbot> Created ACTION-1683 - Review css basic user interface module level 3 (css3 ui) http://www.w3.org/tr/2015/cr-css-ui-3-20150707/ [on James Nurthen - due 2015-07-22].
JamesN: I am going to look at it anyway. Might not raise real comments.
MichaelC: Should have at least one other person
Cyns: timeline?
janina: I would like to do something by early August.
MichaelC: its about 50 pages.
Cyns: I could have something near the end of August...
<MichaelC> ACTION: cynthia to review CSS Basic User Interface Module Level 3 (CSS3 UI) http://www.w3.org/TR/2015/CR-css-ui-3-20150707/ - due 30 Aug [recorded in http://www.w3.org/2015/07/15-pf-minutes.html#action03]
<trackbot> Created ACTION-1684 - Review css basic user interface module level 3 (css3 ui) http://www.w3.org/tr/2015/cr-css-ui-3-20150707/ [on Cynthia Shelly - due 2015-08-30].
<MichaelC> action-1684 due 27 Aug
<trackbot> Set action-1684 Review css basic user interface module level 3 (css3 ui) http://www.w3.org/tr/2015/cr-css-ui-3-20150707/ due date to 2015-08-27.
MichaelC: Make it due the 27th August. Put it on the agenda for that day
<MichaelC> action-1683 due 27 Aug
<trackbot> Set action-1683 Review css basic user interface module level 3 (css3 ui) http://www.w3.org/tr/2015/cr-css-ui-3-20150707/ due date to 2015-08-27.
<MichaelC> action-1682 due 27 Aug
<trackbot> Set action-1682 Review css basic user interface module level 3 (css3 ui) http://www.w3.org/tr/2015/cr-css-ui-3-20150707/ due date to 2015-08-27.
<MichaelC> Tracking Compliance and Scope
MichaelC: last call ends 7 October 2015
<MichaelC> ACTION: janina to manage review of http://www.w3.org/TR/2015/WD-tracking-compliance-20150714/ Tracking Compliance and Scope (note explicit review request needs response) [recorded in http://www.w3.org/2015/07/15-pf-minutes.html#action04]
<trackbot> Created ACTION-1685 - Manage review of http://www.w3.org/tr/2015/wd-tracking-compliance-20150714/ tracking compliance and scope (note explicit review request needs response) [on Janina Sajka - due 2015-07-22].
<MichaelC> action-1685 due 29 July
<trackbot> Set action-1685 Manage review of http://www.w3.org/tr/2015/wd-tracking-compliance-20150714/ tracking compliance and scope (note explicit review request needs response) due date to 2015-07-29.
ShaneM: I need a pointer to the problems about embedding content via CSS.
janina: might have discussed it at the CSS joint meeting in Santa Clara
MichaelC: we have been going back
and forth on this. It isn't clear that it is always a
problem.
... there are philosophical reasons to not do it
janina: but we haven't resolved the issues with it so we prefer it is avoided
MichaelC: the CSS object model accommodates embedded content but not sure where that is with browser implementation
JamesN; WAI allows this already. the content gets included in the accessible name calculation
scribe: it is true that it is
less robust than having the content included in the
document.
... but conforming user agents expose the information through
the accessibility API
<MichaelC> https://www.w3.org/WAI/PF/testharness/testresults?testsuite_id=1&testcase_id=522
<MichaelC> https://www.w3.org/WAI/PF/testharness/testresults?testsuite_id=1&testcase_id=552
ShaneM: Sounds like modern user agents do this right. I am going to let it go.
<MichaelC> Accessible Online Learning Community Group
<MichaelC> Decentralized Sharing Community Group
MichaelC: Seems dead
janina: 15 more days to vote. AC reps please get your comments in!
janina: no particular progress to report.
Cyns: who should I talk to about things to do in Sapporo?
MichaelC: Naomi Yoshizawa (sp?) I will forward an introduction email
JohnF has a matrix to update
janina has to send out an email to the commentors to review our resolutions.
Document is up to date.
janina: could we add multifactor authentication to this? They are not dissimilar
ShaneM: Good point - we should incorporate that
janina: there are a fair number of resources when we looked at this before. Let's get a draft out before TPAC.
janina: when we have a meeting
with them we could offer to do a DUAR document.
... this is bigger than you think and sooner than you
think
... we can provide the A11Y thinking and also interact with
this new working group
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/30 pages/50 pages/ Succeeded: s/hat/that/ Found ScribeNick: ShaneM Inferring Scribes: ShaneM Present: Janina Katie_Haritos-Shea MichaelC ShaneM JamesN WARNING: Replacing previous Regrets list. (Old list: Fred) Use 'Regrets+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Regrets+ JohnF Regrets: JohnF Fred Found Date: 15 Jul 2015 Guessing minutes URL: http://www.w3.org/2015/07/15-pf-minutes.html People with action items: cooper cynthia janina nurthen[End of scribe.perl diagnostic output]