20:01:49 RRSAgent has joined #aria-at 20:01:49 logging to https://www.w3.org/2022/12/15-aria-at-irc 20:02:11 MEETING: ARIA and Assistive Technologies Community Group 20:02:28 CHAIR: Matt King 20:02:34 present+ 20:02:39 rrsagent, make log public 20:02:48 rrsagent, make minutes 20:02:48 I have made the request to generate https://www.w3.org/2022/12/15-aria-at-minutes.html Matt_King 20:05:00 present+ James 20:09:08 TOPIC: Closing out testing of plans for APG support tables 20:09:31 Michael: Get email about Dillon helping with testing 20:09:43 James: dillon has done some sample testing. 20:09:58 MJ also expressed interest 20:10:22 Michael: MJ moved jobs outside Deque but may investigate how to continue working with project 20:10:42 James: PAC closes tomorrow, matt can you you do some admin next week? 20:11:05 scribe+ 20:11:39 Matt: Yes I can, Tuesday through Thursday of next week I can work on this project 20:12:04 Present+ Howard 20:12:20 Present+ Michael Fairchild 20:12:30 Present+ Seth 20:13:19 Matt: Link and Command Button would be the two we can use JAWS 2022 results and put them in a APG table 20:13:43 Matt: Those should be ready to publish by EOD tomorrow 20:14:08 Matt: We will also update results for Toggle button and Alert, for Voiceover and NVDA 20:14:46 Matt: Alyassa and Myself, maybe Louis can work on testing Alert, Toggle Button, and Radio Group for Jaws 2022 20:15:09 Matt: We can test those three next week 20:15:35 James: The only testing that is incomplete is radio group on iOS, which could be that Louis hasn't gotten to it, I can send an email. 20:15:53 James: There are a couple of conflicts we will deal with tomorrow, then it should be in a clean state 20:16:07 Matt: Lets look at the Queue now 20:16:57 Matt: Are there any conflicts in link or command button? 20:17:22 James: No there are no conflicts in either of those 20:19:47 Matt: Alyssa thank for completing your testing, and there are no conflicts there 20:19:59 Matt: Alert for NVDA is also complete 20:20:47 Matt: For Voiceover, no conflicts for alert thats ready to go, for command button there is no conflicts and its complete, and link that has no conflicts. 20:21:25 Matt_King: When JAWS update comes out, Alyssa, Louis and I need to test Alert, Command Button, and Link 20:21:44 Matt_King: So for sure, we are well positioned for button and link, everything is done. 20:21:56 Matt_King: We could also do alert if we can get two people to test next week 20:22:04 Matt_King: Alyssa can you help testing? 20:22:25 Alyssa: No next week I am unavailable next week, but I am available the week of the 26th 20:22:50 James: Please be sure to use JAWS 2023 20:23:02 Matt_King: Seth can Louis help out testing JAWS next week? 20:23:34 Seth: I think he was waiting to see when the new release came out to scheudle the work. I think I just need to have that conversation with him now that we know when that will be 20:24:03 Matt_King: Link and Alert button don't require much testing, so if he could focus on those two first that would be great. 20:24:33 Matt_King: The JAWS December release should be early next week, probably Tuesday 20:25:02 James: For Louis's testing is he testing with 2023? 20:25:52 Matt_King: It would be great to test Alert Command button, link, and toggle button with JAWS so that we have results for all AT 20:26:07 James: There are some conflicts for Toggle Button, we should be able to resolve them 20:26:44 Matt_King: If Louis can test these, then Alyssa we wont need you to do any testing 20:26:58 Seth: James will you follow up with Louis regarding these notes? 20:27:06 James: Yes I will follow up 20:27:39 James: For the new year, we will have Dillion and a new person at PAC. They can start in January 20:28:12 Matt_King: The plan now is for Louis and I to do the testing with JAWS next week 20:28:48 Matt_King: As of this moment, if we did not more testing, we can send the Preview of the APG support tables for link and command button to vispero 20:29:01 TOPIC: Process for publishing re-tested plans 20:29:39 Matt_King: Lets start with the mechanics for the ARIA AT App 20:30:14 Matt_King: So we have these buttons in the table, labeled "Mark as in review" What does that button do? 20:33:39 Howard: In Prod now if you press Mark as in review, then that button becomes Mark as finalized, which when pressed would put the test plan it in final reports. But there are changes to this now that we added language for recommended 20:34:08 Matt_King: If I press that button now for link and command button what will happen? 20:34:20 Howard: It will just mark it as in review 20:34:46 James: I just fixed the conflicts on toggle button 20:35:19 Matt_King: I will try to press this button on NVDA and Chrome on the command button plan 20:35:28 Matt_King: Did it do anything? 20:35:55 Matt_King: It reloads the page, updating test plan status 20:36:10 James: I don't see any change yet 20:36:25 Matt_King: Now it says in review, mark as candidate 20:36:36 Matt_King: I'm a little confused if i pressed the wrong one 20:36:41 Matt_King: Now it says, mark as candidate 20:37:09 James: Lets establish what will happen when we press that 20:37:49 Matt_King: We changed it from draft to in review, did that just change visibility of the status on test queue page, but didn't change anything on the results page? Yes 20:38:13 Matt_King: Right now there is a NVDA Command button row in the candidate test queue already 20:39:01 Matt_King: If we go to the candidate tests, and go to NVDA 20:39:21 Matt_King: I dont see anything about the date of the test 20:39:35 James: No that page doesn't show any data about the test plan 20:39:58 Matt_King: So this currently says "Review status on candiate page is ready for review" 20:41:19 Matt_King: We need to discuss how we want this to work 20:43:06 James: Lets take command button, and say we want to publish the report for NVDA what do we want to happen? Right now it will add a row to the reports page, but they will both say Toggle button 20:43:17 Matt_King: We would ideally have access to all the test data 20:43:58 James: So we wont replace the data, we want to add the data with the new version to the run history. Is it then codified somewhere that the support level will be calculate only based on the latest version of a Screen reader? 20:44:26 James: If the support level is based on a amlagam of the versions than that will be inaccurate. 20:44:39 Howard: Yes confirming the report data will be based on the latest data 20:44:55 Howard: So for clarity, we are working on displaying the data in one row on the reports page 20:45:20 Howard: However, to capture the run history, we need to work on collecting and displaying this data 20:45:56 James: The run history is currently being scoped to the report, we want it on the test plan 20:46:08 Matt_King: Based on our website design, we want to surface the latest data only 20:46:30 Matt_King: We will need to change the website to be able to show test results from earlier versions of the screen reader or browser 20:46:49 Matt_King: So right now, add additional rows becomes problematic. We just want to surface the latest datea 20:47:06 Matt_King: Our website isn't designed to drill into previous results 20:48:25 Seth: There are two pieces in transition, that required to be revisited, one is how do browse reports across time, the other one is in a slightly differnet level of support depending on where in the app, is allow the review determinations to be made on the test plan, divorced from the res'ults 20:48:41 Seth: We are currently unbundling the test plan and results 20:49:19 Seth: Next year, alot of this will become natural when we shift of view of plans and data 20:49:53 Matt_King: So for now, if we press the mark as candidate it will add another row to the reports table, then Bocoup would manually change what is displayed onm the reports page and results page? 20:50:24 Matt_King: I am concerned about having multiple rows for JAWS, if we update alert and have two rows on the results page that will be confusing for Roxanna 20:50:48 Howard: So can we manual change the table? Yes we can edit to have a single slice of data on both reports 20:51:43 Seth: One thing I want to say is Howard has been working on the reports page to seem like there is no duplicate rows, Matt you are asking can we do the same thing o the candiate page, I think its possible but its a little more complicated 20:51:53 Seth: Howard and I can work on this 20:52:21 Matt_King: So we want to do this for Button and Link, sounds like the more we do, the more work there is to make it seem like things are the way they are 20:53:02 James: I'm also concerned that the publication dates are represented on all pages. I'm also concerned that if we make these changes while people are on holiday, we will all loose track of what has been published and not 20:53:12 Matt_King: Any manual changes we make should be in a github issue 20:54:29 Matt_King: Lets use Link, its in candidate test page for all 3 SR and in the reports page. It sounds like another option is to make it appear as there is no problems. If we do this we will have two rows on canidate page, I guess we can figure out what the consequences are in the next year 20:54:46 Matt_King: there will not be anyone reviewing this until sometime in January 20:54:59 Matt_King: So the risk of having duplicate data is zero 20:55:14 Seth: Also there is no pubic view of candiate test currently 20:55:41 James: Seth you mentioned you worked around this for the reports page, what will happen when you press that button now? 20:55:57 Howard: Its a change we have been working this week, we need to still deploy it 20:56:31 James: How would the feature work? 20:57:09 Howard: A new report would get added to candiate test, along with the recommended status, it will compare its self with other test plans, and if its at a later date it wil override it 20:57:16 James: What happens to that old data? 20:57:28 Howard: It still exists, its just not reachable on the webiste 20:57:37 James: Does it change the dates? 20:57:46 Howard: When it gets promoted it will have a new date 20:57:54 Matt_King: There will be two rows remember 20:58:52 James: So theoretically, when we publish a new report, the newer test result will display 20:59:25 Matt_King: There is some confusion here about versions 21:01:03 Matt: We have test plan version 1 t1 and screen reader version 1 v1, if they currently show 96% on the reports page, if the next step is we have Test 2 T2 and Screen reader V2, that the results of Test 2 and Version 2 will display. 21:01:39 Howard: Right now the version of the AT is not being considered, just the test plan date 21:01:50 Matt_King: How does the current feature you are working on work 21:01:58 Howard: It doesn't take the AT Version into account 21:02:07 Howard: It just takes the latest version 21:02:34 Howard: What ever the newest date is takes precedence 21:04:18 Matt_King: We might want to investigate that logic, it will work for now 21:05:09 James: If the logic is based on whenever you republish a test plan the candiate date will change, we don't want it to reset the beginning of the candidate phase 21:06:07 James: We also don't want to retest the plan when we republish it 21:06:37 Seth: Yeah this is just a quick work around, we can revisit it in the new year 21:06:45 Matt_King: when do we plan to have this change in prod? 21:06:49 Howard: Early next week 21:06:57 Matt_King: I wont push any buttons before then 21:07:07 Matt_King: Seth we will need tight communication 21:07:22 Matt_King: who will be available next week to work with me to make sure we get the support table out? 21:07:49 Seth: Alex is working next week, Howard is working Monday through Thursday, I think we should start a email thread and use that as a channel 21:07:54 Matt_King: Okay that sounds good to me 21:08:20 Seth: We are having some challenges what the status or issue of the deployment process 21:08:33 Seth: I asked for clarification on that threa 21:08:57 Seth: As we get the work done, you might want to try a different channel with Shawn and Michael 21:10:14 Seth: We could help, but we haven't been given any info on the issue, thats causing the delay 21:10:27 Seth: You could wait til next week after this deploy 21:10:35 Matt_King: I was thinking to get an update this afternoon 21:11:17 Matt_King: This is also a potential blocking issue to publishing 21:13:14 rrsagent, make minutes 21:13:14 I have made the request to generate https://www.w3.org/2022/12/15-aria-at-minutes.html Matt_King 21:14:41 present+ Alysa 21:14:49 rrsagent, make minutes 21:14:49 I have made the request to generate https://www.w3.org/2022/12/15-aria-at-minutes.html Matt_King