Meeting minutes
Meeting Setup
<Matt_King> You can find agenda at https://
<Sam_Shaw> Agenda: No meeting on March 16, Meeting tine survey part 2, AT Support Table, Launch Plan App update plan
Meeting schedule
Matt_King: both AXE Con and CSUN are happening next week
Matt_King: that means I won't be able to lead, so let's plan to skip next week's meeting and continue as scheduled on March 23
<Sam_Shaw> Link to meeting Poll: https://
Matt_King: This is "round 2" of the survey. I'll make that clear in an announcement that I send to the list
AT Support Table Launch Plan
Matt_King: Several things are coming together to make this happen
Matt_King: First, get the preview of "support tables" ready for the five tables we've tested
Matt_King: Then send some communications to Apple and Vispero that they're ready
Matt_King: Prepare some public communications
Matt_King: (oh, I skipped over the testing we've already done)
Matt_King: Then share our projected outlook for testing in 2024 and beyond
Matt_King: I'd like to have all of this done by the end of this month [March]
Matt_King: I'll have a draft of the announcement (which will be a W3C blog post) by our next meeting [March 23]
Matt_King: https://
Matt_King: All of the feedback which we previously discussed is all here
Matt_King: Keep in mind that all of the URLs are pointing at Bocoup's "sandbox" server
AlexFlenniken: there are a few pull requests which need to be merged in a certain order to make this happen
AlexFlenniken: we've merged the bulk of the work already--that's what's visible on the "sandbox" server
Matt_King: Next in line is updating aria-at-app, and then I want to update the APG pull request
Matt_King: I'd like to add support tables to Radio, Alert, and Link in APG
AlexFlenniken: currently, you'd need to get the iframe code which exists and then update the values in the code
AlexFlenniken: we don't have a UI for generating that code right now
Matt_King: I don't know if I want to make that public-facing, yet
Matt_King: the support tables look pretty awesome to me
howard-e: We are versioning VoiceOver according to the macOS version in use, not a version number that Apple has specifically assigned to Voiceover
Isabel: I am maintaining the AT version information
Matt_King: I've previously asked Alex to replace the cells which say "none" to instead say "no data" (since the term "none" can be misleading in the context of a support table)
Matt_King: And I also requested a change to the warning text
Matt_King: Is the code ready to handle data in the "Recommended" phase?
AlexFlenniken: It's not hard coded. It is, in fact, dynamically pulling in the value.
AlexFlenniken: That said, the code doesn't have copy text for that phase, so we'll need another patch to add that
howard-e: The copy that appears ("warning" in a disclosure element on the "reports" page). When we move a plan to "recommended", that disclosure changes from a warning to "recommended report." It isn't available right now, but I wrote the code and can merge it today and deploy it at any time
Matt_King: Can we move some of these to "Recommended" before we launch?
James: purely in terms of the data which we have available, the answer is "yes"
Matt_King: For this launch, we'll be using the first five patterns: the two buttons, link, radio, and alert
Matt_King: So, to recap
Matt_King: The first things that need to be merged will be merged in the app
Matt_King: But first, we have three fixes: two changes to copy, the Date problem (which I need to raise an issue in the ARIA-AT App to make sure the problem is understood), and for howard-e to merge the changes to the sandbox so we can ensure the transition to "recommended" works as expected
Matt_King: Once all those are done, I think we'll be able to merge the changes to ARIA-AT App
AlexFlenniken: That sounds right to me!
Matt_King: Once that's merge, does that mean that the preview in ARIA-Practices would then point to the production ARIA-AT site?
AlexFlenniken: Yes. Once ARIA-AT App is updated, I'll update ARIA-Practices to use production
Matt_King: So we have to change the iframe code there
AlexFlenniken: right, because they're currently pointed at the sandbox server
Matt_King: Okay. Then once that's all done, I can send preview links to Apple and Vispero
Matt_King: if we get those e-mails out around the 21st or 22nd [of March], then we can talk about the quarterly plan for future testing and work that into the announcement
Matt_King: I think that gets all our "ducks lined up" in terms of what we need for the launch
Matt_King: It looks like the actual publication will occur during the first week in April
Matt_King: Once we verify that's all good, we'll do our communications (blog posts, tweets, and all of that stuff)