jugglinmike

Heads up: I won't be able to review this [until I can run the build script](https://github.com/w3c/aria-at/issues/890).

This branch now conflicts with the target branch. Because this has been open for a while, there's a possibility that the conflicts are substantial, so I'd prefer to wait on...

It looks like I'll need more than "just a moment" to create that event. I hope to post it here within 24 hours.

[Here are the meeting details.](https://www.w3.org/events/meetings/5a773225-a0a0-4443-9e4b-38fcc2a2cf27)

At the end of today's meeting, @mcking65 expressed a desire for AT responses to be collected by a human "at least once." I'd like to nail that down a little...

[The meeting minutes are available on w3.org.](https://www.w3.org/2023/03/20-aria-at-minutes.html) The full IRC log of that discussion <jugglinmike> MEETING: ARIA-AT Community Group Automation Workstream <jugglinmike> present+ jugglinmike <jugglinmike> scribe+ jugglinmike <jugglinmike> Topic: Considering...

@mcking65 as per our conversation on 2023-03-27, I've updated the name of this issue and added a checklist describing the next steps. Does that reflect your understanding of the work...

@mcking65 In addition to the above, I'm wondering if the following change makes sense for the app. Currently, the app includes "unexpected behaviors" in its description of test results. If...

The ARIA and Assistive Technologies Community Group just discussed this issue. [Meeting minutes are available on w3.org](https://www.w3.org/2023/03/30-aria-at-minutes.html#t06) and also included below. The full IRC log of that discussion <jugglinmike> Matt_King:...

The first solution that comes to mind is for Infra to define a macro-like shorthand named "throw if abrupt". It could look something like this: > Algorithms steps that say...