Meeting minutes
scribe pkra
New Issue Triage
jamesn: no new issues
New PR Triage
jamesn: aria#1993 is about improving contributors data in document.
… better than the fixed list. It seems like a good selection. Based on contributions to the repository.
… contributions will be spec-specific. The list of participants will remain.
… we might want to have the evergreen specs simply point to the WG member list
spectranaut_: unfortunate not to have fly-by contributors
jamesn: if you have any comments, please let us know.
… aria#1991 matching braillelabel prohibiting
jamescraig: will review
… we were discussing this last week and want to make sure we don't miss interesting edge cases
jamesn: thanks. will try to get Aaron or someone from Chrome with braille path experience.
WPT Open PRs
spectranaut_: I'm handling the core-aam ones.
jcraig: generic test is a bigger one. many reviewers already.
… lots of notes
… hopefully those make it easy to review
jamesn: my interpretation was that this comes from the different platforms
… having different names?
jcraig: yes. we accepted to avoid churn.
… core-aam tests are Val's
… I'll review howard's - 1 review is enough. Rahim maybe too?
… fallback roles. pretty straight forward.
… has reviewers but any are welcome
jamesn: more than one is good, especially if complex
… can we remove manual tests so we can ignore them in query?
spectranaut_: yes. but you won't see them often once this batch is merged
jcraig: one very old manual one
spectranaut_: not sure it's worth maintaining some of these
… other old ones back to spectranaut
… and that's it.
Deep Dive planning
jamesn: let's combine with TPAC planning.
… does anyone want to do either of these? (hidden really hidden, windows/mac implicit roles)
… I'll add them to TPAC in any case.
jcraig: windows/mac discussion might be easier at TPAC
TPAC Candidate Issues
jamesn: 11 potential items
… chairs will plan next week
… if there's anything you want to discuss, you need to label it F2F candidate.
… if you're not at TPAC but you want to attend, please comment with location so we can aim for reasonable times for you.
jcraig: I wanted to pitch a break out session with browser testing tool, on AOM issue. I'll file a new issue pointing to AOM issue.
mattking: could also include AT driver?
… I think that would be good.
<spectranaut_> list of registered: https://
jamesn: let's see who's coming.
… again, please add items for TPAC agenda
Discussion tracking for ARIA Notification proposal
Doug: "using arrays confusion". Right now I don't think it makes sense.
… right could be on any element, presented as array
… then could do things, e.g., flush pending.
… browsers won't be able to do much with this as soon as it went to AT
… so probably the browser passes it to API, then array probably only happens on the AT level
… so array seems wrong. grouping is probably still helpful.
… if people agree, then what should be done.
mattking: on the app side, if there's a situation where it's aware of a lot of notifications and you want to manage this
… do we need something in the API that would help with queue management
… e.g., chat app, 15-20 notifications, on different threads
… and app wants to provide feature to manage that.
Doug: on windows, platform notification API, e.g., progress bar ticking away. if everytime the percentage changes, the synthesizer would be jammed with starting sound.
… so instead it allows not constantly interrupt.
… allowing AT to complete voicing and then take the next latest one.
… but that's really on the AT side.
… I'd imagine AT allowing users to prioritize notifications. Not sure how often we'll see that.
mattking: right. I have definitely run into it. But I can see how the API is treated as a dispatcher.
Doug: yes, I can imagine that users set verbosity to control.
mattking: see that in meetings. joining, leaving, raising hand, chat etc
… seems like the app could have verbosity setting
Doug: we discuss having the burden on the app side or the AT side
… hard to make it generic.
jamesn: I'd lean towards doing a lot of this in the AT rather than the app
… almost feels like you'd want priorities. E.g., starting leaving at beginning on meeting.
… would want that but not have to do that in the settings of the app
mattking: I think that AT could only do the big hammer. The app would have to do the detailed ones.
jamesn: but I'd hope they can handle the most common use cases.
… if we say apps have to do this, we may miss out on a lot of usefulness
mattking: not saying they have to but an option. E.g., workout app I want it speaking, control interval, verbosity etc.