18:56:22 <RRSAgent> RRSAgent has joined #aria-at
18:56:22 <RRSAgent> logging to https://www.w3.org/2022/04/14-aria-at-irc
18:56:41 <Zakim> Zakim has joined #aria-at
18:56:52 <Matt_King> rrsagent, make log public
18:57:16 <Matt_King> MEETING: ARIA and Assistive Technologies Community Group
18:57:27 <Matt_King> CHAIR: Matt King
18:57:31 <Matt_King> present+
18:57:36 <Matt_King> rrsagent, make minutes
18:57:36 <RRSAgent> I have made the request to generate https://www.w3.org/2022/04/14-aria-at-minutes.html Matt_King
19:00:47 <Sam_PAC> Sam_PAC has joined #aria-at
19:00:51 <Sam_PAC> Present+
19:04:06 <michael_fairchild> michael_fairchild has joined #aria-at
19:05:10 <Alyssa_G> Alyssa_G has joined #aria-at
19:05:13 <Alyssa_G> present+
19:08:54 <Matt_King> TOPIC: Update on meetings with screen reader developers
19:09:24 <Rich_Noah> Rich_Noah has joined #aria-at
19:09:30 <michael_fairchild> present+
19:09:31 <Matt_King> present+
19:09:34 <Rich_Noah> present+
19:09:39 <Matt_King> present+ James
19:09:53 <Rich_Noah> Jes present+
19:10:07 <Matt_King> scribe: sam_PAC
19:10:17 <Sam_PAC> Agenda Item 1 Update on Planning for Meeting with Screen Reader Developers
19:10:39 <Sam_PAC> Meeting with Apple tomorrow April 15th
19:10:49 <Sam_PAC> Meeting with Vispero on April 22nd
19:11:55 <Sam_PAC> The primary goal for these meetings it to figure our logistics around collaborating, identify Point of contacts at each company, review project timeline and goals
19:13:58 <Matt_King> TOPIC: May test running plans
19:15:21 <Sam_PAC> Each test phase will last 180 days
19:16:26 <Sam_PAC> We plan to start testing the 8 Recommended test plans in May
19:17:09 <Sam_PAC> We will need to manually track AT and Broswer Version.
19:19:04 <Sam_PAC> Seth and Rich plan to manually input the AT and Browser version data at a later date
19:20:10 <Sam_PAC> We need to define a place for testers to manually enter their AT and Broswer version
19:21:18 <Sam_PAC> Both PAC and Bocoup will provide someone to run tests
19:22:27 <Sam_PAC> We will need to be careful to track if a browser updates while someone is performing test
19:22:54 <Sam_PAC> We may be able to utilize the browser release schedule to infer this information
19:23:52 <Sam_PAC> Some companies, like Meta, control the browser update process for the machines they manage
19:24:53 <Sam_PAC> There are 140 tests in total
19:28:45 <Sam_PAC> Test plans vary in size, some are small with 3 tests, some are larger up to 26 test
19:31:18 <Sam_PAC> We will need to ask the AT Developers how many versions of the AT they want to consider results for
19:32:48 <Sam_PAC> We will need two testers on each screen reader
19:33:24 <Sam_PAC> The preference would be to have each PAC and Bocoup perform all tests with each screen reader
19:34:25 <Sam_PAC> PAC will ask Apple tomorrow if they can provide anyone to run tests
19:35:31 <Sam_PAC> Seth asked about the 180 day duration of a test plan, and where this came from
19:35:55 <Sam_PAC> James stated there is a minimum of a 120 day duration for a test
19:37:22 <Sam_PAC> Matt said these durations were what felt right to when our collective team define the working mode. The working mode is a draft and open to change
19:38:36 <Sam_PAC> Open questions: Can Louis test with a Mac?
19:39:32 <Sam_PAC> We want to start testing asap, we will be ready to begin testing April 21st
19:40:08 <Sam_PAC> However to begin testing, we need a way to track to AT and Broswer version info
19:40:42 <Sam_PAC> Alyssa said she can commit to some testing at the end of April and in May
19:40:56 <Sam_PAC> PAC will provide a tester
19:42:27 <Sam_PAC> Matt stated it would be great it the test runner software could time the duration of a test
19:43:08 <Sam_PAC> In the next week, Seth, Rich, and Bocoup will get back to the group with an answer on if they can provide a tester
19:43:28 <Sam_PAC> In the next community group meeting we will define which tests are assigned to who
19:43:54 <Sam_PAC> Seth asked - Do we want to do any cleanup on the test queue as it is?
19:44:27 <Sam_PAC> Matt - Yes, lets make Test Queue Cleanup a topic for next meeting
19:45:32 <Sam_PAC> Matt asked if the Update test button appears only if there is an update available for that test?
19:45:55 <Sam_PAC> Seth - No the button appears if there are any updates available for all test plans
19:46:51 <Sam_PAC> Seth mentioned that if there are updates to Test plan instructions, now would be a good time to apply those updates
19:47:05 <Sam_PAC> James stated yes this work is in progress
19:47:58 <Sam_PAC> PAC has been updating the 8 recommended test plans, and will update the 16 candidate test plans in May
19:48:31 <Sam_PAC> Matt stated that these tests are all still in a draft form
19:51:05 <Matt_King> TOPIC: user journeys for the next set of app changes
19:51:18 <Matt_King> https://github.com/w3c/aria-at/wiki/User-Journeys-2022-(Draft)#user-persona-at-developer
19:52:14 <Sam_PAC> Matt asked Bocoup, what is the timeline to incorporate Community Group feedback into these user journeys?
19:52:59 <Sam_PAC> Seth Bocoup will implement feedback in two weeks, next week Bocoup is away at an all hands meeting
19:57:07 <Sam_PAC> Everyone agreed to continue this discussion in future community group meetings
20:01:01 <Matt_King> rrsagent, make minutes
20:01:01 <RRSAgent> I have made the request to generate https://www.w3.org/2022/04/14-aria-at-minutes.html Matt_King
21:47:48 <Matt_King> Matt_King has joined #aria-at