<Wilco> clear agenda

<scribe> scribe: kasper

Final call https://github.com/act-rules/act-rules.github.io/issues/461;

<Wilco> https://github.com/act-rules/act-rules.github.io/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+label%3A%22Final+call+1+week%22+

<Wilco> https://github.com/act-rules/act-rules.github.io/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+label%3A%22Final+call+2+weeks%22+

Jean-Yves: Wondering if we should have a generic rule that checks for accessible names of things that can be tabbed to.

Wilco: I don't think. The ARIA working group is pushing back on things needing accessible names. In the future, some things way even be disallowed from having an accessible name.

Reviewers wanted https://github.com/act-rules/act-rules.github.io/issues/462;

Wilco: Should we revisit everything that has "reviewer wanted"?

Jean-Yves: Don't think so.

Jey: One of my PRs need Dagfinn. What should we do now?

Wilco: Can I do it?

Jey: Sure.

Wilco: Anything else?

Jean-Yves: Wilco, if you could take a look at the form field label rule, that would be good.

One element relevant for multiple success criteria https://github.com/act-rules/act-rules.github.io/issues/1049;

<EmmaJ_PR> +present

Wilco: Emma had some question about how we scope our rules. This got started on the image button rule. So one rule maps to one success criteria, and another maps to two success criteria. The initial thinking was to avoid duplicate results where one element would fail two rules for the same reason but for different success criteria.

Jean-Yves: There would be other ways to exclude elements from rules in order to avoid duplicate results. We already do this for certain rules.

Emma: But the different rules are really reporting different things.

<Wilco> https://act-rules.github.io/rules/59796f

Wilco: Not really. They're just reporting on different success criteria.

Emma & Jean-Yves discussing the possibility of using composite rules for buttons/image buttons, but determining that this is not possible due to requiring that a composite rule have the same applicability as its atomic rules.

Wilco: As a CG, we are not required to deduplicate results. Tool developers could deduplicate results themselves.
... What are actionable items here? What do we want to change?

Jean-Yves: Do we want a change or not?

Emma: I think having a separate composite rule makes sense to me.

Jean-Yves: There might be a way.

Emma: The composite rules we have at the moment have the same applicability as their atomic rules?

Wilco: It's required, yes.

Emma: To my mind, that's a legit reason to have a separate atomic rule for image buttons.

Wilco: Do you want to make a proposal, Emma?

Emma: I don't like 1.1.1 being in there as it's not really tested by the rule.

Jean-Yves: I will try to make a proposal that we can discuss.

Add note on difference between accessibility and DOM trees https://github.com/act-rules/act-rules.github.io/issues/1114;

Jean-Yves: This was started based on a comment from Carlos, but it turned out that it might not even solve the original issue.

Carlos: The issue was raised by Brian when validating tools. QualWeb failed something that the other tools were not failing. Apparently, Alfa does fail this as well so it's only Axe that doesn't fail it.

Jey: I'm checking the paths that Brian sent to check if they're correct.

Carlos: So, do we want to change the definition or check if Axe is correct?

<Wilco> https://github.com/w3c/aria/pull/1162/files

Wilco: I need to check if Axe is correctly considering this. I don't think it should be descendants.

<Wilco> https://github.com/act-rules/act-rules.github.io/pull/1114#issuecomment-577063595

Applicability for Button has accessible name is not clear. (97a4e1) https://github.com/act-rules/act-rules.github.io/issues/1061;

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

Wilco: I think it's on the task force to clarify the different parts of the rules format.
... I'll take this one back to the task force.

Rule: "id attribute value is unique" should explain why further testing is needed (3ea0c8) https://github.com/act-rules/act-rules.github.io/issues/1079;

Jean-Yves: That's the same thing.

meta viewport does not prevent zoom [b4f0c3] https://github.com/act-rules/act-rules.github.io/issues/1060;

<Jey> Rule page - https://act-rules.github.io/rules/b4f0c3

Wilco: Let's add a note about accessibility support.

<Wilco> trackbot, end meeting

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
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/They/They're/
Succeeded: s/Do/To/
Default Present: Wilco_, Jean-Yves, Dagfinn, Adil, Jey, kasper, Wilco, carlos, present
Present: Wilco_ Jean-Yves Dagfinn Adil Jey kasper Wilco carlos present
Found Scribe: kasper
Inferring ScribeNick: kasper

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

Found Date: 23 Jan 2020
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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.)