Meeting minutes
New Issue Triage<https://bit.ly/3k5wSpJ >
<joanie> https://
jamesn: we need to discuss this again in the 1.3 time frame
https://
jamesn: triage to 1.3
https://
jamesn: editorial, 1.3
New PR Triage<https://bit.ly/3qIjOcB >
jamesn: no PRs
Meaty topic for next week<https://bit.ly/3qw3sUa >: Privacy Part 2 on Feb 25, 2021
jamesn: next week is privacy part 2 - anybody have anything for the week after that?
pkra: trees on touch/mobile?
jamesn: create an issue with details, and label deep dive, and we'll consider for the next week
Github Discussions - testing on accname repo<https://github.com/w3c/accname/discussions >
jamesn: prototyping "github discussions" in accname to see if it's useful for us
jamesn: first impression is that this is "stack overflow for a specific repo"
jamesn: each repo can have a Discussions tab
<pkra> teams discussions: https://
mck: I tried this a while ago, and the screen reader support wasn't great
carmacleod: please try it again, Matt - it's the Discussions tab in accname
Updated aria-setsize and aria-posinset to clarify usage for authors<https://github.com/w3c/aria/pull/1332 >
jamesn: I had one suggested change
carmacleod: I thought your suggestion looked good
msumner: I'll put that in
jamesn: feel free to wordsmith
Spec is unclear on aria-invalid="spelling" | "grammar" uses<https://github.com/w3c/aria/issues/989 >
jamesn: Aaron's spelling/grammar issue
jamesn: there are 2 comments waiting for thums up or thumbs down
jamesn: will leave it until next week
1.2 Status and next steps with 1.3
jamesn: Michael, when are we going to CR?
MichaelC: I am planning to publish on Tuesday
carmacleod: Yes! Fabulous!
jamesn: then we will almost immediately publish the FPWD of 1.3
jamesn: Everyone, please look through the 1.3 issues, pick some, raise a PR
<jamesn> https://
jamesn: 184 open 1.3 issues
msumner: are they prioritized?
jamesn: it would be useful, but lots of them are equal priority
jamesn: the things people want to work on are the things we should be working on
msumner: if you can say "these are the top 10 issues", then I would try to focus my energy on those
jamesn: we do have privacy and internationalization that other groups raised on us - those are high priority
jamesn: one thing that keeps coming up is the "container can't contain child elements", and everybody always wants to create child elements
jamesn: that keeps coming up over and over again
Matt_King: that may be related to secondary actions
jamesn: there may be some overlap
jamesn: that would be an awesome problem to solve
Matt_King: currently screen readers have to do a lot of work to support aria-live
Matt_King: should ARIA dictate more of what browsers should do with aria-live?
<jamesn> https://
Matt_King: I'd like to put some real group focus on it
msumner: I agree that we need a way to know when an even has occurred. Similar to pop state.
Matt_King: does it fall into the scope of ARIA - or does ARIA need to stay declarative
msumner: for me, ideally HTML and the browsers give us what we need so that we don't always have to struggle to have accessibility parity
jamesn: if folks want to work on this for 1.3, that sounds ambitious...
jamesn: this may be a deep dive topic
Matt_King: I do think that aria-live and notifications and our approach to that does deserve a deep dive
Matt_King: also, the containerization thing that you mentioned
msumner: Matt, let's have a call or email conversation to decide which topic (of the 3) is the most important and we can come up with some points for the deep dive
Matt_King: Sounds great