18:06:04 <RRSAgent> RRSAgent has joined #aria-at
18:06:04 <RRSAgent> logging to https://www.w3.org/2021/06/17-aria-at-irc
18:06:14 <Zakim> Zakim has joined #aria-at
18:06:17 <jesdaigle> jesdaigle has joined #aria-at
18:06:26 <s3ththompson> zakim, clear agenda
18:06:26 <Zakim> agenda cleared
18:06:40 <s3ththompson> rrsagent, make log public
18:06:55 <s3ththompson> rrsagent, make minutes
18:06:55 <RRSAgent> I have made the request to generate https://www.w3.org/2021/06/17-aria-at-minutes.html s3ththompson
18:07:12 <Matt_King> Matt_King has joined #aria-at
18:08:02 <Matt_King> MEETING: ARIA and Assistive Technologies Community Group
18:08:13 <Matt_King> present+
18:08:21 <s3ththompson> present+
18:08:28 <jesdaigle> present+
18:08:35 <Matt_King> TOPIC: Update on sprint 8
18:09:27 <Matt_King> Seth: Howard and Alex are both in the co-design workshop day 2.
18:10:04 <Matt_King> We didn't get logistics coordinated to get w3c and non-w3c people together at same time.
18:10:21 <Matt_King> We will try this again to get that part coordinated better.
18:10:49 <Matt_King> Current workshop we are learning a lot, but no significant design decisions will be made.
18:11:20 <Matt_King> We'll have a topic on this in CG meeting later in the month.
18:11:38 <Matt_King> About the sprint progress ...
18:11:59 <Matt_King> Progress on fixing merges of test prs
18:12:24 <Matt_King> Merged the new git attributes PR.
18:12:57 <Matt_King> Merged a PR with some tests, and that worked, but there were problems with a script was running on Windows.
18:13:20 <Matt_King> So, we reverted and started working a fix to that script.
18:17:50 <s3ththompson> https://github.com/w3c/aria-at/issues/422
18:18:02 <Matt_King> Discussed support for windows in scripts.
18:18:52 <s3ththompson> https://github.com/w3c/aria-at/pull/446
18:22:37 <Matt_King> We think the PR is now ready; waiting on review from James.
18:22:56 <Matt_King> Howard can help with some of the merging.
18:27:02 <Matt_King> mk: other sprint 8 updates?
18:27:15 <Matt_King> seth: working on test queue
18:28:28 <Matt_King> The conversion to graphQL will for test queue components is starting. Plan to complete by end of sprint.
18:29:14 <Matt_King> We have also tackled the permission issues so we can move away from the github team for testrs.
18:29:28 <Matt_King> We will be able to use our own allow list.
18:30:00 <Matt_King> Open question is how to build the allow list process. where should it live? who should edit, etc?
18:33:57 <tzviya> tzviya has joined #aria-at
18:36:08 <Matt_King> TOPIC: Sprint 9 planning
18:37:54 <Matt_King> Seth: Question is w3c moving away from travis?
18:38:59 <Matt_King> We will work on this in sprint 9.
18:39:58 <Matt_King> Work on changing test run pages to the new graphQL componentry.
18:41:36 <Matt_King> Only user visible change will be using native formrather than iFrames.
19:03:34 <Matt_King> TOPIC: Test Writing Community Group Agenda Starts Here
19:09:25 <Matt_King> TOPIC: Construction of test titles and instruction text -- issue 364
19:10:38 <Matt_King> https://github.com/w3c/aria-at/issues/364
19:11:38 <Matt_King> Test title tends to consist of action direction subject and mode.
19:11:49 <Matt_King> How much detail do we want to include in the title?
19:12:05 <Matt_King> James: some of these get very long
19:12:49 <Matt_King> we're trying to be more concise and not necessarily describe everything about the subject
19:13:18 <Matt_King> so, for example, don't have to say the slider is horizontal
19:18:05 <Matt_King> mk: need to be sure the title is unique within a plan and is sufficient to help people reading reports
19:18:16 <Matt_King> James: but not necessarily across plans
19:18:21 <Matt_King> mk: yes
19:20:21 <Matt_King> mk: need to be consistent in our wording, especially the actions
19:20:44 <Matt_King> James: other aspect is instruction text
19:20:52 <Matt_King> sometimes seems superfluous
19:21:01 <michael_fairchild> michael_fairchild has joined #aria-at
19:21:27 <Matt_King> Often what is in the instructions is conveyed in the title.
19:22:00 <Matt_King> This makes the instructions seem not that helpful.
19:24:53 <Matt_King> mk: in a sense, the insturctions are not just there for testers but also to document what testers have done.
19:30:03 <michael_fairchild> present+
19:30:32 <Matt_King> mk: In future, we may have some test-specific configuration instructions.
19:31:16 <jongund> present+ jongund
19:31:36 <Matt_King> mk: do we have a separate issue for the wording of a text
19:31:49 <Matt_King> s/text/test/
19:32:16 <Matt_King> James: yes, issue 413, we decided to wait to discuss that later.
19:32:47 <Matt_King> TOPIC: Add ability to distinguish between property, role, and state metadata
19:33:15 <Matt_King> https://github.com/w3c/aria-at/issues/345
19:33:47 <Matt_King> james: in test format we havea references file where each row is a role, state, or property
19:34:04 <Matt_King> Then, we use those references in a test.
19:34:23 <Matt_King> There can be multiple spec references for a test.
19:34:53 <Matt_King> This system does not allow us to distinguish between multiple values of a state.
19:35:09 <Matt_King> For instance, true or flase for expanded.
19:35:17 <Matt_King> s/flase/false/
19:35:56 <Matt_King> Then, you can't search for data related to a given state value.
19:36:12 <Matt_King> mf: I think it is important to distingusish between the values
19:37:17 <Matt_King> mk: I want to understand use case for data
19:38:44 <Matt_King> James: When reporting coverage, we need to make sure we cover all values of a property. Just saying we tested aria-live is ambiguous.
19:38:59 <Matt_King> Same for HTML, for instance, which input types have we tested?
19:39:08 <Matt_King> Need to be able to answer these kinds of questions.
19:45:36 <Matt_King> mf: we also need to ensure we report on coverage of value change events
19:47:00 <Matt_King> jes: There was request in last iteration of reports page to be able to facilitate sorting
19:48:52 <Matt_King> James: should we have seprate issue for coverage maps generation
19:49:07 <Matt_King> mk: yes
19:49:47 <Matt_King> James: after we have covered all APG, then we can see what the gaps in coverage are.
19:49:55 <Matt_King> by using a coverage map.
19:54:40 <Matt_King> mk: what is the decision we need to make now?
19:55:56 <Matt_King> James: The implementation decision is either multiple values per row or one row per value
19:56:50 <Matt_King> James: how would you spec this for aria-label?
19:57:05 <Matt_King> mk: do not need to specify value for all properties.
19:57:17 <Matt_King> we would skip for aria-label.
19:57:40 <Matt_King> mk: should be only for booleans and tokens
20:01:14 <Matt_King> Group decision: we want to do this, it is now a matter of deciding implementation. James will make separate issue for that.
20:14:46 <Matt_King> rrsagent, make minutes
20:14:46 <RRSAgent> I have made the request to generate https://www.w3.org/2021/06/17-aria-at-minutes.html Matt_King
20:16:20 <Matt_King> rrsagent, make log public
21:39:24 <jongund_> jongund_ has joined #aria-at