Matthew: This is interesting. Assigned myself to this during triage, seems nobody else assigned. This is new, haven’t looked at it yet. Will have a look early next week.

Matthew: Already looked at this in APA. There are several interesting discussions going in within the CSS WG regarding what the limits of this should be. Combining this with a screen magnifier may also render it too big. Know that they have a similar discussion about the <meta> text-scale feature. APA is working with them. Try to put together a TAG comment as soon as possible. There's a lot of caveats to consider.

Matthew: I proposed a draft comment. This is about changing the height of a font so that the text is more justified in the container that it’s in, to make sure lines start and end properly. I have some concerns about edge cases. There is cross-engine commitment. Jeffrey put up a comment that seems to be in agreement with my points.

Ehsan: Had a brief look, but didn’t see any privacy section for this. Skimming through the explainer, I believe it can have potential for fingerprinting, given it’s adaptive to various screen sizes. Would love to see their point on this.

Matthew: Agree that’s worth asking.

Lola: They have an issue about a11y open, and it’s still open. What are your thoughts?

Matthew: Largely good, they have done serious work on it.

Lola: So you would draft a comment related to WCAG, baseline mechanics, …?

Matthew: Yes.

Ehsan: Happy to help.

Matthew: Jeffrey posted a good point on this one (requirements changing in WCAG 3). He suggested that we raise that as a question. Will draft something along these lines. Number of concerns, related to CSS, about growing or shrinking the problem. Ironically, growing the size can turn out to be a problem if you zoom in. I will check to see if there’s anything we’ve got that we can forward to APA. There’s a lot of concern about this. Lots of author consideration required. Not as helpful as what Jeffrey suggested. Will work on a comment.

Hadley: Priorities? Deadlines?

Matthew: Was merged into CSS three weeks ago, we didn’t have long. Guess this is rather urgent. Lots of open issues.

Hadley: As they are asking, we should give them feedback.

Luke: Think merging into a draft with open question seems fine. Seems like this is how CSS works.

Hadley: Seems to be a Chromium thing without a position from Mozilla or WebKit.

Lola: skip

Matthew: This is the other one I talked about earlier. (…) Would draft something based on Jeffrey’s points. Any concerns, Xiaocheng?

Xiaocheng: No.

Matthew to draft the comment.

Matthew: we need to give them some feedabck. This came in a while ago. Basically, I put in a very early draft that could be turned into a comment. Jeffrey wanted something a bit more concrete, but it might be ok. I can see why developers would want this. But this might be something that users might want to toggle this off in the browser. Do TAG members agree with this overall feature? We could take my initial text as a draft... there's some significant a11y issues that have gone quiet, so we could poke them.

Christian: turning it into a comment seems reasonable.

Matthew: there's not mozilla or webkit position yet.

Christian: seems that it's all still in the discussion phase.

For discussion https://github.com/w3ctag/design-reviews-private-brainstorming/issues/263#issuecomment-4797237927

Matthew: Another one where I proposed a shape of a comment. Got the impression that everyone except me like this. See the benefit, but I also see why this can be a really bad feature. Recommend that UAs can opt-out of that via a toggle in a11y settings. Seems like introducing non-determinsim to layouting. Wonder how this will affect developer experience. WCAG 3 approach is slightly different. Might make things much harder to read.

Luke: On turning it off, in an ideal world that would be great. In a real world I don’t expect UAs to implement that, similar to interest target and the delays due to observability. Personal opinion is, a11y concern should win. If the feature seems very problematic, we should then rather say that.

Matthew: We could say "don’t make the text too large/too small“, but that might break the feature. Generally, a11y and design don’t have to be in conflict, but sometimes it’s inevitable. We shouldn’t put people in a position where they should trade off a11y with privacy. Will come up with an indication of how it affects (how many) people. It may only be a few, but they may be heavily affected. Worried about privacy issues related to a11y, but this is an aesthetic thing. Might discuss this during a breakout at TPAC. Would love other people’s opinion on this.

Luke: This key bit needs a discussion, it has come up before. Like, "this is our red line," and then we need to stick to this. Guess that’s like CSS grid lanes, which doesn’t see much usage. Is that worth it with the possible harm? Personal opinion is no.

Matthew drafting comment based on proposal and discussion last week.

Matthew still working on the comment - sorry for the delay

Regarding the discussion about accessibility, ATs, fingerprinting, that we discussed: Matthew raised this on a recent Web Accessibility Initiative (WAI) Coordination Call, and it got a good reception; working on a draft breakout proposal and will circulate to anyone who's interested in joining, so we're ready to propose it when proposals open.

Matthew to post comment.