W3C

- DRAFT -

ACT Rules Community Group Teleconference

11 Nov 2021

Attendees

Present
CarlosD, Jean-Yves, Kristian, Helen
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Wilco, CarlosD

Contents


<Wilco_> scribe: Wilco

<Wilco_> Carlos: Delay the presentation, conversation until the next meeting

Defining Implementations: https://github.com/w3c/wcag-act/pull/522/files

<CarlosD> scribe: CarlosD

Wilco_: ACT TF has been discussing a new definition for implementations that would be approved in the ACT rules format

https://github.com/w3c/wcag-act/pull/522/files

Wilco_: This PR defines two metrics
... consistency and coverage
... they are updates to metrics we already have
... There are 3 levels of consistency: complete, partial and minimal
... minimal is for tools that only report on the applicability of a rule
... For a rule to be completely consiste it needs to report on all the success criteria

Jean-Yves: this is specific to WCAG
... we already have rules on ARIA
... how will it handle other standards?

Wilco_: that's a fair point... WCAG has SC to map to, but ARIA doesn't
... Conceptually we seem to agree... the TF also discussed this and supported it
... One other difference is that complete no longer allows untested
... The total coverage checks how much of your results are not cantTell and untested
... The automated coverage checks this for automated checks
... these can be reported using the test mode property in the report
... We're not looking at the difference between semi-automated and manual

<Wilco_> scribe: Wilco

Promoting ACT Rules proposal

Call for review https://github.com/act-rules/act-rules.github.io/issues/461

<Wilco_> Jean-Yves: I just merged mine

<Wilco_> Carlos: No other calls for review

Assigned issues: https://github.com/act-rules/act-rules.github.io/issues?page=1&q=is%3Aissue+is%3Aopen

<Wilco_> Carlos: Some progress on aria-hidden thanks to Wilco

<Wilco_> ... Will try to address feedback next week.

<Wilco_> JY: No progress on my side

<Wilco_> Helen: Need to commit a few more suggestions on 1729, should be ready then

<Wilco_> Wilco: Working on 1738, thank you for reviews

Update from the ACT Task Force https://github.com/w3c/wcag-act/pull/522/files

<scribe> scribe: CarlosD

<Wilco_> Element with lang attribute has valid language tag

Wilco_: 6 rules are going for approval

<Wilco_> Form field has non-empty accessible name

<Wilco_> autocomplete attribute has valid value

<Wilco_> Element marked as decorative is not exposed

<Wilco_> Word/Letter spacing in style attributes is not !important

Wilco_: we're getting approval to update all the published rules
... we're slightly late for the update of valid language definition

<Wilco_> scribe: Wilco

<Wilco_> Carlos: Has the common input aspects been approved?

<Wilco_> Wilco: This is also on the AG survey for next week

Collision between hidden and display: none https://github.com/act-rules/act-rules.github.io/issues/1698

<Wilco_> JY: We have a definition of hidden state, it is hidden if it has the hidden attribute, or if it has display:none

<Wilco_> ... The problem is the hidden attribute is implemented with display:none, which mean you can override it with CSS.

<Wilco_> .. haven't tested with AT, but this is a situation where I'm not sure what to do. Something can have the hidden attribute but still be visible.

<Wilco_> JY: HTML AAM seems to account for it by making hidden conditional to its display not being changed.

<Wilco_> ... Some new user agent doing this different is unlikely. I'm not sure it is a problem we need to consider.

<Wilco_> Carlos: If there's a user agent that starts doing this we can handle that.

<Wilco_> ... I think the assumption would be enough.

<Wilco_> Wilco: Suggest remove the hidden attribute from the definition, and add a note about it

<Wilco_> ... That way we don't have to add an assumption to lots of rules.

<Wilco_> JY: HTML has a description of this, we can remove the hidden attribute and link to the HTML spec

<Wilco_> Helen: Whenever I have things that follow the spec, it should be a pass

<Wilco_> JY: It's not a normative part of the spec. W3C suggests you do it some way, but allows you to do it another way.

Final thoughts

<Wilco_> Helen: Sorted merge conflicts out, please review my PR

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: 2021/11/11 16:03:11 $

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)

Succeeded: s/ACT has been/ACT TF has been/
Succeeded: s/coverage/total coverage/
Default Present: CarlosD, Jean-Yves, Kristian, Helen
Present: CarlosD, Jean-Yves, Kristian, Helen
Found Scribe: Wilco
Found Scribe: CarlosD
Inferring ScribeNick: CarlosD
Found Scribe: Wilco
Found Scribe: CarlosD
Inferring ScribeNick: CarlosD
Found Scribe: Wilco
Scribes: Wilco, CarlosD

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]