W3C

Accessibility Conformance Testing Teleconference

22 May 2017

See also: IRC log

Attendees

Present
Chris, MaryJo, Kathy, Romain, Debra, Moe
Regrets
Chair
MaryJoMueller
Scribe
Chris

Contents


Issue 86 - Update Abstract to not focus only on automated test tools - Pull Request 90

<maryjom> https://github.com/w3c/wcag-act/pull/90/files

MaryJo: We will look at changes on update to rules format

Note: General consensus is that changes look good.

Issue 88 - Update Outcomes section "Cannot tell" - Status

<maryjom> https://github.com/w3c/wcag-act/issues/88

MaryJo: Update from Mo will follow later

Getting Draft 2 of the document out the door (Planned for Aug.) - Action items, concerns

MaryJo: There are a couple of notes on accessibility supports and what that means.

<maryjom> https://www.w3.org/TR/act-rules-format/#structure-acc-supp

MaryJo looks to expand on the editor's notes and what accessibility support means. Opens comments on what language is needed

Kathy W: Testing tools look at DOM vs. responsive designs, possible add in language to clarify that.

MaryJo: We talk to that in Test Subject Types section..we could talk to that in Accessibility Support section. Not all UAs render features etc.

Kathy W: with the selector, we may want to have what version of page we are reviewing. Or maybe that is the "context"...

MaryJo: Wilco wanted to have us look at test cases, vs. checks, vs. unit tests. Settle on single term used.

<maryjom> https://www.w3.org/TR/act-rules-format/#test-proc-cases

Kathy W: No preference on which one we choose.

Romain: No preference. Test Case sounds good.

MaryJo: Test case sounds good

Did we want to have this as a resolution?

MaryJo: Prepare to discuss the contents and what is needed on document before we go forward on 2nd draft.

Wilco will be pulling in examples to help better understand the scope.

Version numbers for rules

MaryJo: Opens comments on version number for rules.

Romain: 7.4.1. is based on semantic versioning. Possible further clarification on text within 7.4.1.

<maryjom> https://www.w3.org/TR/act-rules-format/#test-proc-cases

different vs. new failure results. needs clarification on what the differences are ? Which version receives the update?

Minor vs. major updates.

MaryJo: Patch updates...usually if there is a bug within a rule. If you are fixing a bug that affects the rule results. Number it as a major updated rather than a patch. Seems that it could be confusing.

Debra: If new results , then a major update should occur.

<rdeltour> http://semver.org/

Romain: If does add a feature, but in a backwards compatible way, it is a minor update. If it breaking the backwards compatibility, it is a major update. Otherwise it is a patch.

Note: Bring point up on Major , Minor and patch up with Wilco and Shadi next week. I.e. what is considered a patch ?

Publication requirements - Issue #81

<maryjom> https://github.com/w3c/wcag-act/issues/81

Note: Stein Erik, not available. We will talk to this next time.

MaryJo: TPAC https://www.w3.org/2017/11/TPAC/#registration

Book hotels as soon as you can.

Kathy: will follow up with Shadi on planning details of days we will meet.

MaryJo: We will wrap up call today. We will meet next week, even though it is a holiday in U.S.

No problem.

Is the meeting made public?

I tried to generate minutes and got an error.

The title is off on the link, but I'll share to the group

OK. Did you want me to send to the email list?

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2017/05/23 17:05:54 $