W3C

Accessibility Conformance Testing Teleconference

09 May 2019

Attendees

Present
Shadi, Wilco, Kathy, Alistair, Charu, Moe
Regrets

Chair
Wilco
Scribe
Charu

Contents


Future role of ACT TF (any spec work, and management of rules process) https://github.com/w3c/wcag-act/issues/353

<Wilco> https://github.com/w3c/wcag-act/issues/353#issue-428734105

Wilco took the proposal and added Proposed places for inclusion and the motivation sections

Alistair its a lot to take in, probably can discuss it as a whole in the next meeting

Wilco: any initial comments

Alistair: If new rules are uploaded in the ACT format with 3 implementations then these rules should be promoted
... if rules are created by people with no understanding of accessibility then irrespective of the implementations there needs to be a panel to approve

Shadi: We need to add, the rules can be vetted by the community group or the task force

Wilco: so now to address Alistairs comment, If the rules are incubated outside the community group with implementations then the load on the community group is less to promote

Alistair: i feel theres needs to be a filter group
... example is Trusted Tester, their rules are good, Why does Trusted tester rule needs to be vetted?

Wilco: The proposed rules needs to have implementation support to be promoted
... for HTML its a big group needs at least 3 implementations

Shadi: i prefer having a separation, else much effort will fall on the task group

Alistair: putting through community group slows down the process, if the rules have been demonstrated with sufficient implementations then we should be able to bypass the community group

Shadi: Ok yeah if the acceptance has been demonstrated then it can be promoted

Alistair: we need to document the process to vet the rules.

Kathy: need to document consistent test results across the board
... For someone who already has a test process, we can submit the rules, where does it go from there

Alistair: If the rules has been working like the trusted tester, i feel it is a waste of time rewriting in the community group

Kathy: i see the advantage of putting it in a consistent format to be accepted
... i am fine with doing that, need to understand the effort on our part from this document

Alistair: having written rules for long, it just needs to pass the unit test
... that not complicated to do and show the implementation support

Wilco: the discussion through the community group needs happen

Alistair: Needs to happen only if you do not have the implementation support

Charu: if someone has the rules and shows the implementation support then it should be good to go

Wilco: sure

Alistair: We should only select only the WCAG 2.X rules and not consider the advisory at this point

Wilco: I have proposed that in the ACT task force to consider

Alistair: we should have a ACT baseline to scope the rules

Wilco: Its different as it is not open for public contribution

Kathy: i do agree, some sorting should happen

Wilco: i do agree, how is it different from what is being proposed

Alistair: where is that proposed?

Shadi: I don't think we have spelled out the acceptance criteria here
... We have to be careful to be not too rigid, we will have to through valuable checks out the window just because it is not WCAG criteria
... so anything widely accepted and useful should be considered

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/05/09 15:01:40 $