Meeting minutes
matt: next meeting is test writing
App Development Workstream Update
Seth: 3 things working on
<Matt_King> Seth: Howard completed work on pagination component
<Matt_King> So, graphQL is now hooked up to test queue
<Matt_King> Second thing is work on test renderer
<Matt_King> Includes fixing the way the setup script runs with a button
<Matt_King> and way to raise an issue from any test.
<Matt_King> Z has PR up for these features
<Matt_King> The PR has a checklist of things covered in the PR that you can read.
<Matt_King> Third area of work in progress is related to generated test files.
<Matt_King> Handed this work off to Howard.
<Matt_King> Git includes functionality called git attributes that allows change of merge behavior for certain files.
<Matt_King> If we treat the generated files as binary, GIT might be able to merge them without complaining; i.e., no conflicts.
<Matt_King> This could unblock conflicts during merge.
<Matt_King> Howeard is continuing to work on the GitHub action we previously discussed.
<Matt_King> JS: for individual html test files seems like a good idea, but could be a problem for index.html
<Matt_King> Seth: this would need to be accompnaied by a GitHub action that triggers a rebuild after the merge is complete.
<Matt_King> That would take care of index.html.
<Matt_King> Howard: tested it with pattern matching to determine which files to treat as generated but the idea of using a build directory would be good way to isolate the treatment as binary
<Matt_King> Michael: likes putting all the generated files into a build dir
<Matt_King> James: +1
<Matt_King> Remember need index.html for githack or netlify
<Matt_King> James: what is pr for setup script button?
<s3ththompson> https://
<Matt_King> James: would be good to get overview of user impacting changes in this PR
<Matt_King> Seth: This PR does not include the user visible changes
<Matt_King> It is the foundation for them
<Matt_King> James: where is it planned for the setup script button to be on the test case page
<Matt_King> Seth: Looking at issue 369
<s3ththompson> https://
<Matt_King> Consensus from March 4 meeting is that it would be autofocused and named run setup
<Matt_King> Not sure where it would be in the DOM
<Matt_King> It would be dynamically inserted
<Matt_King> James: the example pages do not have dynmic content
<Matt_King> Discussion of location and purpose of setup button and how it impacts experience of person running tests.
<Matt_King> It needs to be in the popup window containing the example.
Test Writing workstream update
<Matt_King> James: Have been working on tests for new slider examples; almost finished.
<Matt_King> Have a bit of a backlog with the PRs. Excited about avoiding merge conflicts on the new PRs.
<Matt_King> Should help a lot with our progress.
<Matt_King> Still owe PR to modify alert example for APG.
<Matt_King> The updated sliders are not appearing on gh-pages for APG.
<Matt_King> Rob: qq about feedback on PRs. What kind of feedback?
<Matt_King> James: feedback about bugs and assertions
<Matt_King> are good.
<Matt_King> The question about hints you raised is a CG discussion.
<Matt_King> We do have an open discussion about hints. we should talk about that a meeting soon.
<Matt_King> everything else is fair game.
Automation workstream update
<Matt_King> Seth: Mainly focused on NVDA prototype; it is rebased.
<Matt_King> Going to investigate the cross-AT approach to examining speech out for all Windows AT.
<Matt_King> Exploring SAPI 5 voidce driver to capture speech output
<Matt_King> Have been able to intercept words in research protytpe.
<Matt_King> James: are there automation meetings?
<Matt_King> Seth: not yet; should be starting soon.
<Matt_King> James: I'd like to join one of the meetings to talk about capturing speech.
<Matt_King> Think we can do it with an NVDA synth driver.
<Matt_King> Need a T that sends otuput to two places.
<Matt_King> If it is system wide, could also work with Narrator
<Matt_King> Seth: when we get it scheduled, we'll post to wiki and notify
<Matt_King> Seth: One other thing, tangential, about co-design. we may have something on this soon. May tackle browsing reports.