Meeting minutes
<Jem> Meeting; ARIA Authoring Practice Guide
<Jem> https://
Setup and Review Agenda
Matt_King: I think it makes sense to skip this meeting on September 5 (since it follows a US holiday) and September 12 (since that overlaps with TPAC)
Jem: That makes sense to me
Status of Site Updates
Matt_King: I will reach out to Shawn to publish on August 29th
Matt_King: It will include the three updates listed in this section of the agenda, plus any of the PRs we're able to merge in the next topic
Pull request reviews
<Jem> https://
Listbox Examples: Update scrolling of listbox item with focus into view when page is magnified
github: w3c/
Matt_King: I believe we were waiting on one last code review from andrea
andrea: I made some very small requests
Matt_King: jongund is out right now. Since andrea wrote these using GitHub's "suggestion" feature, I can apply the changes on jongund's behalf. I'll follow up with that after this meeting
<Jem> w3c/
Move feed example inside the page
github: w3c/
arigilmore: The original "feed" example is presented in a separate page, and it uses an infinite scroll so that you cannot reach the bottom of the page
arigilmore: That's why I placed the feed in a modal dialog, so that the dynamically-generated content wouldn't prevent viewers from accessing the content that follows the example
Matt_King: It being in a dialog feels somewhat irregular to me
Matt_King: Could we put it in a disclosure, instead?
Matt_King: We could also make sure the "collapse" button is fixed to the top of the feed so that it's always present even as you scroll down on the feed example
Jem: We could have a "load more" button so that the user can control when more content is inserted
Matt_King: But if the example behaved that way, it would no longer be a feed
jugglinmike: We could just do this with a fixed-height container whose CSS "overflow-y" property is set to "scroll"
arigilmore: I'll experiment with the disclosure element and with the fixed-height element
arigilmore: The only con is that neither of these are quite representative of the "feed" instances we've been discussing (Facebook, Amazon, etc.)
<Jem> https://
jugglinmike: We might also use the example as it exists today, but just insert it inline via an iframe (rather than linking to it as a standalone document). In that form, the nested document would more accurately mimic the examples we've been considering (to arigilmore's point)
<Jem> https://
Matt_King: Whatever form this takes, it's going to be a great improvement, arigilmore. We appreciate your work on it!
New contributing page
Matt_King: I am wondering if people have any others idea about content that we ought to include here
Matt_King: Especially arigilmore and andrea since you two have so recently experienced the learning curve for what it takes to submit a pull request
Matt_King: This is designed for new contributors who are "starting from zero". These folks might not have joined the group
Matt_King: I don't want to promote the ARIA-AT group so highly. It might fit at the end of the document, but I do want to keep folks focused on the APG itself
Jem: We can lower the barrier of entry by suggesting that people join the community group (since you need to be a W3C member to join the ARIA Working Group and the ARIA Authoring Practices Task Force)
arigilmore: At the beginning, andrea and I kind of forgot how direct the contribution experience is in regards to the source files. We're used to projects that have associated tooling, and we were looking for instructions about npm or yarn or similar. This documentation doesn't explicitly say that, actually, you just interact with the source files directly.
arigilmore: From a "Getting started" standpoint, it might be helpful to organize content according to the kinds of contributions folks might want to offer. For instance, it could say, "If you want to change *this* page, then..."
andrea: Something that's helped me in getting situated was having access to arigilmore. It might be a lot to ask, but having an "onboarding buddy" can really help!
<arigilmore> maybe a good example: i was forking and creating a branch off my fork then creating a PR, but then Matt lmk to actually just make a branch off the main repository
Matt_King: It sounds like we should spend more time thinking about the "readme" file!
Jem: Right, maybe getting to the point faster
New Issue Action Planning
Combobox example's text doesn't fit in its input element on Safari iOS
github: w3c/
<Jem> w3c/
andrea: I can review this. I'll try to reproduce it and weigh in about the suggested fix
Jem: I'll add the "bug" label and the "example pattern implementation" label and the "qa for apg examples" label
<Jem> w3c/
Clarify whether Tabbed Carousel may have aria-roledescription
github: w3c/
Matt_King: This looks potentially editorial.
Matt_King: I think the description isn't in line with the information that's in that table
Matt_King: Now that I understand what that image is about, I think I can respond
Jem: I'll assign this issue to you, then