Meeting minutes
Update on meetings with screen reader developers
<Rich_Noah> Jes present+
Meeting with Apple tomorrow April 15th
Meeting with Vispero on April 22nd
The primary goal for these meetings it to figure our logistics around collaborating, identify Point of contacts at each company, review project timeline and goals
May test running plans
Each test phase will last 180 days
We plan to start testing the 8 Recommended test plans in May
We will need to manually track AT and Broswer Version.
Seth and Rich plan to manually input the AT and Browser version data at a later date
We need to define a place for testers to manually enter their AT and Broswer version
Both PAC and Bocoup will provide someone to run tests
We will need to be careful to track if a browser updates while someone is performing test
We may be able to utilize the browser release schedule to infer this information
Some companies, like Meta, control the browser update process for the machines they manage
There are 140 tests in total
Test plans vary in size, some are small with 3 tests, some are larger up to 26 test
We will need to ask the AT Developers how many versions of the AT they want to consider results for
We will need two testers on each screen reader
The preference would be to have each PAC and Bocoup perform all tests with each screen reader
PAC will ask Apple tomorrow if they can provide anyone to run tests
Seth asked about the 180 day duration of a test plan, and where this came from
James stated there is a minimum of a 120 day duration for a test
Matt said these durations were what felt right to when our collective team define the working mode. The working mode is a draft and open to change
Open questions: Can Louis test with a Mac?
We want to start testing asap, we will be ready to begin testing April 21st
However to begin testing, we need a way to track to AT and Broswer version info
Alyssa said she can commit to some testing at the end of April and in May
PAC will provide a tester
Matt stated it would be great it the test runner software could time the duration of a test
In the next week, Seth, Rich, and Bocoup will get back to the group with an answer on if they can provide a tester
In the next community group meeting we will define which tests are assigned to who
Seth asked - Do we want to do any cleanup on the test queue as it is?
Matt - Yes, lets make Test Queue Cleanup a topic for next meeting
Matt asked if the Update test button appears only if there is an update available for that test?
Seth - No the button appears if there are any updates available for all test plans
Seth mentioned that if there are updates to Test plan instructions, now would be a good time to apply those updates
James stated yes this work is in progress
PAC has been updating the 8 recommended test plans, and will update the 16 candidate test plans in May
Matt stated that these tests are all still in a draft form
user journeys for the next set of app changes
<Matt_King> https://
Matt asked Bocoup, what is the timeline to incorporate Community Group feedback into these user journeys?
Seth Bocoup will implement feedback in two weeks, next week Bocoup is away at an all hands meeting
Everyone agreed to continue this discussion in future community group meetings