Jean-Yves Moyen

We went for enriching the data type with external layout information that is provided by the various entry points. This seems to have closed most of the problems described here....

Decision: * we need "implicitly set" and "explicitly set" definitions. * "required state" rule should accept implicitly set states (i.e., this example is good, there is no author error) *...

Automated the full change at website generation time: https://github.com/act-rules/act-tools/pull/22.

Closed by #1923

The ACT rule format is moving toward having secondary requirements, which would be a better way to handle this kind of cases. Closing this.

ARIA PR that removed the requirement for `aria-controls` on `combobox`: https://github.com/w3c/aria/pull/1335 I think we should follow suit, even if it's only in ARIA 1.3, because the authoring practice say so....

Decision: the rules should be about case-insensitive comparison (as per spec), plus AS note that some UA/AT combinations don't respect this, so there is no examples of case insensitive values...

Looks like both `content-visibility` and `hidden="until-found"` have poor browser support for now. Parking these to revisit later.

For gifs and `alt`, I think this is covered by allowing the alternative to **not** be visible (whether it's a `sr-only` text or an `alt` attribute is pretty much the...

They are both instances of "Presentational conflict is not triggered". With the presentational conflict moving toward being an author error (in the ARIA 1.3 draft, [Presentational Roles Conflict Resolution](https://w3c.github.io/aria/#conflict_resolution_presentation_none) is...