Meeting minutes
July meeting schedule
Matt: July meeting dates. Any adjustments?
James: PAC out first meeting. Will give over to another workstream.
Seth: Bocoup not available the week of July 5th
Seth: available July 8th
Matt: July 1st, no need for sprint planning meeting. Can discuss async.
Matt: cancel both meetings for the week June 28th
Matt: July 8th, cancel meeting and return to normal July 15th
Matt: All meetings on July 1 and July 8th.
Seth: cancel July 5th Automation meeting
Workstream Updates
Matt: call for rollup on app development.
Seth: main work is to update the BE to support working mode changes, i.e. testing individual test plans more frequently. Laying ground work to display automated tests along manual tests.
Seth: test-queue in final stage with clean up on PR
Seth: Individual changes can be made without effecting a whole
Matt: What environment will PRs land in, when will changes be available, and might testing be needed?
Seth: PR will be on sandbox url, will initial be week of 6/28. Question of production deployment is larger scale and requires coordination to migrate so that back end can be updated.
Matt: testing somewhat paused right now. Thinking getting starting in July merging tests. Kicking tires on tests and new test-queue
Seth: connecting pages one by one. Not as heavy as a lift for test-run. Could go without reports page.
Matt: what is the best way to coordinate?
Seth: Get sandbox up and running.
Matt: send email to list for sandbox. Not an issue. Possible available before July 15th meeting. James use portion of meeting for test-queue.
Seth: need to check with team
Matt: Crystal if test-queue is ready attending July 15th might be a good idea.
Matt: any other updates
Seth: implemented new permissions model. No have PR open for new allow list. As simple as opening a PR to add testing.
Seth: James, Howard, and I have been reviewing new test generation workflow. If goes well can start merging next week. This will be to update all the open test plan PRs.
rob-fentress: how do screen readers join?
Matt: that is a part of onboarding, Issue 420
Matt: any other updates for app development. Updates on automation.
michael_fairchild: met earlier this week. updates on new prototype.
michael_fairchild: new prototype goal of not being tightly coupled with NVDA. New prototype lives closer to the OS level. It looks at everything sent to speech synthesizer. Prototype demoed with next steps identified. Synthesizer does not output audio. Not optimal for a contributor that is blind.
Matt: question on driving the screen reader. Do we plan driving everything with the screen reader? Possibly use key commands? Possibly coupled to screen reader but possible abstraction.
Seth: Currently MVP. Intercept commands. Use learnings to implement more native protocol.
Matt: so are you still looking at keyboard commands?
Sina: do we need that if we have the speech?
Seth: long term benefit to have api
Matt: making it robust, more than on one screen reader and making it not dependent on UI of screen reader. You don't have any feedback.
James: have discussed some convenience features. More than automation, how to make human tester's life easier. Example, how do we know NVDA is in focus mode.
Matt: good with approach of MVP and have ambition for driver protocol.
James: role and name could be reported separately
michael_fairchild: that is tricky
James: it would be the speech, synthesis of the role.
Matt_King: michael is thinking inline with what I am thinking. Part of it is a learning process and moving the project forward. Make better over time.
Seth: that is correct. dev tools often use the same tools.
Matt_King: great update Michael
Matt_King: move on to test writing
James: process has slowed and the resolution to the merge conflicts, windows support. Hopefully all things can be in place on Monday. Such as new sliders, breadcrumb and alert.
Matt_King: I have seen the PR
Matt_King: do we have more grid tests and assertions in the work?
James: working through the new APG.
Sina: not a lot of consensus on how grids should work.
Sina: I would like to get power users together to put tests through their paces
Matt_King: I will have some available to put them through their paces
James: once comes down the pipeline we can prioritize.
James: excited about coverage reporting to start preparing test cases.
Sina: will we be unblocked on Monday?
James: I will have PR reviewed Monday.
Seth: we can do that async after review
Getting started page for test reviewers and testers
https://github.com/w3c/aria-at/issues/420
Matt_King: Sina would you be comfortable including this in your work for current scope so new members can get up to speed. Need getting started materials
Seth: have some initial notes
James: need to start posting and making items available
Matt_King: last comment by James July 7th. Can you update Seth?
Seth: allow list is an update
Matt_King: possible wiki page so a link could be sent. It would step them through getting started.
James: can we use the July 15th meeting to decide that? Currently do not have bandwidth to create content between now and then.
Matt_King: Seth will you please add your findings
rob-fentress: where can I direct people at this time
Matt_King: will have content prepared by the end of July
Windows support
Matt_King: windows ci is complicated and most projects run platform independent. what does have to be windows specific?
James: windows does not accept backward slash. new test scripts don't need to be accepted on windows. have members of the team don't use cli.
Matt_King: shelling out from a node script seems clunky.
Matt_King: howard mzgoddard can we use an npm package?
James: we are all on windows
Sina: let us not make windows a blocker
James: let us identify when we need an OS specific solutions
Seth: like uri path
James: generation of tests and validations needs to run on windows
Seth: PRs and issues are open and underway now.
Matt_King: I did not want to ask the engineering team to make any large changes and not effect velocity
Seth: should put to paper all scripts should be cross platform.
Matt_King: I think we are good on issue 445