W3C

– DRAFT –
Accessibility Conformance Testing Teleconference

22 August 2024

Attendees

Present
Daniel, Helen, kathy, thbrunet, Wilco
Regrets
-
Chair
Wilco
Scribe
kathy

Meeting minutes

Reminder, F2F meeting survey: https://www.w3.org/2002/09/wbs/114156/f2f-2025/

wilco: survey due next week
… looks like it'll be in Europe

Changing meeting time?

wilco: we aren't running TF meetings every week since we have joint CG meetings every other week

daniel: WCAG2ICT meetings conflict

wilco: we are considering moving the TF call to 10am Eastern

daniel: when WCAG2ICT move to maintenance, I can work out alternating meetings

helen: no

tom: easier for me

helen: no conflict for me

daniel: CG chairs had conflict with changing to TF time

wilco: TF doesn't need to meet every week. Hoping that less frequent meetings allow for work to be done
… any concerns with TF just meeting every other week
… let's discuss with CG chairs before final decision

Composite rule applicability

wilco: this came out of new rule for target size
… a lot of complexity and exceptions. Each pass scenario is it's own rule
… exceptions in separate rules

<Wilco> https://github.com/act-rules/act-rules.github.io/pull/2167/files

helen: exceptions should be in a composite

wilco: can atomic rule be used in applicability as an exception to the applicability?
… option 2 is to use a definition of the exception

tom: want to avoid test cases that cause conflicts

wilco: rules format avoids complex relationships between rules
… composite rules can use atomic rules but not other composite rules

tom: worried exceptions are not documented

wilco: this rule adds 2 exceptions to the applicability of 2 rules

tom: separate exceptions as definitions

wilco: definition is complex
… and test cases would need to be duplicated
… in the target size rule, option 1 would move 3 of the 7 rules from expectation to applicability exception
… option 2 the 3 rules that are moved to applicability would be definitions, not rules
… definitions only in composite rule, not atomic rules
… current rules format would repeat the exceptions in every atomic rule

helen: homework needed to identify blockers for the options

tom: atomic rules would need the exceptions noted somewhere
… composite rule exceptions must be in atomic rules?

wilco: currently, yes
… composite rules current inputs are only the results from atomic rules
… current format requires composite and atomic rules to have the same applicability

tom: most concerned that exception in composite are in the atomic

helen: consider wcag3?

kathy: like definitions approach better than rules in the applicability
… lower number of duplicative exception test cases across rules could be managable

<Helen> +1 to the proposition

wilco: propose definition approach to CG

<thbrunet> +1

Minutes manually created (not a transcript), formatted by scribe.perl version 229 (Thu Jul 25 08:38:54 2024 UTC).

Diagnostics

Maybe present: tom

All speakers: daniel, helen, kathy, tom, wilco

Active on IRC: dmontalvo, Helen, kathy, thbrunet, Wilco