18:47:08 <RRSAgent> RRSAgent has joined #aria-at
18:47:08 <RRSAgent> logging to https://www.w3.org/2022/07/28-aria-at-irc
18:47:21 <Zakim> Zakim has joined #aria-at
18:47:47 <Matt_King> MEETING: ARIA and Assistive Technologies Community Group
18:47:57 <Matt_King> CHAIR: Matt King
18:48:06 <Matt_King> rrsagent, make log public
18:48:20 <Matt_King> rrsagent, make minutes
18:48:20 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/28-aria-at-minutes.html Matt_King
19:05:12 <michael_fairchild> michael_fairchild has joined #aria-at
19:06:40 <Matt_King> TOPIC: Status of app performance issues
19:07:20 <Alyssa_G> Alyssa_G has joined #aria-at
19:07:22 <Alyssa_G> present+
19:07:25 <michael_fairchild> present+
19:07:29 <Matt_King> present+ James_Schoels
19:08:44 <Matt_King> rich: over last 3 weeks have made several iterative updates to app to improve page loads.
19:09:09 <Matt_King> currently averaging 15 to 22 seconds in test queue
19:10:40 <Matt_King> PR 441 and 448 coming next week for query per improvements
19:11:01 <Matt_King> Should bring some additional improvements
19:11:41 <Rich_Noah> Rich_Noah has joined #aria-at
19:11:42 <Matt_King> The gains are difficult to predict because local and server environments are so different, and staging is different from prod.
19:12:01 <Rich_Noah> present+
19:12:05 <Matt_King> Seth: We are not sure why staging and prod are so different today.
19:14:54 <Matt_King> TOPIC: Status of collaboration with screen reader developers on first 8 plans
19:16:05 <Matt_King> James: We created 16 issues on GitHub; 8 for Visper and 8 for Apple
19:16:28 <Matt_King> Vendors have acknowledged receipt of links to issues.
19:16:45 <Matt_King> Apple has shared some feedback on toggle button plan.
19:17:00 <Matt_King> That will be a futre agenda item.
19:19:49 <Matt_King> TOPIC: Progress on preparing next 16 tests for candidate review
19:22:55 <joeHumbert> joeHumbert has joined #aria-at
19:24:43 <Matt_King> Matt: we want to complete testing on 16 more examples before mid november
19:25:06 <Matt_King> James: 6 of 16 could be ready as soon as next week
19:25:25 <Matt_King> the next 10 are in triage now
19:30:47 <Matt_King> Joe: Do I still need to retest that one test I didn't finish for modal
19:30:58 <Matt_King> James: No, we were able to move that along
19:31:20 <Matt_King> Joes: I've done testing for some of these, do we need to retest them?
19:31:28 <Matt_King> James: Yes, we have changed some of the plans
19:31:54 <Matt_King> Joe: When I was testing last time, some of the version detection was not correct
19:32:04 <Matt_King> Seth: was it in the minor version
19:32:41 <Matt_King> James: was it for browser or screen reader
19:32:50 <Matt_King> Joe: I think screen reader:
19:33:16 <Matt_King> Matt: We are not auto-detecting screen reader versions; that is manually generated data for the dropdowns
19:33:39 <Matt_King> James: we will make sure those lists are updated to most recent and placeholder values are removed
19:34:07 <Matt_King> Joe: How will conflicts resolved; I was not involved in some of that resolution last time.
19:35:43 <Matt_King> James:  We were able to resolve some of them by reproducing results  that matched what you sproduced.
19:36:16 <Matt_King> all: discussion of how conflict resolutions should be discussed and coumented in GitHub.
19:37:28 <Matt_King> TOPIC: App design for Candidate Review Experience
19:38:03 <Matt_King> Seth: Since last meeting, we updated the github issue
19:38:28 <s3ththompson> s3ththompson has joined #aria-at
19:38:35 <s3ththompson> present+
19:38:35 <s3ththompson> https://github.com/w3c/aria-at-app/issues/437
19:38:52 <s3ththompson> Latest feedback from Matt: https://github.com/w3c/aria-at-app/issues/437#issuecomment-1197687829
19:39:09 <Matt_King> Matt: I commented on the issue last night
19:39:33 <Matt_King> Seth: On monday we posted a summary of structural changes
19:39:54 <Matt_King> Part is hierarchy of how plans are displayed; organizing it by AT
19:40:14 <Matt_King> Also revisiting the view we use for reviewing the content
19:40:34 <Matt_King> Was previously like report page but now more like test runner, with one page per test
19:41:07 <Matt_King> We proposed it would be more like the test run page with instructions and link to open test page and output presented as assertions
19:44:20 <s3ththompson> SCRIBE: s3ththompson
19:44:58 <s3ththompson> Matt_King: top concern was around nomenclature, e.g. saying a plan has "open issues". you're not going to know if that was an issue for your screen reader or with the plan itself, etc.
19:46:54 <s3ththompson> Matt_King: the other thing was clearing up "status". i think we want to use that there's a status for the entire test plan, and not use that language at all when we get to the test granularity.
19:49:12 <s3ththompson> Matt_King: one process change came about: if vispero asks for a change, i don't think test should move back to draft. it should simply show up in test queue to make changes / results, but still be visible in candidate view
19:54:20 <s3ththompson> Matt_King: on candidate test page, i saw 2 gaps in design: 1) we should have some additional information in the table about results / target date for exiting candidate test page, 2) we shoudl add an additional summary table that shows status for each AT for each test plan
20:10:23 <Matt_King> rrsagent, make minutes
20:10:23 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/28-aria-at-minutes.html Matt_King
20:14:54 <Matt_King_> Matt_King_ has joined #aria-at
20:19:26 <Matt_King_> present+
20:20:25 <Matt_King_> scribe: matt_king
20:21:04 <Matt_King> All: discussion of process for when candidate test plans change and the consequences on the UX
20:22:01 <Matt_King> Currently, a test plan shows up in only one place in the app; test queue or candidate review or reports
20:22:14 <Matt_King> this does not necessarily match the needs of the working mode
20:23:07 <Matt_King> For example, plans that are recommended need testing to be run when new versions of AT and browsers are released, that work needs to show in test queue.
20:23:36 <Matt_King> Discussion of centering pages around users, e.g., tester, at dev, public
20:25:07 <Matt_King> seth: We need to design this wholisticly. we should make sure we understand the implications before going too far down the path of implementation of the canditate test review UI.
20:25:32 <Matt_King> Matt: I will own scheduling a workshop for this sometime in the next 2 weeks
20:25:48 <Matt_King> rrsagent, make minutes
20:25:48 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/28-aria-at-minutes.html Matt_King
23:35:00 <Matt_King> Matt_King has joined #aria-at