Meeting minutes
Agenda Review & Announcements
CTAUR CfC
https://
janina: candidate publications . there is call for consensus for the following documents.
https://
* CTAUR was developed by our Research Questions Task Force (RQTF) over the past 2.5 years. It's FPWD was published in October 2022, and we published a second wide review draft in June 2024. RQTF's resolution requesting publication of the above snapshot version as an APA Note is recorded here:
https://
* The W3C Note track process is described here:
https://
please review and comment
Special APA Telecon on Music Tech this Friday
janina: organizational meeting to know who wants to talk about music tech.
janina: we may have a lot of work on this and willing to facilitate
<matatk> https://
janina: coming friday at 9AM we are meeting to discuss this.
matatk: it should have gone to everybody. make sure that you can access the link. if not, reach out to Janina, Roy, or Matthew
Re-chartering
matatk: Notes the biannual rechartering heartbeat--it's now our time to recharter
matatk: Notes we review charters so should be familiar: mission, remit, scope, deliverables
matatk: every couple of years, the working group must renew the charter which is a standard process.
matatk: If we previously promissed a deliverable--we update. Complete? Not? If not, why?
matatk: Notes APA participants are almost all in at one APA TF. We need info on deliverables to add to draft charter
matatk: Also note any new deliverables
<steveF> apologies for my lateness
janina: we need TF inputs by end of January on current charter.
Fazio: if you send me the repo, I can work on this and create a github issue if required.
Spec review requests
<JenStrickland> Do we have style guides for our documents? I notice that we are not using the Oxford comma in the CTAUR document, for example.
matatk: Jen is asking if we have a styleguide for our document
janina: APA mostly follow oxford commas
Input events
<matatk> w3c/
<matatk> Due: 2024-12-19
matatk: Most recently review by Dr Keith and Matthew -- No concerns presently
matatk: Noted 2017 era requests unconfirmed -- Implemented? Not? We don't know
matatk: May have not been sufficiently clear
matatk: We wanted notification to a11y api of a text change
matatk: This one of the two we don't have an update on
matatk: Notes we're still discovering history that was minuted
matatk: Asks Janina to help find Lyon TPAC minutes conversation
WebRTC API
<matatk> w3c/
<matatk> Due: 2025-01-31
<matatk> janina: will look this week
Final Review Request of seven (7) W3C VCWG Specifications
matatk: Notes most changelogs are human readable
<matatk> w3c/
<matatk> Due: about now-ish
WebCodecs
<matatk> w3c/
<matatk> Due: 2025-02-28
matatk: Is this a path to separate foreground/background audio? To minimize audio distractions?
janina: The MAUR calls it Clear Audio
matatk: Notes mentioned in TAG to check possibilities
matatk: Notes due end of February
Fredrik: Will help
NehaJ: Also me
matatk: [On ACT rules] Resuming a review ...
matatk: Was an email in December
<PaulG> w3c/
Comment review requests
Update the Writing Testable Outcomes Document
<matatk> source: w3c/wcag3#47
<matatk> tracking: w3c/
matatk: Is guidance howto objectively test WCAG3 normative requirements
matatk: Currently looking on updating maturity levels within the WCAG; not our more global mm
<Fazio> Again, I think they should stop using that verbiage "maturity"
matatk: Wondering whether it's a labeling problem--maybe they mislabeled in our repo
Fazio: The terminology clashes with our mm; we need to resolve to avoid confusions
matatk: Recalls initial conversation at TPAC
matatk: We can figure out how to go further
[focusgroup] clarify and handle cases where scrollable regions have focusgroups (accessiblity)
<matatk> source: openui/open-ui#1008
<matatk> tracking: w3c/
matatk: Is anybody involved with OpenAI work?
Fredrik: I am interested; could be involved
matatk: Not CSS scroll; but related
matatk: Chairs can do a bit of triage aqnd then return to an APA agenda
CSS Update (Paul)
<PaulG> w3c/
PaulG: A change to native behavior
PaulG: Will trigger hover when hovering over li items
PaulG: So an optin
matatk: Changing default style sheet
PaulG: No, the power of css to control such things
matatk: Only mentions hover, not focus ...
PaulG: Select would still have the focus, no?
PaulG: There's proposals for hover-stop, etc
PaulG: we now have more control over native widgets, and this is some outcome
matatk: Should picker get focus? Platforms diverge; but the sudo helping this make more distinct