Meeting minutes
update on status of automation UI in ARIA-AT App
<jugglinmike> w3c/
That link is to the conversation we've had to design the interface for the automated response collection in ARIA-AT App
jugglinmike: My most recent comment describes what we have planned for the MVP of the ARIA AT App
jugglinmike: The flow begins with adding a test plan to the test queue
jugglinmike: You can assign a tester or not. If you assign a tester, it will also assign a bot user
jugglinmike: This MVP is only supporting NVDA and Windows
jugglinmike: As previously discussed, the bot will not assign verdicts
jugglinmike: The status of the collection of tests will be formatted as follows "Responses for x of y tests recorded. Verdicts for x of y assertions assigned."
jugglinmike: We need to consider in the future when it will be appropriate to disclose when humans are editing test results, and when bots begin to
JS: I think once results are published, it will be important disclose this change
JS: Currently we don't disclose who performed each test to the public
jugglinmike: Test admins can mark test plan runs as finished
jugglinmike: Everyone is invited to review our conversation and how we got here
jugglinmike: The good new is we've made progress on this and have been implementing as its materialized
jugglinmike: We are close to deploying to the sandbox server
jugglinmike: We maintain 3 publicly available versions of the app, Production, Staging, and Sandbox
jugglinmike: I think that's everything I wanted to cover for this agenda item. Feel free to email me any questions
Collaborating on the NVDA add-on
jugglinmike: In implementing the automation MVP, Corey at Bocoup has identified a few issues with the NVDA add-on.
https://
They are reported in the repo linked above
jugglinmike: We at Bocoup are not skilled in Go and are not familiar with the overall architecture
jugglinmike: This division of responsibility has worked fine for us
PAC has been maintaining this repo
jugglinmike: Issue #46 is a pressing issue up and down presskey events don't seem to be working #46
JS: I agree I've been thinking about this
JS: Down is not a key it recognizes. I didn't write the translation code, but I'm hoping it will be straightforward
jugglinmike: Great, we do want to be collaborative, and Corey is willing to take a shot at it
JS: To be realistic, you have surpassed us to verify a fix. The project really needs a test suite that isn't implementation specific. We welcome any input
JS: We are working to assign a resource to these issues, we are always happy to review a PR
JS: If you ever have any issues that have been filed and not acknowledged, especially blocking ones, please feel free to ping me
jugglinmike: Thank you
jugglinmike: The only thing for me, is a project manger thing, to coordinate and not step on each others toes.
jugglinmike: Corey will look at this after he reviews a few items for the aria at app. He will be vocal once he begins to make sure everyone on the project knows what each other are doing
jugglinmike: I think thats it for this meeting