Meeting minutes
<Jem> https://
Jem: We will have no meeting next week. Our next meeting will be on May 9
Status of Site Updates
Alex_Flenniken: we have been working on the side navigation on the "patterns" page
Matt_King: We need a green light from Sean on the design of those things
dmontalvo: I am taking over staff contact responsibilities for the ARIA working group; that includes APG
dmontalvo: Hopefully I can help with communications
Matt_King: We're talking about w3c/
Alex_Flenniken: no update on w3c/
Matt_King: 2535 is higher priority
APG browser support requirements
github: w3c/
Matt_King: Just prior to this meeting, I added a comment about the policy
Matt_King: But we should probably add something about this to the project's contribution guidelines
jamesn: I don't think people care about old versions of browsers anymore because everything auto-updates
Matt_King: I think this is most important for folks who are in enterprise environments where browsers don't update as often
Matt_King: I wonder if we should remove even the reference to Internet Explorer in the text since that tends to make it feel dated
<Jem> jugglinmike: I will document this in the code guidance and update the apg doc regarding IE mention.
Matt_King: We don't have to worry about enterprise as an audience for APG itself. It's enough to warn readers about the support considerations in their own projects (and the text already does include such a warning)
"Using ARIA" to APG
github: w3c/
Matt_King: We have the information architecture we need to support this, so the timing is pretty perfect in my mind
Matt_King: The first thing to do is to go through the headings in the "Using ARIA" document, and identify which of those sections are either (1) already covered, (2) appropriate to be discarded, or (3) appropriate for some section of APG
Jem: This seems like a good task for newcomers
Andrea: Can we think of this as an audit?
Matt_King: Not exactly. The end goal is that "Using ARIA" is going to go away. But there's information in "Using ARIA" that APG can inherit. The task is to identify which information can be salvaged and where it belongs (e.g. in a pattern or in a practice)
jongund: I can help with this because I'm familiar with both documents
Matt_King: I'm not sure of the best way to structure this, but I've been imagining taking the table of contents and then categorizing each item in an issue comment
Andrea: I'm interested in helping, too
Jem: I'll assign Matt_King, jongund, and Andrea
Jem: I'll assign myself as well so I can review
Andrea: I'll coordinate the work to start us off
Pull request reviews
PR 2622 - Listbox Examples: Update scrolling of listbox item with focus into view when page is magnified by jongund
github: w3c/
Matt_King: I recently noticed a bug. There are checkmark icons in the list box, and they're getting announced by screen readers
Matt_King: Because it's related to the accessibility features documentation, I think we should address it in this pull request
jongund: I can fix it in this pull request. It should be done by tomorrow
Matt_King: I'll continue my editorial work on the comments
New Issue Action Planning
Grid cell content can be actionable and editable
github: w3c/
Matt_King: It's not clear to me what the question is. Maybe we should talk about this when Curt is here.
jamesn: I agree, we should probably wait for Curt
jamesn: I also don't think we should try to solve every single weird case of a grid, though this is not so weird of a case
Skipto Script is loaded twice for practice, pattern and about pages
github: w3c/
Alex_Flenniken: there's code that switches between two configurations of skipto--that must be malfunctioning
Alex_Flenniken: I think we can share the same configuration; I will remove it from APG. It will be in the website, but not in the raw development HTML files
Listbox example - ESlint error
github: w3c/
Alex_Flenniken: This was originally reported by Aleena, but we couldn't reproduce it. Since Aleena has moved on from Bocoup, I think we should close this
<Jem> https://
Matt_King: Let's make this issue about moving toward ECMAScript modules.
jugglinmike: I'll reframe the issue
Matt_King: Let's make it about using import declarations in the JavaScript where appropriate
end topic
github-bot: end topic