Meeting minutes
setup and review agenda
<Jemma> no update for the agenda
APG issue triage
jemma: Let's do issue triage, like the ARIA WG does. We have 14 new open issues.
<Jemma> https://
carmacleod: This is something Michael C. has to do.
<Jemma> https://
<Jemma> https://
mck: Add question and feedback labels, and 2198 can be closed
mck: This is editorial.
carmacleod: I'll create a PR.
<Jemma> https://
<Jemma> https://
mck: 2196 seems like more of a tutorial. It's beyond the scope of the APG. Assign it to me, probably will close as won't fix.
mck: 2195 needs a group discussion. Adding agenda label.
<Jemma> https://
<Jemma> Listbox with Multiple Selection: "Recommended selection model" is uncommon #2193
<Jemma> https://
mck: For 2193, are they saying that the interaction is different from html select? Anyhow, this should be discussed in the group. Adding agenda label.
mck: Can we move 2192 to aria?
jamesn: why move to aria?
mck: The question is "can we add aria-expanded to searchbox?" which is more a question for aria than apg
setup and review agenda
ARIA 1.3 annotation
<Jemma> https://
<Jemma> https://
mck: Do we have an issue to write annotations examples?
jamesn: There are separate issues open for each of the new roles, but TBH it's probably going to be a single pattern.
mck: Is there such a thing as a Pattern, to describe how to do annotations?
jamesn: I think there's a pattern
jemma: There are example use cases in the explainer.
mck: Is each use case a different pattern? How do we imagine people looking for annotations in the APG?
carmacleod: It could be a separate section, like the landmarks section?
mck: I like that, although we have discussed having a landmarks pattern at some point.
Jemma: I think it's a matter of having a pattern that describes the various use cases.
mck: I think the use cases for these new annotations roles are very different
mck: So it's difficult to imagine a 1 or 2 sentence description that describes "annotations".
<Jemma> http://
<Jemma> http://
mck: We could maybe have a footnote-endnote-comment pattern.
jamesn: Or maybe a "Document annotation" pattern
mck: Maybe that does work
<Jemma> Web Content use cases
<Jemma> Document editor: suggestions, revisions, comments, footnotes and other authors present
<Jemma> Code editor: breakpoints, revision history, errors and warnings, code comments, etc.
<Jemma> Published content: attributions, footnotes and comments
jamesn: We shouldn't make it too generic. Make something simple to start.
jamesn: A simple example will help AT test whether they work with it.
<CurtBellew> I need to run. Bye all.
<Jemma> we are "framing and scoping original work of annotation"
tab example
mck: Ok, moving forward, lets create a pattern section called "Document annotations" to help us scope the work
<Jemma> group is taking about Carolyn's comment, https://
mck: I thought the pattern explicitly says not to use up/down in a horizontal tablist
mck: Zoe brought that up, and we added it
jongunderson: It's just the example that has up/down - the pattern is correct. I'll remove the up/down from the example.