Jean-Yves Moyen

This is supposed to be done by the [link-reference-has-definition test](https://github.com/act-rules/act-rules.github.io/blob/develop/__tests__/link-reference-has-definition.js). I agree I've seen it messed up recently. I think it mostly failed on glossary items. Are we somehow only...

This touches the more global question of "how do we test definitions?" In that case, we have 50 rules who use "visible" and this would maybe need 3-4 cases to...

Let's try to have "rules" for testing definition. Put the rules in a separate directory (not `__rules`). Put the test cases in a separate JSON file. We (ACT rules) will...

I think we only need to test definitions separately when they are broadly used in other rules. So for now mostly the "core concepts" of visibility, and inclusion in the...

I've done most changes. I've also removed the inclusion in the accessibility tree from the Applicability in order to be able to also test `role="presentation"`.

> What is this rule supposed to do with `role="generic"` or with ARIA deprecated roels such as `directory`? According to how this is written I'd say these pass, but different...

@scottaohara Thanks a lot for the feedback. This is a rule designed for ARIA, not WCAG, so it is ultimately up to ARIA group to decide what fails and what...

@giacomo-petri I think this is where I make the difference between ARIA (authoring) error and end user accessibility problem (more or less the same as WCAG violation). It's a bit...

Given the amount of discussion we're having, I think it is safer to take it to the rest of the group on a call. Feel free to continue discussing it...

CG decision: restrict rule to elements in the applicability tree and explicit role of presentation/none (or not in hidden state), add background note that stuff out of the accessibility tree...