19:54:36 <RRSAgent> RRSAgent has joined #aria-at
19:54:36 <RRSAgent> logging to https://www.w3.org/2021/03/11-aria-at-irc
19:54:54 <Matt_King> MEETING: ARIA and Assistive Technologies Community Group
19:55:06 <Matt_King> CHAIR: James Schoels
19:55:16 <Matt_King> rrsagent, make log public
19:55:23 <Matt_King> present+
19:55:30 <Matt_King> rrsagent, make minutes
19:55:30 <RRSAgent> I have made the request to generate https://www.w3.org/2021/03/11-aria-at-minutes.html Matt_King
19:55:55 <Matt_King> zakim, clear agenda
19:55:55 <Zakim> agenda cleared
20:02:56 <jongund> jongund has joined #aria-at
20:09:47 <Matt_King> TOPIC: Test planning - issue 385
20:09:51 <Matt_King> https://github.com/w3c/aria-at/issues/385
20:11:23 <Matt_King> james: we are rapidly through the patterns we decided on last time and some have changes coming.
20:11:38 <Matt_King> we'd like a progress update b/c we may need to change the plan
20:11:45 <Matt_King> just to keep momentum going.
20:12:48 <Matt_King> Spin button toolbar, and sliders
20:12:58 <Matt_King> which ones need updating in APG.
20:13:28 <Matt_King> jg? we are working on sliders now
20:13:50 <Matt_King> mk: we merged horizontal slider last week
20:14:20 <Matt_King> James: what about other sliders
20:15:08 <Matt_King> mk: the thermostat slider coming next week
20:15:25 <Matt_King> jg: updates are done and ready for reivew
20:15:38 <Matt_King> James: that leaves tree
20:16:31 <Matt_King> mk: nav tree is stable, the other 2 trees we are still planning what to do
20:16:59 <Matt_King> james: ok, we can check back on that in a couple weeks and then decide if we need to update plan
20:18:13 <Matt_King> TOPIC: Tracking status of tests -- issue 300
20:18:18 <Matt_King> https://github.com/w3c/aria-at/issues/300
20:18:49 <Matt_King> James: we started this discussion last week, matt riased issue that this may not be as simple as keeping track of a binary state
20:19:33 <Matt_King> mk: what is the life cycle of a test plan. When we first merge, we can mark draft
20:27:04 <Matt_King> Discussion of AT release timing and versions and how that can impact the process.
20:29:33 <Matt_King> mk: process is something like cg makes draft test, then agrees read for AT dev review, then test is reviewed and agreed as ready to be mark final
20:32:49 <Matt_King> mk: stages could be: draft, ready for wide review, final
20:33:14 <Matt_King> james: thsi raises question of what happens when AT vendor disagrees with a test during the wide review window
20:33:31 <Matt_King> mk: the wide review window proposal is 120 days
20:34:06 <Matt_King> james: let's say that near end of wide review window, sr developtells about several problems, what do we do?
20:36:06 <Matt_King> Sina: maybe first 60 days of wide review is for raising issues, then 60 days emain for fixing issues
20:36:21 <Matt_King> james: so we always have at least 60 days to fix issues
20:37:45 <Matt_King> hadi: How do we have regular conversation with AT vendors to include them in the process and give us real time feedback instead of batching it all up. Are they onboard?
20:39:32 <Matt_King> mk: We have been keeping them up to date, but have not had a lot of content for them to chew on.
20:39:58 <Matt_King> James: we can have it in real time, but having deadlines is important to keep the project moving.
20:44:08 <Matt_King> James: are we going to target during test runs for every public release of an AT
20:50:47 <Matt_King> next step: work out what needs to change in working mode and james will post in comment in issue 300.
20:51:26 <Matt_King> TOPIC: Revisiting command sequences - issue 363
20:51:28 <Matt_King> https://github.com/w3c/aria-at/issues/300
20:52:01 <Matt_King> James: we d3ecided we do not want open-ended sequences. we will always have exact number of key presses.
20:52:12 <Matt_King> Worked out syntax in the issue.
20:52:34 <Matt_King> we did not talk about commands that need to be done in a certain time frame, like typeahead in a combobox
20:52:57 <Matt_King> e.g., type :"ap" to get to apple in the combobox listbox
20:53:14 <Matt_King> These two letters would need to be typed quickly.
20:53:37 <Matt_King> That could be like testing the example, not the assistive tech.
20:54:02 <Matt_King> Sina: that could depend on where the ARIA plays a role in the experience
20:55:13 <Matt_King> It doesn't seem like this is an AT function, it is an function of the example being tested
20:59:08 <Matt_King> mk: maybe punt
20:59:17 <Matt_King> sina: +1, we can do this later
20:59:44 <Matt_King> mk: Propose that this would be a single "type string" command, e.g., "type("ap");\
21:00:00 <Matt_King> rrsagent, make minutes
21:00:00 <RRSAgent> I have made the request to generate https://www.w3.org/2021/03/11-aria-at-minutes.html Matt_King