W3C

Protocols and Formats Working Group Teleconference
17 Sep 2014

See also: IRC log

Attendees

Present
janina, Michael_Cooper, Fred_Esch, Tim_Boland, James_Nurthen, Gottfried, ShaneM, Jon_Gunderson, Rich_Schwerdtfeger, Cooper, JF, Cynthia_Shelly
Regrets
Chair
Janina
Scribe
Tim

Contents


preview agenda with items from two minutes

<MichaelC> scribe: Tim

js: introductions around the table
... anything to report to group?

Previous Meeting Minutes https://www.w3.org/2014/09/10-pf-minutes.html

RESOLUTION: minutes approved for publication as submitted

TPAC 2014 http://www.w3.org/WAI/PF/meetings/tp2014

js: draft agenda imminent..
... registration and hotel deadlines approaching

Actions Review (Specs) http://www.w3.org/WAI/PF/Group/track/actions/open

mc: actions re: css device adaptations

js: janina sent response - concerns re: ability to zoom

<MichaelC> action-1502 due 1 week

<trackbot> Set action-1502 Ask the mozilla people about whether CSS Device Adaptations fixed zoom is being implemented. due date to 2014-09-24.

js: implementation experience desired

<MichaelC> close action-1501

<trackbot> Closed action-1501.

mc: close apple leave microsoft open

rs: why do we want to inhibit zooming?

jn: there are reasons for various apps..
... mobile is driver for it

js.. will come back to this

mc: action on svg integration

js: will try to get to it soon

new on TR http://www.w3.org/TR/tr-status-drafts.html#tr_LCWD

mc: no new publications of note

js: html5 status is pr

<MichaelC> Linked Data Platform

mc: looked at something related to this recently

js: can let this one go

mc: line grid module, css display module, mixed content - these are not FPWDs
... probably don't need to look at them

sm: html media capture cr - have we looked at this?

mc: we've reviewed already - no comments received

ARIA.Next Items

rs: there are remaining issues - get backlog done
... breakout name and description computation into separate document that can be referenced by ARIA 1.1, SVG 2
... Steve F will help work on this to get ready hopefully to TPAC
... keyboard help pushed off to ARIA 2.0
... separate out ARIA implementation guide to support host languages on web
... webaim survey - awareness/use of ARIA has grown dramatically recently

<ShaneM> http://webaim.org/blog/practitioner-survey-results/

<jongund> http://webaim.org/projects/practitionersurvey/#aria

jn: wcag techniques will increase awareness also

<jongund> http://webaim.org/projects/screenreadersurvey5/#landmarks

rs: use of aria landmarks for navigation has been widely adopted
... authors like live regions for doing status updates
... screen reader usage - jaws and nvda (picking up)

js: what end users should know about aria - maybe a useful document?
... maybe mention on WAI CG?
... requirements for ARIA 1.1 need to be organized
... digital publishing interest group moving towards joint work statement re: document accessibility

rs: do ARIA 1.1 requirements include issues (what is included)?

mc: issues list helps us to arrive at requirements
... doc says what we plan to do and scope information
... which issues stay and which pushed off
... need to know whether spec meets requirement

rs: higher level view

js: rely on digital publishing to support that

rs: greater support for digital publishing industry?

mc: separate requirement

Other Task Force Updates--HTML; SVG; COGA

js: still waiting on info re:longdesc html accessibiltiy task force related objection
... html 5.1 focus item discussion
... maybe break spec into modules? get aired in task force
... aria authoring progress?

CSS Device Adaptation http://www.w3.org/TR/css-device-adapt/

jn: sent email suggested meetings on Fridays
... maybe regular meetings with agendas (starting on 26th)?

js: defer css device adaptation

CSS Overview Redux

js: what should next steps be?

cs: assign someone(s) to do CSS reviews? I could help in Oct

fe: I could help also

js: there is history to this (pointers in agenda)
... overall problem with review strategy is css highly modularized
... so reviews are in bits and pieces
... maybe joint meetings with CSS WG in future?

jf: one issue is zooming (others as well)

cs: suggest set up wiki page re: css review to better organize questions

jf: will review previous minutes first

<fesch> http://www.w3.org/WAI/PF/wiki/CSS/Spec_Review

there's already a css spec wiki (maybe out oof date)

cs: revisit this in several weeks

there is css snapshot document which may be helpful

js: goal is to get issues list together before TPAC to ask CSS WG for discussion

<JF> ACTION: JF to research open CSS issues and add to the wiki page [recorded in http://www.w3.org/2014/09/17-pf-minutes.html#action01]

<trackbot> Created ACTION-1508 - Research open css issues and add to the wiki page [on John Foliot - due 2014-09-24].

<MichaelC> action-1508: bounce action to Cynthia and Fred after

<trackbot> Notes added to action-1508 Research open css issues and add to the wiki page.

sm: maybe CSS WG already has this info
... have automated linking of their specs to cross-reference definitions

Summary of Action Items

[NEW] ACTION: JF to research open CSS issues and add to the wiki page [recorded in http://www.w3.org/2014/09/17-pf-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2014/09/24 16:11:28 $