See also: IRC log
Wilco: task force tools setup
... want to have a call next week to introduce new participants to these
tools
<Ryladog> Sorry I will be on a plane at that time
https://www.w3.org/WAI/GL/task-forces/conformance-testing/
<Wilco> https://www.w3.org/WAI/GL/task-forces/conformance-testing/
<Wilco> shadi: please see the information on the conformance testing homepage
Wilco: plan is to have weekly meetings for
ACT TF
... need to determine possible times
... either Thursday at this time, or same time on Wednesday
... preference for Wednesday, to avoid rescheduling auto-WCAG
Katie: Wednesday works for me
Rob: when is auto-WCAG?
<Alistair> Wednesday +1
Wilco: at this time
Jon: can you describe the relationship between auto-WCAG and ACT TF?
<Wilco> https://www.w3.org/WAI/GL/task-forces/conformance-testing/
Wilco: ACT TF will focus on standardizing
the format of test rules
... and auto-WCAG will continue to develop test rules according to that
new standard
Rob: so auto-WCAG will develop a tool?
Wilco: no, the rules that get implemented by tools
Rob: how is that different to ACT TF?
Wilco: auto-WCAG writes the tools, ACT TF standardizes the format
Shadi: output of ACT TF is a standard of
the rule format and the benchmark requirements
... and output of auto-WCAG is a repository of test rules
... those that pass the benchmark will be marked as such
Wilco: back to agenda - hearing no objections to Wednesday
Charu: fine for me
David: fine too
Lori: fine too
Romain: probably fine too
RESOLUTION: ACT TF will meet Wednesday from end-September onwards
Wilco: need to register for ACT TF
<Wilco> shadi: the act tf will be a taskforce of the wcag wg, who are responsible for the standardization. they will do the validation and vatting to ensure uniform interpretations
<Wilco> ... the work will start very soon. If you want to participate, you need to join WCAG WG
<Wilco> ... there are different procedures if you work for a w3c member organization or you don't
https://www.w3.org/WAI/GL/task-forces/conformance-testing/
<Wilco> ... on the homepage of the act tf there is information, go to 'how to participate'. there is a link to wcag wg participation
<Wilco> ... if you work for a w3c member, your ac rep need to asign you to the working group. You need to let Shadi know that you want to join
<Wilco> ... also let the chairs of the wcag wg know if you only want to participate in the taskforce
<Wilco> ... if you are not from a w3c member org, there is a procedure for invited experts
<Wilco> ... this is reviewed case by case, depending on what organization you are from
<Wilco> ... We will move all activities to the ACT TF, and auto-wcag will only keep working on test rules.
<Wilco> ... You are welcome to participate in both groups.
<Wilco> David: Do I need to reapply as a invited expert?
<Wilco> shadi: I'll need to check
<Wilco> shadi: Let us look separately
<Wilco> Charu: I have to get internal permission internally as well
<Wilco> shadi: if you have any questions please email me
<Wilco> rob: question, the auto-wcag group is a CG, and it does not go through the same process
<Wilco> shadi: yes
<Wilco> shadi: depending on your organization, you may need permission, but anyone can join a community group. It is much more open and easy to get involved
<Wilco> ... we want to do the rule development in that group
Wilco: several people not on the call
... can I send them the links
https://www.w3.org/WAI/GL/task-forces/conformance-testing/#contribute
Shadi: suggest that link from the homepage
Alistair: not attending in-person
Wilco: goal is to work on the requirements document
<david> regrets, conflict with usbln conference
<Wilco> shadi: TPAC is from the 19th to the 23rd of september, you can still join until tomorrow
<Wilco> ... This is an informal meeting to interact with the WCAG WG to get the group started
<Wilco> ... We'll work on the requirements to help kickstart the work
<Wilco> ... there will be remote participation for ACT participants
<Wilco> 5) User stories: https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/User_stories
Wilco: approach to help evolve the
requirements
... grouped user stories into specific groups
[Wilco walks through the document]
David: like the approach and categorization
... just nit-pick on #7
... think policy makers often don't get to that level of detail implied
... likely will refer to a body of work that their team is allowed or
encouraged to use
Katie: can leave it as-is
... but rephrase a "QA-lead following a policy"
... or such
David: agree with Katie
... this work relates to policy but not policy
... agree that QA is where rubber will hit the road
Wilco: agree, QA-lead is that I was thinking about
Katie: but ensure to say "following a
policy"
... QA lead not typically write policy
David: mention of policy important, though
... want to encourage use of repository
Alistair: this group is not designed to do
that
... it is this group plus auto-WCAG
... suggest to drop out what is not being done by ACT TF
Katie: think keep together
... large organizations will be thinking "what is the least I could do"
Alistair: need to decide which tests are
good or bad
... repository open to any contribution
... concerned about watch-keeping
Wilco: put this in because expected this
discussion
... want to clarify scope
... repository will be developed by ACT but who will maintain it is
still open
... will decide which get included and which not
... will need at least a set of acceptance criteria to get to REC
... need to figure how to maintain that repository
Alistair: did not realize that this is part of ACT
Jon: had trouble with Techniques on which
ones get in and which not
... some get left out for whatever reason
... hope that there will be a clear process
... to ensure transparency and reduce frustration
... also to know which kind of rules should be submitted and which not
Wilco: looking at how this is done for
Techniques will be important
... will come later down the road
<jongund> i need to leave a little early
Alistair: still concerned about scalability
... took me a year to get a Technique accepted
... lots of discussion
... didn't realize we are going to vet rules
Wilco: not sure we will come up with a set
that is definitive
... but have a benchmarking deliverable
... still have to figure out exactly how
... will need to consider implementation time
... also manage the quantity of rules
Alistair: talking about industry consortium rather than W3C group
Wilco: don't see why
Alistair: because knock-effect on entire industry
Wilco: again, manufacturers can go beyond
... this is a minimum set that we all agree on
... document these agreed rules in a repository
Charu: reiterated that ACT will deliver
framework, benchmark, and repository
... repository includes test rules developed by auto-WCAG
Wilco: rules in the repository is at least
test rules we agree on
... figure out how to maintain ACT after we've solved the acceptance
Charu: trying to understand the relationship to auto-WCAG
Wilco: auto-WCAG writing rules but rules can come from other organizations as well
Wilco: please use Discussion Page to comment on these
Shadi: need to join ACT TF
Rob: next auto-WCAG meeting?
Wilco: 29 September
... same time
... next ACT TF meeting next Thursday same time