Accessible Platform Architectures Working Group Teleconference -- 18 May 2016

preview agenda with items from two minutes

<scribe> scribe: fesch

js: may go over usual items and look at next steps... any additions?
... any news?

Web Payments Subteam--What do we need to do differently?

js: no one on call last week, because we are behind... I propose we try again for Monday, we have things to look at, comments?

Blockchains Workshop Call https://www.w3.org/2016/04/blockchain-workshop/

js: end of june workshop on blockchains, Any accessibility issues? upcoming deadline for submitting papers, in Boston
... invoices...

sm: in webpayments we are looking at blockchains....

js: is there an accessibility implications?

sm: Katie and I are heavily envolved

TPAC 2016 Planning

js: registration is open, early registration is appreciated, may be wise to book hotel early, may be tight in Lisbon at that time

lw: if we need webplatforms and APA to meet then Tuesday would be the best day

js: we haven't decided how to bundle stuff at TPAC...

lw: there are days chairs need to meet...

js: both APA and ARIA will be busy

mc: I put in the info in the wiki pages
... meeting hotel near the conference center, be aware that there is a no cancellation policy
... may just be one hotel
... construction noise may be going on... but within walking distance

Actions Checkin (Specs) https://www.w3.org/WAI/APA/track/products/8

action-2037

<trackbot> action-2037 -- Joanmarie Diggs to Re-review https://www.w3.org/tr/selection-api/ selection api -- due 2016-05-11 -- OPEN

<trackbot> http://www.w3.org/WAI/APA/track/actions/2037

<MichaelC> action-2037 due 1 week

<trackbot> Set action-2037 Re-review https://www.w3.org/tr/selection-api/ selection api due date to 2016-05-25.

action-2036

<trackbot> action-2036 -- Janina Sajka to Review https://www.w3.org/tr/dpub-accessibility/ digital publishing and accessibility in w3c documents -- due 2016-05-11 -- OPEN

<trackbot> http://www.w3.org/WAI/APA/track/actions/2036

js: that one is done... should be closed

<MichaelC> close action-2036

<trackbot> Closed action-2036.

action-2035

<trackbot> action-2035 -- Shane McCarron to Review https://www.w3.org/tr/annotation-model/ web annotation data model, https://www.w3.org/tr/annotation-protocol/ web annotation protocol, https://www.w3.org/tr/annotation-vocab/ web annotation vocabulary -- due 2016-05-11 -- OPEN

<trackbot> http://www.w3.org/WAI/APA/track/actions/2035

sm: no accessibility anything... no UI

<MichaelC> close action-2035

<trackbot> Closed action-2035.

mc: may still have accessibility guidance - like don't mess it up.... we often give guidance to try to avoid bad implementations
... there is now in the charter template for working groups - you should have an accessibility section in your spec

js: great, congrats .... you have been after that for a while

sm: accessibility would be the next level up

mc: sometimes a community group will draft a bunch of use cases and a real low level API...

sm: interesting on what gets put in a charter...

action-2034

<trackbot> action-2034 -- Janina Sajka to Review https://www.w3.org/tr/css-snappoints-1/ css scroll snap points module level 1 -- due 2016-05-11 -- OPEN

<trackbot> http://www.w3.org/WAI/APA/track/actions/2034

<janina> https://drafts.csswg.org/css-scroll-snap/https://drafts.csswg.org/css-scroll-snap/

js: might want low vision folks to look at it, it might be helpful... nothing else to look at and may have lots of changes
... would ai2 be the right group?

mc: WCAG wg doesn't want anything else...

jf: happy to dialog with ai2... can have them look at it... we haven't responded yet
... if we want to ask ai2 to look at css-snappoints I can ask them...

<MichaelC> ACTION: foliot to reach out to AI2 on CSS scroll snap points [recorded in http://www.w3.org/2016/05/18-apa-minutes.html#action01]

<trackbot> Created ACTION-2040 - Reach out to ai2 on css scroll snap points [on John Foliot - due 2016-05-25].

<MichaelC> action-2040?

<trackbot> action-2040 -- John Foliot to Reach out to ai2 on css scroll snap points -- due 2016-05-25 -- OPEN

<trackbot> http://www.w3.org/WAI/APA/track/actions/2040

jf: would love to give them feedback from the last call

lw: OK talk to me offline

<MichaelC> action-2040: see ACTION-2034

<trackbot> Notes added to action-2040 Reach out to ai2 on css scroll snap points.

<MichaelC> action-2034: see ACTION-2040

<trackbot> Notes added to action-2034 Review https://www.w3.org/tr/css-snappoints-1/ css scroll snap points module level 1.

<MichaelC> close action-2034

<trackbot> Closed action-2034.

<MichaelC> action-2040 due 4 weeks

<trackbot> Set action-2040 Reach out to ai2 on css scroll snap points due date to 2016-06-15.

action-2033

<trackbot> action-2033 -- Shane McCarron to Review https://www.w3.org/tr/tracking-compliance/ tracking compliance and scope -- due 2016-05-11 -- OPEN

<trackbot> http://www.w3.org/WAI/APA/track/actions/2033

action-2030

<trackbot> action-2030 -- John Foliot to See if reporting api 1 https://www.w3.org/tr/reporting-1/ has applicability to a11y policy reporting -- due 2016-05-11 -- OPEN

<trackbot> http://www.w3.org/WAI/APA/track/actions/2030

jf: spoke to engineers at deque, doc very early, lets track... may have applicability to reporting... not ready

<MichaelC> close action-2030

<trackbot> Closed action-2030.

action-2027

<trackbot> action-2027 -- John Foliot to Solicit gregg vanderheiden review of secure contexts https://www.w3.org/tr/powerful-features/ -- due 2016-04-27 -- OPEN

<trackbot> http://www.w3.org/WAI/APA/track/actions/2027

<MichaelC> close action-2027

<trackbot> Closed action-2027.

action-2039

<trackbot> action-2039 -- Fred Esch to Review https://www.w3.org/tr/css-sizing-3/ css intrinsic & extrinsic sizing module level 3 -- due 2016-05-18 -- PENDINGREVIEW

<trackbot> http://www.w3.org/WAI/APA/track/actions/2039

this spec is about box sizes

<MichaelC> close action-2039

<trackbot> Closed action-2039.

mc: reads note, we can close

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

<MichaelC> CSS Positioned Layout Module Level 3

fe: probably has similar issues as flexbox and grid layout
... can give me an action

lw: I can look at it

<MichaelC> ACTION: watson to review https://www.w3.org/TR/css-position-3/ CSS Positioned Layout Module Level 3 [recorded in http://www.w3.org/2016/05/18-apa-minutes.html#action02]

<trackbot> Created ACTION-2041 - Review https://www.w3.org/tr/css-position-3/ css positioned layout module level 3 [on Léonie Watson - due 2016-05-25].

<MichaelC> ACTION: esch to review https://www.w3.org/TR/css-position-3/ CSS Positioned Layout Module Level 3 [recorded in http://www.w3.org/2016/05/18-apa-minutes.html#action03]

<trackbot> Created ACTION-2042 - Review https://www.w3.org/tr/css-position-3/ css positioned layout module level 3 [on Fred Esch - due 2016-05-25].

<MichaelC> ACTION: cynthia to review https://www.w3.org/TR/css-position-3/ CSS Positioned Layout Module Level 3 [recorded in http://www.w3.org/2016/05/18-apa-minutes.html#action04]

<trackbot> Created ACTION-2043 - Review https://www.w3.org/tr/css-position-3/ css positioned layout module level 3 [on Cynthia Shelly - due 2016-05-25].

mc: having webex sound problems

js: if we just have issues that should be in the css YAMM
... that is good info to know

<MichaelC> DOM Parsing and Serialization

mc: if there is a section then... I don't know if we care

fe: rich had an issue with another parsing spec, because it talked about content injection

<MichaelC> ACTION: Léonie to review DOM Parsing and Serialization https://www.w3.org/TR/DOM-Parsing/ [recorded in http://www.w3.org/2016/05/18-apa-minutes.html#action05]

<trackbot> Created ACTION-2044 - Review dom parsing and serialization https://www.w3.org/tr/dom-parsing/ [on Léonie Watson - due 2016-05-25].

<MichaelC> ACTION: esch to review DOM Parsing and Serialization https://www.w3.org/TR/DOM-Parsing/ [recorded in http://www.w3.org/2016/05/18-apa-minutes.html#action06]

<trackbot> Created ACTION-2045 - Review dom parsing and serialization https://www.w3.org/tr/dom-parsing/ [on Fred Esch - due 2016-05-25].

js: I wonder if the updated spec has any influence on reordering the DOM (flexbox)

cs: unintelligable
... [unintelligable]

sm: ready to give up WebEx

<MichaelC> Input Method Editor API

LW: this is effectively abandoned...
... will be converted to a Note

mc: spec review not needed

HTML 5.1 Review Discussion

js: will call the meeting webex is breaking up voice too much
... will do HTML 5.1 review next week

rrs, make minutes

- DRAFT -

Accessible Platform Architectures Working Group Teleconference

18 May 2016

Attendees

Contents