James Craig

Yes. WebKit change will be in https://webkit.org/b/233907 AXRole: AXGroup (already implemented) AXSubrole: AXLandmarkForm (new)

I mispoke on the call. A "hidden" project would include more than just aria-hidden: inert, css visibility, display:none, content-visibility, etc.

…but the issues span across various specs: html (main spec), html-aam, css, aria, accname, etc. I'm not sure we can make a project in the aria repo that cross-references non-aria-spec...

FWIW, I think it's okay to have extended notes and examples in a collapsed `details`. My concern was the buried normative requirement in a collapsed `details`.

We discussed this in the last two meetings, but I wanted to make sure we had a specific tracker for it. This might get incorporated into #220

> Check if PR introduces errant RFC-2119 > Error: The added code should not contain must | must not | shall | shall not | should | should not |...

Perhaps the compromise is in the `assertive` value... ```html Default for aria-live is assertive. ``` Which would account for the default `alert` behavior Dominic wanted ("The exception is `role=alert`.") but...

Yes, @minorninth helped me remember the `alert` exceptionalism is in part due to the alert notifications, separate from other live region types, regardless of their assertiveness. As called out in...

@MelSumner @minorninth @0ddfell0w Draft PR is #2116. Unless you have major feedback, I plan to change it to a non-draft PR before tomorrow's ARIA WG meeting.

Related to #205. I'm going to check in [the WPT test](https://github.com/web-platform-tests/wpt/pull/42407) using the Chrome behavior, since that's what the editors have indicated should happen, even though it's not in the...