Protocols and Formats Working Group Teleconference -- 24 Nov 2014

<trackbot> Date: 24 November 2014

<richardschwerdtfeger> meeting: W3C WAI-PF ARIA Caucus

<richardschwerdtfeger> http://lists.w3.org/Archives/Public/public-pfwg/2014Nov/0260.html

<richardschwerdtfeger> scribe: fesch

janina: revisit timelines

mc: Judy is working on getting charter approved - involved to include mappings and update deliverables, ARIA 1.1 CR June 2015

rs: have gone through most issues at least once, implementation guide off and running

mc: Name computation is seperate spec - can have own timeline

rs: name computation has dependencies

mc: timelines for mapping guilde could be earlier than aria

rs: identify things at risk in mapping guide - right away, then can roll into a dot release
... relationship related stuff is at risk

mc: workout timelines for core mappings and accessible name mappings - then work out other mappings

rs: what is likelyhood we will get action items done by February?

mc: explains new document process (without last call) - what is the timeline for CR?

rs: Thinks can do a June/July time frame for 1.1

<Zakim> Joseph_Scheuhammer, you wanted to note that, roughly, for every new aria 1.1 feature, there is a new mapping in the core.

js: when we walk through core mapping guide - can have a feedback loop - then need test. Would like list of what is included in 1.1.

rs: doesn't see any new features to 1.1 - based on what we said at face to face meeting

general discussion on modal... - with related to 1.1

<Stefan> +q

stefan: what about aria-help?

rs: believes aria-help got moved to aria 2.

stefan: got odd results for experiment
... is odd results with role and relationships - is it a bug or not well defined?

rs: you do not have to have a role.

bg: can have a problem when a label and a role.

<Stefan> +q

rs/bg: discussion on labelby

stefan: role text would like to have an additional description. When have red letters, red reflects status, experiment with IE.

<clown> http://rawgit.com/w3c/aria/master/aria/aria.html#aria-labelledby

rs: role not required, for instance a div that is a labeledby does not need a role. Browsers may have inconsistent behavior. MS (IE) has had it as a group for a long time.

Stefan: OK with rs answer

rs: may not always need a role, especially when native element has a default role

bg: spans may be more a problem than things with a native role

rs: we need to define a mapping for them
... June or July should be OK and mark things that are at risk

PROPSAL: move to new process, that does not require a last call

mc: CR doubles as last call and CR

rs: any objections to proposal?

RESOLUTION: move to new recommendation track process which excludes a last call draft.

rs: CSUN and vacation - is July ok or do we need more time?

<Zakim> Joanmarie_Diggs, you wanted to ask if we resolved to move or resolved to CfC about moving

rs: getting computed role and getting computed label - proposal sent to HTML working group, got kicked out. Never found a home.
... because css not writing things into the DOM, we will need some of these APIs, we should come up with a plan and have the plan come back to PF>

<jongund> +1

<jongund> +q

rs: do we want it in the accessibility API or some other way? Anyway someone needs to write something up.

jg: are we worried about event handlers as a class?

rs: does anyone know why it got bounced from HTML?

janina: I like the idea of getting events under our control!
... Lets make it as an extension....

rs: name computation can be pull aside - any objection?
... aria 1.1 would not be held up for name computation...

<MichaelC> ACTION: rschwer to research pulling together a group to address some aapi extensions e.g., getcomputedrole [recorded in http://www.w3.org/2014/11/24-aria-minutes.html#action01]

<trackbot> Created ACTION-1537 - Research pulling together a group to address some aapi extensions e.g., getcomputedrole [on Richard Schwerdtfeger - due 2014-12-01].

<MichaelC> trackbot, associate action-1537 with product-17

<trackbot> action-1537 (Research pulling together a group to address some aapi extensions e.g., getcomputedrole) associated with product-17.

rs: July does not seem to an issue for CR.

janina: we might have a 6 month delay

<MichaelC> ¨Recommendation¨

mc: does a date of March 2016 for recommendation
... work?

jg: I have a testing group that meets once a week, can do testing.

janina: Thanks JG, I know we have a block.

mc: other mappings would be on a later timeline, HTML and SVG later. Core and HTML on earlier timeline.

rs: firefox has not been looking at SVG for a while. Apple and chrome have are ahead. SVG may be later.
... want a SVG draft in Q1 2015.
... aria 1.1 should be in time for HTML 5.1

janina: is very pleased :)

mc: charter - standard 3 years

janina: will get new name - API
... PF -> Accessible Platform Architectures WG

<MichaelC> public-svg-a11y list

rs: discussed organizing SVG accessibility task force

<scribe> ACTION: 1520 to [recorded in http://www.w3.org/2014/11/24-aria-minutes.html#action02]

<richardschwerdtfeger> http://lists.w3.org/Archives/Public/public-pfwg/2014Nov/0103.html

<clown> action-1520?

<trackbot> action-1520 -- Jon Gunderson to Create a definition of "value" as per issue-679 -- due 2014-11-10 -- PENDINGREVIEW

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

<clown> issue-679?

<trackbot> issue-679 -- Glossary definition of value is inaccurate -- raised

<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/679

<clown> A literal that solidifies the information expressed by a state, property, role, or text content.

<clown> the above is the text of the current glossary entry

rs: JS do we want to call this the value of a control?

JS: the glossary rule appears to not be the value of control. In that case Jon is on track.

rs: we can change the definition of value (as Jon has defined it) and add value of control which we would need.

jg: will make another defintion for value of control.

joseph: will have a final version of the editors' draft to use to make the working draft of name computation and core mapping spec - and give them to MC.

<richardschwerdtfeger> https://www.w3.org/WAI/PF/Group/track/issues/623

rs: I believe that we do not want inert and will go with modal. Does JD have any actions for modal?

<clown> issue-623

<trackbot> issue-623 -- Consider aria-inert for disambiguation of modal states (re: html|*@inert) -- open

<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/623

<clown> issue-568

<trackbot> issue-568 -- Introduce system modal attributes for dialogs -- open

<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/568

<clown> action-1347

<trackbot> action-1347 -- James Craig to Add an attribute for differentiating modal vs non-modal dialogs/menus/etc. (possibly aria-modal) -- due 2014-10-07 -- CLOSED

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

RESOLUTION: close issue 623 in favor of using an aria-modal state.

JN: need two weeks for action.

<clown> action-1438

<trackbot> action-1438 -- Michael Cooper to Set up auto publish to GH Pages for editors' drafts https://pages.github.com -- due 2014-10-15 -- OPEN

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

<richardschwerdtfeger> https://www.w3.org/WAI/PF/Group/track/actions/1438

rs: JD is the queen of github.

<joanie> jd: git; not github.

<clown> action-1440?

<trackbot> action-1440 -- Joanmarie Diggs to landmarks section uses "region of page" in prose even though "region" is not a landmark -- due 2014-10-06 -- OPEN

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

<clown> https://twitter.com/stevefaulkner/status/467345068287090688

<joanie> 1. http://rawgit.com/w3c/aria/master/aria/aria.html#region

<joanie> Current text: "When defining regions of a web page, authors are advised to consider using standard document landmark roles. If the definitions of these regions are inadequate, authors can use the region role and provide the appropriate accessible name."

<joanie> Proposed text: "A region is not a navigational landmark. Content authors SHOULD use standard document landmark roles for regions which are meant to be treated as landmarks."

rs: at IBM we use region as a landmark.

<joanie> https://twitter.com/stevefaulkner/status/467345068287090688

joseph: listed subclass of regions

jg: quoted HTML use of region

<clown> region role's subclasses: alert, article grid, landmark, list, log, status, tabpanel

<clown> landmark role is abstract, and its subclasses are: application, banner, complementary, contentinfo, form, main, navigation, search.

<jongund> I need to go

rs: will resume landmarks next week

- DRAFT -

Protocols and Formats Working Group Teleconference
24 Nov 2014

Attendees

Contents

Summary of Action Items