W3C

Protocols and Formats Working Group Teleconference
01 Apr 2015

See also: IRC log

Attendees

Present
Gottfried, JF, James_Nurthen, Joanmarie_Diggs, Michael_Cooper, ShaneM, [IPcaller], [Microsoft], janina
Regrets
Rich
Chair
Janina
Scribe
me

Contents


<trackbot> Date: 01 April 2015

<janina> agenda: this

preview agenda with items from two minutes

<scribe> scribe: me

<janina> http://lists.w3.org/Archives/Public/public-pfwg/2015Mar/0253.html

Previous Meeting Minutes https://www.w3.org/2015/03/25-pf-minutes.html

Janina: Have a close look - we talked about the new charter.

JamesN: Can i have a look at it after this meeting - i am on travel right now.

Janina: Okay.
... Can i request approval on the list after James has looked at it?

(no objection)

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

action-1580?

<trackbot> action-1580 -- John Foliot to Review screen capture http://www.w3.org/tr/screen-capture/ -- due 2015-04-01 -- OPEN

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

<MichaelC> action-1580 due 1 week

<trackbot> Set action-1580 Review screen capture http://www.w3.org/tr/screen-capture/ due date to 2015-04-08.

action-1572?

<trackbot> action-1572 -- Cynthia Shelly to Look at the possibility of using browser code for alpha transparency checking due 2014-02-11 -- due 2015-04-01 -- OPEN

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

<MichaelC> action-1572 due 2 weeks

<trackbot> Set action-1572 Look at the possibility of using browser code for alpha transparency checking due 2014-02-11 due date to 2015-04-15.

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

<MichaelC> Media Source Extensions

Janina: Includes an edit from the task force.

<JF> https://www.w3.org/Bugs/Public/show_bug.cgi?id=27054

John: There was a bug, we are looking for feedback. Question about supplemental accessibility material, should not be encoded. The group will likely try to finish this in their f2f meeting in 2 weeks.

<MichaelC> ACTION: janina to make sure HTML A11Y TF reviews Media Source Extensions http://www.w3.org/TR/media-source/ - due 2 weeks [recorded in http://www.w3.org/2015/04/01-pf-minutes.html#action01]

<trackbot> Created ACTION-1609 - Make sure html a11y tf reviews media source extensions http://www.w3.org/tr/media-source/ [on Janina Sajka - due 2015-04-15].

<MichaelC> CSS Scroll Snap Points Module Level 1

Michael: Features for panning and scrolling with snap points, vertically or horitzontally.
... Can be used to simulate "paging experience".
... Not sure if this has a11y issues.

James: Potentially an issue.

Michael: Snapping done on a container level
... No example when the content is bigger than the viewport.

Janina: i can read it on this level

<MichaelC> ACTION: janina to skim CSS Scroll Snap Points Module Level 1 to see if there are issues with content bigger than viewport http://www.w3.org/TR/css-snappoints-1/ [recorded in http://www.w3.org/2015/04/01-pf-minutes.html#action02]

<trackbot> Created ACTION-1610 - Skim css scroll snap points module level 1 to see if there are issues with content bigger than viewport http://www.w3.org/tr/css-snappoints-1/ [on Janina Sajka - due 2015-04-08].

John: It says: UAs must provide an accessible alternative.

Michael: This is just an example, in the document conventions section.

Community Groups http://www.w3.org/community/groups/

<MichaelC> HTML 5 Japanese CG

Janina: We are not worried.

<MichaelC> Trust & Permissions Community Group

Michael: Only 6 messages on this list. Might be a dead group. But should be of interest in general.

Janina: Come back to it in 3 months?

Michael: Okay, i note this.
... in the Wiki.

<MichaelC> HTML Tidy Advocacy Community Group

Michael: Continued support for the HTML tidy library. We don't need to participate from PF, i think.

Janina: right

Rechartering Continued

WAPA Proposal https://rawgit.com/cyns/wapa/master/wapa.html

Web Accessibility Properties and Actions (WAPA) Explainer

Cynthia: Allows for ARIA to be inserted and manipulated based on events. To allow properties that might be HTML properties to be connected up to a11y APIs.
... I'll try to give you URLs for some scripts.

<cyns> https://rawgit.com/cyns/wapa/master/ol-wapa.html

<cyns> https://rawgit.com/cyns/wapa/master/wapa-demo.html

Cynthia: Scenario 1: Web application represented in JS objects, don't touch the DOM.
... Look at the source of wapa-demo.html.
... See function HandleRequest(event). When this is fired, it will fill in the ARIA information.
... Scenario 2: Virtualized list scenario. Look at wapa-demo.html.
... Unordered list with 4 items, items are injected at runtime, but not all are in the DOM.
... Having to maintain a DOM with 1000 objects is not good to be dealt with in the DOM.
... Scenario 3: Change ARIA properties from script. Works with the same event handler.
... Example at CSUN was a checkbox. If a toggle request comes in the script can react to it. No need for simulated scripts, etc.
... This fits in with the way that Webapps are going. Idea of command events coming in.
... Solves many problems that IndieUI addresses, but in a more appropriate way, we think.
... Internally we call this "dynamic ARIA".

Joanie: Why doesn't this already work now?

Cynthia: A new way to react when an accessibility tool has connected to the browser.
... ARIA request events are new.

Joanie: We have multiple actions on platform, every action can be triggered through the a11y API.

Cynthia: Runs only when the AT connects.

Joanie: We have an accessible action interface. Firefox expose an accessible action. For example, i can trigger an "show longdesc" action.
... There is no standard that tells which actions should be supported.

Janina: For NVDA, we discussed the longdesc example.

Cynthia: IE has an ancient longdesc implementation. Thinking about doing something more modern.

Joanie: We are lacking an ARIA API.

Cynthia: The third demo filters on what kind of request this is (toggle, selector, etc.). This is not in the set of examples i provided.

<jamesn> I showed the draft spec to some of our toolkit devs and they all agreed WAPA would be useful

Cynthia: There is a property on the event object saying what kind of action it was. The handler can react on that.

Joanie: Could we base this on ARIA actions.

Cynthia: Currently based on UIA actions. But could be extended.

Joanie: We need a defined set of these actions.

Cynthia: This work needs to happen here or in Webapps.

Joanie: Drag me in.

<janina> Can people hear me?

<janina> Argh!

<cyns_> this is the line of script I was talking about

<cyns_> if (event.target === myCheckbox && event.commandName === "toggle")

Rechartering Continued

Janina: Would everybody agree, that WAPA would be an ARIA activity?

Cynthia: Not sure whether ARIA or Webapps.

<MichaelC> ackme

Janina: Should be both, as a tf between ARIA and Webapps.
... Would also subsume the IndieUI story.
... What they don't pick up would like for AT and ARIA events.

We agree on the what but need to figure out the how.

Janina: Next week, Gregg Vanderheiden will join to talk about contrast ratios.
... PF adjourned.

actions?

Summary of Action Items

[NEW] ACTION: janina to make sure HTML A11Y TF reviews Media Source Extensions http://www.w3.org/TR/media-source/ - due 2 weeks [recorded in http://www.w3.org/2015/04/01-pf-minutes.html#action01]
[NEW] ACTION: janina to skim CSS Scroll Snap Points Module Level 1 to see if there are issues with content bigger than viewport http://www.w3.org/TR/css-snappoints-1/ [recorded in http://www.w3.org/2015/04/01-pf-minutes.html#action02]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/04/08 16:18:49 $