19:02:13 <RRSAgent> RRSAgent has joined #aria-at
19:02:13 <RRSAgent> logging to https://www.w3.org/2022/09/29-aria-at-irc
19:02:23 <Matt_King_> rrsagent, make log public
19:02:44 <Matt_King_> MEETING: ARIA and Assistive Technologies Community Group
19:02:50 <Matt_King_> CHAIR: Matt King
19:02:55 <Matt_King_> present+
19:03:01 <Matt_King_> rrsagent, make minutes
19:03:01 <RRSAgent> I have made the request to generate https://www.w3.org/2022/09/29-aria-at-minutes.html Matt_King_
19:04:47 <Sam_PAC> Sam_PAC has joined #aria-at
19:06:24 <michael_fairchild> michael_fairchild has joined #aria-at
19:09:53 <Matt_King_> TOPIC: App Development Update: Candidate Review queue
19:10:38 <Matt_King_> Seth: Erica almost ready for review on the PR to add the CR queue
19:10:54 <Matt_King_> Howard now focusing fully on performance.
19:11:21 <Matt_King_> Identified a few issues, added comment on issue raised by James Criag.
19:11:39 <Matt_King_> App hitting a memory limit, which may opena conversation about the hosting environment.
19:11:58 <Matt_King_> Parsing error is a side effect due to timing/out of memory.
19:12:17 <Matt_King_> App is currently getting 1G of RAM.
19:12:25 <Matt_King_> Pretty low for a prod app.
19:12:37 <Matt_King_> Going to see if we can get limit raised.
19:12:50 <Matt_King_> We are also looking at mitigations in code.
19:13:17 <Matt_King_> Looking at performing some of the more intensive calculations off line.
19:13:33 <Matt_King_> Bocoup realizes it is preventing work.
19:14:09 <Matt_King_> James: Wonder if we want to host the app elsewhere.
19:14:19 <Matt_King_> Get cloud vendor sponsor.
19:14:51 <Matt_King_> Seth: Might be reaching point where w3c infra is potentially not sufficient.
19:15:00 <Matt_King_> Might be a good idea.
19:23:11 <Matt_King_> James: should we hold off on people running more tests.
19:23:31 <Matt_King_> Seth: I don't think there is a risk of losing data.
19:24:00 <Matt_King_> It still might be a good idea to hold off.
19:24:21 <Matt_King_> James: the only left in the queue is checkbox, but have not emailed Lewis about it yet.
19:25:29 <Matt_King_> Matt: how does this impact the QR queue deployment.
19:26:00 <Matt_King_> Seth: still expect new CR Review queue in sandbox at end of next week.
19:26:09 <Matt_King_> That is by October 7.
19:26:35 <Matt_King_> Matt: will need reviewers of new experience during week of October 10.
19:26:59 <Matt_King_> TOPIC: Mode switching tests
19:27:48 <Sam_PAC> SCRIBE+
19:28:49 <Sam_PAC> We are going to look at a Combo box example with Default NVDA settings
19:30:23 <Matt_King_> Discussing mode switching for this example: https://www.w3.org/WAI/ARIA/apg/example-index/combobox/combobox-autocomplete-both.html
19:31:39 <Sam_PAC> To start we want to review navigating to a combo box
19:33:14 <Sam_PAC> The issue we face is so far all of the asserted behavior has been the same. The assertions are all inserted on a per test basis, instead of per assertion
19:37:18 <Sam_PAC> Matt: Instead of incorporating this into the test navigating forward or backward to a combo box, we could have another test, potentially called  activate a combo box. I had an idea to separate this test from navigation test, and the only assertion was did the mode switch?
19:38:21 <Sam_PAC> James: Before we go on to that, we should discuss as the tests are written, even if we remove c, f, and tab because we are going to remove those separately, would that change current tests?
19:39:20 <Sam_PAC> Matt: No, the current tests would stay the same, you just wouldn't added new assertions to them. Then have a new test with a certain set of commands to change more or not
19:41:54 <Sam_PAC> James: If we have tests that only test when the mode should change, that feels unbalanced. We should have tests with assertions for cases when the mode should stay the same, and tests with assertions for one the mode should change
19:44:41 <Sam_PAC> Matt: The fundamental thing that would be helpful would be to have different assertions for different commands within the same test, which is not currently possible and would be a nightmare to implement
19:45:11 <Sam_PAC> James: We would have to overhaul the experience and make it backward compatible
19:45:34 <Sam_PAC> Matt: The other option is to have more tests for each example of mode switching
19:45:51 <Sam_PAC> James: Already the test plans names are getting pretty long
19:46:48 <Sam_PAC> Matt: We have to think about the fact that humans and machines will have read these longs strings
19:47:35 <Sam_PAC> James: These test names appear in multiple places, so that increases the time to read and might eventually become lost within the context
19:48:08 <Sam_PAC> If we remove the state from the test name, that would result in 12 tests with the same name
19:51:35 <Sam_PAC> Matt: We could change the test plan names to include "with automated change to interaction mode" or "in reading mode" or "Without interaction mode change"
19:52:19 <Sam_PAC> James: I would prefer to keep "in reading mode" suffix, with mode switching commands
19:52:37 <Sam_PAC> James: To keep the test names following a similar format
19:53:09 <Sam_PAC> James: we have some automation for creating these names, so from a work flow perspective to would easier to change the task name, than change the entire ending
20:01:34 <Sam_PAC> We had a discussion of the scope of tests, testing for known bugs in mode changes vs testing unknown bugs. This will need more discussion
20:02:27 <Sam_PAC> Matt: I feel this is too important of thing to not test
20:02:44 <Sam_PAC> James: I will work on creating some examples for Combo box
20:02:53 <Sam_PAC> Matt: Grid is another important one to tes
20:03:23 <Matt_King_> rrsagent, make minutes
20:03:23 <RRSAgent> I have made the request to generate https://www.w3.org/2022/09/29-aria-at-minutes.html Matt_King_
22:20:33 <jongund> jongund has joined #aria-at