<Wilco> hi shadi, you coming?

<scribe> Scribe: charu

TPAC meeting

Shadi: We should not hold a formal meeting as people have not made travel arrangements, we can have a meeting with a phone bridge, have asked the WCAG group to have a small slice of time to have a formal blessing and good tie in with the TPAC group

We have rooms for both Thursday and Friday, have to confirm the timings

<rdeltour> I'll be there, can attend Thu and/or Fri

Wilco: i can attend on Thursday

<shadi> https://www.w3.org/2002/09/wbs/35125/TPAC2016/

Shadi: we have five attendees and several observers, the chart is not publicly visible

<shadi> https://www.w3.org/WAI/GL/

Shadi: technical issue, this is a community group, we have to get the group on the task force, you have to join the task force or the WCAG working group

<shadi> https://www.w3.org/WAI/GL/participation.html

Shadi: on the left side there are couple of steps to follow and complete to participate in the task force
... Participation in the task force is enough but encouraged to joined the WCAG working group to have more cordination
... AS registered participants we have Allen as observer, Several people marked as observers, Katie and i are registered, Roman is as well

Wico: sounds good, do we need to send out an announcement

Shadi: Separate discussion on that, We can say we will have an informal get together

Allan: if it is just saying hello then it is better t do it on the phone

Shadi: Start thinking about the requirement and the output

<agarrison> Alistair: it would be useful to have an agenda produced reasonably soon, so people can decide whether to attend in person or not.

Wilco: thinking along the same lines, Do you suggest we start working on the infrastructure, output is one, or is the requirement the right thing to start with

Shadi: it should be the requirements

Wilco: look at existing project and see if we can learn from those to start with

Alistair: thinking may be there are similar thing out there, piggy backing on the known processes

Wico: we should explore that, i would look at related projects for accessibility testing, what we like about that and take that as the outline for what we want to do

Allister: define what we are looking for in a simple sentence

Wilco: i am looking for project related to standardization and automation related to accessibility testing, iso standards, looking at the accessibility testing, what did they get right and what we can improve

Shadi: how about we set up a wiki page where we list all the related work in some format that we can scan and people could add information on what their organization is working on
... Should this be a task force wiki or working group
... all the work should be in a certain space that can be licensed and made public, so put it in the Auto WCAG

Wilco: we may have something

<Wilco> https://www.w3.org/community/auto-wcag/wiki/List_of_other_WCAG_test_specifications

Shadi: you can send that out and that could be input for our face to face

Allister: they just look like test

Wico: we want to put it there as projects then just framework

Wilco: take an action item to set up a list and send out a call

Allister: that would be a call for framework

Wilco: yes, rules themselves are Auto WCAG, but the design is also related to ACT, we can consider that in the standard.

Allister: is that not too prescriptive?
... tools architecture might be different
... if you have a set of tests and then you run multiple tools to get same set of results, conform to test results

Wilco: ideas in the tool can be used as standard

Allister: i would be skeptical to tell people how to architect their tools

Katie: we should prescribe the parameters

Wilco: i feel we should work on the details

Allister: separation between the ACT and Auto WCAG is necessary, it is blur

Wilco: what we have done from the start what we want from the rules, as we write the rules we are finding things and separating out as we have our group formed and architecture going

Al: we need to clearly define and separate out

Wico: what we can do is, if you want to write ACT rules it should be Earl as a prerequisite and the environment your are testing in and parsing

Al: those are good examples that will help clearly layout as a backgroud

Shadi: i do think we should have an re introductory meeting, what are the possible output format and add other formats and ideas and the same for frameworks
... In the early phase we should pull out the specification and relation of different parts to justify why we picked certain framework or outputs

Wilco: We can layout the proffered way of doing

Shadi: define the assumptions and parameters i a requirement document

Allister: not all tools require framework

Wilco: Framework is not a software framework, just how rules will be build

Shadi: you have a glossary? we need terms defined

Wico: During the workshop we came up with definations

Shadi: yes that will be helpful as background
... we may not require framework

Allister: how does Selenium tie in?

Wilco: Selenium drives the environment

Shadi: We need to have a way to support different framework

Katie: We need to define rules and parameters that support different frameworks

Wilco: what is relevant how to eliminate false positive irrespective of how they build the tool

Allister: As long as the tool out puts correct results, they should be OK, need a testsuite that runs against any tool with right results

Katie: WCAG needs to be outcome based

Shadi: we need bit of both, need a rules repository that tools can run, probably want people to contribute tests as well,

<Avneesh> I have to leave for another call, sorry. Thanks for god discussion.

Katie: inter operable format

Al: there is proprietary stuff, we need control data to validate or it will not be good. Building rules and control data that people can validate is what we need

<emmaPR_bbc> Is the control data similar to the benchmarking that is marked out as the second ACT deliverable?

Alistair: Going to the techniques and pulling the test procedure and run the tests

Wilco: Thats the direction we all are leading too
... Question for Shadi, What do we need to do to get invited experts?

Shadi: there are steps to follow, please encourage them to start the process to join or get in touch with me

Al: Do we know PA11y group?

<emmaPR_bbc> Pa11y are London based

Wico: next meeting in 2 weeks, next rules meeting will be next week

<Wilco> RSSagent, make minutes

rss make minutes

rss: make minutes

<Wilco> RSSagent, create minutes

<emmaPR_bbc> Look at previous minutes

<emmaPR_bbc> SOmeone asked last time

Zakim create minuts

ok thanks

<shadi> rrsganet, make minutes

This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/Alliser/Alistair/
Succeeded: s/Emma/Katie/
No ScribeNick specified.  Guessing ScribeNick: cpandhi
Found Scribe: charu
Default Present: Avneesh, shadi, Charu, Katie_Haritos-Shea
Present: Avneesh shadi Charu Katie_Haritos-Shea

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 25 Aug 2016
Guessing minutes URL: http://www.w3.org/2016/08/25-auto-wcag-minutes.html
People with action items: 

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