Meeting minutes
Candidate test queue
Matt: Are we on track to test the Canidate Test queue next week?
Seth: We are still track to test this next week, Louis is scheduled to perform some testing next Monday.
Bocoup will send out a email on Tuesday to let the community know the Canidate Test queue is ready for review
We will plan to discuss any issues in next weeks Community Group meeting
Seth: As a reminder, most of the features are for the vendor or Admin roles
The CG group should review the public view
Seth: When the email goes out to instruct people to review the Canidate Test Queue, it will include a definition of where people should provide feedback
Plan for sharing test results in APG
Planning for the sharing of our results in the APG
Matt_King: This is a big deal!
Isaac Durazo let us know that Next week, the APG task force will be discussing the idea of having ARIA-AT Test Reports embedded in APG’s Pattern Example pages .
<Matt_King> APG GitHub issue for design: https://
He created the issue linked above to share mockups of this idea. If anyone in this group wishes to participate in the discussion, please join next week’s APG meeting or comment on the issue.
Matt_King: This will drastically increase the visibility of the ARIA AT Project
Matt_King: Our side of this is making sure we have the data ready, our goal was to get the first 8 plans we've been working on by the end of the year
Matt_King: We got some feedback that may push this date back a little bit
In addition, Vispero is working on some fixes based on the existing test results, that will be released in next version of JAWS in the second or third week of December
Matt_King: I still want to try to release the test results for one or two tests by the end of the year
Matt_King: but that will be a tight window
JoeHumbert: I would love to help test at the end of the year, but I no longer have a JAWS License that I can use.
JoeHumbert: Could the results just be published and updated in the future based on newer releases? Do we need to wait for the new version of JAWS?
Matt_King: We are timing the release of the first set of results in an effort to increase and encourage collaboration with our partners
JoeHumbert: In the future, we want to avoid situations where we delay the results of tests to wait for updates from a vendor. As we haven't released any data yet, this is okay, but is worth discussing for the future
Matt_King: When you go to the reports page now, the URL seems to change, I want to understand the constraints of how to label the data in the APG, and when linking to test results will the test reports page have a static URL?
Seth: Currently the Test Queue does create a URL for a specific test result. My understanding is we would want a URL that reflects the most recent test data
Matt_King: For sties that reference these test results, The calling site will need to know the status of the test plan
Seth: The fact that we both author ARIA AT and APG, might be a distraction. If this was MDM, wouldnt we want to update the content on our end?
James: I think there are two questions. Are we pulling in a UI in the traditional fashion of a embed, or are using a API?
James: Does the calling site need to know the status?
Matt_King: There a part of me that thinks we need to send the data and the presentation
Seth the easiest thing is to deliver an iframe that includes data and presentation
Seth: If we control all of this, we could offer a second API the request this kind of data
Seth: I think we would want the iFrame first, before we work on a custom presentation
Seth: It also takes a customized website experience to manage the API calls and deal with errors etc
James: The iframe allows people to embed in non web based ways like a spreadsheet
Seth: We can expose Query parameters that customize the way we format the data in the iframe
Seth: These could help match CSS on the calling site
Matt: On the APG side, I'm thinking what we will do is by default we will put on every page the heading that says there is no data available, and on the ones we want to expose it we will use the iframe and change the content accordingly
Matt_King: I want to include Roxanna and James Craig in the review of these pages and the way the results are presented and get their feedback
Matt_King: Where do we want to have all of these discussions on how this will be built and architected?
Matt_King: The Design is up tp the APG Task force
Seth: Yes they are the first client to this data, so we will tailor it to their needs
Seth: There are some more questions that relate to the ARIA AT App, like what the URLs look like and how do they show the most recent data
Seth: Could you expound on what those conversations would include?
Matt_King: Basically spec-ing out what are the basic requirements for URL parameters, what does the Query need to do. The requirements come from the APG side, but for our project we need to think about this in a way that we aren't just targeting the APG
Matt: There is a technical implementation question of how to respond to querys.
Seth: I will start an issue
Matt_King: I'm most concerned about the concept of pulling in the latest results
Matt_King: For now thats what we need in the APG, but we need to design that in a way we could pull in something other than the latest
Matt_King: But that is a future requirement
Seth: Is there a use case for embedding a data from a certain point in time?
Matt_King: Yes when we get to experimental stuff in the APG, we may need this to version test plans
Matt_King: I'm thinking about when we add support for touch screen readers, and we may want to not necessarily pull in the most recent tests.
Matt_King: What the latest test result means is still a little murky
Additional upcoming testing
Matt_King: I am looking to get updated test results based on the JAWS release in December
Matt_King: We aren't sure of the exact date
James: PAC will be closed after Friday December 16th
Seth: Bocoup is closed from December 26th to the 30th
Seth: I will check on Louis's availability to test after the JAWS release in december
James: The mixed state check box is ready to be assigned for testing
James: The disclosure navigation is in a good place, hopefully by Monday we can get this merged and ready for testing
James: There is some additional retesting that needs to occur for Breadcrumb
James: I'm not sure on the exact details of whether we just need to rerun a certain command or rerun the whole test
Isa: People just need to run the test with the additional command as soon as its updated
James: Two plans that need testing from scratch, and one that just needs some retesting
Matt_King: For Breadcrumb we will have to go into the admin test panel and update the test plan, theoretically this should retain the test data
Matt_King: This will be a good test for the result site
James: There are no results for the breadcrumbs because its currently in the queue not in the report page
James: There is one test result published, that we need Seth to look into deleting
JoeHumbert: When is the timing for the retesting of breadcrumb?
James: We will look at who did the original testing and decide next week who needs to retest
Seth: We will unpublished the disclosure navigation report. We will try to soft delete this and report back
Seth: Could you send a heads up when you are ready to update the Breadcrumb? I want to do a final check internally to make sure this feature is ready