W3C

Accessibility Conformance Testing Teleconference

01 Feb 2018

Attendees

Present
Stein-Erik, Shadi, Wilco, Alistair, Moe
Regrets
MaryJo, Charu
Chair
Wilco
Scribe
Stein-Erik

Contents


Stein Erik: How do we handle issues and editors note when the draft is published

Wilco: We'll keep the notes/issues when publishing

<Wilco> "An expectation is a statement that must be true about each test target (see Applicability)." Suggest clarifying what we mean by an Expectation by stating, " An expectation is a conformance statement that must be discrete and true about each test target"

AG: All of my images have alt atributes. That is a positive statement that your material conforms. I found images that lack alt texts that is a negative statement.
... an expectation is a statement that you are making about an aspect or element being conformant rather then a conformance statement

Shadi: If we use the word conformance we exclude advisory rules in the future
... conformance statement or statement of conformance may narrow it down more than we intend to

AG: Exectation is a statement I expect to be true

No objections to leaving the draft as it is

<scribe> ACTION: Wilco: open an issue for discussion on performance statements

<trackbot> Created ACTION-25 - Open an issue for discussion on performance statements [on Wilco Fiers - due 2018-02-08].

Wilco: Comment from Romiane on points where notes should be added to the draft

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

Shadi: To what degree is the output format a part of this particular spec

Wilco: It is not, but I can ad a comment in editors notes that we are reviewing how much detail we need from the output format

<Wilco> https://github.com/w3c/wcag-act/issues/164

AG: Would only have one test, as applicability is tested by proxy.. We wouldn't assert a pass or a fail but our array of results look like this

No editors note will be included for issue 164

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

No editors note for issue 165 is needed

Wilco: I'll make sure we make the note for 162

Shadi: Suggests a CFC for final approval

<Wilco> https://github.com/w3c/wcag-act/pull/168/files

Wilco: pull requests, mostly editorial.

Shadi, it is customary to include the title of the standard/specification in the abstract

<Wilco> https://github.com/w3c/wcag-act/pull/170/files

Wilco will merge pull requests before doing a CFC

Survey question 1: ACT Rules Format 1.0 Working Draft approval to publish https://www.w3.org/2002/09/wbs/93339/ACTTF01FEB/results#xq1

Wilco: 3 yes, 1 yes with changes.
... thinks Deltour is right to add CSS selectors to rules examples. Also a link to previous version.

Shadi: Where is the template? I have a related comment.

Wilco: No template at the moment.

Shadi: Rules are taken from Auto-WCAG. How do people feel about adding an acknowledgement section?

<Wilco> https://auto-wcag.github.io/auto-wcag/rules/SC1-1-1-aria-describedby.html

Mo: Should we have a project page or github page

Shadi: May be better to keep it in the footer
... Demonstrate the author/person, the source and potential inputs from the group

Survey question 2: ACT sample rules approval to publish https://www.w3.org/2002/09/wbs/93339/ACTTF01FEB/results#xact2

<Wilco> https://www.w3.org/WAI/GL/task-forces/conformance-testing/wiki/Talk:ACT_Review_Process

Shadi: Some comments in the wiki

Stein Erik: Suggesting pushing the item to next meeting

Wilco puts this into a pull request in the ACT-Rules repository

Summary of Action Items

[NEW] ACTION: Wilco: open an issue for discussion on performance statements
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/02/02 08:20:15 $