Protocols and Formats Working Group Teleconference
03 Sep 2014

<trackbot> Date: 03 September 2014

preview agenda with items from two minutes

<scribe> scribe: JF

Previous Meeting Minutes https://www.w3.org/2014/08/27-pf-minutes.html

RESOLUTION: publish last weeks minutes as submitted

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

JS: time to start thinking about proposed agenda for TPAC - within 60 days now
... a number of cross meetings emerging

Rich wants to meet with SVG group, and perhaps have the ARIA folks there too

MC: SVG is Thurs/Fri

JS: we need to talk with SVG, Digital Publishing, Web & TV all want to meet with PF
... there is likely one other as well

what kind of agenda do we want to accomp0lish with each group

need to look at ARIA issues

what will we best benefit on in F2F meetings?

JS: we need to talk with the CSS folks as well

we need to start focussing on that soon - next week?

JF: have we asked about availability of the other groups?

JS: want to specify detailed discussion points

not just "we should meet"

RS: there is a joint task force between PF and SVG

ARIA - taxonomy around semantics & graphics

IBM has a draft taxonomy on this

RS: 2 things - implementation guide and the taxonomy (SVG)

need to talk about the merger into HTML

RS: how do we coordinate that?

JS: sounds like a 3-way meeting: SVG, HTML, PF

RS: might be able to get Fred (IBM) to come - but would need to join one of the working groups

JS: any other TPAC agenda items?

JF: suggestion to reconvene the media subteam of a11yTF, to discuss items with Web & TV folks

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

MC: Action 1500

<MichaelC> action-1500?

<trackbot> action-1500 -- Cynthia Shelly to Find out if ms is implementing CSS Device Adaptations fixed zoom. -- due 2014-09-03 -- OPEN

<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1500

<MichaelC> action-1501?

<trackbot> action-1501 -- Janina Sajka to Ask james craig about whether apple is implementing CSS Device Adaptations fixed zoom. -- due 2014-09-03 -- OPEN

<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1501

<MichaelC> action-1502?

<trackbot> action-1502 -- Janina Sajka to Ask the mozilla people about whether CSS Device Adaptations fixed zoom is being implemented. -- due 2014-09-03 -- OPEN

<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1502

JS: keep these open

MC: after that, we go back to march

JS: we need to keep them open and get them done

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

MC: one last call

<MichaelC> Battery Status API

JS: seems there is no concern

MC: 2 working drafts

<MichaelC> HTML Canvas 2D Context, Level 2

MC: this is covered, correct?

JS: Rich is watching this

RS: there is a meeting next monday

JS: is there a chair?

RS: not sure what status is. mark continues to participate, and may continue
... will see what's going on next monday

<MichaelC> Encrypted Media Extensions

MC: have had a quick look - neither better or worse than for any other user

might consider asking for a section on accessibility, as there are sections on privacy and security

MC: not sure what it would say.

JS: there have been repeated assurances that there is no UI impact here

MC: what if AT cannot access at other levels? Not sure if there is any use-case

JS: makes me nervous to find nothing

JF: suggest to add this to the TPAC agenda with WEb and TV folks

ARIA.Next Items

RS: had a meeting with digital pub IG

looking to arrange a F2F at TPAC

to finalize what this subteam would be like

discussed requirement on authors for fall-back roles

ie. epub-footer falling back to content-info

what they would like to do, is leverage the mechanism that says that if the semantic doesn't exist in ARIA, fallback to native host language

question around what to do with validator and new roles

?

RS; there seems to be some next steps, but they want to wait for TPAC

JS: they need a draft work statement

needs to start - met last week

JS: Tzviya has agreed to draft first cut of work statement

RS: you were going to let me review it

JS: we don't have it yet
... something went out late yesterday, but have not had time to review it yet
... hope to have more details next week

RS: will be travelling 3rd week of September, hope to see that before then
... returning to the taxonomy module for ARIA, which could be used with SVG, Canvas, etc.

also need to look at authoring guidance too

RS: Fred is willing to chair this, well positioned to do this

JS: a bit nervous about a new member taking such a large role so quickly

RS: will work with him

JS: not saying no, but mindful of those concerns
... reminder that this will be a joint TF with SVG

RS: likely the most interested SVG person is Doug

JS: understand that PF will likely drive this, but we must ensure that SVG are involved

JG: also interested in this as well - especially the authoring practices

JN: we need to get this rolling, but summer has been very busy
... will get this going. Need to get with Matt
... its a bit of a bandwidth issue - a lot of work has been done

JS/RS; Clarrification that this will not be ARIA 1.1 effort (laughter)

RS: need to review outstanding action items. then circle back to ensure we've gotten everything we need
... remember what we wanted, need to ensure we achieved that

JS: we also set outselves to publish FPWD and heart-beats before TPAC
... we need to make as a priority the FPWD

RS: the name computation item needs to be addressed

JS: decision is - go for it. if it needs to be seperated out, then do so

RS: small issue - waiting on cyns to write that.

she is currently on vacation - may not be back in time. may mean that joseph of rich will need to write it

RS: need to ping cyns to see if she can do this

Steve Faulkner has a draft - may be over-simplified, but headed in the right direction

there are a number of name suggestions for this - need to settle on a name

the name computation for html/aria/svg all needs to be in one document

MC: only concern is coming up with a name that re-enforces that

erring on side of caution, but as long as we can argue that it is aligned with Core then we should be ok

(agreement that including Core in name is Good Thing)

JS: any other ARIA issues?
... need to circle back and ensure we have met all requirements - will need to start thinking on testing too
... discussion on use-cases being crystal clear for ARIA 1.1

Other Task Force Updates--HTML; SVG; COGA

JS: we've pretty much covered most of this
... any further questions/progress on any of the remaining agenda items?

(no response)

JS: adjouned

michael cooper - do I make logs public? (ie ask the rrsagent to do that?)