W3C

– DRAFT –
APA Weekly Teleconference

30 April 2025

Attendees

Present
chiace, Demelza, Fredrik, janina, JonCohn, matatk, Neha, PaulG, Roy_Ruoxi
Regrets
-
Chair
Matthew
Scribe
janina, matatk

Meeting minutes

Date 30 Apr 2025

Agenda Review & Announcements

Re-chartering

<matatk> Latest draft: https://raw.githack.com/w3c/apa/charter-2025/charter.html

<matatk> Pronunciation bit, for context: https://lists.w3.org/Archives/Public/public-pronunciation/2025Apr/0008.html

matatk: Reviews output from Spoken Presentation for our new Charter ...

matatk: Proposes 'Best Practices for Achieving " based on existing standards ...

<Fredrik> We#ve heretofore been brilliant at giving names and acronyms to brilliant documents (the AURs come to mind). Why not the gap analysis annd so forth? Or can one give names retroactively when the charter is already chartered?

<Fredrik> Proven Practices for Predictable Pronunciation.

[group tries different titles ...]

RESOLUTION: Best Practices for Author-Controlled Pronunciation

matatk: proposing tentative normative ...

matatk: A CSS extract ...

matatk: extensions for existing normative

matatk: CSS Break is one

matatk: Notes we RESOlVED #4 from email above

matatk: We're now talking 2 and 3

matatk: AAM would be likely HTML AAM extensions

<Roy_Ruoxi> example: https://www.w3.org/2025/02/wg-fedid.html

matatk: Noting only names are missing; reinforces these are tentative

New on TR

Web Cryptography Level 2

<Roy_Ruoxi> - tracker: w3c/apa-longituidinal-tracking#21

<Roy_Ruoxi> - spec: https://www.w3.org/TR/webcrypto-2/

matatk: Expects out of scope for us?

janina: More low level than out of scope -- especially in API

Subresource Integrity

<Roy_Ruoxi> - tracker: w3c/apa-longituidinal-tracking#22

<Roy_Ruoxi> - spec: https://www.w3.org/TR/sri-2/

matatk: yeah! A dark-mode style sheet!

Fredrik: Raises hand to read

matatk: Too low level?

<Roy_Ruoxi> w3c/apa-longituidinal-tracking#22

Fredrik: Would like to check

Privacy-Preserving Attribution: Level 1

<Roy_Ruoxi> - tracker: w3c/apa-longituidinal-tracking#23

<Roy_Ruoxi> - spec: https://www.w3.org/TR/privacy-preserving-attribution/

matatk: Expects an approach to start moving away from proprietary cookies

matatk: The ecommerce site wants to know what leads to sales; so challenge is to not identify an individual--just the sale

matatk: Goal is to balance user's privacy perogative and commerce data gathering

matatk: So an aggregation approach

matatk: How effective are my advert campaigns?

matatk: From Mozilla and Meta ...

matatk: Has a bit less than the Google approach

matatk: Don't believe there's an a11y angle here

matatk: Other than general increased privacy

matatk: This current proposal may be new, but approach has been under dev in a cg for sometime

matatk: Notes this goes along with the desire to bring horizontal review to CG developed tech as that tech moves into adoption

matatk: Including comm with TAG for hor-rev

CSS Gap Decorations Module Level 1

<Roy_Ruoxi> - tracker: w3c/apa-longituidinal-tracking#24

<Roy_Ruoxi> - spec: https://www.w3.org/TR/css-gaps-1/

matatk: Asks Paul?

PaulG: Unsure this has even been discussed yet ...

PaulG: Seems essentially white space, so no particular a11y impact?

PaulG: Willing to hear otherwise from anyone?

matatk: Notes this will come back via HR

Spec review requests

Audio Session

<matatk> w3c/a11y-request#108

<matatk> Due: 2025-04-24

janina: I took on trying to figure this out. Struck me that they're figuring out how to balance all things audio, but there's no consideration of TTS. At least we need an accessibility considerations section, saying there may be TTS, which will be critical to managing their audio environment.
… But just saying 'be careful about TTS' seems insufficient. What can we point them to?
… Do we look for TTS?

matatk: Goes back to Author Proposes ...

matatk: Maybe we file an issue to figure this out with them?

janina: I can draft an issue

matatk: Anyone with ideas on starting this dialog?

[crickets]

Web Neural Network API

w3c/a11y-request#105

Due: 2025-06-20

chiace: Notes this assigned already, her, Dr Keith, Janina

<Neha> w3c/apa#350

janina: Thanks her for suggestions!

matatk: We can continue discussing, and perhaps plan a discussion next week, or soon after

Comment review requests

[menu] define orientation attribute

source: openui/open-ui#1201

tracking: w3c/a11y-review#228

How OS font settings affect UA font-size (medium)

source: UNKNOWN!

tracking: w3c/a11y-review#227

paul: First round was what to name it; though discussion of what it is is far more interesting!

paul: Giving CSS a variable to understand scale of OS font choices

janina: Also last week's conversations!

paul: Building to parity across platforms--a good thing

paul: Most needed phps on IOS!

matatk: Notes our emerging way to flag everyone who needs flagging ...

paul: Before you label ...

paul: So far about naming, but it's what follows we'll want to track and comment

matatk: Anything at the moment?

matatk: Thumbs Up to Fantasie?

paul: will happen anyway

Be done

Summary of resolutions

  1. Best Practices for Author-Controlled Pronunciation
Minutes manually created (not a transcript), formatted by scribe.perl version 244 (Thu Feb 27 01:23:09 2025 UTC).

Diagnostics

Maybe present: Due, paul, source, tracking

All speakers: chiace, Due, Fredrik, janina, matatk, paul, PaulG, source, tracking

Active on IRC: chiace, Demelza, Fredrik, janina, JonCohn, matatk, Neha, PaulG, Roy_Ruoxi