W3C

Accessible Rich Internet Applications Working Group Teleconference

19 Oct 2016

Agenda

See also: IRC log

Attendees

Present
Joanmarie_Diggs, Tzviya, MichaelC, Rich_Schwerdtfeger, Michiel_Bijl, JamesN, ShaneM, Joseph_Scheuhammer
Regrets
Chair
MichaelC
Scribe
MichaelC

Contents


<scribe> meeting: ARIA Editors

<scribe> scribe: MichaelC

Timeline check http://www.w3.org/WAI/ARIA/project

ARIA going to CR next week

Core and AccName Jan, but still Rec April

DPub roles and AAM for early Nov

let´s target 17 Nov for CR, so final version by 3 Nov

Practices using milestones at https://github.com/w3c/aria-practices/milestones

a ¨minimum viable product¨ when ARIA goes to Rec

and an new Note about 6 months later

next WD Dec

graphics stuff ???

Approach to common files after repository split https://lists.w3.org/Archives/Public/public-aria-editors/2016Oct/0008.html

<ShaneM> boooo to 4

<joanie> ShaneM++ (do not like 4)

<jamesn> NOT 4

<joanie> +1 to 1

<MichielBijl> +1 to 1

<Rich> 1 is ok

<ShaneM> +1 to 1

<ShaneM> git submodule --init --update

<jamesn> +1 to 1

RESOLUTION: take up option 1

<ShaneM> oops git submodule update --init

Integration with automated tests

hopefully generate test assertions from AAMs

if they´re complete

though not right away

right now maintaining tests in wiki

a few things to sort out

at this point not much needed in base specs

would like to annotate assertions so they´re more readily discoverable

but no conventions or built-in support right now

<scribe> ACTION: cooper to bring question about annotating test assertions with spec requirements to whomever is working on testing [recorded in http://www.w3.org/2016/10/19-aria-editors-minutes.html#action01]

<trackbot> Created ACTION-2123 - Bring question about annotating test assertions with spec requirements to whomever is working on testing [on Michael Cooper - due 2016-10-26].

Issues with common tools check-in

• Term converter not including accessible description, referenced by accessible name

• Term converter including empty dt

• Need to automate changing ../common/ references

• Need to remove that stupid para that invites self-subscription to comment list

Respec Lint says we need a security statement

might be nice to have a way to tell Respec that it´s been determined not needed

<scribe> ACTION: cooper to ask Ralph about emerging practices for X considerations sections [recorded in http://www.w3.org/2016/10/19-aria-editors-minutes.html#action02]

<trackbot> Created ACTION-2124 - Ask ralph about emerging practices for x considerations sections [on Michael Cooper - due 2016-10-26].

AOB

APG switching to biweekly teleconferences

<joanie> +1 to every two weeks, focused, etc.

Next meeting

Next meeting is 2 Nov 2016

Summary of Action Items

[NEW] ACTION: cooper to ask Ralph about emerging practices for X considerations sections [recorded in http://www.w3.org/2016/10/19-aria-editors-minutes.html#action02]
[NEW] ACTION: cooper to bring question about annotating test assertions with spec requirements to whomever is working on testing [recorded in http://www.w3.org/2016/10/19-aria-editors-minutes.html#action01]
 

Summary of Resolutions

  1. take up option 1
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.148 (CVS log)
$Date: 2016/10/19 17:36:43 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.148  of Date: 2016/10/11 12:55:14  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found embedded ScribeOptions:  -final

*** RESTARTING DUE TO EMBEDDED OPTIONS ***

Found Scribe: MichaelC
Inferring ScribeNick: MichaelC
Present: Joanmarie_Diggs Tzviya MichaelC Rich_Schwerdtfeger Michiel_Bijl JamesN ShaneM Joseph_Scheuhammer
Agenda: https://lists.w3.org/Archives/Public/public-aria-editors/2016Oct/0007.html
Found Date: 19 Oct 2016
Guessing minutes URL: http://www.w3.org/2016/10/19-aria-editors-minutes.html
People with action items: cooper

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]