Accessibility Conformance Testing Teleconference

01 Mar 2018


Wilco, MaryJo, Romain, Shadi, Charu

Wilco, MaryJo


Pull request 182: Test definitions (from issues 158 and 173 https://github.com/w3c/wcag-act/pull/182/files?diff=split

<Wilco> The applicability MUST only use information provided through test aspects. No other information should be used in the applicability.

<cpandhi> +1

shadi: maybe need to identify key terms like "test aspects"

wilco: not very consistent across the document

shadi: raise an issue on that?

wilco: done

shadi: need to say test aspects *of the same rule*?

wilco: yes, will make that change

romain: saying expectation allows some level of subjectivity, which might contradict being able to use test aspects from other expectations

wilco: don't see how

<rdeltour> +1 on the PR!

romain: agree, I revoke that

maryjo: editorial suggestion

wilco: done

Issue 179: Ediorial differences between spec and example rules https://github.com/w3c/wcag-act/issues/179

maryjo: inconsitency across the rules

wilco: agree, need to be consistent

shadi: do we have a template?

wilco: no

maryjo: we should

wilco: yes, we should

<Wilco> https://github.com/auto-wcag/auto-wcag/blob/fad3275c90c4450e8f3c18948e6093098df1d170/pages/design/rule-template.md

shadi: test procedure -> test definition
... move "background" down, after "implementation tests"

maryjo: "issues" section

wilco: will be dynamic

shadi: implementation tests?

wilco: no, now called "test cases"
... render test aspects lower down in the template
... test requirements below description

shadi: want to think more about crediting different contributors
... may come back with more suggestions

maryjo: change log entries sometimes miss required aspects

wilco: in the template

Issue 180: Create understanding documentation for ACT Rules https://github.com/w3c/wcag-act/issues/180


wilco: let's capture some of the requirements

#1. how should one use rules

#2. how does automated vs manual testing fit in

#3. how can one contribute rules

romain: rule aggregation unclear in the spec

shadi: think may need to be in the spec, not here

romain: maybe call it "Primer" rather than "Understanding"

shadi: think different from this?

wilco: often get questions, and need to explain background, motivation, and other aspects

#4. why ACT is important

<rdeltour> https://github.com/w3c/wcag-act/issues/162

<rdeltour> https://github.com/w3c/wcag-act/issues/165

Any other topics


Online Symposium ACT Rules for Manual Web Accessibility Evaluation Methodologies


Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/03/01 15:43:30 $