18:37:12 <RRSAgent> RRSAgent has joined #aria-at
18:37:12 <RRSAgent> logging to https://www.w3.org/2022/04/07-aria-at-irc
18:37:27 <Zakim> Zakim has joined #aria-at
18:37:44 <Matt_King> MEETING: ARIA and Assistive Technologies Community Group
18:37:55 <Matt_King> CHAIR: Matt King
18:38:06 <Matt_King> present+
18:38:13 <Matt_King> rrsagent, make log public
18:38:22 <Matt_King> rrsagent, make minutes
18:38:22 <RRSAgent> I have made the request to generate https://www.w3.org/2022/04/07-aria-at-minutes.html Matt_King
19:01:09 <Alyssa_G> Alyssa_G has joined #aria-at
19:01:21 <Alyssa_G> present+
19:01:52 <Sam> Sam has joined #aria-at
19:01:56 <Sam> present+
19:02:09 <Matt_King> present+ James
19:02:30 <Rich_Noah> Rich_Noah has joined #aria-at
19:02:33 <Matt_King> TOPIC: Recent and upcoming app changes
19:02:39 <Rich_Noah> present+
19:03:10 <jongunderson> jongunderson has joined #aria-at
19:07:19 <Matt_King> Rich: shipped test plan version updater. Is now in prod as of March 30.
19:07:26 <Matt_King> no reported issues as of today.
19:07:39 <Matt_King> Current work underway is for capturing browser and AT versions.
19:08:47 <Matt_King> May 17 is target date for sandbox and reviews starting on 19th
19:08:54 <Matt_King> prod launch on May 23
19:09:21 <Matt_King> Didn't find a way to deliver in phases
19:09:30 <Matt_King> so it will all come at once
19:17:13 <Matt_King> mk: this is blocker for more testing. How can we continue testing in the meantime.
19:17:42 <Matt_King> Seth: perhaps we can find a way to collect the data offline and then backfill it.
19:20:16 <Matt_King> TOPIC: Screen Reader Developer Engagement
19:31:10 <s3ththompson> s3ththompson has joined #aria-at
19:31:24 <s3ththompson> SCRIBE: s3ththompson
19:32:29 <s3ththompson> Matt King: we're meeting with screen reader vendors to kick off the effort in the next 2 weeks (JAWS/Vispero, Apple) and we'll have the first 8 plans ready for the community group by April 26 and then ready for screen reader vendors in May
19:36:20 <s3ththompson> Matt_King: plan is to have the reports in a state where screen reader vendors can provide feedback with the tools that we have
19:36:53 <s3ththompson> Matt_King: since these are the least contentious 8 plans, we think we might be able to avoid handling a more complex review / reconciliation process
19:36:58 <Matt_King> TOPIC: Screen Reader Dev Journey
19:37:08 <Rich_Noah> scribe: Rich_Noah
19:37:27 <Rich_Noah> TOPIC: Screen Reader Developer User Journey
19:37:45 <s3ththompson> https://github.com/w3c/aria-at-app/issues/409
19:37:57 <Rich_Noah> Matt_King: I would like to make this week about the Developer User Journey and next week the Administrator User Journey
19:38:09 <s3ththompson> https://github.com/w3c/aria-at/wiki/User-Journeys-2022-(Draft)#user-persona-at-developer
19:38:19 <Rich_Noah> s3ththompson: the link goes to the wiki page we have created for these journeys
19:39:05 <Rich_Noah> s3ththompson: 3 scenarios listed and all related to reviewing candidate test plans
19:40:41 <Rich_Noah> Matt_King: I am thinking that in terms of planning app changes I was imaging a Job to be Done.
19:40:56 <Rich_Noah> s3ththompson: I believe we can massage these into that form
19:46:26 <Rich_Noah> Matt_King: A job to be done sounds like "I want to indicate that I have reviewed it". I wonder if we want something similar to GH review.
19:48:30 <Rich_Noah> james: this user journey implies they will file an issue and I don't believe that is the case
19:49:32 <Rich_Noah> Matt_King: you need to know which ones at the test level and not at the test plan level
19:50:16 <Rich_Noah> Matt_King: not at the assertion level
19:50:28 <Rich_Noah> Matt_King: reviewing at a test would be reasonable
19:51:04 <Rich_Noah> Matt_King: 1. Provide Approval 2. Request Changes 3. Have Questions - we want to make it easy to track these
19:51:23 <Rich_Noah> s3ththompson: I agree and can share those with Isaac
19:53:16 <Rich_Noah> Matt_King: we want to know where the bugs are raised and we would capture that information
19:54:29 <Rich_Noah> Matt_King: The trigger to rerun automation should be the release of a new version
19:54:39 <Rich_Noah> Matt_King: success is measured by how the SR developers change and react to it.
19:56:01 <Rich_Noah> s3ththompson: what are the requirements around the process of reading these reports.  The reports page is a better summary of information for someone coming new to the page to view it v. the runner.
19:56:41 <Rich_Noah> Matt_King: I think the reports format is pretty good but I imagine something similar to the queue so they can see a list in their queue.
19:57:35 <Rich_Noah> Matt_King: I think it will have to look something like a to-do list
19:58:06 <Rich_Noah> s3ththompson: we have not talked about authentication, we would obviously want this to be a privileged role
19:58:32 <Rich_Noah> Matt_King: we can assume all SR vendors will have GH accounts
19:59:31 <Rich_Noah> Matt_King: these approvals are more of a project tracking as opposed to a formal approval.  Would want to be careful on how we cast that.
20:01:34 <Rich_Noah> Matt_King: there will be some political sensitivity as the project gains public credibility.  how demanding we can be.
20:02:37 <Rich_Noah> s3ththompson: I will revise this on the issue and I believe Isaac will be amenable to this.  Then process to convert these to a set of requirements.
20:03:11 <Rich_Noah> Matt_King: I think we might have to have a longer workshop.
20:03:13 <Matt_King> rrsagent, make minutes
20:03:13 <RRSAgent> I have made the request to generate https://www.w3.org/2022/04/07-aria-at-minutes.html Matt_King
20:50:45 <Jem> Jem has joined #aria-at
20:50:48 <s3ththompson> s3ththompson has joined #aria-at
20:51:04 <Rich_Noah> Rich_Noah has joined #aria-at
20:51:06 <Travis> Travis has joined #aria-at