Jean-Yves Moyen

For now, we do a case-by-case decision of whether secondary requirements are included or not, with only one kind of requirement internally. Parking this issue and we'll revisit later if...

Yes, all interactive content should be considered for spacing (main use case: touchscreen with low granularity where the contact point might cover more than one element).

Other cases of "boundary examples" would typically be for [Image has non-empty accessible name](https://www.w3.org/WAI/standards-guidelines/act/rules/23a2a8/) (or similar rules) to have an example with a non-descriptive name (`img src="/test-assets/shared/w3c-logo.png" alt="foo" />`), showing...

It hasn't been discussed yet 🙂 I think I'll make a draft PR at some point to have something concrete to talk about (I don't think it requires a change...

Note: modals that are opened (`showModal`) also make the rest of the content inert, which is going to be a bit annoying to handle.

!pr extract

Decision: add an Accessibility Support note to every rule using "Accessibility tree" as input aspect, stating that "`aria-busy` exists but isn't widely supported (JAWS only, currently, it seems), so the...

@tombrunet I think nothing is blocking us from doing it, but we probably want to have some (internal) guidelines on how to do it both on the syntactical level (sublist,...

Decision: let's try this. Start with making the changes in a few rules, and gather data how it looks. See how it goes and whether we can figure out some...

Yes, the example is here to show that the rule does not care about nested documents, only the top-level ones. OTOH, since it is not a `srcdoc`, it seems that...