W3C

- DRAFT -

Accessibility Conformance Testing Teleconference

09 Apr 2026

Attendees

Present
Kathy, giacomo-petri, Jean-Yves
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Kathy

Contents


scribe+

standup

giacomo-petri: wcag3 topic, verify consistency through page views requires a broader scope. Applicability is challenging

kathy: in a recent rule review, it had applicability to content and examples of pages which I didn't think were correct. my subgroup also has difficulty with terminology

shunguo: working on interactive subgroup, going pretty well

jean-yves: looking at rule sound not relied upon. not sure generic rules will work in the end.
... they are getting used to ACT

shunguo: rule is very composite. a good start

jean-yves: maybe they picked a rule that is too difficult to start with.
... not specific enough, what does it mean
... think it will improve

shunguo: suggested use ACT rules to replace their examples
... if ACT can be part of WCAG spec, it's a good sign

kathy: technical language seems to be a challenge for all subgroups

jean-yves: having examples would help
... if applicability and expectation are too technical, we as liaisons can ask questions to help get them to reduce ambiguity
... rules are for a technical audience

giacomo-petri: need clarifications or it will be too generic

shunguo: I try to push that wcag requirement is clear as possible, list exceptions so ACT rule can be followed strictly
... if requirement has issues then bigger problem

godwin: my subgroup has technical folks but are still struggling with ACT

why isn't ACT writing the rules

kathy: the scag 3 requirements are still in draft and the ACT rule writing has helped my subgroup refine the requirement

giacomo-petri: applying ACT rules is helpful to refine and understand severity, principles and requirements

godwin: agree, but seeing the group struggle with ACT structure

giacomo-petri: maybe start with creating examples, agree to pass and fail
... demonstrate the feasibility of the requirement to move forward

godwin: will this content be moved to ACT?

giacomo-petri: it could be

https://docs.google.com/document/d/1i_O5J7D4BWMZAB7NaD4iplDRuqOjCvCGAaHdAirLUhE/edit?tab=t.bo2e33svugxv#heading=h.8k3m19m21u2

<giacomo-petri> https://github.com/w3c/wcag3/wiki

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.200 (CVS log)
$Date: 2026/04/09 15:03:01 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: Kathy, giacomo-petri, Jean-Yves
Present: Kathy, giacomo-petri, Jean-Yves
No ScribeNick specified.  Guessing ScribeNick: Kathy
Inferring Scribes: Kathy

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]
This is scribe.perl Revision VERSION of 2020-12-31 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Default Present: Kathy, giacomo-petri, Jean-Yves Present: Kathy, giacomo-petri, Jean-Yves No ScribeNick specified. Guessing ScribeNick: Kathy Inferring Scribes: Kathy WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.) line 157 column 1 - Warning: trimming empty <ol> Info: Document content looks like HTML Proprietary Tidy found 1 warning and 0 errors! One or more empty elements were present in the source document but dropped on output. If these elements are necessary or you don't want this behavior, then consider setting the option "drop-empty-elements" to no. About HTML Tidy: http